cinder backup stuck in Error if created on controller-1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Irina Mihai |
Bug Description
Brief Description
-----------------
On controller-1, cinder-backup created using CLI went and remained in "error" status. "cinder backup-show" displayed "An unknown exception occurred."
No file(s) generated under /opt/backups
Severity
--------
Minor
Steps to Reproduce
------------------
1 make sure controller-1 is the active controller
2 execute CLI:
cinder backup-create --container cinder --name <bk_name> <vol_id>
Expected Behavior
------------------
a "cinder-backup" was expected to be created and eventually reached 'available' status; files for the volume were generated under /opt/backups
Actual Behavior
----------------
The "cinder-backup" went and remained in "error". "cinder backup-show" displayed "An unknown exception occurred."
No file(s) generated under /opt/backups
Traceback/errors were found in log files.
Reproducibility
---------------
Reproducible
System Configuration
-------
Dedicated storage
Branch/Pull Time/Commit
-------
master as of build-date-time
StarlingX_Upstream as of 2019-01-02_20-18-00
Timestamp/Logs
Jan 3 10:46
--------------
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
From Wei Zhou: ceph.client. None.keyring which is a workaround for an upstream bug in rbd is not created on the standby controller because of commit http:// git.openstack. org/cgit/ openstack/ stx-config/ commit/ ?id=2a99d0b4b95 348ea849ed6f6f1 e7b34f76e2ec84. In the test cinder backup was done after controller swact which means on the newly active controller file /etc/ceph/ ceph.client. None.keyring doesn't exist; therefore cinder backup failed.
The root cause is that the empty file /etc/ceph/