Comment 5 for bug 1828271
Revision history for this message
| Ovidiu Poncea (ovidiuponcea) wrote Re: config out of date after unlocking AIO-SX controller | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The issue is related to config_target and config_apply limitations not to storage stuff. A config uuid with the reboot flag is passed to puppet ONLY when host is unlocked (which makes sense as this is when we do the reboot). Runtime manifests don't pass the reboot flag to puppet (it is a runtime, reboot flag has to remain). So, at unlock we set it correctly then... since the last operation in Ansible is to run a set of runtime manifests we reset it one more time to a value w/o the reboot flag => the reboot flag is no longer set, that's why after unlock we get the one bit difference in:
after unlock
------------
| config_applied | 62228cc1-
| config_status | Config out-of-date |
| config_target | e2228cc1-