B&R with stx-openstack: Unlock failed after restore playbook was run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Dan Voiculeasa |
Bug Description
Brief Description
-----------------
Restoring a system that had stx-openstack applied prior to the backup will fail.
Failure at unlocking controller-0. Root cause: no plugins detected.
Severity
--------
Critical: System/Feature is not usable due to the defect
Steps to Reproduce
------------------
Do B&R on a system with stx-openstack applied.
Expected Behavior
------------------
Controller can be unlocked after restore_platform playbook is run.
Actual Behavior
----------------
Failed to unlock.
Reproducibility
---------------
100% reproducible
System Configuration
-------
AIO-SX ipv4, but this should be seen on all types
Branch/Pull Time/Commit
-------
4 Aug 2020
Last Pass
---------
May/June, maybe more recent.
Timestamp/Logs
--------------
File "/usr/lib64/
**args)
File "/usr/lib64/
result = getattr(proxyobj, method)(ctxt, **kwargs)
File "/usr/lib64/
self.
File "/usr/lib64/
func(self, *args, **kwargs)
File "/usr/lib64/
config.
File "/usr/lib64/
keystone_
File "/usr/lib64/
return func(self, *args, **kwargs)
File "/usr/lib64/
keystone_
KeyError: 'keystone'
Test Activity
-------------
Developer Testing
Changed in starlingx: | |
assignee: | nobody → Dan Voiculeasa (dvoicule) |
summary: |
- B&R: Unlock failed after restore playbook was run, the system had stx- - openstack applied + B&R with stx-openstack: Unlock failed after restore playbook was run |
Fix proposed to branch: master /review. opendev. org/745332
Review: https:/