Bug #21587
open
Create host fails but the task is marked as succeeded. No useful logs are created that show why the task failed.
Added by Aaron Glenn over 7 years ago.
Updated over 7 years ago.
Description
When creating a vmware vm, and a bug is triggered like #21586, the production log doesn't show anything useful even when set to debug, even though the on-screen play-by-play shows the steps of creating the vm and a failure is noted.
Files
Related issues
1 (1 open — 0 closed)
I also saw this behaviour, during #21587
Attaching an example log in debug mode
Chris Routh wrote:
I also saw this behaviour, during #21587
Attaching an example log in debug mode
Er... #21586
- Related to Bug #21586: Chef Plugin causes failure in VM creation in Foreman 1.15.6 added
Thanks for the report and sorry for the delay. According to the trace, Chef communication worked just fine, the CR communication for some reason failed. Did you test it with chef plugin disabled? This does not look like foreman_chef bug. Anyway, I'll be releasing 0.6.0 soon where are many fixes. So far it seems to work fine. If I build an rpm or gem for you, would you be able to test in you environment before we push the build to 1.15 repos?
Also one more note, the task really succeeded so you most likely have chef client created on chef-server, the rollback does not work since the core orchestration uses different technology that foreman tasks. Sadly, foreman-tasks were reverted from core around 1.15
Aaron, Chris, just to be sure, what is your bootstrap method? You can find out at Setting -> Chef -> validation_bootstrap_method, it's either true (then it uses validation.pem) or false (then it creates client manually and stores host private key in Foreman DB) so it can be deployed during provisioning.
Also available in: Atom
PDF
Updated by 
Updated by Greg Sutcliffe over 7 years ago
Updated by