Bug 1514303
Summary: | QEMU Guest Agent VSS Provider service is being installed with startup type: Automatic | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | xiagao |
Component: | virtio-win | Assignee: | Sameeh Jubran <sjubran> |
virtio-win sub component: | qemu-ga-win | QA Contact: | Virtualization Bugs <virt-bugs> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | ailan, lijin, mtessun, sjubran, wyu |
Version: | 7.5 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 06:31:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xiagao
2017-11-17 02:46:06 UTC
Please test this version: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14584177 (In reply to Sameeh Jubran from comment #2) > Please test this version: > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14584177 Tested in this version, steps like comment 0. The result is: 1) startup type: Manual -->Expected 2) issue {"execute":"guest-fsfreeze-freeze"} in host and create snapshot, check VSS status is started -->Expected 3) issue {"execute":"guest-fsfreeze-thaw"} in host,check VSS service's status is still started. -----> It should be null. So this bug is not fixed. I think this should be resolved in this build: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14587298 What do you mean by "null status"? (In reply to Sameeh Jubran from comment #4) > I think this should be resolved in this build: > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14587298 > > What do you mean by "null status"? I think VSS service should be stop status after executing {"execute":"guest-fsfreeze-thaw"} in host. (In reply to xiagao from comment #5) > (In reply to Sameeh Jubran from comment #4) > > I think this should be resolved in this build: > > > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14587298 > > > > What do you mean by "null status"? > > I think VSS service should be stop status after executing > {"execute":"guest-fsfreeze-thaw"} in host. I mean VSS Service status should be empty rather than "started" in guest after issuing {"execute":"guest-fsfreeze-thaw"}. Test with the latest build you provided. https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14587298 The result is: 1) startup type: Manual -->Expected 2) issue {"execute":"guest-fsfreeze-freeze"} in host and create snapshot, check VSS status is started -->Expected 3) issue {"execute":"guest-fsfreeze-thaw"} in host,check VSS service's status is empty. -----> Expected. So this bug is fixed. I will verify this bug in an official build. mingw-qemu-ga-win v2.9.3 build is ready: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=14628546 reproduce with previous version, and verified with mingw-qemu-ga-win v2.9.3 steps as comment#0 So, this bug has been fixed version: qemu-ga-win-2.9.3-2.el7ev.noarch qemu-kvm-rhev-2.10.0-7.el7.x86_64 Thanks Yu Wang 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/RHBA-2018:0657 |