[02:49] <edwin86>  Hi, I have a question about "runcmd", there are some shell scripts under runcmd field , where I can find the install logs
[03:05] <blackboxsw> edwin86: 1. cloud-init status --long to make sure there were no errors rendering your runcmd YAML as a shell script (very frequent problem).  2. check that the script was emitted to /var/lib/cloud/instance/scripts/runcmd.  (If not you'll probably see a Failed to shellify in /var/log/cloud-init.log).    3. stdout/stderr of your script typically go to /var/log/cloud-init-output.log   
[03:06] <blackboxsw> edwin86: 4. check content in the rendered /var/lib/cloud/instance/scripts/runcmd to make sure it looks like the script that you intend... and 5. If you don't see errors or output indicating problems in cloud-init*.log, try re-running the script with `sudo /var/lib/cloud/instance/scripts/runcmd`  to see those errors on the terminal.
[03:08] <blackboxsw> blackboxsw_away
=== blackboxsw is now known as blackboxsw_away
[08:12] <edwin93> blackboxsw_away got it ,thanks.
[08:15] <edwin93> another question is that , When I execute the runcmd command, which user is used to execute the specific command? Is it root， or someuser as root ？
[08:16] <meena> edwin93: cloud-init runs as root, it does everything as root 
[08:18] <edwin93> got it , if I want to specify some folder to some user , I need to run "chown $USER:$USER /data ", is it right?
=== smoser1 is now known as smoser
=== blackboxsw_away is now known as blackboxsw
=== CodeMouse92 is now known as Guest2830
=== Guest2830 is now known as CodeMouse92
=== hyperreal5 is now known as hyperreal