Hello Owen,

Your con1 gets bootstrapped successfully and when it goes to reboot, it comes up again on PXE network of con0 I.e. mgmt network which results in creation of 3rd node which again says waiting to be configured.

Solution 1 is to keep watching con1 and when it goes to reboot, then change the boot order to hard drive first. But this is only for one time. In future if your system reboots, you will loose your deployment.

Solution 2 is to set the boot order of con1 like hard drive and then pxe boot in bios. Now you can manually put con1 to one shot boot up on pxe and then it will boot up from hard drive always. 

Regards
Akshay
Hughes Systique Corporation HSC

Sent from my iPhone

On 10-Feb-2021, at 1:49 AM, Owen Yuen <OwenYuen@cmail.carleton.ca> wrote:

Hi I’m configuring a distributed cloud AIO duplex setup with 2 subclouds.

 

On the second subcloud I’ve successfully bootstrapped con-0 but I’m having issues unlocking con-1

 

After I start con-0, I go on con-0 and do the “system host-update 2 personality=controller” command and wait for con-1 to reboot but after waiting over an hour it still says offline

 

[sysadmin@controller-0 ~(keystone_admin)]$ system host-list

+----+--------------+-------------+----------------+-------------+--------------+

| id | hostname     | personality | administrative | operational | availability |

+----+--------------+-------------+----------------+-------------+--------------+

| 1  | controller-0 | controller  | unlocked       | enabled     | available    |

| 2  | controller-1 | controller  | locked         | disabled    | offline      |

| 3  | None         | None        | locked         | disabled    | offline      |

+----+--------------+-------------+----------------+-------------+--------------+

 

Also I don’t know why ID: 3 showed up when it wasn’t there before.

 

When I try to console into con-1 it says “waiting for this node to configured”.

 

Any helps is appreciated, please let me know how I can find log files to help further troubleshoot.

 

Thanks

 

Owen

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss