-
Notifications
You must be signed in to change notification settings - Fork 596
Revert "rbd: fetch the volumeIds from VGRContent's status for omap data" #5962
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: devel
Are you sure you want to change the base?
Conversation
0171692 to
cc587a9
Compare
|
Please update the details in the commit message too. The description of the PR should include a path forward. Why not propose that downstream change here as well? |
|
Does this need a backport to one or more release branches? |
The d/s change is not part of u/s yet, hence only reverting the change here. |
It has to be backport to |
This reverts commit e62e083. The commit needs to be reverted as on further testing it was found that fetching the omap data from status could mean that we would trigger a modify operation during promotion of a group which could lead to inconsistency. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
cc587a9 to
2cd7076
Compare
Done. |
|
@Mergifyio queue |
❌ The pull request has been removed from the queue
|
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 17 minutes 31 seconds in the queue, including 17 minutes 18 seconds running CI. Required conditions to merge
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
❌ The pull request has been removed from the queue
|
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 16 minutes 59 seconds in the queue, including 16 minutes 47 seconds running CI. Required conditions to merge
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
❌ The pull request has been removed from the queue
|
Merge Queue Status🚫 The pull request has left the queue (rule: This pull request spent 21 minutes 5 seconds in the queue, including 20 minutes 55 seconds running CI. Required conditions to merge
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
|
#5968 addresses the CI issue. Please wait with re-queuing until that PR is merged. |
|
@Mergifyio requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
🟠 The pull request is queued to be mergedDetailsBranch devel (cba25cb) and #5962 are embarked together for merge. Required conditions of queue
Required conditions to stay in the queue:
|
Merge Queue Status🟠 Waiting for merge conditions (rule: Entered the queue at: Required conditions to merge
Required conditions to stay in the queue
|
This PR reverts commit e62e083.
The commit needs to be reverted as on further testing it was found that fetching the omap data from status could mean that we would trigger a modify operation during promotion of a group which could lead to inconsistency.
A safer option to check the sanity of groups before modifying is added in the d/s PR: red-hat-storage#687 before attempting to modify the group.