host-lock storage node failed by "Cannot lock a storage node when ceph pools are not empty and replication is lost"

Bug #2043495 reported by Douglas Gameiro Diniz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
In Progress
Undecided
Unassigned

Bug Description

Brief Description
-----------------
In storage system, host-lock storage node failed. The error msg shows,
failed to execute. Output: "Cannot lock a storage node when ceph pools are not empty and replication is lost. This may result in data loss".

Severity
--------
Minor

Steps to Reproduce
------------------
None. It appears to be a data race, so the problem happens rarely during installation.

Expected Behavior
------------------
We should be able to lock the node.

Actual Behavior
----------------
We can't lock the node.

Reproducibility
---------------
Random.

System Configuration
--------------------
Storage 2+2+2

Branch/Pull Time/Commit
-----------------------

Last Pass
---------

Timestamp/Logs
--------------

Test Activity
-------------
Developer Testing

Workaround
----------
None.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/900926

Changed in starlingx:
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.