RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 871811 - 3.1 [vdsm] createVolume failsfor file based storage (NFS and local storage)
Summary: 3.1 [vdsm] createVolume failsfor file based storage (NFS and local storage)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Federico Simoncelli
QA Contact: Jakub Libosvar
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-31 13:11 UTC by Jakub Libosvar
Modified: 2022-07-09 05:40 UTC (History)
11 users (show)

Fixed In Version: vdsm-4.9.6-41.0
Doc Type: Bug Fix
Doc Text:
Previously, attempts to suspend a virtual machine with local storage using the REST API failed, with an error stating the volume didn't exist. The REST API was patched to make fileVolume a real classmethod, symmetrical with block domains. Virtual machines with disks on local storage domains can now be suspended using the REST API.
Clone Of:
Environment:
Last Closed: 2012-12-04 19:13:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Logs (2.12 MB, application/x-gzip)
2012-10-31 13:11 UTC, Jakub Libosvar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2012:1508 0 normal SHIPPED_LIVE Important: rhev-3.1.0 vdsm security, bug fix, and enhancement update 2012-12-04 23:48:05 UTC

Description Jakub Libosvar 2012-10-31 13:11:24 UTC 
Created attachment 636125 [details]
Logs

Description of problem:
When test tries to suspend VM on local storage via API we got exception in createVolume that Volume doesn't exist

to API was sent:
url:/api/vms/83c5e31c-2397-4a7e-9996-46034c46c303/suspend 
body:<action>
    <async>false</async>
    <grace_period>
        <expiry>10</expiry>
    </grace_period>
</action>

Version-Release number of selected component (if applicable):
rhev-3.1 revision c0c61931cc2d4690a6ddb32b0a52f2989b6ae0b6
vdsm-4.9.6-40.0.el6_3.x86_64

How reproducible:
Last two tests on Jenkins

Steps to Reproduce:
1. Suspend VM on local storage
  
Actual results:


Expected results:


Additional info:
Not sure if vdsm bug, please move to correct component if not vdsm bug
There should be sufficient space on host 
/dev/sda3             453G  1.8G  428G   1% /

78ee923f-328a-4e5b-850e-ac5f5e255241::INFO::2012-10-31 13:12:04,966::fileVolume::153::Storage.Volume::(_create) Request to create RAW volume /rhev/data-center/b4997363-604b-4392-8250-3ccae29c3223/87fca1e4-9191-4337-9fb9-b01b88be7e32/images/7b50d791-02a9-4da3-ae39-a0075d599b18/1d8baec6-36b6-4109-b6a3-beb342f20672 with size = 2637824 sectors

78ee923f-328a-4e5b-850e-ac5f5e255241::DEBUG::2012-10-31 13:12:05,014::fileVolume::558::Storage.Volume::(validateVolumePath) validate path for 1d8baec6-36b6-4109-b6a3-beb342f20672

78ee923f-328a-4e5b-850e-ac5f5e255241::ERROR::2012-10-31 13:12:05,016::volume::509::Storage.Volume::(create) Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/volume.py", line 484, in create
    apparentSize = cls.getVSize(dom, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/fileVolume.py", line 463, in getVSize
    return sdobj.produceVolume(imgUUID, volUUID).getVolumeSize(bs)
  File "/usr/share/vdsm/storage/fileSD.py", line 174, in produceVolume
    return fileVolume.FileVolume(repoPath, self.sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/fileVolume.py", line 71, in __init__
    volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/volume.py", line 128, in __init__
    self.validate()
  File "/usr/share/vdsm/storage/volume.py", line 141, in validate
    self.validateVolumePath()
  File "/usr/share/vdsm/storage/fileVolume.py", line 567, in validateVolumePath
    self.validateMetaVolumePath()
  File "/usr/share/vdsm/storage/fileVolume.py", line 576, in validateMetaVolumePath
    raise se.VolumeDoesNotExist(self.volUUID)
VolumeDoesNotExist: Volume does not exist: ('1d8baec6-36b6-4109-b6a3-beb342f20672',)
Comment 7 Jakub Libosvar 2012-11-02 08:26:16 UTC 
(In reply to comment #3)
> is this only via API or via UI as well?
I can't tell, it runs on Jenkins and I think UI is not built for this test.
> since flagged as a regression, can you please specify which version worked?
rhevm-3.1.0-20.el6ev.noarch
Comment 8 Ayal Baron 2012-11-04 10:47:53 UTC 
http://gerrit.ovirt.org/#/c/8995/
Comment 10 Ayal Baron 2012-11-04 18:47:56 UTC 
Change ID: I336d4e763da4ddc3c0dd8eacb68e84305995e6ab
Comment 11 Jakub Libosvar 2012-11-06 12:32:22 UTC 
Verified rhevm-3.1.0-26.el6ev.noarch
Comment 13 errata-xmlrpc 2012-12-04 19:13:47 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html
Note You need to log in before you can comment on or make changes to this bug.