Comment 3 for bug 1826418

From a similar instance, the information below was found.
5af3bc55-6caf-4b1b-bced-4c33a5f87b7c was the config_uuid that system complain not being applied on controller-0

[wrsroot@controller-1 ~(keystone_admin)]$ system host-swact controller-1
controller-0 target Config 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c not yet applied. Apply target Config via Lock/Unlock prior to Swact

prior to the instance, active controller swact from controller-0 to controller-1, command issued at 2019-04-29T10:20:50
2019-04-29T10:20:50.000 controller-0 -sh: info HISTORY: PID=258916 UID=1875 system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.2:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne host-swact controller-0

sysinv conductor detected the mismatch of target config_uuid and applied config_uuid, it tried to apply the config:
2019-04-29 10:22:52.316 110549 WARNING sysinv.conductor.manager [-] controller-0: iconfig out of date: target 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c, applied 6f0146c3-3e60-40be-bcf9-d72e9e9751ca
2019-04-29 10:22:52.316 110549 WARNING sysinv.conductor.manager [-] SYS_I Raise system config alarm: host controller-0 config applied: 6f0146c3-3e60-40be-bcf9-d72e9e9751ca vs. target: 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c.
2019-04-29 10:22:52.340 110549 WARNING sysinv.conductor.manager [-] controller-1: iconfig out of date: target 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c, applied 6f0146c3-3e60-40be-bcf9-d72e9e9751ca
2019-04-29 10:22:52.340 110549 WARNING sysinv.conductor.manager [-] SYS_I Raise system config alarm: host controller-1 config applied: 6f0146c3-3e60-40be-bcf9-d72e9e9751ca vs. target: 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c.
2019-04-29 10:22:52.435 110549 INFO sysinv.conductor.manager [-] _config_update_hosts config_uuid=5af3bc55-6caf-4b1b-bced-4c33a5f87b7c

The target config (uuid 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c) was applied to controller-1 successfully a few seconds after the config mismatched was detected.
2019-04-29 10:24:19.929 19382 INFO sysinv.agent.manager [req-fb0f7abe-917e-4285-a061-365669a34b89 admin None] Agent config applied 5af3bc55-6caf-4b1b-bced-4c33a5f87b7c
2019-04-29 10:24:19.964 110549 INFO sysinv.conductor.manager [req-fb0f7abe-917e-4285-a061-365669a34b89 admin None] SYS_I Clear system config alarm: controller-1

Not log was found to indicate attempt had been made to apply the same config to controller-0

An error msg was found but may not be related with the instance.
2019-04-29 10:22:54.370 110549 ERROR stevedore.extension [-] Could not load 'stx-openstack': No module named systemconfig.helm_plugins.stx_openstack