May 2016 - Devel - oVirt List Archives

oVirt Community Newsletter: April 2016
by Brian Proffitt 09 May '16

09 May '16

Spring has sprung in the Northern Hemisphere, and oVirt dev team is preparing for the upcoming 4.0 release, even as the 3.6 tree continues. And while oVirt has taken a respite from the event extravaganzas of January and February, there's still some positive moves happening in the oVirt community. ----------------- Software Releases ----------------- oVirt 3.6.5 Final Release is now available http://lists.ovirt.org/pipermail/announce/2016-April/000247.html oVirt Live 3.6.6 First Release Candidate is now available for testing http://lists.ovirt.org/pipermail/users/2016-April/039430.html oVirt 3.6.6 Second Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2016-May/000251.html oVirt Node Next Beta http://lists.ovirt.org/pipermail/announce/2016-April/000250.html ---------------- In the Community ---------------- Schedule for oVirt 4.0.0 http://lists.ovirt.org/pipermail/announce/2016-April/000246.html Prepare for version 4 of oVirt API http://lists.ovirt.org/pipermail/users/2016-May/039624.html RCC adopts oVirt for Virtualization https://rcc.fsu.edu/news/rcc-adopts-ovirt-virtualization oVirt Makes Impact at ROSS'16 [Russian] http://www.pcweek.ru/foss/article/detail.php?ID=184736 ------------------------------------ Deep Dives and Technical Discussions ------------------------------------ Advanced users authentication, using Kerberos, CAS SSO and Active Directory http://www.ovirt.org/blog/2016/04/sso/ DevNation: oVirt, Uninterrupted and Integrated Virtualization http://bit.ly/1VQxRKv oVirt-Specific Aspect Languages http://ahadas.github.io/oVirt-Specifc-Aspect-Languages/ Downstream News: RHEV To Make Impact at DevNation http://bit.ly/1VQxQ9p Downstream: Scaling Up On Demand with Red Hat Enterprise Virtualization http://red.ht/1VI1HR8 -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

1 0

ioprocess logs
by Piotr Kliczewski 09 May '16

09 May '16

All, Whenever I see build failure on my laptop there is bunch of ioprocess logs. Can we find fix the issues? Exception AttributeError: "'NoneType' object has no attribute 'write'"Exception in thread ioprocess communication (15770) (most likely raised during interpreter shutdown): in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb84a510>> ignored Exception AttributeError: "'NoneType' object has no attribute 'wrTraceback (most recent call last): ite'" File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f7b5b10>> ignored Exception AttributeError File "/usr/lib64/python2.7/threading.py", line 757, in run : File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 180, in _communicate"'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f831950>><type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'close' ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84fe90>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f866850>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f82fbd0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f7b5310>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb84a350>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb919550>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f861690>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f8342d0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0b8491610>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0b8187ed0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb800ad0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f861a10>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb791090>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb774650>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f834b10>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f77fb50>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84ad90>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84f690>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f60f510>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84a4d0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f82f150>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f831290>> ignored Thanks, Piotr

2 3

Ondra Machacek is now the main maintainer of the Python and Java SDK
by Juan Hernández 09 May '16

09 May '16

Hello, Ondra Machacek has been doing an excellent work in the new versions of the Java and Python SDKs for version 4 of the engine. As a result we have decided to appoint him as the main maintainer of these two components. Starting intermediately he will take full responsibility and ownership of version 4 of these SDKs. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

1 0

[ATTN] VDSM netinfo changes break hosted-engine --deploy
by Roy Golan 09 May '16

09 May '16

VDSM's commit ef992682782853a20d8f537a96ba376286ef10df moved netinfo under network folder and that break hosted-engine --deploy. It will fail with ``` # hosted-engine --deploy ***L:ERROR Internal error: No module named netinfo.cache ``` Please review the fix: https://gerrit.ovirt.org/57228 Adapt to netinfo namespace change under network [DRAFT]

1 0

