[vdsm] configNetwork issue
Hi,
I'm trying to create a bridge adding as config bootproto='dhcp'
but I've the following error:
import sys
sys.path.append('/usr/share/vdsm/')
import configNetwork
configNetwork.addNetwork(network='engine', nics=['em1'],
bootproto='dhcp')
TypeError: objectivizeNetwork() got multiple values for keyword argument
'bootproto'
seems like objectivizeNetwork already take bootproto from **opts and fails.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] configNetwork issue
Il 06/06/2013 16:29, Alon Bar-Lev ha scritto:
/usr/share/vdsm/addNetwork', 'ovirtmgmt', '', '', u'eth0', 'BOOTPROTO=dhcp',
'ONBOOT=yes', 'blockingdhcp=true']
# /usr/share/vdsm/addNetwork ovirtmgmt '' '' em1 BOOTPROTO=dhcp
ONBOOT=yes blockingdhcp=true
WARNING:root:options BOOTPROTO is deprecated. Use bootproto instead
WARNING:root:options ONBOOT is deprecated. Use onboot instead
INFO:root:Adding network ovirtmgmt with vlan=, bonding=, nics=['em1'],
bondingOptions=None, mtu=None, bridged=True, options={'bootproto':
'dhcp', 'blockingdhcp': 'true', 'onboot': 'yes'}
Traceback (most recent call last):
File /usr/lib64/python2.7/runpy.py, line 162, in _run_module_as_main
__main__, fname, loader, pkg_name)
File /usr/lib64/python2.7/runpy.py, line 72, in _run_code
exec code in run_globals
File /usr/share/vdsm/configNetwork.py, line 664, in module
main()
File /usr/share/vdsm/configNetwork.py, line 633, in main
addNetwork(bridge, **kwargs)
File /usr/share/vdsm/configNetwork.py, line 198, in addNetwork
configurator, **options)
TypeError: objectivizeNetwork() got multiple values for keyword argument
'bootproto'
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] configNetwork issue
Il 06/06/2013 17:10, Giuseppe Vallarelli ha scritto:
- Original Message -
| From: Sandro Bonazzola sbona...@redhat.com
| To: Alon Bar-Lev alo...@redhat.com
| Cc: vdsm-devel@lists.fedorahosted.org
| Sent: Thursday, June 6, 2013 4:38:41 PM
| Subject: Re: [vdsm] configNetwork issue
|
| Il 06/06/2013 16:29, Alon Bar-Lev ha scritto:
| /usr/share/vdsm/addNetwork', 'ovirtmgmt', '', '', u'eth0',
| 'BOOTPROTO=dhcp', 'ONBOOT=yes', 'blockingdhcp=true']
|
| # /usr/share/vdsm/addNetwork ovirtmgmt '' '' em1 BOOTPROTO=dhcp
| ONBOOT=yes blockingdhcp=true
| WARNING:root:options BOOTPROTO is deprecated. Use bootproto instead
| WARNING:root:options ONBOOT is deprecated. Use onboot instead
| INFO:root:Adding network ovirtmgmt with vlan=, bonding=, nics=['em1'],
| bondingOptions=None, mtu=None, bridged=True, options={'bootproto':
| 'dhcp', 'blockingdhcp': 'true', 'onboot': 'yes'}
| Traceback (most recent call last):
| File /usr/lib64/python2.7/runpy.py, line 162, in _run_module_as_main
| __main__, fname, loader, pkg_name)
| File /usr/lib64/python2.7/runpy.py, line 72, in _run_code
| exec code in run_globals
| File /usr/share/vdsm/configNetwork.py, line 664, in module
| main()
| File /usr/share/vdsm/configNetwork.py, line 633, in main
| addNetwork(bridge, **kwargs)
| File /usr/share/vdsm/configNetwork.py, line 198, in addNetwork
| configurator, **options)
| TypeError: objectivizeNetwork() got multiple values for keyword argument
| 'bootproto'
Hi Sandro, a very dirty and quick fix may be the following one.
Inside configNetwork reach the addNetwork function and
before the call to objectivizeNetwork:
bootproto =options.get('bootproto')
if bootproto:
del options['bootproto']
netEnt = objectivizeNetwork(network if bridged else None, vlan, bonding,
bondingOptions, nics, mtu, ipaddr, netmask,
gateway, bootproto, _netinfo,
configurator, **options)
Giuseppe
Thanks Giuseppe, that seems to fix the issue also if I don't really like
using del as solution.
This however is a workaround that fix it for me.
|
| --
| Sandro Bonazzola
| Better technology. Faster innovation. Powered by community collaboration.
| See how it works at redhat.com
|
| ___
| vdsm-devel mailing list
| vdsm-devel@lists.fedorahosted.org
| https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
|
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] issue while creating data domain over NFS
-center/1fa7166d-ca70-4c02-acec-bd888aa8e5f9/mastersd/master/tasks/5ee704f3-4834-4413-8e5b-9e22852fac5b.temp
5ee704f3-4834-4413-8e5b-9e22852fac5b::DEBUG::2013-06-07
09:49:31,268::task::736::TaskManager.Task::(_save)
Task=`5ee704f3-4834-4413-8e5b-9e22852fac5b`::_save: orig
/rhev/data-center/1fa7166d-ca70-4c02-acec-bd888aa8e5f9/mastersd/master/tasks/5ee704f3-4834-4413-8e5b-9e22852fac5b
temp
/rhev/data-center/1fa7166d-ca70-4c02-acec-bd888aa8e5f9/mastersd/master/tasks/5ee704f3-4834-4413-8e5b-9e22852fac5b.temp
5ee704f3-4834-4413-8e5b-9e22852fac5b::INFO::2013-06-07
09:49:31,573::fileVolume::154::Storage.Volume::(_create) Request to
create RAW volume
/rhev/data-center/1fa7166d-ca70-4c02-acec-bd888aa8e5f9/5569b4ce-c43b-434e-b0d2-7066a6e9489a/images/2fdbf1be-f028-492c-8741-a46789f8660a/316faf9c-1780-4820-85bf-c886c3894a09
with size = 41943040 sectors
Thread-263::DEBUG::2013-06-07
09:49:44,063::fileSD::238::Storage.Misc.excCmd::(getReadDelay)
'/usr/bin/dd iflag=direct
if=/rhev/data-center/mnt/192.168.1.104:_var_lib_images2/5569b4ce-c43b-434e-b0d2-7066a6e9489a/dom_md/metadata
bs=4096 count=1' (cwd None)
Thread-263::DEBUG::2013-06-07
09:49:44,068::fileSD::238::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
err = '0+1 records in\n0+1 records out\n479 bytes (479 B) copied,
5.6832e-05 s, 8.4 MB/s\n'; rc = 0
Thread-263::ERROR::2013-06-07
09:49:44,069::misc::240::Storage.Misc::(readspeed) Unable to parse dd
output: '479 bytes (479 B) copied, 5.6832e-05 s, 8.4 MB/s'
Thread-263::ERROR::2013-06-07
09:49:44,069::domainMonitor::225::Storage.DomainMonitorThread::(_monitorDomain)
Error while collecting domain 5569b4ce-c43b-434e-b0d2-7066a6e9489a
monitoring information
Traceback (most recent call last):
File /usr/share/vdsm/storage/domainMonitor.py, line 203, in
_monitorDomain
self.nextStatus.readDelay = self.domain.getReadDelay()
File /usr/share/vdsm/storage/fileSD.py, line 238, in getReadDelay
stats = misc.readspeed(self.metafile, 4096)
File /usr/share/vdsm/storage/misc.py, line 241, in readspeed
raise se.MiscFileReadException(path)
MiscFileReadException: Internal file read failure:
('/rhev/data-center/mnt/192.168.1.104:_var_lib_images2/5569b4ce-c43b-434e-b0d2-7066a6e9489a/dom_md/metadata',)
Thread-263::DEBUG::2013-06-07
09:49:44,069::domainMonitor::233::Storage.DomainMonitorThread::(_monitorDomain)
Domain 5569b4ce-c43b-434e-b0d2-7066a6e9489a changed its status to Invalid
Thread-274::DEBUG::2013-06-07
09:49:44,070::misc::925::Event.Storage.DomainMonitor.onDomainConnectivityStateChange::(_emit)
Emitting event
Thread-274::DEBUG::2013-06-07
09:49:44,070::misc::935::Event.Storage.DomainMonitor.onDomainConnectivityStateChange::(_emit)
Calling registered method `_upgradePoolDomain`
Thread-274::DEBUG::2013-06-07
09:49:44,071::misc::945::Event.Storage.DomainMonitor.onDomainConnectivityStateChange::(_emit)
Event emitted
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] delNetwork issue
After having created the engine bridge, trying to remove it leads to:
# /usr/share/vdsm/delNetwork engine '' '' em1
INFO:root:Removing network engine with vlan=None, bonding=None,
nics=['em1'],options={}
Traceback (most recent call last):
File /usr/share/vdsm/configNetwork.py, line 666, in module
main()
File /usr/share/vdsm/configNetwork.py, line 641, in main
delNetwork(bridge, **kwargs)
File /usr/share/vdsm/configNetwork.py, line 355, in delNetwork
_removeUnusedNics(network, vlan, bonding, nics, configWriter)
File /usr/share/vdsm/configNetwork.py, line 259, in _removeUnusedNics
ifup(nic)
File /usr/share/vdsm/netconf/ifcfg.py, line 739, in ifup
rc, out, err = _ifup(iface)
File /usr/share/vdsm/netconf/ifcfg.py, line 728, in _ifup
out[-1] if out else '')
ConfigNetworkError: (29, '')
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] issue while creating data domain over NFS
Il 07/06/2013 10:05, Federico Simoncelli ha scritto:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: vdsm-devel@lists.fedorahosted.org
Cc: Federico Simoncelli fsimo...@redhat.com, Alex Lourie
alou...@redhat.com, Moran Goldboim
mgold...@redhat.com
Sent: Friday, June 7, 2013 9:58:46 AM
Subject: issue while creating data domain over NFS
Hi here is the relevant log in vdsm.log: vdsm is taken from master,
commit 419cafb
09:49:44,068::fileSD::238::Storage.Misc.excCmd::(getReadDelay) SUCCESS:
err = '0+1 records in\n0+1 records out\n479 bytes (479 B) copied,
5.6832e-05 s, 8.4 MB/s\n'; rc = 0
Thread-263::ERROR::2013-06-07
09:49:44,069::misc::240::Storage.Misc::(readspeed) Unable to parse dd
output: '479 bytes (479 B) copied, 5.6832e-05 s, 8.4 MB/s'
My bad this is an issue I introduced recently. I didn't know that dd could
output such a human-friendly string. I thought I got it all covered, but I
didn't take in consideration the exponential notation (and your super-fast
storage domain :)
5.6832e-05
Thread-263::ERROR::2013-06-07
09:49:44,069::domainMonitor::225::Storage.DomainMonitorThread::(_monitorDomain)
Error while collecting domain 5569b4ce-c43b-434e-b0d2-7066a6e9489a
monitoring information
Traceback (most recent call last):
File /usr/share/vdsm/storage/domainMonitor.py, line 203, in
_monitorDomain
self.nextStatus.readDelay = self.domain.getReadDelay()
File /usr/share/vdsm/storage/fileSD.py, line 238, in getReadDelay
stats = misc.readspeed(self.metafile, 4096)
File /usr/share/vdsm/storage/misc.py, line 241, in readspeed
raise se.MiscFileReadException(path)
MiscFileReadException: Internal file read failure:
('/rhev/data-center/mnt/192.168.1.104:_var_lib_images2/5569b4ce-c43b-434e-b0d2-7066a6e9489a/dom_md/metadata',)
I'll get it fixed soon.
Thanks!
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] bridge name in vdsClient conf file
Hi, Is there a way for specify a bridge name in a vm.conf file to be used by vdsClient create command? defaults is engine and I would like to specify ovirtmgmt. Thanks -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Ovirt live build failure
Il 12/06/2013 09:30, Ohad Basan ha scritto: Hello everyone. The jenkins ovirt live job is failing due to libvirt dependency: Error creating Live CD : Failed to build transaction : vdsm-4.11.0-28.git634b9f4.fc18.x86_64 requires libvirt = 1.0.2-1 http://jenkins.ovirt.org/job/ovirt_live_create_iso/151/artifact/ovirt-live-1.0.0-0.1.master.20130611.gitc7da94a.log Does anyone have an idea how to solve it? the only thing I thought about is compiling libvirt from source in the job itself. Thanks Ohad ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel I can see 2 solutions: add libvirt = 1.0.2 to f18 nightly repo (that would be great) or rebuild for fedora 18 the latest libvirt .src.rpm from ftp://libvirt.org/libvirt/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] boot order in vm.conf
Hi, This is my vm.conf: vmId=f785ebfd-a9dc-4453-be0e-ae7e57a804b0 memSize=4096 macAddr=00:16:3e:71:bb:e5 display=vnc drive=pool:63570f35-35b9-4f82-aea5-7a34535a670d,domain:77a192ce-175e-4085-bd1f-342e4993b802,image:279076a8-a888-4ac2-8b40-b72fd488c173,volume:bf24cc76-ada5-428a-8ded-0662d08fe5d5 cdrom=/Fedora-18-x86_64-DVD.iso boot=d vmName=oVirt Hosted Engine spiceSecureChannels=_main,_display,_inputs,_cursor,_playback,_record,_smartcard,_usbredir bridge=ovirtmgmt nicModel=virtio I create the vm calling vdsClient create. After Fedora installation I need to boot from HD instead of cdrom. How may I specify the boot order for having it as hd,cdrom booting from hd on reboot? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Fwd: Re: [libvirt] AttributeError in virConnect.__del__ at program exit
FYI Messaggio originale Oggetto:Re: [libvirt] AttributeError in virConnect.__del__ at program exit Data: Thu, 13 Jun 2013 09:10:13 +0200 Mittente: Sandro Bonazzola sbona...@redhat.com A: Cole Robinson crobi...@redhat.com CC: libvir-l...@redhat.com Il 13/06/2013 08:54, Sandro Bonazzola ha scritto: Il 12/06/2013 19:31, Cole Robinson ha scritto: On 06/12/2013 04:10 AM, Sandro Bonazzola wrote: Il 11/06/2013 18:21, Cole Robinson ha scritto: On 06/11/2013 07:58 AM, Sandro Bonazzola wrote: Hi, using vdsm python code, I've the following error at program exit that seems to be related to libvirt python code, something wrong in a destructor: Exception AttributeError: AttributeError(virConnect instance has no attribute 'domainEventCallbacks',) in bound method virConnect.__del__ of libvirt.virConnect instance at 0x4280f38 ignored I'm using libvirt 1.0.6 Is it a known issue? Is there any workaround / fix ? I've seen this too, sometimes via the virtinst test suite. Once upon a time I tracked it down to whether the virtinst code did 'import selinux' or not, so maybe it's a just some weird race, or a side effect of something other libraries do in their cleanup path. By inspection alone the __del__ handler doesn't seem to be doing anything wrong. - Cole It seems related only to domainEventCallbacks so maybe it appears only after a domain creation / modification. Oh, sorry, now that I look at the code it makes a bit more sense. The error I was recalling was a __del__ Exception but wasn't involving domain events. But I still don't see why __del__ is complaining, since the whole thing is wrapped in try: ... except AttributeError. So not sure what the issue is. - Cole According to the python documentation, you can't handle exception in __del__: http://docs.python.org/2/reference/datamodel.html#object.__del__ Warning Due to the precarious circumstances under which __del__() http://docs.python.org/2/reference/datamodel.html#object.__del__ methods are invoked, exceptions that occur during their execution are ignored, and a warning is printed to sys.stderr instead. So you have to test the existence of the attribute before using it and not try to use it and try to handle an exception that can't be handled. You can use hasattr for checking if the object has the needed attribute. -- libvir-list mailing list libvir-l...@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- libvir-list mailing list libvir-l...@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] boot order in vm.conf
Il 13/06/2013 09:06, Sandro Bonazzola ha scritto:
Hi,
This is my vm.conf:
vmId=f785ebfd-a9dc-4453-be0e-ae7e57a804b0
memSize=4096
macAddr=00:16:3e:71:bb:e5
display=vnc
drive=pool:63570f35-35b9-4f82-aea5-7a34535a670d,domain:77a192ce-175e-4085-bd1f-342e4993b802,image:279076a8-a888-4ac2-8b40-b72fd488c173,volume:bf24cc76-ada5-428a-8ded-0662d08fe5d5
cdrom=/Fedora-18-x86_64-DVD.iso
boot=d
vmName=oVirt Hosted Engine
spiceSecureChannels=smain,sdisplay,sinputs,scursor,splayback,srecord,ssmartcard,susbredir
bridge=ovirtmgmt
nicModel=virtio
I create the vm calling vdsClient create.
After Fedora installation I need to boot from HD instead of cdrom.
How may I specify the boot order for having it as hd,cdrom booting from
hd on reboot?
drive=pool:63570f35-35b9-4f82-aea5-7a34535a670d,domain:77a192ce-175e-4085-bd1f-342e4993b802,image:279076a8-a888-4ac2-8b40-b72fd488c173,volume:bf24cc76-ada5-428a-8ded-0662d08fe5d5,bootOrder:1
seems to work for setting the HD as first device. However using this introduce
a conflict on boot=d, boot option can't be used. cdrom also seems that can't be
used if I specify the cdrom device. However, I'm not able to create a valid
cdrom device:
I'm trying with:
devices={deviceType:disk,type:disk,device:cdrom,readonly:true,bootOrder:2,alias:cdrom0,iface=ide'}
and I've:
Bad volume specification {'index': '0', 'iface': ide', 'bootOrder': '2',
'alias': 'cdrom0', 'readonly': 'true', 'deviceType': 'disk', 'device': 'cdrom',
'type': 'disk'}
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [libvirt] qemu64 - not valid cpu with 'Intel Westmere Family'
Il 03/07/2013 16:40, Sandro Bonazzola ha scritto:
Hi,
I'm trying to run latest vdsm master on RHEL-6.4.
I've built the rpms against livirt-1.10
I'm creating a VM using cpu family = 'Intel Westmere Family'
cpu match=exact
modelqemu64/model
feature name=svm policy=disable/
/cpu
Thread-40::DEBUG::2013-07-03
15:47:47,150::libvirtconnection::136::vds::(wrapper) Unknown
libvirterror: ecode: 1 edom: 31 level: 2 message: internal error Cannot
find suitable CPU model for given data
Thread-40::DEBUG::2013-07-03
15:47:47,150::vm::2003::vm.Vm::(_startUnderlyingVm)
vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::_ongoingCreations released
Thread-40::ERROR::2013-07-03
15:47:47,150::vm::2029::vm.Vm::(_startUnderlyingVm)
vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 1989, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/vm.py, line 2862, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py,
line 112, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.6/site-packages/libvirt.py, line 2848, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error Cannot find suitable CPU model for given data
Is it required a more updated qemu? Is it a vdsm or a livirt bug?
It seems that qemu knows qemu64 as cpu
# /usr/libexec/qemu-kvm --cpu ?
x86 Opteron_G5 AMD Opteron 63xx class CPU
x86 Opteron_G4 AMD Opteron 62xx class CPU
x86 Opteron_G3 AMD Opteron 23xx (Gen 3 Class Opteron)
x86 Opteron_G2 AMD Opteron 22xx (Gen 2 Class Opteron)
x86 Opteron_G1 AMD Opteron 240 (Gen 1 Class Opteron)
x86 Haswell Intel Core Processor (Haswell)
x86 SandyBridge Intel Xeon E312xx (Sandy Bridge)
x86 Westmere Westmere E56xx/L56xx/X56xx (Nehalem-C)
x86 Nehalem Intel Core i7 9xx (Nehalem Class Core i7)
x86 Penryn Intel Core 2 Duo P9xxx (Penryn Class Core 2)
x86 Conroe Intel Celeron_4x0 (Conroe/Merom Class Core 2)
x86 cpu64-rhel5 QEMU Virtual CPU version (cpu64-rhel5)
x86 cpu64-rhel6 QEMU Virtual CPU version (cpu64-rhel6)
x86 n270 Intel(R) Atom(TM) CPU N270 @ 1.60GHz
x86 athlon QEMU Virtual CPU version 0.12.1
x86 pentium3
x86 pentium2
x86 pentium
x86 486
x86 coreduo Genuine Intel(R) CPU T2600 @ 2.16GHz
x86 qemu32 QEMU Virtual CPU version 0.12.1
x86kvm64 Common KVM processor
x86 core2duo Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz
x86 phenom AMD Phenom(tm) 9550 Quad-Core Processor
x86 qemu64 QEMU Virtual CPU version 0.12.1
libvirt-1.1.0-1.el6.x86_64
libvirt-client-1.1.0-1.el6.x86_64
libvirt-daemon-1.1.0-1.el6.x86_64
libvirt-daemon-config-network-1.1.0-1.el6.x86_64
libvirt-daemon-config-nwfilter-1.1.0-1.el6.x86_64
libvirt-daemon-driver-interface-1.1.0-1.el6.x86_64
libvirt-daemon-driver-lxc-1.1.0-1.el6.x86_64
libvirt-daemon-driver-network-1.1.0-1.el6.x86_64
libvirt-daemon-driver-nodedev-1.1.0-1.el6.x86_64
libvirt-daemon-driver-nwfilter-1.1.0-1.el6.x86_64
libvirt-daemon-driver-qemu-1.1.0-1.el6.x86_64
libvirt-daemon-driver-secret-1.1.0-1.el6.x86_64
libvirt-daemon-driver-storage-1.1.0-1.el6.x86_64
libvirt-daemon-kvm-1.1.0-1.el6.x86_64
libvirt-daemon-lxc-1.1.0-1.el6.x86_64
libvirt-debuginfo-1.1.0-1.el6.x86_64
libvirt-devel-1.1.0-1.el6.x86_64
libvirt-docs-1.1.0-1.el6.x86_64
libvirt-lock-sanlock-1.1.0-1.el6.x86_64
libvirt-python-1.1.0-1.el6.x86_64
qemu-img-0.12.1.2-2.355.el6_4.5.x86_64
qemu-kvm-0.12.1.2-2.355.el6_4.5.x86_64
vdsm-4.11.0-84.gitc4e3dd0.el6.x86_64
vdsm-cli-4.11.0-84.gitc4e3dd0.el6.noarch
vdsm-gluster-4.11.0-84.gitc4e3dd0.el6.noarch
vdsm-python-4.11.0-84.gitc4e3dd0.el6.x86_64
vdsm-python-cpopen-4.11.0-84.gitc4e3dd0.el6.x86_64
vdsm-xmlrpc-4.11.0-84.gitc4e3dd0.el6.noarch
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [libvirt] qemu64 - not valid cpu with 'Intel Westmere Family'
Il 03/07/2013 18:28, Dan Kenigsberg ha scritto:
On Wed, Jul 03, 2013 at 04:51:30PM +0200, Sandro Bonazzola wrote:
Il 03/07/2013 16:40, Sandro Bonazzola ha scritto:
Hi,
I'm trying to run latest vdsm master on RHEL-6.4.
I've built the rpms against livirt-1.10
I'm creating a VM using cpu family = 'Intel Westmere Family'
cpu match=exact
modelqemu64/model
feature name=svm policy=disable/
/cpu
Thread-40::DEBUG::2013-07-03
15:47:47,150::libvirtconnection::136::vds::(wrapper) Unknown
libvirterror: ecode: 1 edom: 31 level: 2 message: internal error Cannot
find suitable CPU model for given data
Thread-40::DEBUG::2013-07-03
15:47:47,150::vm::2003::vm.Vm::(_startUnderlyingVm)
vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::_ongoingCreations released
Thread-40::ERROR::2013-07-03
15:47:47,150::vm::2029::vm.Vm::(_startUnderlyingVm)
vmId=`9deae1fb-e0c5-4362-8f3c-657f39893b8b`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 1989, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/vm.py, line 2862, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py,
line 112, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.6/site-packages/libvirt.py, line 2848, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: internal error Cannot find suitable CPU model for given data
Is it required a more updated qemu? Is it a vdsm or a livirt bug?
It seems that qemu knows qemu64 as cpu
# /usr/libexec/qemu-kvm --cpu ?
And what does `virsh -r capabilities` report?
# virsh -r capabilities
capabilities
host
uuid3f8f4b81-f54b-4e49-8fe1-a55618c9c5f6/uuid
cpu
archx86_64/arch
modelSandyBridge/model
vendorIntel/vendor
topology sockets='1' cores='4' threads='2'/
feature name='erms'/
feature name='smep'/
feature name='fsgsbase'/
feature name='rdrand'/
feature name='f16c'/
feature name='osxsave'/
feature name='pcid'/
feature name='pdcm'/
feature name='xtpr'/
feature name='tm2'/
feature name='est'/
feature name='smx'/
feature name='vmx'/
feature name='ds_cpl'/
feature name='monitor'/
feature name='dtes64'/
feature name='pbe'/
feature name='tm'/
feature name='ht'/
feature name='ss'/
feature name='acpi'/
feature name='ds'/
feature name='vme'/
/cpu
power_management
suspend_mem/
suspend_disk/
/power_management
migration_features
live/
uri_transports
uri_transporttcp/uri_transport
/uri_transports
/migration_features
topology
cells num='1'
cell id='0'
memory unit='KiB'16661036/memory
cpus num='8'
cpu id='0' socket_id='0' core_id='0' siblings='0,4'/
cpu id='1' socket_id='0' core_id='1' siblings='1,5'/
cpu id='2' socket_id='0' core_id='2' siblings='2,6'/
cpu id='3' socket_id='0' core_id='3' siblings='3,7'/
cpu id='4' socket_id='0' core_id='0' siblings='0,4'/
cpu id='5' socket_id='0' core_id='1' siblings='1,5'/
cpu id='6' socket_id='0' core_id='2' siblings='2,6'/
cpu id='7' socket_id='0' core_id='3' siblings='3,7'/
/cpus
/cell
/cells
/topology
secmodel
modelselinux/model
doi0/doi
/secmodel
secmodel
modeldac/model
doi0/doi
/secmodel
/host
guest
os_typehvm/os_type
arch name='i686'
wordsize32/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
/domain
/arch
features
cpuselection/
deviceboot/
acpi default='on' toggle='yes'/
apic default='on' toggle='no'/
pae/
nonpae/
/features
/guest
guest
os_typehvm/os_type
arch name='x86_64'
wordsize64/wordsize
emulator/usr/libexec/qemu-kvm/emulator
machinerhel6.4.0/machine
machine canonical='rhel6.4.0'pc/machine
machinerhel6.3.0/machine
machinerhel6.2.0/machine
machinerhel6.1.0/machine
machinerhel6.0.0/machine
machinerhel5.5.0/machine
machinerhel5.4.4/machine
machinerhel5.4.0/machine
domain type='qemu'
/domain
domain type='kvm'
emulator/usr/libexec/qemu-kvm/emulator
/domain
/arch
features
cpuselection/
deviceboot/
acpi default='on' toggle='yes
[vdsm] /etc/logrotate.d/libvirtd duplicate log entry
From cron daemon:
Date: Fri, 5 Jul 2013 13:40:01 +0200
From: Cron Daemon r...@dellserver.home
To: r...@dellserver.home
Subject: Cron root@dellserver /usr/sbin/logrotate
/etc/logrotate.d/libvirtd
error: /etc/logrotate.d/libvirtd:13 duplicate log entry for
/var/log/libvirt/libvirtd.log
/etc/logrotate.d/libvirtd content:
8--8
# vdsm
/var/log/libvirt/libvirtd.log {
rotate 100
missingok
copytruncate
size 15M
compress
compresscmd /usr/bin/xz
uncompresscmd /usr/bin/unxz
compressext .xz
}
# end vdsm
/var/log/libvirt/libvirtd.log {
weekly
missingok
rotate 4
compress
delaycompress
copytruncate
minsize 100k
}
8--8
libvirt-daemon-1.1.0-1.fc18.x86_64
vdsm-4.11.0-95.git003cd7a.fc18.x86_64
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Error while rebooting VM
', 'txRate': '0.0', 'rxRate':
'0.0', 'txErrors': '0', 'state': 'unknown', 'speed': '1000', 'name':
'vnet0'}}
displayType = qxl
cpuUser = 0.69
boot = d
elapsedTime = 3400
vmType = kvm
cpuSys = 0.13
appsList = []
hash = -6106157858121768929
pid = 26846
displayIp = 0
cdrom = /home/Fedora-19-x86_64-DVD.iso
guestIPs =
kvmEnable = true
disks = {'hdc': {'readLatency': '0', 'apparentsize': '0',
'writeLatency': '0', 'flushLatency': '0', 'readRate': '0.00',
'truesize': '0', 'writeRate': '0.00'}, 'hda': {'readLatency': '0',
'apparentsize': '26843545600', 'writeLatency': '0', 'imageID':
'9ac2ea13-1de5-4a60-83c5-8700a23203b7', 'flushLatency': '0', 'readRate':
'0.00', 'truesize': '1594064896', 'writeRate': '0.00'}}
monitorResponse = -1
statsAge = 559.96
clientIp = 127.0.0.1
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Error while rebooting VM
Pushed a patch for the issue here: http://gerrit.ovirt.org/#/c/17599/ Now I see the following traceback in the logs: Traceback (most recent call last): File /usr/share/vdsm/clientIF.py, line 382, in teardownVolumePath res = self.irs.teardownImage(drive['domainID'], File /usr/share/vdsm/vm.py, line 1343, in __getitem__ raise KeyError(key) KeyError: 'domainID' Il 01/08/2013 14:10, Dan Kenigsberg ha scritto: On Thu, Aug 01, 2013 at 05:31:44AM -0400, Antoni Segura Puimedon wrote: Looking at clientIF.py on the patch Michal pointed to, concretely on: +def removeVmFromMonitoredDomains(self, vmId): +for dom in self.domainVmIds: +#only take lock here to allow runVm to take the lock in-between +with self.domainVmIdsLock: +try: +self.domainVmIds[dom].remove(vmId) +except ValueError: +pass +else: +if not self.domainVmIds[dom]: +del self.domainVmIds[dom] If there is no exception we will be deleting an element from a dictionary while iterating it. This is dangerous and should be avoided. The fastest alternative to implement would be that in the else we append dom to a list of domainsToRemove and after the iteration we get a lock and remove all of them. Alternatively, I believe we could do without maintaining the domain-vmId mapping. I did not understand why having each VM hold its domains is not enough. The said patch has another problem - a single SIGSTOPped qemu process can block all SPM operations (in case its storage domain has become active again and we attempt to cont the VM). Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] vdsClient networking (addNetwork with existing bond)
Hi, I'm trying to fix https://bugzilla.redhat.com/999577 which in short is failing to create bridge specifying a bond interface as nic using vdsClient. The failing command line is: '/usr/bin/vdsClient', '-s', 'localhost', 'addNetwork', 'bridge=rhevm', 'vlan=', 'bond=', 'nics=bond2', 'force=False', 'bridged=True', 'BOOTPROTO=dhcp', 'ONBOOT=yes', 'blockingdhcp=true' I suppose that 'nics=bond2' and 'bond=' are wrong. I'm searching for a man page or something like that for understanding how to prepare the command line without success. http://www.ovirt.org/VdsClient is outdated and says anything about networking. I've seen in http://www.ovirt.org/Vdsm_Network that using a bond should be supported but for the supported topologies there are no command line examples. For: bridge1 --- bond --- nic1 \ -- nic2 I suppose that the command line should have 'bond=bond' 'nics=nic1,nic2' is this right? If the bond already exists is it enough specifying 'bond=bond', 'nics=' ? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] VDSM sync meeting September 9th 2013
Il 10/09/2013 15:42, Eduardo Warszawski ha scritto: - Original Message - On Tue, Sep 10, 2013 at 09:55:57AM +0100, Dan Kenigsberg wrote: On Tue, Sep 10, 2013 at 08:34:42AM +0200, Sandro Bonazzola wrote: Il 09/09/2013 16:09, Dan Kenigsberg ha scritto: - Master branch is broken for EL6 since we've taken Id8e514df1ca88500f746242134ddb24c31588046 with its daemonAdapter Yaniv Bronheim is working with Zhou and Alon Bar Lev to mend this. Please review http://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic:error-handling-daemonAdapter,n,z - Another breakage of master is the libvirt requirement introduced by me in http://gerrit.ovirt.org/18937. libvirt-0.10.2-18.el6_4.10 is not yet public. Current workaround is to take a newer libvirt from virt-preview, or ignore this dependency (which makes you unable to re-wire networks for a running VM). - We now require gluster-3.4.0 which is not yet availabled from koji for EL6. That's why we ship it in http://resources.ovirt.org/releases/3.3/rpm/EL/6/x86_64/ However, it is missing from the nightly repos. Can we softlink to them from the nightly repo, Eyal? - Timothy reports that the gluster team is working on geo-replication. One of the patches under review is http://gerrit.ovirt.org/#/c/17766/ Have I missed something? Please report it as a response! Master branch is also broken for Fedora 18, missing selinux-policy-targeted = 3.12.1-71 Eduardo, this has been introduced by your one shot prepare http://gerrit.ovirt.org/4220 . Once Bug 1005950 - Current selinux policy prevents running a VM with volumes under /var/run/vdsm/storage is solved in Fedora 18, we should require the proper version of selinux in our spec. Untill then, Vdsm cannot work with and enforcing F18's selinux. https://bugzilla.redhat.com/show_bug.cgi?id=1005950#c2 is done and it's selinux-policy-3.11.1-103.fc18. Eduardo, Sandro, could you fix the spec? Sure. Up to now we waited only for f19 and RHEL. patch pushed: http://gerrit.ovirt.org/19061 However, note that the package for fedora 18 has not hit updates-testing yet. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Recent changes in vdsmd startup
Il 10/10/2013 15:32, Yaniv Bronheim ha scritto: Hey Everybody, FYI, Recently we merged a fix that changes the way vdsmd starts. Before that service vdsmd start command performed its main logic in addition to related services manipulation, as configure libvirt service and restart it for example. Now we are trying to avoid that and only alert the user if restart or other operations on related services are required. So now when you perform vdsmd start after clear installation you will see: ~$ sudo service vdsmd restart Shutting down vdsm daemon: vdsm watchdog stop [ OK ] vdsm: not running [FAILED] vdsm: Running run_final_hooks vdsm stop [ OK ] supervdsm start[ OK ] vdsm: Running run_init_hooks vdsm: Running gencerts hostname: Unknown host vdsm: Running check_libvirt_configure libvirt is not configured for vdsm yet Perform 'vdsm-tool libvirt-configure' before starting vdsmd vdsm: failed to execute check_libvirt_configure, error code 1 vdsm start [FAILED] This asks you to run vdsm-tool libvirt-configure After running it you should see: ~$ sudo vdsm-tool libvirt-configure Stopping libvirtd daemon: [ OK ] libvirt is not configured for vdsm yet Reconfiguration of libvirt is done. To start working with the new configuration, execute: 'vdsm-tool libvirt-configure-services-restart' This will manage restarting of the following services: libvirtd, supervdsmd After performing: 'vdsm-tool libvirt-configure-services-restart' you are ready to start vdsmd again as usual. All those vdsm-tool commands require root privileges, otherwise it'll alert and stop the operation. Over systemd the errors\output can be watched in /var/log/messages Hi, is this change targeted to oVirt 3.3.z? or is it targeted to 3.4.0? I think it will affect hosted-engine-setup and host-deploy for all-in-one setups at least. Thanks, Yaniv Bronhaim. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] daily oVirt 3.3.1 blocker status
Hi, The following blockers are still not fixed: VDSM: Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI Bug 1022975 - [vdsm] storage domain upgrade fails with attributeError Federico, Eduardo, can you provide an ETA for those? The following patches are targeted 3.3 and needs to be reviewed: http://gerrit.ovirt.org/#/q/branch:%255Eovirt*-3.3.*,n,z vdsm: support VIR_MIGRATE_ABORT_ON_ERRORPeter V. Saveliev vdsm ovirt-3.3 Oct 27 hsm: fix isoprefix KeyError for inactive domainsFederico Simoncelli vdsmovirt-3.3 Oct 20 +1 Read pool metadata once in StoragePool.getInfo()Federico Simoncelli vdsmovirt-3.3 Oct 15 Make hsm.getVolumesList() pool independent. Federico Simoncelli vdsm ovirt-3.3 Oct 15 Adding [start|stop]MonitoringDomain(). Federico Simoncelli vdsm ovirt-3.3 Oct 15 stats: return domain lockspace status Federico Simoncelli vdsm ovirt-3.3 Oct 15 Make getRepoStats() a hsm method. Federico Simoncelli vdsm ovirt-3.3 Oct 15 Fix getStorageDomainInfo() logic. Federico Simoncelli vdsm ovirt-3.3 Oct 15 vm: add the transient disk support Federico Simoncelli vdsm ovirt-3.3 Oct 15 please review them and merge ASAP the patches meant to be in 3.3.1. I'm not aware of other blockers. If you're aware of any other blocker, please add it to the tracker bug (Bug 1019391 - Tracker: oVirt 3.3.1 release) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] daily oVirt 3.3.1 blocker status
Il 31/10/2013 08:49, Sandro Bonazzola ha scritto: Hi, The following blockers are still not fixed: VDSM: Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI Bug 1022975 - [vdsm] storage domain upgrade fails with attributeError Federico, Eduardo, can you provide an ETA for those? Still not fixed with no ETA. I'm not aware of other blockers. If you're aware of any other blocker, please add it to the tracker bug (Bug 1019391 - Tracker: oVirt 3.3.1 release) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] daily oVirt 3.3.1 blocker status
Il 04/11/2013 10:26, Dan Kenigsberg ha scritto: On Mon, Nov 04, 2013 at 09:05:19AM +0100, Sandro Bonazzola wrote: Il 31/10/2013 08:49, Sandro Bonazzola ha scritto: Hi, The following blockers are still not fixed: VDSM: Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI Bug 1022975 - [vdsm] storage domain upgrade fails with attributeError Federico, Eduardo, can you provide an ETA for those? Still not fixed with no ETA. WWIW, Bug 1022975 is solved by http://gerrit.ovirt.org/20721; waiting only for a formal verification. patch merged and pushed to 3.3 branch http://gerrit.ovirt.org/#/c/20891/ the patch has been verified so it just need to be merged for closing Bug 1022975 - [vdsm] storage domain upgrade fails with attributeError I don't see any activity about Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI still no ETA for this? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [partially solved] Re: Host local_host running without virtualization hardware acceleration
Il 05/11/2013 09:08, Sandro Bonazzola ha scritto: Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it) Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore. I've found that: # modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license:GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool) # /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory looking at strace: open(/dev/kvm, O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) Any clue on what may be happened? I've found kvm_intel module not loaded. I've created a new conf file for loading it automatically at boot so I've solved on my system. However, what has been changed for not having it loaded automatically as it was done before? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [libvirt] Host local_host running without virtualization hardware acceleration
Il 05/11/2013 10:49, Martin Kletzander ha scritto: On Tue, Nov 05, 2013 at 09:08:33AM +0100, Sandro Bonazzola wrote: Hi, I had to reinstall ovirt yesterday and now it seems that it doesn't work anymore. I'm running nightly on Fedora 18. kernel-3.11.4-101.fc18.x86_64 sanlock-2.8-1.fc18.x86_64 libvirt-1.1.4-1.fc18.x86_64 qemu-1.5.1-1.fc18.x86_64 vdsm-4.13.0-93.gitea8c8f0.fc18.x86_64 ovirt-engine-3.4.0-0.2.master.20131104192919.git3b65870.fc18.noarch engine-setup with all-in-one detects hardware virtualization and allow me to configure the system. (it fails detecting engine health status due probably to recent changes in its URL, I'm already looking into it) Once added localhost to the engine, it has been moved to non operational mode saying I don't have virtualization hardware acceleration anymore. I've found that: # modinfo kvm filename: /lib/modules/3.11.4-101.fc18.x86_64/kernel/arch/x86/kvm/kvm.ko license:GPL author: Qumranet depends: intree: Y vermagic: 3.11.4-101.fc18.x86_64 SMP mod_unload parm: min_timer_period_us:uint parm: ignore_msrs:bool parm: tsc_tolerance_ppm:uint parm: allow_unsafe_assigned_interrupts:Enable device assignment on platforms without interrupt remapping support. (bool) This is good, but AFAIK this module is not what provides /dev/kvm. Depending on the processor you're using, try checking 'kvm_intel' or 'kvm_amd'. Also make sure both are loaded. I've found that, missing kvm_intel. # /usr/bin/qemu-kvm Could not access KVM kernel module: No such file or directory failed to initialize KVM: No such file or directory looking at strace: open(/dev/kvm, O_RDWR|O_CLOEXEC) = -1 ENOENT (No such file or directory) What does ls -lZ /dev/kvm tell you? it doesn't existed, now it's working again after modprobe kvm_intel Any clue on what may be happened? No idea, but I'm basing everything on the fact that it worked before the re-install, am I right? right. something was loading that module automatically before reinstall and now I needed to create a conf file for having it loaded. Martin -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] daily oVirt 3.3.1 blocker status
Hi, only one bloker remains to be fixed: Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI I don't see any activity about it. Can anybody join Eduardo for fixing it ASAP? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] /etc/sysctl.d/vdsm
Hi On Fedora 19 I can see /etc/sysctl.d/vdsm but it seems that it's not read because it should be /etc/sysctl.d/vdsm.conf ( see sysctl --system output ) Is that file really needed? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] /etc/sysctl.d/vdsm
Il 12/11/2013 09:36, Dan Kenigsberg ha scritto: On Tue, Nov 12, 2013 at 08:00:44AM +0100, Sandro Bonazzola wrote: Hi On Fedora 19 I can see /etc/sysctl.d/vdsm but it seems that it's not read because it should be /etc/sysctl.d/vdsm.conf ( see sysctl --system output ) Is that file really needed? It is, according to Bug 740887 - Tune dirty_ratio and dirty_background_ratio and it seems to have been broken by commit c737fa2 Replace configure_sysctl with /etc/sysctl.d/vdsm quite a long time ago. Douglas, Sandro, anyone: could you address this? It seems that this affects only Fedora since on RHEL and probably CentOS sysctl doesn't support --system and init just read everything in /etc/sysctl.d. So I'll open a bug against vdsm on oVirt and I'll push the fix for the renaming. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] /etc/sysctl.d/vdsm
Il 12/11/2013 10:39, Yaniv Bronheim ha scritto: If you already in the fix scope, i think this part should move to lib/vdsm/tool/configurator.py and we can call it from spec if required the administrator might use it to check configurations and set them So, can you take the bug? If it was just renaming the file I could have done that myself, but I've not enough time for changing the architecture of that solution and test it. - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Dan Kenigsberg dan...@redhat.com, dougsl...@redhat.com Cc: vdsm-devel vdsm-de...@fedorahosted.org Sent: Tuesday, November 12, 2013 11:33:24 AM Subject: Re: [vdsm] /etc/sysctl.d/vdsm Il 12/11/2013 09:36, Dan Kenigsberg ha scritto: On Tue, Nov 12, 2013 at 08:00:44AM +0100, Sandro Bonazzola wrote: Hi On Fedora 19 I can see /etc/sysctl.d/vdsm but it seems that it's not read because it should be /etc/sysctl.d/vdsm.conf ( see sysctl --system output ) Is that file really needed? It is, according to Bug 740887 - Tune dirty_ratio and dirty_background_ratio and it seems to have been broken by commit c737fa2 Replace configure_sysctl with /etc/sysctl.d/vdsm quite a long time ago. Douglas, Sandro, anyone: could you address this? It seems that this affects only Fedora since on RHEL and probably CentOS sysctl doesn't support --system and init just read everything in /etc/sysctl.d. So I'll open a bug against vdsm on oVirt and I'll push the fix for the renaming. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Engine-devel] daily oVirt 3.3.1 blocker status
Hi, Bug 1022961 - Running a VM from a gluster domain uses mount instead of gluster URI is not blocking anymore 3.3.1 release as decided in yesterday oVirt sync meeting. We have only one bug blocking 3.3.1 release: Bug 1029584 - create vm does not work with display protocol vnc and operating system linux patch is already in 3.3 branch and just need to be backported to 3.3.1 branch (now available again) so hopefully we can have the bug in modified state later today. Just after that, ovirt engine will be rebuilt. I'm not aware of other blockers. If you're aware of any other blocker, please add it to the tracker bug (Bug 1019391 - Tracker: oVirt 3.3.1 release) Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] oVirt 3.3.2 beta status
Hi, we're going to branch and build oVirt 3.3.2 beta on Nov 27th. A bug tracker is available at [1] and it shows only 2 bugs blocking the release: Bug 1029792 - VDSM does not report the qemu version in capabilities, if qemu-kvm-rhev is used Bug 1029885 - cloud-init testcase does not work in engine 3.3.1 The following is a list of the bugs still open with target 3.3.2 or 3.3: Whiteboard Bug ID Summary 991267 [RFE] Add TUI information to log file. infra 987982 When adding a host through the REST API, the error message says that rootPassword is required, but ... infra 1017267 Plaintext user passwords in async_tasks database infra 1020344 Power Managent with cisco_ucs problem infra 1009899 exportDbSchema scripts generates output file with wrong name infra 1029792 VDSM does not report the qemu version in capabilities, if qemu-kvm-rhev is used integration 1026933 pre-populate ISO domain with virtio-win ISO integration 1026930 Package virtio-win and put it in ovirt repositories integration 1030437 RFE: Configuration of email notifications integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password network 988002 [oVirt] [network] Add button shouldn't appear on specific network network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 906313 [oVirt-webadmin] [setupNetworks] No valid Operation for network_name and Unassigned Logical Networks panel network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1016118 async between masterVersion : can't connect to StoragePool storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Please set the target to 3.3.2 and add the bug to the tracker if you think that 3.3.2 should not be released without it fixed. Please also update the target to 3.3.3 or any next release for bugs that won't be in 3.3.2: it will ease gathering the blocking bugs for next releases. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. [1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.2 beta status
Hi, we're going to branch and build oVirt 3.3.2 beta TODAY. A bug tracker is available at [1] and it shows only 3 bugs still blocking the release: Whiteboard Bug ID Summary storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once virt1029885 cloud-init testcase does not work in engine 3.3.1 Please provide an ETA for the above bugs. The following is a list of the non-blocking bugs still open with target 3.3.2: Whiteboard Bug ID Summary infra 1017267 Plaintext user passwords in async_tasks database infra 987982 When adding a host through the REST API, the error message says that rootPassword is required,... infra 1020344 Power Managent with cisco_ucs problem integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 1019818 Support OpenStack Havana layer 2 agent integration network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 906313 [oVirt-webadmin] [setupNetworks] No valid Operation for network_name and Unassigned Logical Networks panel network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1016118 async between masterVersion : can't connect to StoragePool ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Please add the bugs to the tracker if you think that 3.3.2 should not be released without them fixed. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [3] http://www.ovirt.org/OVirt_3.3.2_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.2 RC status
Hi, we've scheduled oVirt 3.3.2 RC build on 2013-12-11 [1] A bug tracker is available at [2] and it shows only 4 bugs still blocking the release: Whiteboard Bug ID Summary integration 1036209 [AIO] ssh issues storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt1029885 cloud-init testcase does not work in engine 3.3.1 virt1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once Please provide an ETA for the above bugs. 1036209 [AIO] ssh issues: patch merged on master branch, ready to be merged (hopefully today) on 3.3 and 3.3.2 branches. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [3]. Thanks to all which have already started testing beta release! Maintainers should fill release notes before RC build, the page has been created here [4] [1] http://www.ovirt.org/OVirt_3.3.z_release-management [2] https://bugzilla.redhat.com/1027349 [3] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [4] http://www.ovirt.org/OVirt_3.3.2_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] SSL timeout
Hi, I'm trying to solve Bug 1034777 - SSL connection times out on read operation when installing from disk. It has been suggested to try tweaking SSL socket timeout on client side, but it seems that the timeout is set on server side to 160 seconds in vdsm/kaxmlrpclib.py [1] I suggest to set it to something higher like 1800 (30 minutes) or allow to specify it in a configuration file. I don't think this can be solved on client side. Can anybody confirm it can be solved only server side? If not, can you provide an example for setting timeout on client side? Thanks. [1] http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/kaxmlrpclib.py;h=735a9e913f86cb8add6a2d12d029c7c1b81dd465;hb=HEAD -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] 3.4.0 Release tracker
to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] [QE] 3.4.0 Release tracker
Il 08/01/2014 10:23, Sander Grendelman ha scritto: Now that BZ#1038525 (live snapshot merge for backup api) is closed as a duplicate of BZ#647386 ( You are not authorized to access bug #647386 ) Shouldn't BZ#647386 targeted for 3.4? Or for a future version? BZ#1038525 is open and targeted to 3.5.0 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] oVirt 3.4.0 release schedule updated
Il 09/01/2014 15:02, Doron Fediuck ha scritto: - Original Message - From: Eli Mesika emes...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: arch a...@ovirt.org, engine-devel engine-de...@ovirt.org, vdsm-devel vdsm-de...@fedorahosted.org, VDSM Project Development vdsm-devel@lists.fedorahosted.org, us...@ovirt.org Sent: Thursday, January 9, 2014 10:40:28 AM Subject: Re: [Users] oVirt 3.4.0 release schedule updated - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: engine-devel engine-de...@ovirt.org, VDSM Project Development vdsm-devel@lists.fedorahosted.org, vdsm-devel vdsm-de...@fedorahosted.org, arch a...@ovirt.org, us...@ovirt.org Sent: Wednesday, January 8, 2014 6:47:58 PM Subject: [Users] oVirt 3.4.0 release schedule updated 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 Please note that some guys from the TLV office could not attend to that due to an Advanced Python Course taking place (27-30 JAN) Hi Sandro, Since there's some activity also around FOSDEM, I suggest we will do the first test day on January 23. Please let me know if there are any objections. I'll update the site with new date, thanks. 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 ___ Users mailing list us...@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list us...@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] oVirt 3.4.0 alpha repository closure failure
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 ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] oVirt 3.4.0 alpha delayed
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/$releasever/ 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/$releasever/ 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 ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Unable to delete a snapshot
Il 12/01/2014 10:40, Maor Lipchuk ha scritto: Adding Sandro to the thread On 01/12/2014 11:26 AM, Maor Lipchuk wrote: On 01/09/2014 12:29 PM, Nicolas Ecarnot wrote: Hi Maor, hi everyone, Le 07/01/2014 04:09, Maor Lipchuk a écrit : Looking at bugzilla, it could be related to https://bugzilla.redhat.com/1029069 (based on the exception described at https://bugzilla.redhat.com/show_bug.cgi?id=1029069#c1) In my case, there where nothing live : the VM was shut down when creating the snapshot as well as when tyring to delete it. I understand though live storage migration sub flows are, creation of live snapshot, so it could be related. The issue there was fixed after an upgrade to 3.3.1 (as Sander mentioned it before in the mailing list) Could you give it a try and check if that works for you? I'm very shy with upgrading my oVirt production framework, but I began to read some things to upgrade it. Maybe you can lead me to a precise way to upgrade vdsm? Sandro, do you aware of any documentation which can help in upgrading ovirt, specifically VDSM? No, I'm not aware of any documentation about it. However since 3.3.1 is in ovirt-stable if you just need to update vdsm on a system I think that yum --enablerepo=ovirt-stable update vdsm* on that system should be enough. CCing Dan and VDSM list for confirming Also it will be great if you could open a bug on that with the full VDSM, engine logs and the list of lvs. Done : https://bugzilla.redhat.com/show_bug.cgi?id=1050901 Thanks ___ Users mailing list us...@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] Issues installing hosted-engine with 3.4.0 alpha
vdsm: failed to execute unified_network_persistence_upgrade, error code 1 vdsm start [FAILED] Any suggestions? Thanks, Andrew ___ Users mailing list us...@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] 3.4.0 alpha release status
Hi, oVirt 3.4.0 alpha has been released and is actually on QA. The bug tracker [1] shows the following bugs blocking the release: There are still 280 bugs [2] targeted to 3.4.0 so please review them as soon as possible Maintainers: - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please start updating the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please start filling release notes, the page has been created here [3] For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://www.ovirt.org/OVirt_3.4.0_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [QE] 3.4.0 alpha release status
Il 15/01/2014 12:24, Sandro Bonazzola ha scritto: Hi, oVirt 3.4.0 alpha has been released and is actually on QA. The bug tracker [1] shows the following bugs blocking the release: Sorry, missed the blocker list: network - Bug 987813 - [RFE] report BOOTPROTO and BONDING_OPTS independent of netdevice.cfg storage - Bug 1032686 - [RFE] API to save OVF on any location gluster - Bug 1038988 - Gluster brick sync does not work when host has multiple interfaces There are still 280 bugs [2] targeted to 3.4.0 so please review them as soon as possible Maintainers: - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please start updating the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please start filling release notes, the page has been created here [3] For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://www.ovirt.org/OVirt_3.4.0_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.3 beta / RC status
Hi, oVirt 3.3.3 beta has been released and is actually on QA. We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC. The bug tracker [1] shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3 - 3.3.3: Whiteboard Bug ID Summary integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 [RFE] oVirt Live - use motd to show the admin password integration 1022440 [RFE] AIO - configure the AIO host to be a gluster cluster/host integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO integration 1050084 Tracker: oVirt 3.3.3 release network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) node906257 USB Flash Drive install of ovirt-node created via dd fails node923049 ovirt-node fails to boot from local disk under UEFI mode node965583 [RFE] add shortcut key on TUI node976675 [wiki] Update contribution page node979350 Changes admin password in the first time when log in is failed while finished auto-install node979390 [RFE] Split defaults.py into smaller pieces node982232 performance page takes 1sec to load (on first load) node984441 kdump page crashed before configuring the network after ovirt-node intalled node986285 UI crashes when no bond name is given node991267 [RFE] Add TUI information to log file. node1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install node1018710 [RFE] Enhance API documentation node1032035 [RFE]re-write auto install function for the cim plugin node1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image storage 987917 [oVirt] [glance] API version not specified in provider dialog virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Maintainers: - We'll start composing oVirt 3.3.3 RC on 2014-01-21 12:00 UTC: all non blockers bug still open after the build will be moved to 3.3.4. - Please add the bugs to the tracker if you think that 3.3.3 should not be released without them fixed. - Please provide ETA on bugs you add as blockers - Please re-target all bugs you don't think that should block 3.3.3. - Please fill release notes, the page has been created here [3] - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.3.3 RC. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Thanks to Gianluca Cecchi for his testing of oVirt 3.3.3 beta on Gluster storage! [1] http://bugzilla.redhat.com/1050084 [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://www.ovirt.org/OVirt_3.3.3_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.4.0 alpha / beta status
Hi, oVirt 3.4.0 alpha has been released and is actually on QA. An issue has been found in VDSM so we have updated the packages in alpha repositories for Fedora. We had an issue with nightly build for EL6 packages yesterday so EL6 repository is not yet updated. We'll try to sync it today, I'm sorry for the inconvenient. We'll start composing oVirt 3.4.0 beta on 2014-01-20 14:00 UTC from 3.4 branches. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Summary gluster 1038988 Gluster brick sync does not work when host has multiple interfaces integration 1054080 gracefully warn about unsupported upgrade from legacy releases network 1054195 [NetworkLabels] Attaching two labeled networks to a cluster result in failure of the latter There are still 280 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 237 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers: - Please remember to rebuild your packages before 2014-01-21 12:00 UTC if you want them to be included in 3.4.0 beta. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-01-23 For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-01-23! Thanks to all people already testing 3.4.0 alpha! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto: Hi, After adding the node to engine, it goes to non operational state with the error Host 10.70.43.160 is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.4.. I have enabled the repo http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ in host. Following is the vdsm version installed in F19 node: [root@localhost ~]# rpm -qa | grep vdsm vdsm-cli-4.14.1-2.fc19.noarch vdsm-4.14.1-2.fc19.x86_64 vdsm-python-4.14.1-2.fc19.x86_64 vdsm-python-zombiereaper-4.14.1-2.fc19.noarch vdsm-xmlrpc-4.14.1-2.fc19.noarch vdsm-gluster-4.14.1-2.fc19.noarch [root@localhost ~]# vdsClient -s 0 getVdsCaps clusterLevels = ['3.0', '3.1', '3.2', '3.3'] Anything I am missing here? Same here, if it's not already there, please open a BZ on VDSM. As temporary workaround, please use cluster with 3.3 cluster level Regards, Ramesh - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: arch a...@ovirt.org, engine-devel engine-de...@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 6:37:23 PM Subject: [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th Hi all, tomorrow Jan 23th we'll have oVirt 3.4.0 test day. On this day all relevant engineers will be online ready to support any issues you find during install / operating this new release. Just make sure you have 1 hosts or more to test drive the new release. If you're curious to see how it works, this is your chance. Thanks again for everyone who will join us tomorrow! Location #ovirt irc channel Please communicate here to allow others to see any issues What In this test day you have a license to kill ;) Follow the documentation to setup your environment, and test drive the new features. Please remember we expect to see some issues, and anything you come up with will save a you when you'll install final release Remember to try daily tasks you'd usually do in the engine, to see there are no regressions. Write down the configuration you used (HW, console, etc) in the report etherpad[1]. Documentation Release notes: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F If you find errors in the wiki please annotate it as well in report etherpad [1] Prerequisites / recommendations Use CentOS or RHEL 6.5 only. 6.4 is unsupported due to various issues (sanlock, libvirt, etc). Use Fedora 19 only. Fedora 20 is unsupported due to various issues (sos, jboss). Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2]. NEW issues / reports For any new issue, please update the reports etherpad [1] Feature owners, please make sure: your feature is updated and referenced on release page [2]. you have testing instruction for your feature either on test day page [3] or in your feature page. your team regression testing section is organized and up to date on test day page [3]. [1] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
Il 23/01/2014 15:21, Brad House ha scritto: On 01/23/2014 08:30 AM, Sandro Bonazzola wrote: It seems that VDSM is not working on your system. Can you attach vdsm logs? vdsm log is empty # ls -l /var/log/vdsm/vdsm.log -rw-r--r-- 1 root root 0 Jan 20 10:13 /var/log/vdsm/vdsm.log # ps -ef | grep -i vdsm root 1628 1 0 09:16 ?00:00:00 /usr/bin/python /usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock # service vdsmd status Redirecting to /bin/systemctl status vdsmd.service vdsmd.service - Virtual Desktop Server Manager Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled) Active: failed (Result: start-limit) since Thu 2014-01-23 09:16:38 EST; 1min 26s ago Process: 2387 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS) Process: 2380 ExecStart=/usr/share/vdsm/daemonAdapter -0 /dev/null -1 /dev/null -2 /dev/null /usr/share/vdsm/vdsm (code=exited, status=1/FAILURE) Process: 2328 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=0/SUCCESS) Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service entered failed state. Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service holdoff time over, scheduling restart. Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Stopping Virtual Desktop Server Manager... Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Starting Virtual Desktop Server Manager... Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: vdsmd.service start request repeated too quickly, refusing to start. what's this . It's the first start of vdsmd! Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Failed to start Virtual Desktop Server Manager. Jan 23 09:16:38 ovirttest.internal.monetra.com systemd[1]: Unit vdsmd.service entered failed state. I've attached the supervdsm.log and ovirt-hosted-engine-setup-20140123091611.log incase that's helpful. Thanks. -Brad -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] ovirt-3.3.3 release postponed due to blockers
Hi, oVirt 3.3.3 release need to be postponed. A recent release of python-cpopen-1.3 is breaking dependency resolution on EL6 and F19 so vdsm can't be installed and node can't be composed. A recent change in vdsm-python-cpopen added the needed conflict against python-cpopen and removed Provides / Obsoletes on python-cpopen. But no new releases of python-cpopen is available fixing the correct Provides / Obsoletes pair. oVirt 3.3.2 / stable is affected too. Please fix Bug 1056470 - python-cpopen-1.3 is not providing obsoleted package. Bug 1056464 - python-cpopen-1.3 is not providing obsoleted package. ASAP. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 10:20, Dan Kenigsberg ha scritto: On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote: Hi, any news regarding my questions? Am 29.01.2014 09:23, schrieb Sandro Bonazzola: Il 29/01/2014 09:21, Sven Kieske ha scritto: Hi, I wanted to try it the other way around, installing vdsm-python-cpopen and check if it runs without python-cpopen . But that leads me to a question: Is there any difference between these packages beside their different name? If yes, what is the difference and which package should be installed? I no, why is there a packet vdsm-python-cpopen ? CCing VDSM python-cpopen includes some improvements and bug fixes, that are going to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3. python-cpopen wast intended to deprecate and replace vdsm-python-cpopen, but we have had way too many issues trying to do that properly in rpm/yum. Most of the bugs are ours, at least one is yum's. At the moment, the existence of python-cpopen in Fedora confuses `yum install vdsm`. To avoid this unfortunate delay, we can either include python-cpopen in ovirt-stable or exclude vdsm-python-cpopen from there. Both options are unfavorable, but so is continuing to wait. If it's enough just to add python-cpopen to ovirt-stable, I'm fine with that. I just need the link to the build to be included there. Regards, Dan. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: Hey, we found this yum bug and still struggling with more issuing according to the relation between those packages if we drop vdsm-python-cpopen the requirement in vdsm takes python-cpopen instead. in python-cpopen we have the same code base and it provides all vdsm-ptyhon-cpopen provides, so shouldn't be any issues with dropping it from the repository is it possible to ship 3.3.3 release that way ? we don't need to change the requirement in the code, if python-cpopen 1.3-1 is part of the release, it will be taken by vdsm spec (tried with vdsm 4.13.3-2 with the available cpopen 1.3-1) I can't release 3.3.3 that way. We're keeping rolling releases on stable repository so if I don't provide 4.13.3-2, previous one will still be available. Sven, for your question, install python-cpopen 1.3-1 for both 3.3 and 3.4 releases that you use, and the upgrade\downgrade should not raise any dependencies issues afaic Yaniv Bronhaim. - Original Message - From: Dan Kenigsberg dan...@redhat.com To: Sandro Bonazzola sbona...@redhat.com, ybron...@redhat.com Cc: Sven Kieske s.kie...@mittwald.de, Trey Dockendorf treyd...@gmail.com, users us...@ovirt.org, VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Thursday, January 30, 2014 4:02:13 PM Subject: Re: [Users] ovirt-3.3.3 release postponed due to blockers On Thu, Jan 30, 2014 at 10:27:34AM +0100, Sandro Bonazzola wrote: Il 30/01/2014 10:20, Dan Kenigsberg ha scritto: On Thu, Jan 30, 2014 at 08:52:36AM +, Sven Kieske wrote: Hi, any news regarding my questions? Am 29.01.2014 09:23, schrieb Sandro Bonazzola: Il 29/01/2014 09:21, Sven Kieske ha scritto: Hi, I wanted to try it the other way around, installing vdsm-python-cpopen and check if it runs without python-cpopen . But that leads me to a question: Is there any difference between these packages beside their different name? If yes, what is the difference and which package should be installed? I no, why is there a packet vdsm-python-cpopen ? CCing VDSM python-cpopen includes some improvements and bug fixes, that are going to be needed in ovirt-3.4. vdsm-python-cpopen is shipped by ovirt-3.3. python-cpopen wast intended to deprecate and replace vdsm-python-cpopen, but we have had way too many issues trying to do that properly in rpm/yum. Most of the bugs are ours, at least one is yum's. At the moment, the existence of python-cpopen in Fedora confuses `yum install vdsm`. To avoid this unfortunate delay, we can either include python-cpopen in ovirt-stable or exclude vdsm-python-cpopen from there. Both options are unfavorable, but so is continuing to wait. If it's enough just to add python-cpopen to ovirt-stable, I'm fine with that. I just need the link to the build to be included there. Yaniv, have you tried if shipping python-cpopen hides this issue? http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc20/x86_64/python-cpopen-1.3-1.fc20.x86_64.rpm http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.fc19/x86_64/python-cpopen-1.3-1.fc19.x86_64.rpm http://kojipkgs.fedoraproject.org//packages/python-cpopen/1.3/1.el6/ppc64/python-cpopen-1.3-1.el6.ppc64.rpm Dropping vdsm-python-cpopen from a stable version seems impolite, but should work, too. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] ovirt-3.3.3 release postponed due to blockers
Il 30/01/2014 22:38, Robert Story ha scritto: Can we revert these packages to previous versions in the 3.3.2 stable repo so those of us who want/need to install new hosts in our clusters aren't dead in the water waiting for 3.3.3? Hi Robert, I think you can still install 3.3.2 on your clusters with the requirement of adding manually oython-cpopen before trying to install vdsm. About 3.3.3, I think vdsm should really drop dependency on vdsm-python-cpopen: it's a package obsoleted by python-cpopen so there's no point in still requiring it especially if keeping that requirement still break dependency resolution. On Thu, 30 Jan 2014 16:26:51 +0100 Sandro wrote: SB Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: SB Hey, SB SB we found this yum bug and still struggling with more issuing SB according to the relation between those packages SB SB if we drop vdsm-python-cpopen the requirement in vdsm takes SB python-cpopen instead. in python-cpopen we have the same code base SB and it provides all vdsm-ptyhon-cpopen provides, so shouldn't be any SB issues with dropping it from the repository SB SB is it possible to ship 3.3.3 release that way ? we don't need to SB change the requirement in the code, if python-cpopen 1.3-1 is part of SB the release, it will be taken by vdsm spec (tried with vdsm 4.13.3-2 SB with the available cpopen 1.3-1) SB SB SB I can't release 3.3.3 that way. SB We're keeping rolling releases on stable repository so if I don't SB provide 4.13.3-2, previous one will still be available. Robert -- Senior Software Engineer @ Parsons -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] ovirt-3.3.3 release postponed due to blockers
Il 02/02/2014 00:05, Dan Kenigsberg ha scritto: On Fri, Jan 31, 2014 at 04:16:54PM -0500, Douglas Schilling Landgraf wrote: On 01/31/2014 05:17 AM, Dan Kenigsberg wrote: On Fri, Jan 31, 2014 at 09:36:48AM +0100, Sandro Bonazzola wrote: Il 30/01/2014 22:38, Robert Story ha scritto: Can we revert these packages to previous versions in the 3.3.2 stable repo so those of us who want/need to install new hosts in our clusters aren't dead in the water waiting for 3.3.3? Hi Robert, I think you can still install 3.3.2 on your clusters with the requirement of adding manually oython-cpopen before trying to install vdsm. About 3.3.3, I think vdsm should really drop dependency on vdsm-python-cpopen: it's a package obsoleted by python-cpopen so there's no point in still requiring it especially if keeping that requirement still break dependency resolution. I really wanted to avoid eliminating a subpackage during a micro release. That's impolite and surprising. But given the awkward yum bug, persistent dependency problems, and the current release delay, I give up. Let's eliminate vdsm-python-cpopen from ovirt-3.3 branch, and require python-cpopen. Yaniv, Douglas: could you handle it? Sure. Done: http://gerrit.ovirt.org/#/c/23942/ Acked. Could you cherry-pick it into dist-git and rebuild the ovirt-3.3.3 candidate (and without other changes that can wait for ovirt-3.3.4). Let me know where I can get the new rpms, so I can add them to 3.3.3 repo and release :-) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] mom RPMs for 3.4
Il 01/02/2014 23:48, Dan Kenigsberg ha scritto: On Fri, Jan 31, 2014 at 04:56:12PM -0500, Adam Litke wrote: On 31/01/14 08:36 +0100, Sandro Bonazzola wrote: Il 30/01/2014 19:30, Adam Litke ha scritto: On 30/01/14 18:13 +, Dan Kenigsberg wrote: On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote: Hi Sandro, After updating the MOM project's build system, I have used jenkins to produce a set of RPMs that I would like to tag into the oVirt 3.4 release. Please see the jenkins job [1] for the relevant artifacts for EL6[2], F19[3], and F20[4]. Dan, should I submit a patch to vdsm to make it require mom = 0.4.0? I want to be careful to not break people's environments this late in the 3.4 release cycle. What is the best way to minimize that damage? Hey, we're during beta. I prefer making this requirement explicit now over having users with supervdsmd.log retate due to log spam. In that case, Sandro, can you let me know when those RPMs hit the ovirt repos (for master and 3.4) and then I will submit a patch to vdsm to require the new version. mom 0.4.0 has been built in last night nightly job [1] and published to nightly by publisher job [2] so it's already available on nightly [3] For 3.4.0, it has been planned [4] a beta 2 release on 2014-02-06 so we'll include your builds in that release. I presume the scripting for 3.4 release rpms will produce a version without the git-rev based suffix: ie. mom-0.4.0-1.rpm? I need to figure out how to handle a problem that might be a bit unique to mom. MOM is used by non-oVirt users who install it from the main Fedora repository. I think it's fine that we are producing our own rpms in oVirt (that may have additional patches applied and may resync to upstream mom code more frequently than would be desired for the main Fedora repository). Given this, I think it makes sense to tag the oVirt RPMs with a special version suffix to indicate that these are oVirt produced and not upstream Fedora. For example: The next Fedora update will be mom-0.4.0-1.f20.rpm. The next oVirt update will be mom-0.4.0-1ovirt.f20.rpm. Is this the best practice for accomplishing my goals? One other thing I'd like to have the option of doing is to make vdsm depend on an ovirt distribution of mom so that the upstream Fedora version will not satisfy the dependency for vdsm. What is the motivation for this? You would not like to bother Fedora users with updates that are required only for oVirt? Vdsm itself is built, signed, and distributed via Fedora. It is also copied into the ovirt repo, for completeness sake. Could MoM do the same? IMHO, if we're distributing mom and vdsm rpms through Fedora yum repository we should not duplicate it on ovirt yum repository. Fedora package is signed and will differ from the one we're shipping within ovirt repo (which is unsigned) We should provide on resource.ovirt.org only packages not available on downstream repositories (like nightly builds). Dan. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] mom RPMs for 3.4
Il 03/02/2014 09:35, Amedeo Salvati ha scritto: Da: arch-boun...@ovirt.org A: Dan Kenigsberg dan...@redhat.com,Adam Litke ali...@redhat.com Cc: engine-de...@ovirt.org,arch a...@ovirt.org,VDSM Project Development vdsm-devel@lists.fedorahosted.org Data: Mon, 03 Feb 2014 08:50:12 +0100 Oggetto: Re: mom RPMs for 3.4 Il 01/02/2014 23:48, Dan Kenigsberg ha scritto: On Fri, Jan 31, 2014 at 04:56:12PM -0500, Adam Litke wrote: On 31/01/14 08:36 +0100, Sandro Bonazzola wrote: Il 30/01/2014 19:30, Adam Litke ha scritto: On 30/01/14 18:13 +, Dan Kenigsberg wrote: On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote: Hi Sandro, After updating the MOM project's build system, I have used jenkins to produce a set of RPMs that I would like to tag into the oVirt 3.4 release. Please see the jenkins job [1] for the relevant artifacts for EL6[2], F19[3], and F20[4]. Dan, should I submit a patch to vdsm to make it require mom = 0.4.0? I want to be careful to not break people's environments this late in the 3.4 release cycle. What is the best way to minimize that damage? Hey, we're during beta. I prefer making this requirement explicit now over having users with supervdsmd.log retate due to log spam. In that case, Sandro, can you let me know when those RPMs hit the ovirt repos (for master and 3.4) and then I will submit a patch to vdsm to require the new version. mom 0.4.0 has been built in last night nightly job [1] and published to nightly by publisher job [2] so it's already available on nightly [3] For 3.4.0, it has been planned [4] a beta 2 release on 2014-02-06 so we'll include your builds in that release. I presume the scripting for 3.4 release rpms will produce a version without the git-rev based suffix: ie. mom-0.4.0-1.rpm? I need to figure out how to handle a problem that might be a bit unique to mom. MOM is used by non-oVirt users who install it from the main Fedora repository. I think it's fine that we are producing our own rpms in oVirt (that may have additional patches applied and may resync to upstream mom code more frequently than would be desired for the main Fedora repository). Given this, I think it makes sense to tag the oVirt RPMs with a special version suffix to indicate that these are oVirt produced and not upstream Fedora. For example: The next Fedora update will be mom-0.4.0-1.f20.rpm. The next oVirt update will be mom-0.4.0-1ovirt.f20.rpm. Is this the best practice for accomplishing my goals? One other thing I'd like to have the option of doing is to make vdsm depend on an ovirt distribution of mom so that the upstream Fedora version will not satisfy the dependency for vdsm. What is the motivation for this? You would not like to bother Fedora users with updates that are required only for oVirt? Vdsm itself is built, signed, and distributed via Fedora. It is also copied into the ovirt repo, for completeness sake. Could MoM do the same? IMHO, if we're distributing mom and vdsm rpms through Fedora yum repository we should not duplicate it on ovirt yum repository. Fedora package is signed and will differ from the one we're shipping within ovirt repo (which is unsigned) We should provide on resource.ovirt.org only packages not available on downstream repositories (like nightly builds). why you can't sign your rpms??? We're working on that :-) on ovirt web page http://www.ovirt.org/Home you can change: Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor with: Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor (but not signed rpms) best regards a Dan. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Arch mailing list a...@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] oVirt 3.3.3 release
The oVirt development team is very happy to announce the general availability of oVirt 3.3.3 as of February 3rd 2013. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. IMPORTANT NOTE: If you're upgrading from a previous version, please update ovirt-release to the latest version (10.0.1-3) and verify you have the correct repositories enabled by running the following commands # yum update ovirt-release # yum repolist enabled before upgrading with the usual procedure. You should see the ovirt-3.3.3 and ovirt-stable repositories listed in the output of the repolist command. A new oVirt Node build will be available soon as well. [1] http://www.ovirt.org/OVirt_3.3.3_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.4.0 beta status
Hi, oVirt 3.4.0 beta has been released and is actually on QA. We're going to tart composing oVirt 3.4.0 beta2 this Thursday 2014-02-06 09:00 UTC from 3.4 branches. This build will be used for a second Test Day scheduled for 2014-02-11. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary gluster 1038988 POSTGluster brick sync does not work when host has multiple interfaces gluster 1059606 POSTErrors in rebalance and remove-brick status and sync integration 1054080 POSTgracefully warn about unsupported upgrade from legacy releases integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None There are still 393 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 238 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers: - Please remember to rebuild your packages before 2014-02-06 09:00 UTC if you want them to be included in 3.4.0 beta. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-11 For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug. Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-11! Thanks to all people already testing 3.4.0 beta! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [Users] [QE] oVirt 3.4.0 beta status
Il 04/02/2014 13:30, Gianluca Cecchi ha scritto: On Tue, Feb 4, 2014 at 1:03 PM, Sandro Bonazzola wrote: Hi, oVirt 3.4.0 beta has been released and is actually on QA. We're going to tart composing oVirt 3.4.0 beta2 this Thursday 2014-02-06 09:00 UTC from 3.4 branches. This build will be used for a second Test Day scheduled for 2014-02-11. Is beta2 expected to be available to run on Fedora 20, engine and hosts? I don't think so. I've opened a tracker for F20 support related issues here: https://bugzilla.redhat.com/show_bug.cgi?id=1060198 Thanks, Gianluca -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Request for 3 PPC64 vm slaves for Jenkins
Il 12/02/2014 01:13, Ewoud Kohl van Wijngaarden ha scritto: On Tue, Feb 11, 2014 at 08:12:45AM +0100, Sandro Bonazzola wrote: Il 10/02/2014 23:15, Ewoud Kohl van Wijngaarden ha scritto: On Mon, Feb 10, 2014 at 08:12:35AM +0100, Sandro Bonazzola wrote: PPC64 support is going to be introduced as new feature in oVirt 3.4.0. So we should start delivering PPC64 packages for arch dependent packages for both EL6 and Fedora. VMs may be small enough since they should only build nightly vdsm and ovirt-host-deploy-offline: 1 core, 512Mb ram, 10Gb disk Software needed: minimal install + vdsm and ovirt-host-deploy-offline build deps. Since we only have x86 hardware which run oVirt. Does it have to be a PPC64 VM because I don't think we can host that right now. AFAIK we can run qemu-system-ppc64 also on x86_64. Or am I missing something? Can we also do this with oVirt as host? Ideally I'd prefer not having to manually host a VM but have oVirt take care of it. Could a VDSM hook possibly solve this if not built in? Never tested such configuration. CCing VDSM developers about this. ___ Infra mailing list in...@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.4 beta status
Hi, we're going to branch and build oVirt 3.3.4 beta on Tue 2014-02-18 09:00 UTC. Repository composition will follow as soon as all packages will be built. A bug tracker is available at [1] and it shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3.4: Whiteboard Bug ID Summary infra 1053576 [abrt] vdsm-python: libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock'... integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) network 1064489 do not report negative rx/tx rate when Linux counters wrap node923049 ovirt-node fails to boot from local disk under UEFI mode node965583 [RFE] add shortcut key on TUI node976675 [wiki] Update contribution page node979350 Changes admin password in the first time when log in is failed while finished auto-install node979390 [RFE] Split defaults.py into smaller pieces node982232 performance page takes 1sec to load (on first load) node984441 kdump page crashed before configuring the network after ovirt-node intalled node986285 UI crashes when no bond name is given node991267 [RFE] Add TUI information to log file. node1018374 ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19: Failed on Auto-install node1018710 [RFE] Enhance API documentation node1032035 [RFE]re-write auto install function for the cim plugin node1033286 ovirt-node-plugin-vdsm can not be added to ovirt node el6 base image storage 987917 [oVirt] [glance] API version not specified in provider dialog virt1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Maintainers / Assignee: Please add the bugs to the tracker if you think that 3.3.4 should not be released without them fixed. Please re-target all bugs you don't think that should block 3.3.4. For those who want to help testing the bugs, I suggest to add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] http://bugzilla.redhat.com/1064462 [2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing [3] http://www.ovirt.org/OVirt_3.3.4_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.4.0 RC status
Hi, oVirt 3.4.0 beta2 has been released and is actually on QA. We're going to tart composing oVirt 3.4.0 RC this Monday 2014-02-17 09:00 UTC from 3.4 branches. This build will be used for a third Test Day scheduled for Wed 2014-02-19. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None storage 1057761 NEW Can't discover iSCSI target virt1062615 POSTutc_diff not updated according to a change in VM settings There are still 376 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 252 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-02-17 09:00 UTC if you want them to be included in 3.4.0 RC. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-19! Thanks to all people already testing 3.4.0 beta 2! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.4 beta / RC status
Hi, we've released oVirt 3.3.4 beta on Wed 2014-02-19. We're going to start building 3.3.4 RC on 2014-02-25 09:00 UTC repository composition will follow as soon as all packages will be built. A bug tracker is available at [1] and it shows no bugs blocking the release The following is a list of the non-blocking bugs still open with target 3.3.4: Whiteboard Bug ID Summary infra 1053576 ASSIGNED[abrt] vdsm-python: libvirt.py:102:openAuth:libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory integration 1026930 NEW Package virtio-win and put it in ovirt repositories integration 1026933 NEW pre-populate ISO domain with virtio-win ISO network 987917 NEW [oVirt] [glance] API version not specified in provider dialog network 997197 NEW Some AppErrors messages are grammatically incorrect (singular vs plural) 1066654 NEW engine-cleanup does not cleanup everything Maintainers / Assignee: Please add the bugs to the tracker if you think that 3.3.4 should not be released without them fixed. Please re-target all bugs you don't think that should block 3.3.4. Bugs still targeted to 3.3.4 after RC announce will be re-targeted to 3.4.1 For those who want to help testing the bugs, I suggest to add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] http://bugzilla.redhat.com/1064462 [2] http://www.ovirt.org/Testing/Ovirt_3.3.4_testing [3] http://www.ovirt.org/OVirt_3.3.4_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.4.0 RC status
Hi, oVirt 3.4.0 beta3 has been released and is actually on QA. We're going to start building oVirt 3.4.0 RC this Monday 2014-02-24 09:00 UTC from 3.4 branches. repository composition will follow as soon as all packages will be built. This build will be used for a third Test Day scheduled for Wed 2014-02-27. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary infra 1055881 POSTREST API: Search for an user in active directory by upn doesn't return any results ... infra 1059258 POSTREST API: Create user user@domain actually creates user only infra 1060528 POSTError response to DELETE request of 'Everyone' group doesn't contains 'detail' field infra 1064829 POSTRegression: Add data center permission to user causes to internal error integration 1058018 POSTupgrade from 3.3 overwrites exports with acl None network 1066953 POSTCannot edit network is setup networks dialog network 1066956 POSTCannot create a bond in 'Setup networks' dialog storage 1057761 NEW Can't discover iSCSI target storage 1066466 POSTDisk name doesn't get assigned automatically after a CREATE command. ux 1066489 POSTEvent list not updating when events happen. ux 1066827 NEW [webadmin] incorrect behavior of manual refresh in Host Main Tab virt1062615 POSTutc_diff not updated according to a change in VM settings Maintainers / Assignee: - Please provide ETA on blockers bugs - Please fix them ASAP There are still 347 bugs [2] targeted to 3.4.0. Excluding node and documentation bugs we still have 222 bugs [3] targeted to 3.4.0. Please review them as soon as possible. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-02-24 09:00 UTC if you want them to be included in 3.4.0 RC. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [4] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-27 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-27! Thanks to all people already testing 3.4.0 beta 3! [1] https://bugzilla.redhat.com/1024889 [2] http://red.ht/1eIRZXM [3] http://red.ht/1auBU3r [4] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] Postponing oVirt 3.4.0 RC build, Test Day and GA
Hi, we still have 3 blockers on POST so we're postponing RC build until all of them will be in MODIFIED state. Here is the list of blockers still open: Whiteboard Bug ID Status Summary infra 1055881 POSTREST API: Search for an user in active directory by upn doesn't return any results... infra 1059258 POSTREST API: Create user user@domain actually creates user only virt1062615 POSTutc_diff not updated according to a change in VM settings We're postponing Test Day too, scheduling it for next week on 2014-03-06. oVirt 3.4.0 GA have been postponed by one week, new tentative date is 2014-03-11. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [ANN] oVirt 3.4.0 Release Candidate is now available
The oVirt team is pleased to announce that the 3.4.0 Release Candidate is now available for testing. Release notes and information on the changes for this update are still being worked on and will be available soon on the wiki[1]. Please ensure to follow install instruction from release notes if you're going to test it. The existing repository ovirt-3.4.0-prerelease has been updated for delivering this release candidate and future refreshes until final release. An oVirt Node iso is already available, unchanged from third beta. You're welcome to join us testing this release candidate in next week test day [2] scheduled for 2014-03-06! [1] http://www.ovirt.org/OVirt_3.4.0_release_notes [2] http://www.ovirt.org/OVirt_3.4_Test_Day -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] oVrit 3.4.0 branch created
Hi, as announced yesterday the new branch ovirt-engine-3.4.0 branch has been created from 3.4. Branch commit was: * 9ab9f01 - (origin/ovirt-engine-3.4) core: Remove error messages from log when adding host lzel...@redhat.com Only critical fixes will be accepted on ovirt-engine-3.4.0 branch. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [ANN] oVirt 3.3.4 release
The oVirt development team is pleased to announce the general availability of oVirt 3.3.4 as of March 4th 2014. This release solidifies oVirt as a leading KVM management application and open source alternative to VMware vSphere. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The existing repository ovirt-stable has been updated for delivering this release without the need of enabling any other repository. A new oVirt Node build is also available [2]. [1] http://www.ovirt.org/OVirt_3.3.4_release_notes [2] http://resources.ovirt.org/releases/3.3.4/iso/ovirt-node-iso-3.0.4-1.0.201401291204.vdsm33.el6.iso -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.3.5 status
Hi, now that 3.3.4 has been released, it's time to look at 3.3.5. Here is the tentative timeline: General availability: 2014-04-09 RC Build: 2014-04-02 Nightly builds are available enabling the oVirt 3.3 snapshots repositories: # yum-config-manager --enable ovirt-3.3-snapshot # yum-config-manager --enable ovirt-3.3-snapshot-static As you can see there won't be any beta release before RC for 3.3.z and the same will be for 3.4.z. Now we've nightly builds also for stable branches so you can test them whenever you want to. If you're going to test it, please add yourself as tester on [3] Note to maintainers: * For Release candidate builds, we'll send to all maintainers a reminder the week before the build on Thursday morning (UTC timezone). Packages that won't be ready before the announced compose time won't be added to the release candidate. Please remember to build your packages the day before repository composition if you want it in. * Release notes must be filled [1] * A tracker bug has been created [2] and shows 1 bug blocking the release: Whiteboard Bug ID Summary virt1071997 VM is not locked on run once * Please add bugs to the tracker if you think that 3.3.5 should not be released without them fixed. [1] http://www.ovirt.org/OVirt_3.3.5_release_notes [2] http://bugzilla.redhat.com/1071867 [3] http://www.ovirt.org/Testing/oVirt_3.3.5_testing Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] [QE] oVirt 3.4.0 status
Hi, oVirt 3.4.0 RC has been released and is currently on QA. While we're preparing for this week Test Day on 2014-03-06 a few blockers have been opened. The bug tracker [1] shows the following bugs blocking the release: Whiteboard Bug ID Status Summary infra 1070742 POST[database] support postgres user length within schema version infra 1071536 POSTNotifier doesn't send any notifications via email integration 1067058 POST[database] old psycopg2 does not accept unicode string as port name integration 1069193 POSTRelease maven artifacts with correct version numbers integration 1072307 POSTremote database cannot be used virt1069201 ASSIGNED[REST]: Missing domain field on VM\Template object. virt1071997 POSTVM is not locked on run once All remaining bugs have been re-targeted to 3.4.1. Maintainers / Assignee: - Please remember to rebuild your packages before 2014-03-11 09:00 UTC if you want them to be included in 3.4.0 GA. - Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed. - Please provide ETA on blockers bugs and fix them as soon as possible - Please fill release notes, the page has been created here [2] - Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-19 Be prepared for upcoming oVirt 3.4.0 Test Day on 2014-03-06! Thanks to all people already testing 3.4.0 RC! [1] https://bugzilla.redhat.com/1024889 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
[vdsm] creating ovirtmgmt bridge using tagged vlans
',
'version': '1.6.1'},
'qemu-kvm': {'buildtime': 1384762225,
'release': '2.fc19',
'version': '1.6.1'},
'spice-server': {'buildtime': 1383130020,
'release': '3.fc19',
'version': '0.12.4'},
'vdsm': {'buildtime': 1394889953,
'release': '2.git7a51fe1.fc19',
'version': '4.14.5'}}
reservedMem = '321'
rngSources = ['random']
software_revision = '2'
software_version = '4.14'
supportedENGINEs = ['3.0', '3.1', '3.2', '3.3', '3.4']
supportedProtocols = ['2.2', '2.3']
uuid = '4C4C4544-0059-4310-8035-C4C04F595831'
version_name = 'Snow Man'
vlans = {'em1.5': {'addr': '',
'cfg': {'DEVICE': 'em1.5',
'HWADDR': 'b8:ca:3a:76:9a:43',
'MTU': '1500',
'ONBOOT': 'yes',
'VLAN': 'yes'},
'iface': 'em1',
'ipv6addrs': ['fe80::baca:3aff:fe76:9a43/64'],
'mtu': '1500',
'netmask': '',
'vlanid': 5}}
vmTypes = ['kvm']
How have I to call vdsClient addNetwork for creating the bridge using em1.5 ?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] creating ovirtmgmt bridge using tagged vlans
Il 19/03/2014 16:03, Antoni Segura Puimedon ha scritto:
- Original Message -
From: Dan Kenigsberg dan...@redhat.com
To: Antoni Segura Puimedon asegu...@redhat.com
Cc: Sandro Bonazzola sbona...@redhat.com, VDSM Project Development
vdsm-devel@lists.fedorahosted.org
Sent: Wednesday, March 19, 2014 3:58:07 PM
Subject: Re: [vdsm] creating ovirtmgmt bridge using tagged vlans
On Wed, Mar 19, 2014 at 08:00:48AM -0400, Antoni Segura Puimedon wrote:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: VDSM Project Development vdsm-devel@lists.fedorahosted.org
Cc: Antoni Segura Puimedon asegu...@redhat.com
Sent: Wednesday, March 19, 2014 12:54:45 PM
Subject: creating ovirtmgmt bridge using tagged vlans
Hi,
I'm working on: Bug 1072027 - hosted-engine setup fails when using VLAN
tagged interfaces
Provided the following caps:
# vdsClient -s localhost getVdsHardwareInfo
systemFamily = 'Not Specified'
systemManufacturer = 'Dell Inc.'
systemProductName = 'OptiPlex 7010'
systemSerialNumber = 'DYC5YX1'
systemUUID = '4C4C4544-0059-4310-8035-C4C04F595831'
systemVersion = '01'
[root@dellserver network-scripts]# vdsClient -s localhost getVdsCap
getVdsCapabilities getVdsCaps
[root@dellserver network-scripts]# vdsClient -s localhost getVdsCaps
HBAInventory = {'FC': [], 'iSCSI': [{'InitiatorName':
'iqn.1994-05.com.redhat:babababa'}]}
ISCSIInitiatorName = 'iqn.1994-05.com.redhat:babababa'
bondings = {'bond0': {'addr': '',
'cfg': {},
'hwaddr': '5a:46:b1:db:ec:9b',
'ipv6addrs': [],
'mtu': '1500',
'netmask': '',
'slaves': []}}
bridges = {';vdsmdummy;': {'addr': '',
'cfg': {},
'gateway': '',
'ipv6addrs':
['fe80::8c8a:edff:fe92:b332/64'],
'ipv6gateway': '::',
'mtu': '1500',
'netmask': '',
'ports': [],
'stp': 'off'}}
clusterLevels = ['3.0', '3.1', '3.2', '3.3', '3.4']
cpuCores = '4'
cpuFlags =
'fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,rdtscp,lm,constant_tsc,arch_perfmon,pebs,bts,rep_good,nopl,xtopology,nonstop_tsc,aperfmperf,eagerfpu,pni,pclmulqdq,dtes64,monitor,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,pcid,sse4_1,sse4_2,x2apic,popcnt,tsc_deadline_timer,aes,xsave,avx,f16c,rdrand,lahf_lm,ida,arat,epb,xsaveopt,pln,pts,dtherm,tpr_shadow,vnmi,flexpriority,ept,vpid,fsgsbase,smep,erms,model_Nehalem,model_Conroe,model_coreduo,model_core2duo,model_Penryn,model_Westmere,model_n270,model_SandyBridge'
cpuModel = 'Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz'
cpuSockets = '1'
cpuSpeed = '1864.156'
cpuThreads = '8'
emulatedMachines = ['pc',
'pc-q35-1.4',
'pc-q35-1.5',
'q35',
'isapc',
'pc-0.10',
'pc-0.11',
'pc-0.12',
'pc-0.13',
'pc-0.14',
'pc-0.15',
'pc-1.0',
'pc-1.1',
'pc-1.2',
'pc-1.3',
'pc-i440fx-1.4',
'pc-i440fx-1.5',
'none']
guestOverhead = '65'
hooks = {}
kvmEnabled = 'true'
lastClient = '127.0.0.1'
lastClientIface = 'lo'
management_ip = '0.0.0.0'
memSize = '15936'
netConfigDirty = 'False'
networks = {}
nics = {'em1': {'addr': '192.168.1.105',
'cfg': {'DEVICE': 'em1',
'HWADDR': 'b8:ca:3a:76:9a:43',
'MTU': '1500',
'ONBOOT': 'yes'},
'hwaddr': 'b8:ca:3a:76:9a:43',
'ipv6addrs': ['fe80::baca:3aff:fe76:9a43/64'],
'mtu': '1500',
'netmask': '255.255.255.0',
'speed': 1000}}
operatingSystem = {'name': 'Fedora', 'release': '8', 'version': '19'}
packages2 = {'kernel': {'buildtime': 1394207804.0,
'release': '100.fc19.x86_64',
'version': '3.13.6'},
'libvirt': {'buildtime': 1387094943,
'release': '1.fc19',
'version': '1.1.3.2'},
'mom': {'buildtime': 1391183561, 'release': '1.fc19',
'version': '0.4.0'},
'qemu-img': {'buildtime': 1384762225,
'release': '2
Re: [vdsm] http://jenkins.ovirt.org/job/vdsm_pep8_gerrit/ broken
Il 21/03/2014 12:03, David Caro ha scritto: On Wed 05 Feb 2014 01:15:40 PM CET, Eyal Edri wrote: not sure sandro meant the patch was broken, it seems job was hang and stuck for a while. dcaro - can you check what could cause this? e. - Original Message - From: Dan Kenigsberg dan...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: VDSM Project Development vdsm-devel@lists.fedorahosted.org, infra in...@ovirt.org Sent: Wednesday, February 5, 2014 2:09:51 PM Subject: Re: http://jenkins.ovirt.org/job/vdsm_pep8_gerrit/ broken On Wed, Feb 05, 2014 at 10:24:47AM +0100, Sandro Bonazzola wrote: Hi, It seems that http://jenkins.ovirt.org/job/vdsm_pep8_gerrit/ is broken, never ending also if all dependent jobs ended successfully. This keep the slaves busy avoiding other jobs to run. Please disable that job or fix ASAP. Sorry, I do not understand what is broken and what should be fixed. A recent patch of mine for an ack by this job http://gerrit.ovirt.org/#/c/24103/ but for some reason its link http://jenkins.ovirt.org/job/vdsm_pep8_gerrit/6962/ is broken, as if it was partially moved to http://jenkins.ovirt.org/view/vdsm/job/vdsm_master_pep8_gerrit/6962/ ___ Infra mailing list in...@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra Getting this a little late sorry, the job Sandro referenced does no longer exist and the one dan references seems to be working ok. Still relevant? I don't thinks so. Thanks, -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] virt-v2v integration feature
Il 09/07/2014 20:26, Arik Hadas ha scritto: Hi All, The proposed feature will introduce a new process of import virtual machines from external systems using virt-v2v in oVirt. I've created a wiki page that contains initial thoughts and design for it: http://www.ovirt.org/Features/virt-v2v_Integration You are more than welcome to share your thoughts and insights. Please use http://www.ovirt.org/Feature_template as template Thanks, Arik ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
