| 2019-10-30 20:47:24 |
Senthil Mukundakumar |
bug |
|
|
added bug |
| 2019-10-30 20:48:08 |
Senthil Mukundakumar |
description |
Brief Description
-----------------
In Regular system Backup & Restore, the active controller did become active after restore (1849379 - verified).
The standby controller after restore and unlock, remain in failed state using 'system host-list'.
[sysadmin@controller-0 ~(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1 | controller-0 | controller | unlocked | enabled | available |
| 2 | controller-1 | controller | unlocked | disabled | failed |
| 3 | compute-0 | worker | locked | disabled | offline |
| 4 | compute-1 | worker | locked | disabled | offline |
+----+--------------+-------------+----------------+-------------+--------------+
Severity
--------
Critical: Unable to restore standby controller in Regular system
Steps to Reproduce
------------------
1. Bring up the Regular system system
2. Backup the system using ansible locally
3. Re-install the controller with the same load
4. Restore the active controller
5. Unlock active controller
6. Boot standby controller via PXE
7. unlock standby controller
Expected Behavior
------------------
The standby controller should be successfully restored and become available
Actual Behavior
----------------
Standby controller failed to become available after unlock
Reproducibility
---------------
Reproducible
System Configuration
--------------------
Regular System
Branch/Pull Time/Commit
-----------------------
BUILD_ID="2019-10-27_20-00-00"
Test Activity
-------------
Feature Testing |
Brief Description
-----------------
In Regular system Backup & Restore, the active controller did become active after restore (1849379 - verified).
The standby controller after restore and unlock, remain in failed state using 'system host-list'.
[sysadmin@controller-0 ~(keystone_admin)]$ system host-list
+----+--------------+-------------+----------------+-------------+--------------+
| id | hostname | personality | administrative | operational | availability |
+----+--------------+-------------+----------------+-------------+--------------+
| 1 | controller-0 | controller | unlocked | enabled | available |
| 2 | controller-1 | controller | unlocked | disabled | failed |
| 3 | compute-0 | worker | locked | disabled | offline |
| 4 | compute-1 | worker | locked | disabled | offline |
+----+--------------+-------------+----------------+-------------+--------------+
SM on controller-1 waiting for config to be completed. Meanwhile the puppet manifest failed with errors:
2019-10-30T16:00:12.002 Notice: 2019-10-30 16:00:12 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/Exec[Adding StarlingX helm repo: starlingx]/returns: Error: Looks like "http://127.0.0.1:8080/helm_charts/starlingx" is not a valid chart repository or cannot be reached: Get http://127.0.0.1:8080/helm_charts/starlingx/index.yaml: dial tcp 127.0.0.1:8080: connect: connection refused
2019-10-30T16:00:12.005 Error: 2019-10-30 16:00:12 +0000 helm repo add starlingx http://127.0.0.1:8080/helm_charts/starlingx returned 1 instead of one of [0]
2019-10-30T16:00:12.102 Error: 2019-10-30 16:00:12 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[starlingx]/Exec[Adding StarlingX helm repo: starlingx]/returns: change from notrun to 0 failed: helm repo add starlingx http://127.0.0.1:8080/helm_charts/starlingx returned 1 instead of one of [0]
2019-10-30T16:00:12.124 Notice: 2019-10-30 16:00:12 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[stx-platform]/Exec[Adding StarlingX helm repo: stx-platform]/returns: Error: Looks like "http://127.0.0.1:8080/helm_charts/stx-platform" is not a valid chart repository or cannot be reached: Get http://127.0.0.1:8080/helm_charts/stx-platform/index.yaml: dial tcp 127.0.0.1:8080: connect: connection refused
2019-10-30T16:00:12.126 Error: 2019-10-30 16:00:12 +0000 helm repo add stx-platform http://127.0.0.1:8080/helm_charts/stx-platform returned 1 instead of one of [0]
2019-10-30T16:00:12.218 Error: 2019-10-30 16:00:12 +0000 /Stage[main]/Platform::Helm::Repositories/Platform::Helm::Repository[stx-platform]/Exec[Adding StarlingX helm repo: stx-platform]/returns: change from notrun to 0 failed: helm repo add stx-platform http://127.0.0.1:8080/helm_charts/stx-platform returned 1 instead of one of [0]
Severity
--------
Critical: Unable to restore standby controller in Regular system
Steps to Reproduce
------------------
1. Bring up the Regular system system
2. Backup the system using ansible locally
3. Re-install the controller with the same load
4. Restore the active controller
5. Unlock active controller
6. Boot standby controller via PXE
7. unlock standby controller
Expected Behavior
------------------
The standby controller should be successfully restored and become available
Actual Behavior
----------------
Standby controller failed to become available after unlock
Reproducibility
---------------
Reproducible
System Configuration
--------------------
Regular System
Branch/Pull Time/Commit
-----------------------
BUILD_ID="2019-10-27_20-00-00"
Test Activity
-------------
Feature Testing |
|
| 2019-10-31 13:27:39 |
Frank Miller |
starlingx: assignee |
|
Ovidiu Poncea (ovidiu.poncea) |
|
| 2019-10-31 13:27:58 |
Frank Miller |
summary |
Backup & Restore: Standby controller failed to come abailable after restore/unlock action in Regular system |
Backup & Restore: Standby controller failed to come available after restore/unlock action in Regular system |
|
| 2019-10-31 16:38:08 |
Yang Liu |
summary |
Backup & Restore: Standby controller failed to come available after restore/unlock action in Regular system |
Backup & Restore HTTPS: Standby controller failed to come available after restore/unlock action in Regular system |
|
| 2019-10-31 16:38:16 |
Yang Liu |
tags |
|
stx.retestneeded |
|
| 2019-10-31 20:28:11 |
Ghada Khalil |
tags |
stx.retestneeded |
stx.retestneeded stx.update |
|
| 2019-11-01 18:59:57 |
Ghada Khalil |
starlingx: importance |
Undecided |
Medium |
|
| 2019-11-01 19:00:00 |
Ghada Khalil |
starlingx: status |
New |
Triaged |
|
| 2019-11-01 19:00:11 |
Ghada Khalil |
tags |
stx.retestneeded stx.update |
stx.3.0 stx.retestneeded stx.update |
|
| 2019-11-06 20:02:13 |
OpenStack Infra |
starlingx: status |
Triaged |
In Progress |
|
| 2019-11-13 14:17:42 |
OpenStack Infra |
starlingx: status |
In Progress |
Fix Released |
|
| 2019-11-13 17:15:47 |
Frank Miller |
bug |
|
|
added subscriber Bill Zvonar |
| 2020-02-21 21:03:39 |
Senthil Mukundakumar |
tags |
stx.3.0 stx.retestneeded stx.update |
stx.3.0 stx.update |
|
| 2020-04-27 16:30:44 |
Ghada Khalil |
tags |
stx.3.0 stx.update |
stx.3.0 stx.4.0 stx.update |
|
