Bug 1554289
Summary: | [downstream clone - 4.1.10] Unable to detach the disk while running commvault backup proxy. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
Component: | vdsm | Assignee: | Daniel Erez <derez> |
Status: | CLOSED ERRATA | QA Contact: | Elad <ebenahar> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.9 | CC: | amureini, bazulay, ebenahar, lsurette, srevivo, tnisan, ycui, ykaul, ylavi |
Target Milestone: | ovirt-4.1.10 | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | v4.19.50 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1547358 | Environment: | |
Last Closed: | 2018-03-20 16:38:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1547358 | ||
Bug Blocks: |
Description
RHV bug bot
2018-03-12 10:51:11 UTC
This is probably another libvirt issue (or a different facet of the same issue) around the same area. Let's revisit once we have the original BZ fixed. (Originally by Allon Mureinik) WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.1.z': '?'}', ] For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.1.z': '?'}', ] For more info please contact: rhv-devops [root@storage-ge7-vdsm1 ~]# repoquery --requires vdsm |grep libvirt-daemon-kvm libvirt-daemon-kvm >= 3.2.0-14.el7_4.8 Used: vdsm-4.19.50-1.el7ev.x86_64 RHEL7.5 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0563 BZ<2>Jira Resync |