Jose, Can you check if you reported issue is similar as the existing one reported here: https://bugs.launchpad.net/starlingx/+bug/1798836 thx. - cindy -----Original Message----- From: Dinescu, Stefan [mailto:Stefan.Dinescu@windriver.com] Sent: Thursday, November 8, 2018 11:01 PM To: Perez Carranza, Jose <jose.perez.carranza@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hello, Depending on the size of your cinder partition and network speed between the two controller nodes, cinder make take some time to sync as it is usually the biggest partition. you can use "drbd-overview" to see the progress of the sync. Thanks, Stefan ________________________________________ From: Perez Carranza, Jose [jose.perez.carranza@intel.com] Sent: Thursday, November 08, 2018 4:56 PM To: 'starlingx-discuss@lists.starlingx.io' Subject: [Starlingx-discuss] Second controller on degraded for long time - Duplex Virtual Hi I setup a Duplex virtual environment and I noticed that after installation and provisioning of second controller (controller-1) this one stays in Degraded for long time (~ 1 hour), and alarm 400.001 is being displayed [1], Is this normal behavior? Is here a way to take out the controller-1 from 'degraded' to 'available' faster? 1- http://paste.openstack.org/show/734425/ Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss