oVirt 3.4.0 alpha repository closure failure
by Sandro Bonazzola
Hi,
oVirt 3.4.0 alpha repository has been composed but alpha has not been announced due to repository closure failures:
on CentOS 6.5:
# repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 8
base
epel
glusterfs-epel
glusterfs-noarch-epel
ovirt-3.3.2
ovirt-3.4.0-alpha
ovirt-stable
updates
Num Packages in Repos: 16581
package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
procps-ng
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6
package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
httpcomponents-client >= 0:4.2
apache-commons-logging
apache-commons-beanutils
package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
vhostmd
On Fedora 19:
# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
fedora
ovirt-3.4.0-alpha
ovirt-stable
updates
Num Packages in Repos: 38832
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
openstack-java-resteasy-connector >= 0:3.0.2
openstack-java-quantum-model >= 0:3.0.2
openstack-java-quantum-client >= 0:3.0.2
openstack-java-keystone-model >= 0:3.0.2
openstack-java-keystone-client >= 0:3.0.2
openstack-java-glance-model >= 0:3.0.2
openstack-java-glance-client >= 0:3.0.2
openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
ovirt-engine-dwh >= 0:3.4.0
On Fedora 20 (ovirt-stable doesn't support Fedora 20):
# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 3
fedora
ovirt-3.4.0-alpha
updates
Num Packages in Repos: 38822
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
openstack-java-resteasy-connector >= 0:3.0.2
openstack-java-quantum-model >= 0:3.0.2
openstack-java-quantum-client >= 0:3.0.2
openstack-java-keystone-model >= 0:3.0.2
openstack-java-keystone-client >= 0:3.0.2
openstack-java-glance-model >= 0:3.0.2
openstack-java-glance-client >= 0:3.0.2
openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
ovirt-engine-dwh >= 0:3.4.0
Please fix dependencies / provide missing packages / provide additional repositories as soon as possible.
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
oVirt 3.4.0 alpha delayed
by Sandro Bonazzola
Hi,
oVirt 3.4.0 alpha will be delayed due to packages dependencies issue.
Maintainers are already working on this, alpha will be released just after all dependency issues will have been fixed.
Details on dependency missing:
on CentOS 6.5:
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/$releasever/
enabled=1
skip_if_unavailable=1
gpgcheck=0
# repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 8
base
epel
glusterfs-epel
glusterfs-noarch-epel
ovirt-3.3.2
ovirt-3.4.0-alpha
ovirt-stable
updates
Num Packages in Repos: 16581
package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
procps-ng
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.el6
package: ovirt-engine-sdk-java-3.4.0.1-1.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
httpcomponents-client >= 0:4.2
apache-commons-logging
apache-commons-beanutils
package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha
unresolved deps:
vhostmd
On Fedora 19:
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$relea...
enabled=1
skip_if_unavailable=1
gpgcheck=0
# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates -l ovirt-stable
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 4
fedora
ovirt-3.4.0-alpha
ovirt-stable
updates
Num Packages in Repos: 38832
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
openstack-java-resteasy-connector >= 0:3.0.2
openstack-java-quantum-model >= 0:3.0.2
openstack-java-quantum-client >= 0:3.0.2
openstack-java-keystone-model >= 0:3.0.2
openstack-java-keystone-client >= 0:3.0.2
openstack-java-glance-model >= 0:3.0.2
openstack-java-glance-client >= 0:3.0.2
openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
ovirt-engine-dwh >= 0:3.4.0
On Fedora 20 (ovirt-stable doesn't support Fedora 20):
[ovirt-3.4.0-alpha]
name=Alpha builds of the oVirt 3.4 project
baseurl=http://resources.ovirt.org/releases/3.4.0-alpha/rpm/Fedora/$relea...
enabled=1
skip_if_unavailable=1
gpgcheck=0
# repoclosure -n -r ovirt-3.4.0-alpha -l fedora -l updates
Reading in repository metadata - please wait....
Checking Dependencies
Repos looked at: 3
fedora
ovirt-3.4.0-alpha
updates
Num Packages in Repos: 38822
package: otopi-devel-1.2.0-0.0.master.20130910.git4387efb.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
otopi-java = 0:1.2.0-0.0.master.20130910.git4387efb.fc19
package: ovirt-engine-3.4.0-0.2.master.20140109103311.git6524789.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
openstack-java-resteasy-connector >= 0:3.0.2
openstack-java-quantum-model >= 0:3.0.2
openstack-java-quantum-client >= 0:3.0.2
openstack-java-keystone-model >= 0:3.0.2
openstack-java-keystone-client >= 0:3.0.2
openstack-java-glance-model >= 0:3.0.2
openstack-java-glance-client >= 0:3.0.2
openstack-java-client >= 0:3.0.2
package: ovirt-engine-reports-3.4.0-0.2.master.20140109102135.fc19.noarch from ovirt-3.4.0-alpha
unresolved deps:
ovirt-engine-dwh >= 0:3.4.0
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
oVirt 3.4.0 release schedule updated
by Sandro Bonazzola
oVirt team has updated the release schedule for 3.4.0 [1]
These are tentative planning dates and may change
General availability: 2014-02-24
oVirt 3.4 Second Test Day: 2014-02-19
RC Build: 2014-02-17
oVirt 3.4 Test Day: 2014-01-27
Beta release: 2014-01-20
Branching / Feature freeze: 2014-01-15
Alpha release: 2014-01-09
more details on test days, etc to come in the next few weeks
[1] http://www.ovirt.org/OVirt_3.4_release-management#Timeline
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 5 months
Fwd: Re: oVirt 3.3.3 tracker
by Sandro Bonazzola
Adding VDSM and devel list.
-------- Messaggio originale --------
Oggetto: Re: oVirt 3.3.3 tracker
Data: Wed, 08 Jan 2014 22:03:07 +0200
Mittente: Itamar Heim <iheim(a)redhat.com>
A: Sandro Bonazzola <sbonazzo(a)redhat.com>, arch <arch(a)ovirt.org>, Doron Fediuck <dfediuck(a)redhat.com>, Dave Neary <dneary(a)redhat.com>,
"users(a)ovirt.org" <users(a)ovirt.org>
On 01/08/2014 07:04 PM, Sandro Bonazzola wrote:
> Hi,
> during today oVirt sync meeting it has been decided to release oVirt 3.3.3 [1] just after 3.4.0 alpha.
> 3.4.0 alpha will be composed tomorrow using next nightly build rpms.
>
> It has been proposed to build 3.3.3 beta next Monday, so here is the proposed schedule:
>
> General availability: 2014-01-28
> RC Build: 2014-01-21
> Beta release: 2014-01-13
make sense.
>
> A tracker bug has been created for blockers tracking: BZ 1050084 - Tracker: oVirt 3.3.3 release
>
> We still have ~30 bugs targeted to 3.3.3 [2], please update target releases and add blocker bugs to the tracker.
I asked for 3.3.4 target release to be added, but i think folks should
consider if to push bugs to 3.3.4, or to 3.4.0 by now.
I've added users mailing list, in case there is a specific bug someone
would like to highlight a specific bug that should go into 3.3.3 or 3.3.4.
>
> Waiting approval before preparing the email for other mailing lists.
>
> [1] http://www.ovirt.org/OVirt_3.3.z_release-management#oVirt_3.3.3
> [2] http://red.ht/1cOYkMo
>
10 years, 5 months
VDSM Sync call
by abaron@redhat.com
The following meeting has been forwarded:
Subject: VDSM Sync call
Organizer: abaron(a)redhat.com
Location: intercall 8425973915
Time: 4:30:00 PM - 5:30:00 PM GMT +02:00 Jerusalem [MODIFIED]
Recurrence : Every 2 week(s) on Monday No end date Effective Jul 4, 2011
Invitees: vdsm-devel(a)lists.fedorahosted.org
*~*~*~*~*~*~*~*~*~*
Most of you already know, but some must have forgotten, that we are
holding a bi-weekly Vdsm meeting over the phone. This is an opportunity
to discuss design problems, pending patches, and persistent bugs.
You are welcome to join. Even if you do not join, you may solicit
subjects for discussion on the mailing list or over
#vdsm(a)irc.freenode.net.
Conference code: 842-597-3915
Dial-in information:
https://www.intercallonline.com/listNumbersByCode.action?confCode=8425973915
Reservationless-Plus Toll Free Dial-In Number (US & Canada): (800) 451-8679
Reservationless-Plus International Dial-In Number: (212) 729-5016
Global Access Numbers Local:
Australia, Sydney Dial-In #: 0289852326
Austria, Vienna Dial-In #: 012534978196
Belgium, Brussels Dial-In #: 027920405
China Dial-In #: 4006205013
Denmark, Copenhagen Dial-In #: 32729215
Finland, Helsinki Dial-In #: 0923194436
France, Paris Dial-In #: 0170377140
Germany, Berlin Dial-In #: 030300190579
Ireland, Dublin Dial-In #: 014367793
Italy, Milan Dial-In #: 0236269529
Netherlands, Amsterdam Dial-In #: 0207975872
Norway, Oslo Dial-In #: 21033188
Singapore Dial-In #: 64840858
Spain, Barcelona Dial-In #: 935452328
Sweden, Stockholm Dial-In #: 0850513770
Switzerland, Geneva Dial-In #: 0225927881
United Kingdom Dial-In #: 02078970515
United Kingdom Dial-In #: 08445790676
United Kingdom, LocalCall Dial-In #: 08445790678
United States Dial-In #: 2127295016
Global Access Numbers Tollfree:
Argentina Dial-In #: 8004441016
Australia Dial-In #: 1800337169
Austria Dial-In #: 0800005898
Bahamas Dial-In #: 18002054776
Bahrain Dial-In #: 80004377
Belgium Dial-In #: 080048325
Brazil Dial-In #: 08008921002
Bulgaria Dial-In #: 008001100236
Chile Dial-In #: 800370228
Colombia Dial-In #: 018009134033
Costa Rica Dial-In #: 08000131048
Cyprus Dial-In #: 80095297
Czech Republic Dial-In #: 800700318
Denmark Dial-In #: 80887114
Dominican Republic Dial-In #: 18887512313
Estonia Dial-In #: 8000100232
Finland Dial-In #: 0800117116
France Dial-In #: 0805632867
Germany Dial-In #: 8006647541
Greece Dial-In #: 00800127562
Hong Kong Dial-In #: 800930349
Hungary Dial-In #: 0680016796
Iceland Dial-In #: 8008967
India Dial-In #: 0008006501533
Indonesia Dial-In #: 0018030179162
Ireland Dial-In #: 1800932401
Israel Dial-In #: 1809462557
Italy Dial-In #: 800985897
Jamaica Dial-In #: 18002050328
Japan Dial-In #: 0120934453
Korea (South) Dial-In #: 007986517393
Latvia Dial-In #: 80003339
Lithuania Dial-In #: 880030479
Luxembourg Dial-In #: 80026595
Malaysia Dial-In #: 1800814451
Mexico Dial-In #: 0018664590915
New Zealand Dial-In #: 0800888167
Norway Dial-In #: 80012994
Panama Dial-In #: 008002269184
Philippines Dial-In #: 180011100991
Poland Dial-In #: 008001210187
Portugal Dial-In #: 800814625
Russian Federation Dial-In #: 81080028341012
Saint Kitts and Nevis Dial-In #: 18002059252
Singapore Dial-In #: 8006162235
Slovak Republic Dial-In #: 0800001441
South Africa Dial-In #: 0800981148
Spain Dial-In #: 800300524
Sweden Dial-In #: 200896860
Switzerland Dial-In #: 800650077
Taiwan Dial-In #: 00801127141
Thailand Dial-In #: 001800656966
Trinidad and Tobago Dial-In #: 18002024615
United Arab Emirates Dial-In #: 8000650591
United Kingdom Dial-In #: 08006948057
United States Dial-In #: 8004518679
Uruguay Dial-In #: 00040190315
Venezuela Dial-In #: 08001627182
10 years, 5 months
gluster verbs are broken due to missing updateTimestamp()
by barumuga@redhat.com
Hi,
I see vdsm master is broken wrt gluster verbs. When I run any gluster verbs, it errors out
Traceback (most recent call last):
File "/usr/share/vdsm/BindingXMLRPC.py", line 941, in wrapper
f.im_self.updateTimestamp()
AttributeError: 'GlusterApi' object has no attribute 'updateTimestamp'
I added a dummy updateTimestamp() in gluster.api.GlusterApi which resolves the issue, but I am not sure whether its correct or not.
Could you provide some info on updateTimestamp() and whether its applicable to gluster module?
Regards,
Bala
10 years, 5 months
before_device_migrate_source not being called after http://gerrit.ovirt.org/#/c/14203/
by amuller@redhat.com
While reviewing some unrelated issue I noticed that before_device_migrate_source is no longer
being called. This would be an oVirt 3.3 regression for hook users. If we could fix this by
3.3 downstream release it'd be a win as well. Vinzenz are you available to fix this in time?
If not please alert early and I'll help out.
Assaf Muller, Cloud Networking Engineer
Red Hat
10 years, 5 months
what does custom option mean when vmcreate ?
by bigclouds
the paramters received when vmCreate has a long part called custom,
do we use custom infomation? what does the long key device_************************* means?
thanks
10 years, 5 months
why i can not live migrate windows which has virtio-device
by bigclouds
hi,all
this error is after launch libvirt's migration API. but this error is common.
a windows guest os which has virtio-device will fail to migration.
------log of that vm-----------
features 0x1e unsupported allowed features 0x71000002
qemu warning error while loading state for instance 0x0 of device '0000:00:04.4/virtio-console'
do you have some idea about that?
thanks
10 years, 5 months
fail to live migration, seem like a libvirt error
by bigclouds
hi,all
there are many channels like spicevmc,unix,vdsm-agent, if that devices impact live migration?
from following erroe message, i have no idea where is the root cause?
please take a look at it.
thanks
Thread-107294::DEBUG::2013-12-26 09:25:24,544::libvirtvm::358::vm.Vm::(cancel) vmId=`5819a89c-7e24-4f5a-8d42-24bfba3a39bf`::canceling migration downtime thread
Thread-107294::DEBUG::2013-12-26 09:25:24,545::libvirtvm::417::vm.Vm::(stop) vmId=`5819a89c-7e24-4f5a-8d42-24bfba3a39bf`::stopping migration monitor thread
Thread-107312::DEBUG::2013-12-26 09:25:24,545::libvirtvm::355::vm.Vm::(run) vmId=`5819a89c-7e24-4f5a-8d42-24bfba3a39bf`::migration downtime thread exiting
Thread-107294::ERROR::2013-12-26 09:25:24,546::vm::196::vm.Vm::(_recover) vmId=`5819a89c-7e24-4f5a-8d42-24bfba3a39bf`::Failed to acquire lock: No such process
Thread-107300::DEBUG::2013-12-26 09:25:24,546::vm::261::vm.Vm::(run) vmId=`43774d10-f550-42f6-81da-6a117df5135e`::migration semaphore acquired
Thread-107294::ERROR::2013-12-26 09:25:24,690::vm::284::vm.Vm::(run) vmId=`5819a89c-7e24-4f5a-8d42-24bfba3a39bf`::Failed to migrate
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 269, in run
self._startUnderlyingMigration()
File "/usr/share/vdsm/libvirtvm.py", line 482, in _startUnderlyingMigration
None, maxBandwidth)
File "/usr/share/vdsm/libvirtvm.py", line 518, in f
ret = attr(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 87, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1178, in migrateToURI2
if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self)
libvirtError: Failed to acquire lock: No such process
Thread-107300::DEBUG::2013-12-26 09:25:24,709::libvirtvm::457::vm.Vm::(_startUnderlyingMigration) vmId=`43774d10-f550-42f6-81da-6a117df5135e`::starting migration to qemu+tls://testserver1.com/system
Thread-107327::DEBUG::2013-12-26 09:25:24,709::libvirtvm::343::vm.Vm::(run) vmId=`43774d10-f550-42f6-81da-6a117df5135e`::migration downtime thread started
Thread-107328::DEBUG::2013-12-26 09:25:24,709::libvirtvm::379::vm.Vm::(run) vmId=`43774d10-f550-42f6-81da-6a117df5135e`::starting migration monitor thread
libvirtEventLoop::DEBUG::2013-12-26 09:25:25,250::libvirtvm::2860::vm.Vm::(_onLibvirtLifecycleEvent) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::event Resumed detail 0 opaque None
libvirtEventLoop::DEBUG::2013-12-26 09:25:25,307::libvirtvm::2860::vm.Vm::(_onLibvirtLifecycleEvent) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::event Resumed detail 1 opaque None
Thread-107296::DEBUG::2013-12-26 09:25:25,331::libvirtvm::358::vm.Vm::(cancel) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::canceling migration downtime thread
Thread-107296::DEBUG::2013-12-26 09:25:25,332::libvirtvm::417::vm.Vm::(stop) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::stopping migration monitor thread
Thread-107296::ERROR::2013-12-26 09:25:25,332::vm::196::vm.Vm::(_recover) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::Domain not found: no domain with matching name 'testZhuomian-1'
Thread-107314::DEBUG::2013-12-26 09:25:25,332::libvirtvm::355::vm.Vm::(run) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::migration downtime thread exiting
Thread-107296::ERROR::2013-12-26 09:25:25,394::vm::284::vm.Vm::(run) vmId=`bdc42fa3-91f0-48d7-b7ed-4908bb86e262`::Failed to migrate
Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 269, in run
self._startUnderlyingMigration()
File "/usr/share/vdsm/libvirtvm.py", line 482, in _startUnderlyingMigration
None, maxBandwidth)
File "/usr/share/vdsm/libvirtvm.py", line 518, in f
ret = attr(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 87, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1178, in migrateToURI2
if ret == -1: raise libvirtError ('virDomainMigrateToURI2() failed', dom=self)
libvirtError: Domain not found: no domain with matching name 'testZhuomian-1'
10 years, 5 months