| Summary: | The storage pool status is active after reboot although "Auto start" is not checked | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | mliu |
| Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> |
| Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | berrange, dallan, dyuan, kxiong, mliu, mzhan, nzhang |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-20 18:52:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
mliu
2011-03-17 10:21:17 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Can you test this outside of virt-manager. Open virt-manager, uncheck the "auto start" option for the pool. Stop virt-manager verify that virsh pool-list --all shows autostart 'no' restart the host before starting virt-manager, check what virsh pool-list --all reports for running pool and autostart values start virt-manager, see what virt-manager reports recheck what virsh is reporting Hi Cole Robinson, I test it according your comment, following is the step and result: 1. My pool default status is: # virsh pool-list --all Name State Autostart ----------------------------------------- default active yes test active yes 2. Open virt-manager, uncheck the "auto start" option for the pool, stop virt-manager, the pool status is: # virsh pool-list --all Name State Autostart ----------------------------------------- default active no test active no 3. Restart the host, before starting virt-manager, the pool status is: # virsh pool-list --all Name State Autostart ----------------------------------------- default active no test inactive no 4. Start virt-manager, I can see the 'default' pool is active, and 'test' pool is inactive 5. virsh report is : # virsh pool-list --all Name State Autostart ----------------------------------------- default active no test inactive no according to this output, at step 3, the default pool is already active. so it doesn't sound like this is virt-manager doing, but I don't know what is causing the problem. is step 3 output correct here? if so, what's the output of 'ls /etc/libvirt/storage/autostart' after each step? Reassigning to libvirt When libvirtd starts up, it'll check to see if any of the storage pools have been activated externally. If this is so, then it'll mark the pool as active. This is independent of autostart. A directory based storage pool is thus pretty much always active (In reply to comment #6) > When libvirtd starts up, it'll check to see if any of the storage pools have > been activated externally. If this is so, then it'll mark the pool as active. > This is independent of autostart. A directory based storage pool is thus > pretty much always active Given that, I'd say this is not a bug. Dan, what do you think? Well the original reporter didn't give any specific info of what type of storage pool they are using, but assuming they hit the scenario I describe, it is not a bug. I have seen this behavior with iSCSI pools as well. The iSCSI initiator logs into the target automatically and libvirt recognizes the pool (correctly) as active. I'm resolving as NOTABUG. |