Bug 2054605: fix: updates lvmvolumegroupnodestatus for vg #112
Conversation
Fixes a bug where the lvmvolumegroupnodestatus was not updated correctly for an existing VG. When adding a new device and restarting the vg-manager pod, the device is added to the LVM VG but is not updated in the lvmvolumegroupnodestatus or the LVMCluster status. Signed-off-by: N Balachandran <nibalach@redhat.com>
nbalacha
changed the title
openshift-ci
bot
added
bugzilla/severity-unspecified
|
@openshift-cherrypick-robot: This pull request references Bugzilla bug 2054605, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (srozen@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: leelavg, openshift-cherrypick-robot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@openshift-cherrypick-robot: All pull requests linked via external trackers have merged: Bugzilla bug 2054605 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is an automated cherry-pick of #110
/assign nbalacha