standby controller was in reboot loop after modifying the partition size
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Wei Zhou |
Bug Description
Bug Description : During the regression testing standby controller was in reboot loop after modifying the partition size for cinder volume and swact controller extra and rebooting the active controller.
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
2018-12-
Severity
--------
Major
Steps to Reproduce
------------------
1. Modify partition size for cinder-volumes for standby controller
2. Swact controllers
3. Modify partition size for cinder-volumes for the newly standby controller
4. Make sure cinder-volumes lvg is resized successfully and no alarms are generated
5. Swact controllers again
6. Reboot active controller (Run “sudo reboot” on the active controller)
Expected Behavior
------------------
No reboot
Actual Behavior
----------------
As per description
Reproducibility
---------------
100% Reproduce-able
System Configuration
-------
duplex system
Branch/Pull Time/Commit
-------
Timestamp/Logs
--------------
2018-10-
------------------- Titanium-specific Information -------------------
* Test case mapping: Regression
* Test-case Title: Verify cloud patch orchestration from horizon
* Lab Name: Distributed cloud lab main cloud is WCP90-91
* Load Information:
Build Server: yow-cgts1-lx
SW_VERSION="18.10"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID=
SRC_BUILD_ID="116"
JOB="StarlingX_
BUILD_BY="jenkins"
BUILD_NUMBER="116"
BUILD_HOST=
* Logs location: /folk/cgts_
* When and where was the last time this test-case passed?..
description: | updated |
Changed in starlingx: | |
assignee: | nobody → Wei Zhou (wzhou007) |
importance: | Undecided → Medium |
tags: | added: stx.2019.03 stx.config |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Reviewed: https:/ /review. openstack. org/625949 /git.openstack. org/cgit/ openstack/ stx-config/ commit/ ?id=0d958de0772 51936a945dc7154 6ee53f924ad345
Committed: https:/
Submitter: Zuul
Branch: master
commit 0d958de07725193 6a945dc71546ee5 3f924ad345
Author: Wei Zhou <email address hidden>
Date: Tue Dec 18 11:17:36 2018 -0500
Standby controller in reboot loop after modifying the partition size
The root cause of this issue is that when the newly standby controller
is coming up, the partition manifest calls "sm-unmanage / sm-manage"
for drbd-cinder service. However at this time /var/run/sm.db is not
available yet which causes "sm-unmanage / sm-manage" to fail.
This commit adds a check in the partition puppet file that only
if the system is up "sm-unmanage" and "sm-manage" will be called.
Change-Id: I1869f024579350 265684f2ee3bb5e 3e74e6427cb
Closes-bug: 1809009
Signed-off-by: Wei Zhou <email address hidden>