| dacamp | Bash scripts in /var/lib/cloud/scripts/per-instance, put there during AMI creation, are expected to be run once per instance right? | 03:18 |
|---|---|---|
| === cpaelzer_ is now known as cpaelzer | ||
| === cpaelzer is now known as cpaelzer_afk | ||
| === Ab_ is now known as Guest65435 | ||
| Guest65435 | Hi There. Is there any way I can check any logs for failed cloud-config part in cloud VMs ? | 13:43 |
| Guest65435 | I have been using cloud-config since long now. But, when it works, I can see everything in cloud-init-output.log file.. but there is absolutely no log if some part in cloud-config section is wrong. | 13:44 |
| Guest65435 | Even the minute 'space' mistake leads to failure of complete cloud-config block. | 13:44 |
| Guest65435 | Can anyone please help? | 13:54 |
| smatzek | the only thing I can think of that may help is to modify the logging level to DEBUG and make cloud-init re-run. That may put something in the logs. | 14:07 |
| Guest65435 | ok. But is there anyway I can re-run my cloud-config template from within OpenStack VM? | 14:09 |
| smatzek | This is what I normally do: Delete the semaphore file for your module in the /var/lib/cloud/instance/sem/ directory (e.g., /var/lib/cloud/instance/sem/config_foo). Then run `/usr/bin/cloud-init modules --mode <init,config,final>` depending on what kind of module you are writing, to have cloud-init re-execute your module. Some versions of cloud-init allow you to run a single module at a time as well. | 14:14 |
| smatzek | remoe cloudinit's data directory (/var/lib/cloud/data) and reboot. | 14:15 |
| Guest65435 | Ok. I will give it a try and share with group. Thanks a lot for the help. | 14:20 |
| === cpaelzer_afk is now known as cpaelzer | ||
| === cpaelzer is now known as cpaelzer_afk | ||
| === cpaelzer_afk is now known as cpaelzer | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!