Ansible: config out of date after unlocking AIO-SX controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Ovidiu Poncea |
Bug Description
Brief Description
-----------------
Following an unlock of an AIO-SX controller that was configured with Ansible, the node remains in a "config-
Severity
--------
Critical, this prevents the following manifests from running as part of the conductor manifest.
'openstack:
'platform:
Aside from those two manifests there is a pending Ansible update in progress (not yet pushed) that will be impacted by this issue because the sysinv.conf defaults will not be copied to the /opt shared mount and therefore no other nodes will be able to report their inventory as they will not be configured with the correct Rabbit URL. At a minimum, that will impact AIO-DX configurations, but it is not clear whether a similar condition can occur for Storage or Standard configurations.
Steps to Reproduce
------------------
Use Ansible to configure an AIO controller. Manually configure the node and then unlock it. Following the unlock/reboot observe that there is a config-out-of-date alarm.
Expected Behavior
------------------
After the unlock there should be no config-out-of-date alarm.
Actual Behavior
----------------
There is a config-out-of-date alarm raised.
Reproducibility
---------------
100%
System Configuration
-------
AIO-DX and AIO-SX at a minimum.
Branch/Pull Time/Commit
-------
Private load rebased on May 6th with some Ansible and networking fixes.
Last Pass
---------
Unknown
Timestamp/Logs
--------------
2019-05-08 17:25:10.516 89124 INFO sysinv.
2019-05-08 17:25:10.673 10680 INFO sysinv.
2019-05-08 17:25:10.703 89124 INFO sysinv.
2019-05-08 17:25:11.036 89124 WARNING sysinv.
2019-05-08 17:25:11.036 89124 WARNING sysinv.
2019-05-08 17:25:11.087 10680 INFO sysinv.
2019-05-08 17:25:13.032 89124 INFO sysinv.
2019-05-08 17:25:13.033 89124 WARNING sysinv.
2019-05-08 17:25:13.525 89124 INFO sysinv.
2019-05-08 17:25:13.526 89124 INFO sysinv.
Test Activity
-------------
Developer Testing
Changed in starlingx: | |
status: | Triaged → In Progress |
summary: |
- config out of date after unlocking AIO-SX controller + Ansible: config out of date after unlocking AIO-SX controller |
It's a strange chain of events, we do reset the node to config-out-of-date when an OSD is configured, which is expected. Yet it should be cleared after unlock, but instead we get this:
after unlock e5da-4f2e- a3c3-c468e9a46f b5 | e5da-4f2e- a3c3-c468e9a46f b5 |
------------
| config_applied | 62228cc1-
| config_status | Config out-of-date |
| config_target | e2228cc1-
if we look closely to the two values, we see that they are identical except the first 'bit'. So we have config-out-of-fate at 1 bit difference :) This means that the config has applied correctly but something else is either not correctly set or not correctly updated in the DB.