Bug 1092034
| Summary: | volume attachment fails on a paused instance | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Yogev Rabl <yrabl> | ||||
| Component: | openstack-nova | Assignee: | RHOS Maint <rhos-maint> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Ami Jeain <ajeain> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.0 | CC: | ndipanov, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-04-29 18:31:39 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: | |||||||
| Attachments: |
|
||||||
I will close this as upstream work. There is already a bug about this upstream and several people are looking into it. I see no value in us tracking this here. Adding the original bug also. |
Created attachment 890514 [details] nova-compute log Description of problem: When running volume attachment on a paused instance, the process seem to succeed, the volume is registered as 'in-use' and there's no error in the nova compute log. But when resuming the instance the OS doesn't see the newly attached volume and when trying to detach the volume it fails with the error "DiskNotFound: No disk at vdb" in the nova compute log. Version-Release number of selected component (if applicable): python-nova-2013.2.3-6.el6ost.noarch openstack-nova-compute-2013.2.3-6.el6ost.noarch python-novaclient-2.15.0-4.el6ost.noarch openstack-nova-common-2013.2.3-6.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. Launch an instance with a working OS with a QCOW image. 2. Pause the instance. 3. Attach a volume to the instance. 4. Resume the instance. 5. In the instance: run the command: # lsblk Actual results: The instance's OS doesn't see the attached volume. Expected results: The instance's OS should see the volume. Additional info: The nova-compute log is attached. (please notice that the log is very long,