[Starlingx-discuss] unexpected behaviour in duplex mode in virtual env

Gomez, Juan P juan.p.gomez at intel.com
Fri Oct 26 23:31:11 UTC 2018

Hi Rajesh,

There have been some changes recently merged
I suggest to  build again your ISO with the latest changes 

There were not screen shot attached, could you share them again?
Could you verify the output from the cmd:  nova service-list, verify the nova-compute services is up and enable?
What is the output from system host-list?

Best Regards,

-----Original Message-----
From: Rajesh Jha [mailto:Rajesh.Jha at rsystems.com] 
Sent: Thursday, October 25, 2018 5:11 AM
To: starlingx-discuss at lists.starlingx.io
Cc: Sachin Alok <Sachin.Alok at rsystems.com>; Sumit Agarwal <Sumit.Agarwal at rsystems.com>; Avanish Yadav <Avanish.Yadav at rsystems.com>; Ajay Tomar <Ajay.Tomar at rsystems.com>; NK Garg <NKGarg at rsystems.com>
Subject: [Starlingx-discuss] unexpected behaviour in duplex mode in virtual env


We have observed an unstable behaviour while running below scenario

Setup- Virtual environment testing using kvm Mode "Duplex" (One active and one standby controller script setup_allinone.sh)


1. Followed steps in document "https://docs.starlingx.io/installation_guide/duplex.html#duplex"
2. Able to proceed till section "system host-unlock controller-0" command. After issuing this command system get reboot as per expectation but once it comes up availability status changed to "degrade" and alarm raised (screen shot attached).
3. Then we execute "destroy_allinone.sh" and "destroy_network.sh" command to cleanup the previous setup to build new one 4. After following same step in above documents till "sudo config_controller" command which was successful and after run "source /etc/nova/openrc" system get reboot again and again and nothing happening after instead of rebooting. Screenshot is attached below.
CLI is no more available to the controller

Thank you,

The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.

Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io

More information about the Starlingx-discuss mailing list