controller-0 cannot unlock

Bug #1865644 reported by 张笑盈
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Won't Fix
Low
Unassigned

Bug Description

After I finished “bash setup_configuration.sh -c simplex -i ./bootimage.iso”,I cannot unlock controller-0.
This made me cannot made apply controller-0 configuration changes and come into service and install controller-1.I cannot continue.

After I finished “bash setup_configuration.sh -c simplex -i ./bootimage.iso”,I log in controller-0.It's ok.Then I made a minimal user configuration override file,then I Run the Ansible bootstrap playbook.But after that,I use "source /etc/platform/openrc" to acquire admin credentials and to config controller-0,then I met problems when I use this command "system host-unlock controller-0".It says that "Host is not online.Wait for online availability status and then 'unlock' ".I reboot controller-0 for several times,but it doesn't work.

Then I use command "system host-list" to see.I found that controller-0 is locked,it's operational is disabled,and it's availability is offline,not online.I ping my host system,OAM and controller-1,they can ping through each other.I don't know why controller-0 is not online.

Also,I want to know how to save the status of controller-0.Because when I reboot it,the configuration was lost,and it have no access to the Internet.

I'm very glad if someone can help me,thank you!

Tags: stx.config
Revision history for this message
Ghada Khalil (gkhalil) wrote :

I suggest you send to the starlingx-discuss mailing list; perhaps somebody can give you pointers on what to check.

This is likely a configuration issue.
Also, which build are you using?

Changed in starlingx:
status: New → Incomplete
Ghada Khalil (gkhalil)
tags: added: stx.config
tags: added: stx.metal
removed: stx.config
tags: added: stx.config
removed: stx.metal
Changed in starlingx:
importance: Undecided → Low
Revision history for this message
John Kung (john-kung) wrote :

There has been no response to question on the build version. Recommend closing LP as over 2 years old. A new LP can be raised with the requested info and relevant logs (such as via a 'collect') if still reproducible.

Revision history for this message
Ramaswamy Subramanian (rsubrama) wrote :

Changing the status to 'Won't Fix' as there is no activity.

Changed in starlingx:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.