Comment 7 for bug 1864221

Hi Frank,

We used the latest layered build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200305T111629Z/

However, we still face the exact same issue with Simplex and Duplex

LOGS
=======
Simplex:
Some outputs: http://paste.openstack.org/show/790365/
Collect: https://files.starlingx.kube.cengn.ca/download_file/54

Duplex:
Some outputs: http://paste.openstack.org/show/790368/
Collect: https://files.starlingx.kube.cengn.ca/download_file/55

HARDWARE DETAILS
=======
Here are some hardware details for our simplex system: http://paste.openstack.org/show/790370/

Both duplex systems have the same hardware specs.

COMMANDS EXECUTED
=======
These are the commands that we ran against the simplex system before doing the unlock:
http://paste.openstack.org/show/790373/
After that, the system boots, but that's when we receive the error "Openstack Admin credentials can only be loaded from the active controller."

NOTE: The exact same steps are followed up for both, monolithic and layered build. Is there a different command that needs to be executed?

QUESTIONS
=======
So regarding the questions:
- We are using the exact same server for Simplex on Monolithic and Layered build.
- Another pair of servers is used on Duplex for Monolithic and Layered build.
- Latest monolithic build doesn't face this error on Simplex, neither on Duplex, Sanity report was sent as green.
- We can arrange the meeting, however, could you please let us know at which point do you want the servers to be left? Just with the Image installed? Or, will it be better to execute every command, just before the "system host-unlock controller-0"? In that way, we can check the status before the unlock and monitor how it progress.