Re: [ovirt-devel] [Fixed][vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

On Sun, May 8, 2016 at 4:11 PM, Maor Lipchuk <mlipchuk(a)redhat.com> wrote: > > > On Sun, May 8, 2016 at 2:22 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, May 8, 2016 at 12:56 PM, Maor Lipchuk <mlipchuk(a)redhat.com> >> wrote: >> > Hi, >> > >> > I've been trying to remove a single snapshot and consistently fail with >> the >> > following error (see [1]). >> > >> > Those are my steps: >> > 1. Create a VM + Disk >> > 2. Create a snapshot >> > 3. Remove the snapshot >> > >> > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) >> > >> > Is there a bug open on it? or even better, fixing patches? >> > >> > [1] >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming >> > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 >> > >> 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease >> > to >> > /rhev/data-center/mnt/10.35.16.43: >> _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f >> > >> /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease >> > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 >> > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute >> > Traceback (most recent call last): >> > File "/usr/share/vdsm/storage/image.py", line 1321, in merge >> > [vols[vName] for vName in chain]) >> > File "/usr/share/vdsm/storage/image.py", line 1146, in >> _baseRawVolumeMerge >> > srcVol.rename(tmpUUID) >> > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename >> > self._manifest.volumePath = volPath >> > AttributeError: can't set attribute >> >> I think this is a bug introduced during the sdm refactorings, and I >> also reproduced it once >> but did not have time to investigate it yet. >> >> If the code expect the replace a volume path during runtime, we should >> have a setter: >> >> @property >> def volumePath(self): >> return self._volumePath >> >> @volumePath.setter >> def volumePath(self, value): >> self._volumePath = value >> >> You can try add this to the manifest class and see if it fixes this issue. >> > > Looks like that fixes the issue. Added a patch at https://gerrit.ovirt.org/#/c/57194/1 Thanks for the help, Maor > > > >> >> Nir >> >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. >> > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS >> > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS >> > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 >> > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error >> > Traceback (most recent call last): >> > File "/usr/share/vdsm/storage/task.py", line 875, in _run >> > return fn(*args, **kargs) >> > File "/usr/share/vdsm/storage/task.py", line 334, in run >> > return self.cmd(*self.argslist, **self.argsdict) >> > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", >> line >> > 78, in wrapper >> > return method(self, *args, **kwargs) >> > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots >> > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) >> > File "/usr/share/vdsm/storage/image.py", line 1339, in merge >> > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) >> > SourceImageActionError: Error during source image manipulation: >> > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source >> > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: >> > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running >> > (force False) >> > >> > >> > >> > Regards, >> > Maor >> > >> > >> > _______________________________________________ >> > vdsm-devel mailing list >> > vdsm-devel(a)lists.fedorahosted.org >> > >> https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org >> > >> > >

1 0

Re: [ovirt-devel] [vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

On Sun, May 8, 2016 at 2:22 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 8, 2016 at 12:56 PM, Maor Lipchuk <mlipchuk(a)redhat.com> wrote: > > Hi, > > > > I've been trying to remove a single snapshot and consistently fail with > the > > following error (see [1]). > > > > Those are my steps: > > 1. Create a VM + Disk > > 2. Create a snapshot > > 3. Remove the snapshot > > > > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) > > > > Is there a bug open on it? or even better, fixing patches? > > > > [1] > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming > > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 > > > 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease > > to > > /rhev/data-center/mnt/10.35.16.43: > _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f > > > /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease > > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute > > Traceback (most recent call last): > > File "/usr/share/vdsm/storage/image.py", line 1321, in merge > > [vols[vName] for vName in chain]) > > File "/usr/share/vdsm/storage/image.py", line 1146, in > _baseRawVolumeMerge > > srcVol.rename(tmpUUID) > > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename > > self._manifest.volumePath = volPath > > AttributeError: can't set attribute > > I think this is a bug introduced during the sdm refactorings, and I > also reproduced it once > but did not have time to investigate it yet. > > If the code expect the replace a volume path during runtime, we should > have a setter: > > @property > def volumePath(self): > return self._volumePath > > @volumePath.setter > def volumePath(self, value): > self._volumePath = value > > You can try add this to the manifest class and see if it fixes this issue. > Which class is it? Where is it located? > > Nir > > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. > > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error > > Traceback (most recent call last): > > File "/usr/share/vdsm/storage/task.py", line 875, in _run > > return fn(*args, **kargs) > > File "/usr/share/vdsm/storage/task.py", line 334, in run > > return self.cmd(*self.argslist, **self.argsdict) > > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line > > 78, in wrapper > > return method(self, *args, **kwargs) > > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots > > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) > > File "/usr/share/vdsm/storage/image.py", line 1339, in merge > > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) > > SourceImageActionError: Error during source image manipulation: > > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source > > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: > > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running > > (force False) > > > > > > > > Regards, > > Maor > > > > > > _______________________________________________ > > vdsm-devel mailing list > > vdsm-devel(a)lists.fedorahosted.org > > > https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org > > >

