swact active controller rejected due to config-out-of-date alarm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Ghada Khalil |
Bug Description
Brief Description
-----------------
Swact active controller is failed after cold migration. The config of standby controller is not applied.
Severity
--------
Major
Steps to Reproduce
------------------
1. Create a flavor with 1 vcpu
2. Add following extra specs: {'hw:cpu_policy': 'shared'}
3. Create a volume from ubuntu_14 image
4. Boot a ubuntu_14 VM with above flavor from volume
5. Live migrate ubuntu_14 VM
6. Ping vm from NatBox after live migration
7. Cold migrate vm and check vm is moved to different host
8. Ping vm from NatBox after cold migration
9. Swact active controller
TC-name:
test_migrate_
Expected Behavior
-----------------
Swact active controller succeed
Actual Behavior
----------------
Swact active controller failed
Reproducibility
---------------
reproducible
System Configuration
-------
Regular standard 2+2
Lab-name:
ip_1_4
Branch/Pull Time/Commit
-------
BUILD_ID=
Timestamp/Logs
--------------
[2021-03-07 07:02:46,315] 1651 DEBUG MainThread ssh.get_
[2021-03-07 07:02:46,315] 479 DEBUG MainThread ssh.exec_cmd:: Executing command...
[2021-03-07 07:02:46,315] 314 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://
[2021-03-07 07:02:47,684] 436 DEBUG MainThread ssh.expect :: Output:
controller-1 target Config 84ef0ae4-
logs of .tar and TIS_AUTOMATION.log as below,
https:/
Note: above url is currently not accessible
Test Activity
-------------
STX Nova regression
tags: | added: stx.distro.openstack |
summary: |
- Nova Swact active controller failure + swact active controller rejected due to config-out-of-date alarm |
The swact rejection is expected from software perspective when standby controller is config out-of-date.
Please look at automation logs to find out when the config out-of-date alarm appeared and stuck. The test case that caused this stuck alarm will need to be investigated instead.