Re: [Users] Problem adding an IPA server to oVirt
Hi, just a little OT: I think it would be awesome if known issues would be documented somewhere else, not just in source code. Am 21.01.2014 12:49, schrieb Juan Hernandez: I think the problem is that your LDAP server is configured with a minimum security strength factor that triggers a bug in the Kerberos support in the Java virtual machine. This is a know issue. See here for details: http://gerrit.ovirt.org/21505 -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt Node Bootloader issue
Am Dienstag, den 21.01.2014, 11:33 +0500 schrieb Nauman Abbas: Hello there I'm facing this problem and this has happened to me multiple times on different machines. I have two hard drives in my system (lets say HDD A and HDD B). I boot the system from the oVirt node CD to install it. Now I want the bootloader and the node installation both to go on HDD B and not HDD A. When I get to the screen which asks me to select the hard-drive for bootloader I use the arrow keys to select HDD B and press Enter (have also tried pressing space or just use tab and continue while it's selected). Then I get to the screen asking where to install the node. I select HDD B and unselect HDD A. I keep the partitioning setup as default ( have also tried manual and kept 5GB unused on HDD A). When I get to install part. It installs the node fine on HDD B as expected but it always gets the boot-loader on HDD A. This issue has wasted many of my days on different machines and I can't seem to find a way around. Nauman, what oVirt Node version were you using? - fabian Nauman Abbas Assistant System Administrator (LMS), Room No. A-207, SEECS, National University of Sciences Technology, + 92 321 5359946 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] no new mom for ovirt?
- Original Message - From: Sven Kieske s.kie...@mittwald.de To: Users@ovirt.org List Users@ovirt.org Sent: Tuesday, January 21, 2014 6:45:10 PM Subject: [Users] no new mom for ovirt? Hi, I just checked this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1025845 This is closed for RedHat but afaik not for upstream. It mentions the fixed mom version: mom-0.3.2-8.el6ev but on resources.ovirt.org I find just older versions like http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm so downstream (payed) red hat has newer versions than upstream how can that be? Or am I looking in the wrong repo? Should this not be hosted on ovirt.org repo? -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen (Adding mom maintainer) Adam, is there a real difference between the versions? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt Node Bootloader issue
fc19 one, the latest On Wed, Jan 22, 2014 at 1:08 PM, Fabian Deutsch fabi...@redhat.com wrote: Am Dienstag, den 21.01.2014, 11:33 +0500 schrieb Nauman Abbas: Hello there I'm facing this problem and this has happened to me multiple times on different machines. I have two hard drives in my system (lets say HDD A and HDD B). I boot the system from the oVirt node CD to install it. Now I want the bootloader and the node installation both to go on HDD B and not HDD A. When I get to the screen which asks me to select the hard-drive for bootloader I use the arrow keys to select HDD B and press Enter (have also tried pressing space or just use tab and continue while it's selected). Then I get to the screen asking where to install the node. I select HDD B and unselect HDD A. I keep the partitioning setup as default ( have also tried manual and kept 5GB unused on HDD A). When I get to install part. It installs the node fine on HDD B as expected but it always gets the boot-loader on HDD A. This issue has wasted many of my days on different machines and I can't seem to find a way around. Nauman, what oVirt Node version were you using? - fabian Nauman Abbas Assistant System Administrator (LMS), Room No. A-207, SEECS, National University of Sciences Technology, + 92 321 5359946 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Nauman Abbas Assistant System Administrator (LMS), Room No. A-207, SEECS, National University of Sciences Technology, + 92 321 5359946 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Vm's being paused
Thanks for the replies guys, Looking at my two VM's that have paused so far through the oVirt GUI the following sizes show under Disks. VM Reports: Virtual Size 35GB, Actual Size 41GB Looking on the Centos OS side, Disk size is 33G and used is 12G with 19G available (40%) usage. VM Babbage: Virtual Size is 40GB, Actual Size 53GB On the Server 2003 OS side, Disk size is 39.9Gb and used is 16.3G, so under 50% usage. Do you see any issues with the above stats? Then my main Datacenter storage is as follows... Size: 6887 GB Available: 1948 GB Used: 4939 GB Allocated: 1196 GB Over Allocation: 61% Could there be a problem here? I can allocate additional LUNS if you feel the space isn't correctly allocated. Apologies for going on about this, but I'm really concerned that something isn't right and I might have a serious problem if an important machine locks up. Thank you and much appreciated. Regards. Neil Wilson. On Tue, Jan 21, 2014 at 7:02 PM, Dafna Ron d...@redhat.com wrote: the storage space is configured in percentages and not physical size. so if 20G is less than 10% (default config) of your storage it will pause the vms regardless of how much GB you still have. this is configurable though so you can change it to less than 10% if you like. to answer the second question, vm's will not pause on ENOSpace error if they run out of space internally but only if the external storage cannot be consumed. so only if you run out of space in the storage and and not if vm runs out of space in its on fs. On 01/21/2014 09:51 AM, Neil wrote: Hi Dan, Sorry, attached is engine.log I've taken out the two sections where each of the VM's were paused. Does the error VM babbage has paused due to no Storage space error mean the main storage domain has run out of storage, or that the VM has run out? Both VM's appear to have been running on node01 when they were paused. My vdsm versions are all... vdsm-cli-4.13.0-11.el6.noarch vdsm-python-cpopen-4.13.0-11.el6.x86_64 vdsm-xmlrpc-4.13.0-11.el6.noarch vdsm-4.13.0-11.el6.x86_64 vdsm-python-4.13.0-11.el6.x86_64 I currently have a 61% over allocation ratio on my primary storage domain, with 1948GB available. Thank you. Regards. Neil Wilson. On Tue, Jan 21, 2014 at 11:24 AM, Neil nwilson...@gmail.com wrote: Hi Dan, Sorry for only coming back to you now. The VM's are thin provisioned. The Server 2003 VM hasn't run out of disk space there is about 20Gigs free, and the usage barely grows as the VM only shares printers. The other VM that paused is also on thin provisioned disks and also has plenty space, this guest is running Centos 6.3 64bit and only runs basic reporting. After the 2003 guest was rebooted, the network card showed up as unplugged in ovirt, and we had to remove it, and re-add it again in order to correct the issue. The Centos VM did not have the same issue. I'm concerned that this might happen to a VM that's quite critical, any thoughts or ideas? The only recent changes have been updating from Dreyou 3.2 to the official Centos repo and updating to 3.3.1-2. Prior to updating I haven't had this issue. Any assistance is greatly appreciated. Thank you. Regards. Neil Wilson. On Sun, Jan 19, 2014 at 8:20 PM, Dan Yasny dya...@gmail.com wrote: Do you have the VMs on thin provisioned storage or sparse disks? Pausing happens when the VM has an IO error or runs out of space on the storage domain, and it is done intentionally, so that the VM will not experience a disk corruption. If you have thin provisioned disks, and the VM writes to it's disks faster than the disks can grow, this is exactly what you will see On Sun, Jan 19, 2014 at 10:04 AM, Neil nwilson...@gmail.com wrote: Hi guys, I've had two different Vm's randomly pause this past week and inside ovirt the error received is something like 'vm ran out of storage and was paused'. Resuming the vm's didn't work and I had to force them off and then on which resolved the issue. Has anyone had this issue before? I realise this is very vague so if you could please let me know which logs to send in. Thank you Regards. Neil Wilson ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt 3.4.0 beta is now available
The oVirt team is pleased to announce that the 3.4.0 Release is now available in beta 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. A new repository ovirt-3.4.0-prerelease has been added for delivering this beta and future refreshes until release candidate. A new oVirt Node build will be available soon as well. You're welcome to join us testing this beta release in tomorrow test day [2]! [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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt 3.3.3 Release Candidate is now available
The oVirt team is pleased to announce that the 3.3.3 Release Candidate is now available in ovirt-updates-testing [1]. Feel free to join us testing it[2] and verifying the bugzilla entries actually under verification [3]. Release notes for this update are available on the wiki [4]. A new oVirt Node build will be available soon as well. [1] http://resources.ovirt.org/releases/updates-testing [2] http://www.ovirt.org/Testing/Ovirt_3.3.3_testing [3] http://red.ht/KEesdK [4] 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Vm's being paused
Thanks Neil, but looking at the logs you sent the ERROR on the vm's have started long before. Can you please to grep this thread from all the logs? Thread-286029: (it's for vm 2736197b-6dc3-4155-9a29-9306ca64881d) lets try to see when the ERROR started for this thread. Thanks, Dafna On 01/22/2014 01:14 PM, Neil wrote: Hi Dafna, Thanks. The vdsm logs are quite large, so I've only attached the logs for the pause of the VM called Babbage on the 19th of Jan. As for snapshots, Babbage has one from June 2013 and Reports has two from June and Oct 2013. I'm using FC storage, with 11 VM's and 3 nodes/hosts, 9 of the 11 VM's have thin provisioned disks. Please shout if you'd like any further info or logs. Thank you. Regards. Neil Wilson. On Wed, Jan 22, 2014 at 10:58 AM, Dafna Ron d...@redhat.com wrote: Hi Neil, Can you please attach the vdsm logs? also, as for the vm's, do they have any snapshots? from your suggestion to allocate more luns, are you using iscsi or FC? Thanks, Dafna On 01/22/2014 08:45 AM, Neil wrote: Thanks for the replies guys, Looking at my two VM's that have paused so far through the oVirt GUI the following sizes show under Disks. VM Reports: Virtual Size 35GB, Actual Size 41GB Looking on the Centos OS side, Disk size is 33G and used is 12G with 19G available (40%) usage. VM Babbage: Virtual Size is 40GB, Actual Size 53GB On the Server 2003 OS side, Disk size is 39.9Gb and used is 16.3G, so under 50% usage. Do you see any issues with the above stats? Then my main Datacenter storage is as follows... Size: 6887 GB Available: 1948 GB Used: 4939 GB Allocated: 1196 GB Over Allocation: 61% Could there be a problem here? I can allocate additional LUNS if you feel the space isn't correctly allocated. Apologies for going on about this, but I'm really concerned that something isn't right and I might have a serious problem if an important machine locks up. Thank you and much appreciated. Regards. Neil Wilson. On Tue, Jan 21, 2014 at 7:02 PM, Dafna Ron d...@redhat.com wrote: the storage space is configured in percentages and not physical size. so if 20G is less than 10% (default config) of your storage it will pause the vms regardless of how much GB you still have. this is configurable though so you can change it to less than 10% if you like. to answer the second question, vm's will not pause on ENOSpace error if they run out of space internally but only if the external storage cannot be consumed. so only if you run out of space in the storage and and not if vm runs out of space in its on fs. On 01/21/2014 09:51 AM, Neil wrote: Hi Dan, Sorry, attached is engine.log I've taken out the two sections where each of the VM's were paused. Does the error VM babbage has paused due to no Storage space error mean the main storage domain has run out of storage, or that the VM has run out? Both VM's appear to have been running on node01 when they were paused. My vdsm versions are all... vdsm-cli-4.13.0-11.el6.noarch vdsm-python-cpopen-4.13.0-11.el6.x86_64 vdsm-xmlrpc-4.13.0-11.el6.noarch vdsm-4.13.0-11.el6.x86_64 vdsm-python-4.13.0-11.el6.x86_64 I currently have a 61% over allocation ratio on my primary storage domain, with 1948GB available. Thank you. Regards. Neil Wilson. On Tue, Jan 21, 2014 at 11:24 AM, Neil nwilson...@gmail.com wrote: Hi Dan, Sorry for only coming back to you now. The VM's are thin provisioned. The Server 2003 VM hasn't run out of disk space there is about 20Gigs free, and the usage barely grows as the VM only shares printers. The other VM that paused is also on thin provisioned disks and also has plenty space, this guest is running Centos 6.3 64bit and only runs basic reporting. After the 2003 guest was rebooted, the network card showed up as unplugged in ovirt, and we had to remove it, and re-add it again in order to correct the issue. The Centos VM did not have the same issue. I'm concerned that this might happen to a VM that's quite critical, any thoughts or ideas? The only recent changes have been updating from Dreyou 3.2 to the official Centos repo and updating to 3.3.1-2. Prior to updating I haven't had this issue. Any assistance is greatly appreciated. Thank you. Regards. Neil Wilson. On Sun, Jan 19, 2014 at 8:20 PM, Dan Yasny dya...@gmail.com wrote: Do you have the VMs on thin provisioned storage or sparse disks? Pausing happens when the VM has an IO error or runs out of space on the storage domain, and it is done intentionally, so that the VM will not experience a disk corruption. If you have thin provisioned disks, and the VM writes to it's disks faster than the disks can grow, this is exactly what you will see On Sun, Jan 19, 2014 at 10:04 AM, Neil nwilson...@gmail.com wrote: Hi guys, I've had two different Vm's randomly pause this past week and inside ovirt the error received is something like 'vm ran out of storage and was paused'. Resuming the vm's didn't work and I had to force them off
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 I didn't found any info about additional repositories in release notes ... Thanks Martin Perina - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: annou...@ovirt.org, arch a...@ovirt.org, Users@ovirt.org, engine-devel engine-de...@ovirt.org Sent: Wednesday, January 22, 2014 11:56:19 AM Subject: [Engine-devel] oVirt 3.4.0 beta is now available The oVirt team is pleased to announce that the 3.4.0 Release is now available in beta 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. A new repository ovirt-3.4.0-prerelease has been added for delivering this beta and future refreshes until release candidate. A new oVirt Node build will be available soon as well. You're welcome to join us testing this beta release in tomorrow test day [2]! [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 ___ Engine-devel mailing list engine-de...@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 I didn't found any info about additional repositories in release notes ... Thanks Martin Perina - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: annou...@ovirt.org, arch a...@ovirt.org, Users@ovirt.org, engine-devel engine-de...@ovirt.org Sent: Wednesday, January 22, 2014 11:56:19 AM Subject: [Engine-devel] oVirt 3.4.0 beta is now available The oVirt team is pleased to announce that the 3.4.0 Release is now available in beta 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. A new repository ovirt-3.4.0-prerelease has been added for delivering this beta and future refreshes until release candidate. A new oVirt Node build will be available soon as well. You're welcome to join us testing this beta release in tomorrow test day [2]! [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 ___ Engine-devel mailing list engine-de...@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Centos 6.5 and bonding: A slave interface is not properly configured
On Wed, Jan 22, 2014 at 07:43:52AM +, Karli Sjöberg wrote: On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote: Hello: I am having problems with bonding I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70. Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error: A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly) Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1. This is my network config: ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no No others ifcfg-* files. I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report? Thanks! Federico PD: Sorry for my basic english I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up: http://www.ovirt.org/Bonding_VLAN_Bridge Hope this helps! Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where 2 is the vlan id of your manamgement network), and from there on, do all configuration via Engine. I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure. One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] fencing: HP ilo100 status does NMI, reboots computer
I am having trouble getting fencing to work on my HP DL180 g6 servers. They have ilo100 controllers. The documentation mentions ipmi compliance, but there are problems. The ipmilan driver gets a response, but it is the wrong response. A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have). Here are some log excerpts: 16:33 just after re-running re-install from engine, which ended: *From oVirt GUI Events tab *Host s1 installed State was set to up for host s1. Host s3 from cluster Default was *chosen* as a proxy to execute Status command on Host s1 Host s1 power management was verified successfully 16:34 *on ssh screen:* Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Uhhuh. NMI received for unknown reason 31 on CPU 0. Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Do you have a strange power saving mode enabled? Message from syslogd@s1 at Jan 21 16:34:14 ... kernel:Dazed and confused, but trying to continue ***from IPMI web interface event log:* Generic 01/21/2014 21:34:15Gen ID 0x21 Bus Uncorrectable Error Assertion Generic 01/21/2014 21:34:15IOH_NMI_DETECT State Asserted Assertion * From oVirt GUI Events tab *Host s1 is non responsive Host s3 from cluster Default was chosen as a proxy to execute Restart command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Stop command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s1 was stopped by engine Manual fence for host s1 was started Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Start command on Host s1 Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 Host s1 was started by engine Host s1 is rebooting State was set to up for host s1. Host s3 from cluster Default was chosen as a proxy to execute Status command on Host s1 16:41 saw kernel panic output on remote KVM terminal computer rebooted itself I have searched for ilo100, but find nothing related to ovirt, so am clueless as to what is the correct driver for this hardware. So far I have seen this mostly on server1 (s1), but that is also the one I have cycled up and down most often. I have also seen where the commands are apparently issued too fast (these servers are fairly slow booting). For example, I found that one server was powered down when the boot process had gotten to the stage where the RAID controller screen was up, so it had not had time to complete the boot that was already in progress. Ted Miller Elkhart, IN, USA ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
Hi, was this resolved for EL 6.5? I'm currently planning to roll out EL 6.5 Nodes and would like to know how to circumvent this issue if it is still present? Am 05.12.2013 12:13, schrieb Martijn Grendelman: I have the same issue on a CentOS node after updating it to 6.5: Resolving Dependencies -- Running transaction check --- Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted --- Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting -- Finished Dependency Resolution Dependencies Resolved Package Arch Version Repository Size Installing: vdsm-python-cpopenx86_64 4.13.0-11.el6ovirt-stable 19 k replacing python-cpopen.x86_64 1.2.3-4.el6 Transaction Summary Install 1 Package(s) Total download size: 19 k Is this ok [y/N]: y On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on. Vinzenz Feenstra schreef op 5-12-2013 8:34: Forwading to vdsm-devel On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: Hello, since yesterday evening I have this sort of dependency problem with updates yum update say Resolving Dependencies -- Running transaction check --- Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting --- Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted -- Finished Dependency Resolution Dependencies Resolved = Package Arch Version Repository Size = Installing: python-cpopenx86_64 1.2.3-4.fc19updates 19 k replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 Transaction Summary = Install 1 Package If I go ahead and run yum update again I have: Dependencies Resolved = PackageArch Version RepositorySize = Installing: vdsm-python-cpopen x86_64 4.13.0-11.fc19 ovirt-stable 20 k replacing python-cpopen.x86_64 1.2.3-4.fc19 Transaction Summary = Install 1 Package and so again in a loop Gianluca -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt Weekly Meeting Minutes -- 2014-01-22
Minutes:http://ovirt.org/meetings/ovirt/2014/ovirt.2014-01-22-15.02.html Minutes (text): http://ovirt.org/meetings/ovirt/2014/ovirt.2014-01-22-15.02.txt Log: http://ovirt.org/meetings/ovirt/2014/ovirt.2014-01-22-15.02.log.html = #ovirt: oVirt Weekly Sync = Meeting started by doron at 15:02:34 UTC. The full logs are available at http://ovirt.org/meetings/ovirt/2014/ovirt.2014-01-22-15.02.log.html . Meeting summary --- * Agenda and roll Call (doron, 15:02:46) * 3.3 update releases (doron, 15:02:47) * 3.4 progress (doron, 15:02:49) * conferences and workshops (doron, 15:02:50) * infra update (doron, 15:02:52) * other topics (doron, 15:02:53) * 3.3 update releases (doron, 15:04:18) * 3.3.3 RC has been released and announced (doron, 15:04:46) * 3.3.2 is currently broken on Fedora due to a recent change in python-cpopen (doron, 15:06:40) * 3.4 progress (doron, 15:14:56) * 3.4.0 beta has been released and announced (doron, 15:15:25) * all-in-one broken in 3.4. Please do not use for now. (doron, 15:17:51) * gluster 3.4 status: Async tasks is in, Volume capacity did not make in. Need to sync on gluster 3.5 and ovirt 3.4 status. (doron, 15:25:00) * infra 3.4 status: SNMP in progress, password change url on login failure when password expires - in develop progress. (doron, 15:27:11) * integration 3.4 status: dwh and hosted engine are in today beta on both centos and fedora 19. jasper server has been ported to centos. reports and virtual appliance are being worked on. (doron, 15:29:17) * network 3.4 status: Labels are ready. migration issue with the Neutron security groups and iproute2 issues became non-blocker bugs. (doron, 15:32:51) * pps 3.4 status: no changes since last week. A few patches being reviewed, non-blocking. (doron, 15:37:23) * sla 3.4 status: hosted engine maintenance still not in- awaiting vdsm maintainers. (doron, 15:40:45) * storage 3.4 status: multipath in. Multiple storage domains merged to master and should be ported. getting rid of storage pool metadata on master storage domain in progress. (doron, 15:43:40) * : ux 3.4 status: 4 features made it in. (doron, 15:44:37) * virt 3.4 status: hotplug merged to master, 3.4 porting in progress. vminit and template versions in progress. (doron, 15:46:06) * 3.4 test day (doron, 15:46:33) * mailing list notified about test day details (doron, 15:47:47) * wiki page being updated. (doron, 15:48:00) * everyone are invited to join us tomorrow. For details please check the mail. Thanks! (doron, 15:49:06) * conferences and workshops (doron, 15:49:36) * fosdem arrangments done. You're all welcome tojoin us in the stand and sessions and social event. (doron, 15:51:36) * bkp to give an Ovirt session in SCALE. (doron, 15:52:00) * infra update (doron, 15:52:55) * LINK: http://lists.ovirt.org/pipermail/infra/2014-January/005064.html (orc_orc, 15:53:22) * In no particular order:Kimchi asks for jenkins coverage #105 (orc_orc, 15:53:49) * ditto standing up an Ubuntu test instance was requested (orc_orc, 15:54:08) * other topics (doron, 16:00:54) Meeting ended at 16:12:39 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * doron (139) * sbonazzo (39) * orc_orc (36) * mskrivanek (15) * ybronhei (12) * apuimedo (11) * bkp (10) * sgotliv (10) * lvernia (9) * kanagaraj (8) * lbianc (8) * eedri (7) * itamar (4) * gtemple (4) * ovirtbot (4) * ybronhei1 (3) * ecohen (3) * freax1 (2) * dneary (2) * BruceShi (2) * vitorlima (2) * ovedo (1) * sherold (1) * danken (1) * alonbl (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] no new mom for ovirt?
On 22/01/14 03:12 -0500, Doron Fediuck wrote: - Original Message - From: Sven Kieske s.kie...@mittwald.de To: Users@ovirt.org List Users@ovirt.org Sent: Tuesday, January 21, 2014 6:45:10 PM Subject: [Users] no new mom for ovirt? Hi, I just checked this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1025845 This is closed for RedHat but afaik not for upstream. It mentions the fixed mom version: mom-0.3.2-8.el6ev but on resources.ovirt.org I find just older versions like http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm so downstream (payed) red hat has newer versions than upstream how can that be? Or am I looking in the wrong repo? Should this not be hosted on ovirt.org repo? Hi Sven! Thanks for bringing this up. You have stumbled upon our completely broken mom build process in oVirt. Part of the problem stems from the fact that MOM is a standalone package (available in upstream Fedora) which is being rebuilt by oVirt. The Fedora releases have typically been much slower than the oVirt releases (and different people are doing each). Here's what we are doing to fix the issues: - Fix the MOM build system (merged) - Create branches in the MOM repo for ovirt releases (in progress) - I will be taking responsibility for oVirt releases of MOM in addition to the Fedora package itself. These changes should lead to a normalized release process for MOM and ensure that built packages for all supported oVirt releases will be made available on resources.ovirt.org. Up until very recently, all MOM development has been done in a single branch. As a workaround for your issue you can build your own rpm from git (use the v0.3.2-stable tag) or grab this [1] nightly build. [1] http://resources.ovirt.org/releases/nightly/rpm/EL/6Server/noarch/mom-0.3.2-20140120.gitfd877c5.el6.noarch.rpm Sorry for all of the confusion! ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Centos 6.5 and bonding: A slave interface is not properly configured
On 22/01/14 12:13, Dan Kenigsberg wrote: On Wed, Jan 22, 2014 at 07:43:52AM +, Karli Sjöberg wrote: On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote: Hello: I am having problems with bonding I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70. Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error: A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly) Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine. Today I solved the issue copying the network config of other host (same hardware), and it worked. The supervdsm.log whith the lines logged yesterday: http://pastebin.com/kpXrRd2w It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive. Thanks I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1. This is my network config: ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no No others ifcfg-* files. I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report? Thanks! Federico PD: Sorry for my basic english I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up: http://www.ovirt.org/Bonding_VLAN_Bridge Hope this helps! Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where 2 is the vlan id of your manamgement network), and from there on, do all configuration via Engine. I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure. One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default. Dan. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] no new mom for ovirt?
Hi, thanks for the exhaustive answer again. But is the mom release all? are the related changes to the guest agent and to vdsm also released? in which version? Also I think this: http://rhn.redhat.com/errata/RHEA-2014-0064.html is incorrect, as it states that this is fixed in the mom release, but it isn't. it relies on swap information from guest-agent which also needs an upgrade (if the guest has swap configured). I think there is some lack of documentation around this. Which version of vdsm and guest agent do you need to use this new mom? Am 22.01.2014 17:52, schrieb Adam Litke: On 22/01/14 03:12 -0500, Doron Fediuck wrote: - Original Message - From: Sven Kieske s.kie...@mittwald.de To: Users@ovirt.org List Users@ovirt.org Sent: Tuesday, January 21, 2014 6:45:10 PM Subject: [Users] no new mom for ovirt? Hi, I just checked this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1025845 This is closed for RedHat but afaik not for upstream. It mentions the fixed mom version: mom-0.3.2-8.el6ev but on resources.ovirt.org I find just older versions like http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm so downstream (payed) red hat has newer versions than upstream how can that be? Or am I looking in the wrong repo? Should this not be hosted on ovirt.org repo? Hi Sven! Thanks for bringing this up. You have stumbled upon our completely broken mom build process in oVirt. Part of the problem stems from the fact that MOM is a standalone package (available in upstream Fedora) which is being rebuilt by oVirt. The Fedora releases have typically been much slower than the oVirt releases (and different people are doing each). Here's what we are doing to fix the issues: - Fix the MOM build system (merged) - Create branches in the MOM repo for ovirt releases (in progress) - I will be taking responsibility for oVirt releases of MOM in addition to the Fedora package itself. These changes should lead to a normalized release process for MOM and ensure that built packages for all supported oVirt releases will be made available on resources.ovirt.org. Up until very recently, all MOM development has been done in a single branch. As a workaround for your issue you can build your own rpm from git (use the v0.3.2-stable tag) or grab this [1] nightly build. [1] http://resources.ovirt.org/releases/nightly/rpm/EL/6Server/noarch/mom-0.3.2-20140120.gitfd877c5.el6.noarch.rpm Sorry for all of the confusion! -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Ovirt 3.3.2. and vdsm 4.14
Hello: Why Ovirt 3.3.2. installs vdsm 4.14 on Centos 6.5?? I am installing 5 nodes with Centos 6.5. I have installed two nodes, I have added: 1 - epel repo (http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm) 2 - ovirt repo (http://ovirt.org/releases/ovirt-release-el.noarch.rpm) In the two first nodes Ovirt engine installed vdsm 4.13. Now I have installed the third node with the same repos and Ovirt installs vdsm 4.14 and when it tries to activate the node complains about the vdsm version, it says that vdsm version is not compatible: Host my-third-node is installed with VDSM version (4.14) and cannot join cluster Cluster-XXX which is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. /etc/yum.repos.d in the trhee nodes are the same: CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo el6-ovirt.repo epel.repo epel-testing.repo glusterfs-epel.repo Why the difference? It is not suppossed that oVirt 3.3.2 should install vdsm 3.13 ?? Thanks, Federico ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Blank VM Install Console
Hi Michal, I am starting from scratch. I set the console to SPICE and restarted the VM. Now if I choose Browser plugin as console option, there is a pop up window saying setting up spice then an error message saying it's fail to connect to the graphics server. I guess this might be because my browser machine doesn't have connection to the ovirt-node machine. It has to go through ovirt-engine machine If I choose SPICE HTML5, then a new browser window shows up but it remains dark. I can't see anything. Any idea what's wrong or missing? I don't see an Spice proxy option. So which option should I use to fit into my setup? None of them seems to work so far. I 'd like to pick the most promising one and pursue it further. Thanks. - Original Message - From: Michal Skrivanek michal.skriva...@redhat.com To: David Li david...@sbcglobal.net Cc: Itamar Heim ih...@redhat.com; d...@redhat.com d...@redhat.com; users@ovirt.org List users@ovirt.org Sent: Tuesday, January 21, 2014 3:03 PM Subject: Re: [Users] Blank VM Install Console On 21 Jan 2014, at 23:18, David Li david...@sbcglobal.net wrote: Hi Michal, Should I use SPICE as console protocol in order to use web proxy? It's for both noVNC and SPICE-HTML5 client Not for virt-viewer or custom native vnc clients Spice proxy would be for similar network layout but native spice client (remote-viewer or firefox/IE plugin) I may have missed that info earlier, are you trying to use browser clients? Those need the websocket translation. Or regular/stable way via standalone client(that's still the predefined default) On my engine, I have: WebSocketProxy: Engine:6100 version: general WebSocketProxyTicketValiditySeconds: 120 version: general So is Webproxy using port 6100? Yes - Original Message - From: Michal Skrivanek michal.skriva...@redhat.com To: David Li david...@sbcglobal.net Cc: Itamar Heim ih...@redhat.com; d...@redhat.com d...@redhat.com; users@ovirt.org List users@ovirt.org Sent: Tuesday, January 21, 2014 2:09 PM Subject: Re: [Users] Blank VM Install Console On 21 Jan 2014, at 22:57, David Li david...@sbcglobal.net wrote: Hi Michal, Itamar asked me to write to you about how to use WebProxy to access the VM console. I have a set up like this on three different physical servers: Browser (RHEL6, firefox 24.2.0) --- ovirt-engine --- host (CPU) However the browser machine doesn't have direct connection to the host. It can only go through ovirt-engine machine to access the host. It might be for this reason that I have failed in using SPICE and VNC to see the VM console. Is websocket proxy the viable solution in this case? What are the steps to set up such a connection? Any pointers? Yes, that's fine, this is the default deployment/installation. You sure you opened firewall for websocket proxy? Is is running? Engine-config's WebsocketProxy(or similar) parameter points to the right thing? Thanks, michal Thanks David - Original Message - From: Itamar Heim ih...@redhat.com To: David Li david...@sbcglobal.net; d...@redhat.com d...@redhat.com; Michal Skrivanek mskri...@redhat.com Cc: users@ovirt.org List users@ovirt.org Sent: Tuesday, January 21, 2014 12:34 PM Subject: Re: [Users] Blank VM Install Console On 01/21/2014 10:31 PM, David Li wrote: Dafna, I have restarted the host and now started to install the Vm from scratch. Following Itamar's suggestion this time, I chose VNC as console option. How can I use vnc viewer to attach to the VM? I don't remember if virt-viewer detects the vnc in the .vv file. but you should have the vnc password and connection details in the vv file to manually connect for sake of testing. you should also be able to use ovirt cli utility to connect to a vm which will launch vnc as well (iirc, via virt-viewer, not vnc viewer) David - Original Message - From: Dafna Ron d...@redhat.com To: Michal Skrivanek mskri...@redhat.com Cc: David Li david...@sbcglobal.net; users@ovirt.org List users@ovirt.org Sent: Tuesday, January 21, 2014 9:38 AM Subject: Re: [Users] Blank VM Install Console David, Let's try to debug the issue you have now. Can you please attach engine and vdsm logs? Thanks, Dafna On 01/21/2014 05:32 PM, Michal Skrivanek wrote: On 21 Jan 2014, at 18:26, David Li david...@sbcglobal.net wrote: Before the VM install console problem, everything was normal, the cpu, host, storage were done following the quick start guide. Well, whatever is the reason the symptoms you see suggests something is either crashing (vdsm on the host) or is unreachable or misconfigured now. Depends what you did...:) Might be easier to start from scratch if
Re: [Users] no new mom for ovirt?
On 22/01/14 17:15 +, Sven Kieske wrote: Hi, thanks for the exhaustive answer again. But is the mom release all? are the related changes to the guest agent and to vdsm also released? in which version? Also I think this: http://rhn.redhat.com/errata/RHEA-2014-0064.html is incorrect, as it states that this is fixed in the mom release, but it isn't. it relies on swap information from guest-agent which also needs an upgrade (if the guest has swap configured). I think there is some lack of documentation around this. Which version of vdsm and guest agent do you need to use this new mom? Adding Martin who should be able to answer these questions better than I... Am 22.01.2014 17:52, schrieb Adam Litke: On 22/01/14 03:12 -0500, Doron Fediuck wrote: - Original Message - From: Sven Kieske s.kie...@mittwald.de To: Users@ovirt.org List Users@ovirt.org Sent: Tuesday, January 21, 2014 6:45:10 PM Subject: [Users] no new mom for ovirt? Hi, I just checked this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1025845 This is closed for RedHat but afaik not for upstream. It mentions the fixed mom version: mom-0.3.2-8.el6ev but on resources.ovirt.org I find just older versions like http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm so downstream (payed) red hat has newer versions than upstream how can that be? Or am I looking in the wrong repo? Should this not be hosted on ovirt.org repo? Hi Sven! Thanks for bringing this up. You have stumbled upon our completely broken mom build process in oVirt. Part of the problem stems from the fact that MOM is a standalone package (available in upstream Fedora) which is being rebuilt by oVirt. The Fedora releases have typically been much slower than the oVirt releases (and different people are doing each). Here's what we are doing to fix the issues: - Fix the MOM build system (merged) - Create branches in the MOM repo for ovirt releases (in progress) - I will be taking responsibility for oVirt releases of MOM in addition to the Fedora package itself. These changes should lead to a normalized release process for MOM and ensure that built packages for all supported oVirt releases will be made available on resources.ovirt.org. Up until very recently, all MOM development has been done in a single branch. As a workaround for your issue you can build your own rpm from git (use the v0.3.2-stable tag) or grab this [1] nightly build. [1] http://resources.ovirt.org/releases/nightly/rpm/EL/6Server/noarch/mom-0.3.2-20140120.gitfd877c5.el6.noarch.rpm Sorry for all of the confusion! -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates)
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
Re: [Users] fencing: HP ilo100 status does NMI, reboots computer
Ted Miller wrote: I am having trouble getting fencing to work on my HP DL180 g6 servers. They have ilo100 controllers. The documentation mentions ipmi compliance, but there are problems. The ipmilan driver gets a response, but it is the wrong response. A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have). Thats weird. I have 2 ML110 G6 desktop servers, as storage servers, and those have ilo100 controllers too and I just checked and they are setup as ipmilan in engine. I have used the Test button more than once and never had problems. My Summary page says: *IPMI Version:* 2.0 *Firmware Version:* 4.23 *Hardware Version:* 1.0 *Description:* ProLiant ML110 G6 *System GUID:* 33221100-5544-7766-8899-AABBCCDDEEFF Mayb that helps you to track down the problem. If you have got question, please ask. Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message - From: Douglas Schilling Landgraf dougsl...@redhat.com To: Eli Mesika emes...@redhat.com, Sandro Bonazzola sbona...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 9:31:59 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo Thanks, I enabled ovirt-updates-testing in ovirt repo . :-( # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message - From: Eli Mesika emes...@redhat.com To: dougsl...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 9:48:54 PM Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available - Original Message - From: Douglas Schilling Landgraf dougsl...@redhat.com To: Eli Mesika emes...@redhat.com, Sandro Bonazzola sbona...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 9:31:59 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo Thanks, I enabled ovirt-updates-testing in ovirt repo . :-( engine-setup fails with the following error Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed to execute any ideas ? # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available:
[Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
I'm trying to test out the oVirt Hosted Engine, but am experiencing a failure early on and was hoping someone could point me in the right direction. I'm not familiar enough with the architecture of oVirt to start to debug this situation. Basically, I run the hosted-engine --deploy command and it outputs: [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140122110741.log Version: otopi-1.2.0_beta (otopi-1.2.0-0.1.beta.fc19) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140122110741.log has: 2014-01-22 11:07:57 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-22 11:07:57 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File /usr/lib/python2.7/site-packages/otopi/context.py, line 142, in _executeMethod method['method']() File /usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py, line 729, in _customization self._check_existing_pools() File /usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py, line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File /usr/lib64/python2.7/xmlrpclib.py, line 1224, in __call__ return self.__send(self.__name, args) File /usr/lib64/python2.7/xmlrpclib.py, line 1578, in __request verbose=self.__verbose File /usr/lib64/python2.7/xmlrpclib.py, line 1264, in request return self.single_request(host, handler, request_body, verbose) File /usr/lib64/python2.7/xmlrpclib.py, line 1292, in single_request self.send_content(h, request_body) File /usr/lib64/python2.7/xmlrpclib.py, line 1439, in send_content connection.endheaders(request_body) File /usr/lib64/python2.7/httplib.py, line 969, in endheaders self._send_output(message_body) File /usr/lib64/python2.7/httplib.py, line 829, in _send_output self.send(msg) File /usr/lib64/python2.7/httplib.py, line 791, in send self.connect() File /usr/lib64/python2.7/site-packages/vdsm/SecureXMLRPCServer.py, line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File /usr/lib64/python2.7/socket.py, line 571, in create_connection raise err error: [Errno 111] Connection refused 2014-01-22 11:07:57 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused Unfortunately I do not know what service this is trying to connect to, or what hostname or port to try to start debugging that. Some other useful information about my environment: - Fedora 19 (64bit), minimal install, selected 'standard' add-on utilities. This was a fresh install just for this test. - 512MB /boot ext4 - 80GB / ext4 in LVM, 220GB free in VG - yum -y update performed to get all latest updates - SElinux in permissive mode - Hardware: - Supermicro 1026T-URF barebones - single CPU populated (Xeon E5630 4x2.53GHz) - 12GB ECC DDR3 RAM - H/W Raid with SSDs - Networking: - Network Manager DISABLED - 4 GbE ports (p2p1, p2p2, em1, em2) - all 4 ports configured in a bond (bond0) using balance-alb - ovirtmgmt bridge pre-created with 'bond0' as the only member, assigned a static IP address - firewall DISABLED - /etc/yum.repos.d/ovirt.rep has ONLY the 3.4.0 beta repo enabled: [ovirt-3.4.0-beta] name=3.4.0 beta testing repo for the oVirt project
Re: [Users] fencing: HP ilo100 status does NMI, reboots computer
On 1/22/2014 2:44 PM, Joop wrote: Ted Miller wrote: I am having trouble getting fencing to work on my HP DL180 g6 servers. They have ilo100 controllers. The documentation mentions ipmi compliance, but there are problems. The ipmilan driver gets a response, but it is the wrong response. A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have). Thats weird. I have 2 ML110 G6 desktop servers, as storage servers, and those have ilo100 controllers too and I just checked and they are setup as ipmilan in engine. I have used the Test button more than once and never had problems. My Summary page says: *IPMI Version:* 2.0 *Firmware Version:* 4.23 *Hardware Version:* 1.0 *Description:* ProLiant ML110 G6 *System GUID:* 33221100-5544-7766-8899-AABBCCDDEEFF Mayb that helps you to track down the problem. If you have got question, please ask. Joop Joop, thanks for the info. That tells me I was not totally off track when I was trying the ipmilan driver. I have firmware 4.21 in my controllers. I'll have to see about updating that. One thing I have figured out, this problem would not have been so noticeable, except that something is causing host s1 to go non responsive every few hours. That provokes a Restart - Stop - Status - Start sequence from the fencing system. I will have to deal with what is causing the non responsive condition, but first I want to work through the fencing problem. I tried the ilo2 driver, but the test of that produced even more convulsive messages from the computer. Ted Miller ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] membership disabled due to bouces again..
Already spotted this problem before... I just found that I lose e-mails from Tue Jan 21 11:45:10 EST 2014 to Wed Jan 22 15:35:51 EST 2014 And received only some minutes ago (22/Jan/2014 21:26 Italy Time) an e-mail regarding my disabled membership apparently occurred at Mon, Jan 20, 2014 at 4:11 PM so that I didn't either know before Any way to solve this? I have to mix e-mail received and archives... Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Reconfirming membership to do excessive bounces
On Wed, 22 Jan 2014, Pat Pierson wrote: Has anyone else had this issue with this list and gmail? if so how can i fix it? The mailing list host lacks some conventional mail filtering setup values -- Infra is aware of it and has requested the needed changes in DNS, etc As a 'workaround' you can also paw through your gmail 'spam' folder, and add a whitelisting rule, which sometimes works. But google 'tunes' its rules over time, and this can be a non-durable fix until proper A, , PTR, and optionally SPF rules are added -- Russ herrold ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
Hi, This looks like this BZ which I reported https://bugzilla.redhat.com/show_bug.cgi?id=1055153 Did you customize your nics before you tried running hosted-engine --deploy? Thanks, Andrew On Thu, Jan 23, 2014 at 7:32 AM, Brad House b...@monetra.com wrote: I'm trying to test out the oVirt Hosted Engine, but am experiencing a failure early on and was hoping someone could point me in the right direction. I'm not familiar enough with the architecture of oVirt to start to debug this situation. Basically, I run the hosted-engine --deploy command and it outputs: [ INFO ] Stage: Initializing Continuing will configure this host for serving as hypervisor and create a VM where you have to install oVirt Engine afterwards. Are you sure you want to continue? (Yes, No)[Yes]: [ INFO ] Generating a temporary VNC password. [ INFO ] Stage: Environment setup Configuration files: [] Log file: /var/log/ovirt-hosted-engine- setup/ovirt-hosted-engine-setup-20140122110741.log Version: otopi-1.2.0_beta (otopi-1.2.0-0.1.beta.fc19) [ INFO ] Hardware supports virtualization [ INFO ] Bridge ovirtmgmt already created [ INFO ] Stage: Environment packages setup [ INFO ] Stage: Programs detection [ INFO ] Stage: Environment setup [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Waiting for VDSM hardware info [ INFO ] Stage: Environment customization --== STORAGE CONFIGURATION ==-- During customization use CTRL-D to abort. [ ERROR ] Failed to execute stage 'Environment customization': [Errno 111] Connection refused [ INFO ] Stage: Clean up [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20140122110741.log has: 2014-01-22 11:07:57 DEBUG otopi.plugins.ovirt_hosted_engine_setup.storage.storage storage._check_existing_pools:631 getConnectedStoragePoolsList 2014-01-22 11:07:57 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File /usr/lib/python2.7/site-packages/otopi/context.py, line 142, in _executeMethod method['method']() File /usr/share/ovirt-hosted-engine-setup/scripts/../ plugins/ovirt-hosted-engine-setup/storage/storage.py, line 729, in _customization self._check_existing_pools() File /usr/share/ovirt-hosted-engine-setup/scripts/../ plugins/ovirt-hosted-engine-setup/storage/storage.py, line 632, in _check_existing_pools pools = self.serv.s.getConnectedStoragePoolsList() File /usr/lib64/python2.7/xmlrpclib.py, line 1224, in __call__ return self.__send(self.__name, args) File /usr/lib64/python2.7/xmlrpclib.py, line 1578, in __request verbose=self.__verbose File /usr/lib64/python2.7/xmlrpclib.py, line 1264, in request return self.single_request(host, handler, request_body, verbose) File /usr/lib64/python2.7/xmlrpclib.py, line 1292, in single_request self.send_content(h, request_body) File /usr/lib64/python2.7/xmlrpclib.py, line 1439, in send_content connection.endheaders(request_body) File /usr/lib64/python2.7/httplib.py, line 969, in endheaders self._send_output(message_body) File /usr/lib64/python2.7/httplib.py, line 829, in _send_output self.send(msg) File /usr/lib64/python2.7/httplib.py, line 791, in send self.connect() File /usr/lib64/python2.7/site-packages/vdsm/SecureXMLRPCServer.py, line 188, in connect sock = socket.create_connection((self.host, self.port), self.timeout) File /usr/lib64/python2.7/socket.py, line 571, in create_connection raise err error: [Errno 111] Connection refused 2014-01-22 11:07:57 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Environment customization': [Errno 111] Connection refused Unfortunately I do not know what service this is trying to connect to, or what hostname or port to try to start debugging that. Some other useful information about my environment: - Fedora 19 (64bit), minimal install, selected 'standard' add-on utilities. This was a fresh install just for this test. - 512MB /boot ext4 - 80GB / ext4 in LVM, 220GB free in VG - yum -y update performed to get all latest updates - SElinux in permissive mode - Hardware: - Supermicro 1026T-URF barebones - single CPU populated (Xeon E5630 4x2.53GHz) - 12GB ECC DDR3 RAM - H/W Raid with SSDs - Networking: - Network Manager DISABLED - 4 GbE ports (p2p1, p2p2, em1, em2) - all 4 ports
Re: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
On 01/22/2014 05:42 PM, Andrew Lau wrote: Hi, This looks like this BZ which I reported https://bugzilla.redhat.com/show_bug.cgi?id=1055153 Did you customize your nics before you tried running hosted-engine --deploy? Thanks, Andrew Yes, I created all the /etc/sysconfig/network-scripts/ifcfg-* for my 4 NICs in the bond, then also created the ifcfg-bond0, as well as an ifcfg-ovirtmgmt which uses the bond0. So the ovirt management interface should be fully configured before even running the hosted-engine --deploy ... when I was testing the all-in-one (non-hosted) I had to do that, so figured it was a good idea for hosted too. I'm trying to understand your BZ 1055153, did you actually get it to work? Or did you get stuck at that point? I have seen the same issue as your BZ 1055129 as well. -Brad ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] oVirt 3.4.0 issues with storage
Hi all, I upgraded to 3.4 beta this evening and seem to have developed a problem with the storage domains. I seem unable to bring them online getting the error in the console Failed to activate Storage Domain. Also alongside this error is a warning, Invalid status on Data Center local_datacenter. Setting status to Non Responsive Anyone seen this? Or any ideas? Thanks Jon ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Centos 6.5 and bonding: A slave interface is not properly configured
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured
eth0 with the vlan of the management network (Vlan 70). Then I
registered the host to the engine (3.3.2-1-el6) and the engine
installed oVirt in the host without problem. Ovirtmgmt was created
automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But
when I try to bond the nics, I get the next error:
A slave interface is not properly configured. Please verify slaves do
not contain any of the following properties: network name, boot
protocol, IP address, netmask, gateway or vlan-ID notation (as part of
interface's name or explicitly)
Federico, where exactly do you get this error? Would you attach the
setupNetwork log from supervdsmd.log?
I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host
(same hardware), and it worked.
The supervdsm.log whith the lines logged yesterday:
http://pastebin.com/kpXrRd2w
It would be nice if the error could be more explicit, i.e. telling
the ifcfg-* that are conflictive.
I do not understand the error yet... I believe that in the text you have
quoted, Engine complains that an interface has not joined a bond. But
Engine's command to Vdsm
MainProcess|Thread-15::DEBUG::2014-01-21
13:13:21,166::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call
setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'vlan': '70', 'ipaddr':
'192.168.1.101', 'netmask': '255.255.255.0', 'STP': 'no', 'bridged': 'true'}},
{}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}
contains no reference to a bond device, and seems to have succeeded.
One notable problem is that the network definitions lack a 'gateway'
parameter, which is very important for ovirtmgmt.
Would you share your vdsm.log, too? The output of getCapabilities before
and after setupNetworks may shed some light on the circumstances.
Regads,
Dan.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] Centos 6.5: mom spam
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
snip
The supervdsm.log whith the lines logged yesterday:
http://pastebin.com/kpXrRd2w
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21
13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call
ksmTune with ({},) {}
MainProcess|PolicyEngine::DEBUG::2014-01-21
13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return
ksmTune with None
MainProcess|PolicyEngine::DEBUG::2014-01-21
13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call
ksmTune with ({},) {}
MainProcess|PolicyEngine::DEBUG::2014-01-21
13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return
ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I
thought we have solved a similar issue in the past.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.4.0 issues with storage
I think I am getting a little closer.
Somewhere during the upgrade the /etc/exports file was modified, so my
iso directory (/var/lib/exports/iso) was set to none, whereas it was
originally set to 0.0.0.0/0.0.0.0(rw).
I was seeing in the vdsm log that the UID for the ISO_DOMAIN was showing
as not existing:
StorageDomainDoesNotExist: Storage domain does not exist:
('69ea8415-8d33-4d9b-a29b-057970984c99',)
That uid was in the metadata file in the above export.
Now, stranger it seems my export_domain (should be NFS to /data2) path
in the GUI is showing as /var/lib/exports/iso
Getting closer but still not working.
Jon
On 22/01/14 23:24, Jon Archer wrote:
Hi all,
I upgraded to 3.4 beta this evening and seem to have developed a
problem with the storage domains. I seem unable to bring them online
getting the error in the console Failed to activate Storage Domain.
Also alongside this error is a warning, Invalid status on Data Center
local_datacenter. Setting status to Non Responsive
Anyone seen this? Or any ideas?
Thanks
Jon
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.4.0 issues with storage
I rebooted the server (probably could have restarted services) and it
all seems to have come back to life...
Seems to be an issue somewhere in there then
Jon
On 23/01/14 00:44, Jon Archer wrote:
I think I am getting a little closer.
Somewhere during the upgrade the /etc/exports file was modified, so my
iso directory (/var/lib/exports/iso) was set to none, whereas it was
originally set to 0.0.0.0/0.0.0.0(rw).
I was seeing in the vdsm log that the UID for the ISO_DOMAIN was
showing as not existing:
StorageDomainDoesNotExist: Storage domain does not exist:
('69ea8415-8d33-4d9b-a29b-057970984c99',)
That uid was in the metadata file in the above export.
Now, stranger it seems my export_domain (should be NFS to /data2) path
in the GUI is showing as /var/lib/exports/iso
Getting closer but still not working.
Jon
On 22/01/14 23:24, Jon Archer wrote:
Hi all,
I upgraded to 3.4 beta this evening and seem to have developed a
problem with the storage domains. I seem unable to bring them online
getting the error in the console Failed to activate Storage Domain.
Also alongside this error is a warning, Invalid status on Data
Center local_datacenter. Setting status to Non Responsive
Anyone seen this? Or any ideas?
Thanks
Jon
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
On 01/22/2014 03:00 PM, Eli Mesika wrote:
- Original Message -
From: Eli Mesika emes...@redhat.com
To: dougsl...@redhat.com
Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org
Sent: Wednesday, January 22, 2014 9:48:54 PM
Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message -
From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Eli Mesika emes...@redhat.com, Sandro Bonazzola
sbona...@redhat.com
Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org
Sent: Wednesday, January 22, 2014 9:31:59 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli,
On 01/22/2014 01:10 PM, Eli Mesika wrote:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto:
Hi,
I tried to install on F19, but openstack* packages = 3.0.2 are
missing:
thanks, updated release page, it needs updates-testing
I had enabled ovirt-updates-testing and still got this :
Here it worked, without looking your 'yum repolist' output I do guess
you need to enable the repo from:
/etc/yum.repos.d/fedora-updates-testing.repo
Thanks, I enabled ovirt-updates-testing in ovirt repo . :-(
engine-setup fails with the following error
Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed
to execute
any ideas ?
Hi Eli,
Would be nice too see your engine-setup log file to determine which
error happened. Should be available here: /var/log/ovirt-engine/setup/
Anyway, I could reproduce a similar output during a setup (below the
log) and in my case was postgresql with error: FATAL: could not create
shared memory segment: Invalid argument
Resolved with wiki:
http://www.ovirt.org/Troubleshooting#Installation
In session:
I am having trouble connecting to the database. In the system log, I
get the following message from Postgres
@Sandro, should or maybe installer detect this kind of situation?
=
2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stderr:
Job for postgresql.service failed. See 'systemctl status
postgresql.service' and 'journalctl -xn' for details.
2014-01-22 17:37:52 DEBUG otopi.context context._executeMethod:152
method exception
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/otopi/context.py, line 142,
in _executeMethod
method['method']()
File
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py,
line 182, in _misc
self._provisioning.provision()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 552, in provision
self._restart()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 407, in _restart
state=state,
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 138,
in state
'start' if state else 'stop'
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 77,
in _executeServiceCommand
raiseOnError=raiseOnError
File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Misc configuration': Command '/bin/systemctl'
failed to execute
2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131
aborting 'Yum Transaction'
2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:92 Yum Performing yum transaction rollback
Loaded plugins: versionlock
--
Cheers
Douglas
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] oVirt 3.4.0 beta - Hosted Engine Setup -- issues
That sounds exactly what I did, do you mind putting those log files into the BZ saves me from having to find some hardware and replicate it again. So what i did was I ended up just nuking the whole OS, and getting a clean start. First after doing all your initial prep EXCEPT configuring your 4 NICs run the hosted-engine --deploy command twice. Assuming the first run fails always like in my case, else once you get to the Configure Storage phase press Ctrl + D to exit. Now configure your NICs (also configure ovirtmgmt manually as there is another BZ about it not being able to create the bridge) and rerun hosted-engine --deploy and you should be back in action. This should get you to a working hosted-engine solution. P.S. could you add me in the CC when you reply, I would've seen your message sooner. On Thu, Jan 23, 2014 at 9:55 AM, Brad House b...@monetra.com wrote: On 01/22/2014 05:42 PM, Andrew Lau wrote: Hi, This looks like this BZ which I reported https://bugzilla.redhat.com/ show_bug.cgi?id=1055153 Did you customize your nics before you tried running hosted-engine --deploy? Thanks, Andrew Yes, I created all the /etc/sysconfig/network-scripts/ifcfg-* for my 4 NICs in the bond, then also created the ifcfg-bond0, as well as an ifcfg-ovirtmgmt which uses the bond0. So the ovirt management interface should be fully configured before even running the hosted-engine --deploy ... when I was testing the all-in-one (non-hosted) I had to do that, so figured it was a good idea for hosted too. I'm trying to understand your BZ 1055153, did you actually get it to work? Or did you get stuck at that point? I have seen the same issue as your BZ 1055129 as well. -Brad ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] another networking question: ssh to VM with private dhcp addr
Hello, I've got oVirt 3.3.x all-in-one up and running on CentOS 6.3. The IP address on the ovirtmgmt bridge is static/public. I have not done any additional network/VLAN configuration. If I create a VM and give it an address on the same subnet, I can ssh to it just fine. If I create a VM and let it use dhcp, it gets a 172.31.x.x address. Outgoing access works fine, but I can't figure out what to do to allow me to be able to ssh into those VMs. With straight KVM the VM private network was on a virtual interface on the host, making it easy. But I can't figure out how to do it with oVirt. Any help greatly appreciated. Thanks in advance. Robert signature.asc Description: PGP signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] fencing: HP ilo100 status does NMI, reboots computer
Hi, - Original Message - From: Ted Miller tmil...@hcjb.org To: users@ovirt.org Sent: Wednesday, January 22, 2014 10:35:51 PM Subject: Re: [Users] fencing: HP ilo100 status does NMI, reboots computer On 1/22/2014 2:44 PM, Joop wrote: Ted Miller wrote: I am having trouble getting fencing to work on my HP DL180 g6 servers. They have ilo100 controllers. The documentation mentions ipmi compliance, but there are problems. The ipmilan driver gets a response, but it is the wrong response. A status request results in the NMI line being asserted, which (in standard PC architecture) is the same as pressing the reset button (which these servers don't have). Thats weird. I have 2 ML110 G6 desktop servers, as storage servers, and those have ilo100 controllers too and I just checked and they are setup as ipmilan in engine. I have used the Test button more than once and never had problems. My Summary page says: IPMI Version: 2.0 Firmware Version: 4.23 Hardware Version: 1.0 Description:ProLiant ML110 G6 System GUID:33221100-5544-7766-8899-AABBCCDDEEFF Mayb that helps you to track down the problem. If you have got question, please ask. Joop Joop, thanks for the info. That tells me I was not totally off track when I was trying the ipmilan driver. I have firmware 4.21 in my controllers. I'll have to see about updating that. One thing I have figured out, this problem would not have been so noticeable, except that something is causing host s1 to go non responsive every few hours. That provokes a Restart - Stop - Status - Start sequence from the fencing system. I will have to deal with what is causing the non responsive condition, but first I want to work through the fencing problem. I tried the ilo2 driver, but the test of that produced even more convulsive messages from the computer. Note that lo100 - afaik there no such a thing as ilo100 - is unrelated to iLo (whatever version). These are two completely different products - lo100 is on the board of some of the lower-end DL1xx series (and iirc also available as an add-on card) and iLo is on the board of DL3xx series servers. -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
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? Regards, Ramesh - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: arch a...@ovirt.org, engine-devel engine-de...@ovirt.org, Users@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 ___ Arch mailing list a...@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Centos 6.5 and bonding: A slave interface is not properly configured
On Wed, 2014-01-22 at 15:13 +, Dan Kenigsberg wrote: On Wed, Jan 22, 2014 at 07:43:52AM +, Karli Sjöberg wrote: On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote: Hello: I am having problems with bonding I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70. Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error: A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly) Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1. This is my network config: ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no No others ifcfg-* files. I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report? Thanks! Federico PD: Sorry for my basic english I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up: http://www.ovirt.org/Bonding_VLAN_Bridge Hope this helps! Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where 2 is the vlan id of your manamgement network), and from there on, do all configuration via Engine. I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure. Couldn´t agree with you more. But it´s always good to have something to fall back on, if only as reference, I think. One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default. Dan. Does that imply that default gateway is supposed to be on the same net as ovirtmgmt? -- Med Vänliga Hälsningar --- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjob...@slu.se ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 19:10, Eli Mesika ha scritto: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-de...@ovirt.org, Users@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : I mean Fedora updates-testing... However today openstak packages should be available also in Fedora updates repository -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
Re: [Users] oVirt 3.4.0 issues with storage
Hi, - Original Message - From: Jon Archer j...@rosslug.org.uk To: users users@ovirt.org Sent: Thursday, January 23, 2014 2:48:13 AM Subject: Re: [Users] oVirt 3.4.0 issues with storage I rebooted the server (probably could have restarted services) and it all seems to have come back to life... What do you mean by that? Did you manually fix your /etc/exports before rebooting? The path for your export_domain? Also, can you please post the upgrade log? If it indeed trashed your /etc/exports that's a bug, please open a bz for that if possible. Thanks! -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] [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, Users@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Upgrade 3.3 - 3.4
Il 23/01/2014 01:52, Maurice James ha scritto: Anyone else seeing this error on upgrade from 3.3 - 3.4? [ ERROR ] Yum [u'Errors were encountered while downloading packages.', u'ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch: failure: noarch/ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch.rpm from ovirt-3.4.0-prerelease: [Errno 256] No more mirrors to try.'] The rpm is there: http://resources.ovirt.org/releases/3.4.0_pre/rpm/EL/6/noarch/ovirt-engine-backend-3.4.0-0.5.beta1.el6.noarch.rpm please run # yum clean metadata and retry ___ Users mailing list Users@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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] no new mom for ovirt?
Hi Sven, Adam already described the status pretty weel, but I have one remark. Please note that the oVirt release of mom has .githash in its release string. It is true that the release number itself is lower, but the RPM actually contains the same or even newer features than the RHEV package (.el6ev). If you check the packaging guidelines and the version string semantics, you will find out that the NVR as we call it is: name-version-release. Name is obvious, but the relationship between version and release is this: - version is the base version of _upstream_tarball_ that was used to create the package (both packages you mentioned have 0.3.2) - release is distribution specific string (all Fedora, oVirt, RHEV have their own _independent_ sequence) that is increased any time there is a change to the _spec_ file for that distribution, it also usually identifies the distribution using the .dist suffix So when we freeze the version of upstream for a specific distribution, we then add patches to the spec file without modifying the base upstream tarball with sources. That is why the RHEV package has -8 as the release number. So in an ideal world the release and packaging situation looks like this: upstream release: mom-0.3.2.tar.gz (distribution agnostic tarball with sources, if there is .gitXYZ it should be part of the version here) Fedora rpm: mom-0.3.2-X.f20 (version based on upstream, release according to the needs of Fedora) EPEL rpm: mom-0.3.2-X.el6 (version based on upstream, release according to the needs of Fedora) RHEV rpm: mom-0.3.2-Y.el6ev (version based on upstream, release according to the needs of RHEV) oVirt rpms: ideally it should use the packages that were built using the proper distribution build process.. Unfortunately oVirt sometimes needs newer version of some dependencies than what are available in the distributions we build our packages for, so we have to use our own repositories and that causes confusion in versioning. What we should do is to always bump only the version and keep the release as -1. But mom did not do it like that and I think that is what Adam was trying to solve for the past couple of days now. I hope this cleared the confusion a bit. Short summary :) -- Please do not mix version and release as release is distribution specific number and can't be compared to packages for other distributions. -- Martin Sivák msi...@redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ - Original Message - On 22/01/14 17:15 +, Sven Kieske wrote: Hi, thanks for the exhaustive answer again. But is the mom release all? are the related changes to the guest agent and to vdsm also released? in which version? Also I think this: http://rhn.redhat.com/errata/RHEA-2014-0064.html is incorrect, as it states that this is fixed in the mom release, but it isn't. it relies on swap information from guest-agent which also needs an upgrade (if the guest has swap configured). I think there is some lack of documentation around this. Which version of vdsm and guest agent do you need to use this new mom? Adding Martin who should be able to answer these questions better than I... Am 22.01.2014 17:52, schrieb Adam Litke: On 22/01/14 03:12 -0500, Doron Fediuck wrote: - Original Message - From: Sven Kieske s.kie...@mittwald.de To: Users@ovirt.org List Users@ovirt.org Sent: Tuesday, January 21, 2014 6:45:10 PM Subject: [Users] no new mom for ovirt? Hi, I just checked this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1025845 This is closed for RedHat but afaik not for upstream. It mentions the fixed mom version: mom-0.3.2-8.el6ev but on resources.ovirt.org I find just older versions like http://resources.ovirt.org/releases/3.4.0-alpha/rpm/EL/6/noarch/mom-0.3.2-3.16.git97e1741.el6.noarch.rpm so downstream (payed) red hat has newer versions than upstream how can that be? Or am I looking in the wrong repo? Should this not be hosted on ovirt.org repo? Hi Sven! Thanks for bringing this up. You have stumbled upon our completely broken mom build process in oVirt. Part of the problem stems from the fact that MOM is a standalone package (available in upstream Fedora) which is being rebuilt by oVirt. The Fedora releases have typically been much slower than the oVirt releases (and different people are doing each). Here's what we are doing to fix the issues: - Fix the MOM build system (merged) - Create branches in the MOM repo for ovirt releases (in progress) - I will be taking responsibility for oVirt releases of MOM in addition to the Fedora package itself. These changes should lead to a normalized release process for MOM and ensure that built packages for all supported oVirt releases will be made available on resources.ovirt.org. Up until very recently, all MOM development has been done in a single branch. As a workaround for your issue
[Users] ovirt-guest-agent beta1 packages for the ovirt 3.4 testday
Hi, For the today's ovirt 3.4 testday I have prepared repositories for Fedora 19, Fedora 20 and el6/CentOS6: http://evilissimo.fedorapeople.org/repos/ovirt-guest-agent/ovirt-3.4/beta1/ Please let me know if you find any issues. -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