1 0

Fwd: [vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

Forwarding to devel@ovirt list. cc'ing Adam as well ---------- Forwarded message ---------- From: Dan Kenigsberg <danken(a)redhat.com> Date: Sun, May 8, 2016 at 2:52 PM Subject: Re: [vdsm] Failing to rename volume on merge (remove snapshot operation) To: Maor Lipchuk <mlipchuk(a)redhat.com> vdsm-devel is long deprecated. Plesae repost to devel@ovirt, and include alitke, the owner of _manifest on your CC. On Sun, May 08, 2016 at 12:56:58PM +0300, Maor Lipchuk wrote: > Hi, > > I've been trying to remove a single snapshot and consistently fail with the > following error (see [1]). > > Those are my steps: > 1. Create a VM + Disk > 2. Create a snapshot > 3. Remove the snapshot > > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) > > Is there a bug open on it? or even better, fixing patches? > > [1] > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 > 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease > to /rhev/data-center/mnt/10.35.16.43: > _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f > /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute > Traceback (most recent call last): > File "/usr/share/vdsm/storage/image.py", line 1321, in merge > [vols[vName] for vName in chain]) > File "/usr/share/vdsm/storage/image.py", line 1146, in _baseRawVolumeMerge > srcVol.rename(tmpUUID) > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename > self._manifest.volumePath = volPath > AttributeError: can't set attribute > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error > Traceback (most recent call last): > File "/usr/share/vdsm/storage/task.py", line 875, in _run > return fn(*args, **kargs) > File "/usr/share/vdsm/storage/task.py", line 334, in run > return self.cmd(*self.argslist, **self.argsdict) > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line > 78, in wrapper > return method(self, *args, **kwargs) > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) > File "/usr/share/vdsm/storage/image.py", line 1339, in merge > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) > SourceImageActionError: Error during source image manipulation: > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running > (force False) > > > > Regards, > Maor > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org

1 0

[IOPROCESS] New builds for testing
by Nir Soffer 07 May '16

07 May '16

Hi all, Fresh ioprocess builds are available for testing. The packages should be available in updates-testing repository on fedora. Please test these builds and provide feedback here: https://bodhi.fedoraproject.org/updates/?packages=ioprocess Thanks, Nir

1 0

[ANN] oVirt 3.6.6 Second Release Candidate is now available for testing
by Sandro Bonazzola 07 May '16

07 May '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.6 for testing, as of May 7th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release candidate includes the following updated packages: * ovirt-engine * ovirt-hosted-engine-setup * ovirt-hosted-engine-ha * vdsm * vdsm-jsonrpc-java See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * A new oVirt Node Next Install ISO will be available soon[3] * Mirrors[4] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.6 release highlights: http://www.ovirt.org/release/3.6.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.6/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/ [3] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node-ng-installer/ [4] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[URGENT][ACTION REQUIRED] fc23 master broken on vdsm-jsonrpc-java-1.2.3 missing
by Sandro Bonazzola 07 May '16

07 May '16

*21:57:45* package: ovirt-engine-backend-4.0.0-0.0.master.20160506110433.gitb791fed.fc23.noarch from check-custom-fc23*21:57:45* unresolved deps: *21:57:45* vdsm-jsonrpc-java >= 0:1.2.3 Please fix ASAP. Just to clarify, when a new build is needed: 1) get all the needed code merged in gerrit 2) tag the commit with the version bump 3) be sure that jenkins build job has been triggered and the package is built successfully 4) push to sonatype / maven central 5) once everything is in place, only then, change the code in ovirt-engine. pushing to sonatype before having code merged, tagged and built and require it will lead to breakage at all levels. This is the 4th time today I hit breakage like this, please avoid that in future. Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0