[ovirt-users] dependency error when upgrade ovirt 3.3 - 3.4 (CentOS)
Hello, I'm trying to upgrade an ovirt 3.3 installation to 3.4, but getting a dependency error. I tried to update the ovirt-engine-setup package to v 3.4.0-1.el6, which requires ovirt-engine-setup-plugin-ovirt-engine = 3.4.0-1.el6, which requires ovirt-engine = 3.3.2. However, it appears that ovirt-engine 3.3 is in the versionlock list and cannot be updated. Should I manually disable the versionlock plugin, or am I missing something? Thanks, Haven ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Unable to Resize VM Disk in oVirt 3.3 (Upgraded from 3.2)
Hello, I upgraded our installation of oVirt from 3.2 to 3.3, and one of the features I was looking forward to was the ability to resize VM disk. However, it appears that the feature is still not available to me. I selected the Virtual Machines tab, selected a VM, selected the Disks sub-tab, and selected a disk; but the Edit button is grayed out. The disk status is OK and the VM status is Up. Help is appreciated. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to Resize VM Disk in oVirt 3.3 (Upgraded from 3.2)
I reinstalled the hosts, and changed DC to 3.3. Both DC and Cluster are reporting Compatibility Version of 3.3 On Sep 24, 2013, at 11:26 AM, Itamar Heim ih...@redhat.com wrote: On 09/24/2013 07:15 PM, H. Haven Liu wrote: Hello, I upgraded our installation of oVirt from 3.2 to 3.3, and one of the features I was looking forward to was the ability to resize VM disk. However, it appears that the feature is still not available to me. I selected the Virtual Machines tab, selected a VM, selected the Disks sub-tab, and selected a disk; but the Edit button is grayed out. The disk status is OK and the VM status is Up. Help is appreciated. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users did you also upgrade the cluster and DC to 3.3 (changing compatibility level, after hosts were upgraded to 3.3 vdsm)? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Unable to Resize VM Disk in oVirt 3.3 (Upgraded from 3.2)
Apparently I needed to logout and log back in? Because after that, the edit button is no longer grayed out! On Sep 24, 2013, at 12:16 PM, H. Haven Liu haven@ucla.edu wrote: I reinstalled the hosts, and changed DC to 3.3. Both DC and Cluster are reporting Compatibility Version of 3.3 On Sep 24, 2013, at 11:26 AM, Itamar Heim ih...@redhat.com wrote: On 09/24/2013 07:15 PM, H. Haven Liu wrote: Hello, I upgraded our installation of oVirt from 3.2 to 3.3, and one of the features I was looking forward to was the ability to resize VM disk. However, it appears that the feature is still not available to me. I selected the Virtual Machines tab, selected a VM, selected the Disks sub-tab, and selected a disk; but the Edit button is grayed out. The disk status is OK and the VM status is Up. Help is appreciated. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users did you also upgrade the cluster and DC to 3.3 (changing compatibility level, after hosts were upgraded to 3.3 vdsm)? ___ 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] Update from 3.2 to 3.3 (CentOS 6.4)
Apparently that's not it. I reinstalled the hosts and managed to get the DC to v3.3, and the VMs are showing up as Cluster Compatibility Version: 3.3, but resize Disk is still no-go. On Sep 23, 2013, at 9:13 AM, Mike Burns mbu...@redhat.com wrote: On 09/23/2013 12:11 PM, H. Haven Liu wrote: I was able to upgrade with engine-setup after running yum update ovirt-engine-setup as requested. The upgrade processes completed successfully (at least according to [ INFO ] Execution of upgrade completed successfully) However, it appears I'm unable to gain the benefits of 3.3, such as Online Virtual Drive Resize[1], which I'm guessing has something to do with that my VMs still report that the Cluster Compatibility Version as 3.2. Is there any way to update the VMs or otherwise enable that feature? [1]http://www.ovirt.org/Features/Online_Virtual_Drive_Resize On Sep 23, 2013, at 5:11 AM, Mike Burns mbu...@redhat.com mailto:mbu...@redhat.com wrote: On 09/23/2013 03:51 AM, Sandro Bonazzola wrote: Il 17/09/2013 00:48, Mike Burns ha scritto: On 09/16/2013 06:41 PM, H. Haven Liu wrote: Thanks for the discussion. But for those of us that are not using gluster, but just good ol' NFS, is updating simply yum update ovirt-*? No, yum update won't upgrade ovirt packages. If you're running on Fedora, you need to update Fedora first, then run engine-upgrade. If you're on EL6, a simple engine-upgrade should work. Ofer, any other gotchas? Can you have someone create a 3.2 to 3.3 upgrade page on the wiki? Here you can find the test results of upgrading from Fedora 18 / oVirt 3.2 to Fedora 19 oVirt 3.3: https://bugzilla.redhat.com/show_bug.cgi?id=1005950 I'm a bit short on time, but I can try to find some for creating that page. Any preference on the URL / page name? Previous ones exist like this: http://www.ovirt.org/OVirt_3.0_to_3.1_upgrade http://www.ovirt.org/OVirt_3.1_to_3.2_upgrade so this would make sense: http://www.ovirt.org/OVirt_3.2_to_3.2_upgrade Thanks Mike On Sep 16, 2013, at 2:54 PM, Mike Burns mbu...@redhat.com wrote: On 09/16/2013 05:26 PM, Joop wrote: Mike Burns wrote: On 09/16/2013 04:30 PM, Joop wrote: H. Haven Liu wrote: Hello, Is there any recommended procedure for updating from 3.2 to 3.3 (namely on a CentOS 6.4 system), or anything one should be careful when doing such update? Be careful when you use glusterfs, not nfs over glusterfs, but read the release-notes. It should have something to say about glusterfs domain not (yet) working on el6. Saw a small discussion on irc just yet and my two cents are that you can't add el6 support to ovirt in release 3.2 and then withdraw it with 3.3 and say well just wait for Centos/Rhel-6.5. We haven't removed any functionality in 3.3. In 3.2, we added support for gluster domains through a POSIXFS interface. In 3.3, we're adding a feature where we support gluster natively. This works in Fedora, but is not available on EL6. The POSIXFS option still exists You're right but what about users who want to use the (much) improved speed of the gluster domain over the POSIXFS interface? They are left out or they should move to Fed19 which I would do but I need to convince a couple of other people as well and they aren't going to agree. I understand the complaint, honestly. And we're working on a solution so that it will work for people on EL6. From the perspective of whether we should release with this limitation or not, I'd point out that by not releasing, we'd be preventing everyone from using any of the new features until we get a solution for this. I'd rather release and make it available for everyone now and say that the Gluster domain for EL6 will come as soon as we can work out the dependency issues. The kernel can come from elrepo so that is not a burden for the ovirt team, qemu/libvirt should be build by the ovirt team and be available from the ovirt repo. At the moment I also see/saw Jboss-7.1.1 qemu/libvirt wouldn't be the first packages to be in the ovirt-repo which are also in the main distributions repos. We're trying to work out a way to do this in a consistent manner going forward. We should have a solution soon, but in the meantime, the other functionality and features should work on both Fedora and EL6. Thanks for the clarification and I'm waiting eagerly for what/when the solution comes out. There have been a few considerations for solving this including rebuilding pure upstream or fedora packages for EL6. That is a risky solution in my mind since there are rather large deltas between Fedora and EL6. We're looking at whether we can have a virt-preview type of repo for EL6 similar to what exists today for Fedora[1]. Thanks Mike [1] http://fedoraproject.org/wiki/Virtualization_Preview_Repository Joop ___ Users mailing list Users@ovirt.org http
[Users] Update from 3.2 to 3.3 (CentOS 6.4)
Hello, Is there any recommended procedure for updating from 3.2 to 3.3 (namely on a CentOS 6.4 system), or anything one should be careful when doing such update? Thanks, Haven ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Update from 3.2 to 3.3 (CentOS 6.4)
Thanks for the discussion. But for those of us that are not using gluster, but just good ol' NFS, is updating simply yum update ovirt-*? On Sep 16, 2013, at 2:54 PM, Mike Burns mbu...@redhat.com wrote: On 09/16/2013 05:26 PM, Joop wrote: Mike Burns wrote: On 09/16/2013 04:30 PM, Joop wrote: H. Haven Liu wrote: Hello, Is there any recommended procedure for updating from 3.2 to 3.3 (namely on a CentOS 6.4 system), or anything one should be careful when doing such update? Be careful when you use glusterfs, not nfs over glusterfs, but read the release-notes. It should have something to say about glusterfs domain not (yet) working on el6. Saw a small discussion on irc just yet and my two cents are that you can't add el6 support to ovirt in release 3.2 and then withdraw it with 3.3 and say well just wait for Centos/Rhel-6.5. We haven't removed any functionality in 3.3. In 3.2, we added support for gluster domains through a POSIXFS interface. In 3.3, we're adding a feature where we support gluster natively. This works in Fedora, but is not available on EL6. The POSIXFS option still exists You're right but what about users who want to use the (much) improved speed of the gluster domain over the POSIXFS interface? They are left out or they should move to Fed19 which I would do but I need to convince a couple of other people as well and they aren't going to agree. I understand the complaint, honestly. And we're working on a solution so that it will work for people on EL6. From the perspective of whether we should release with this limitation or not, I'd point out that by not releasing, we'd be preventing everyone from using any of the new features until we get a solution for this. I'd rather release and make it available for everyone now and say that the Gluster domain for EL6 will come as soon as we can work out the dependency issues. The kernel can come from elrepo so that is not a burden for the ovirt team, qemu/libvirt should be build by the ovirt team and be available from the ovirt repo. At the moment I also see/saw Jboss-7.1.1 qemu/libvirt wouldn't be the first packages to be in the ovirt-repo which are also in the main distributions repos. We're trying to work out a way to do this in a consistent manner going forward. We should have a solution soon, but in the meantime, the other functionality and features should work on both Fedora and EL6. Thanks for the clarification and I'm waiting eagerly for what/when the solution comes out. There have been a few considerations for solving this including rebuilding pure upstream or fedora packages for EL6. That is a risky solution in my mind since there are rather large deltas between Fedora and EL6. We're looking at whether we can have a virt-preview type of repo for EL6 similar to what exists today for Fedora[1]. Thanks Mike [1] http://fedoraproject.org/wiki/Virtualization_Preview_Repository Joop ___ 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] received packet with own address as source address
While I see the messages even with no VMs running, I don't see any messages before installing oVirt. Additionally, is there any reason that the school network would selectively affect some nodes but not others? Thanks On Aug 22, 2013, at 2:49 AM, Assaf Muller amul...@redhat.com wrote: I'd enable STP on all ports, including the port connecting your switch to the school switch. VSDSM configures the ovirtmgmt bridge on installation. The reason I'm suggesting that it's not VDSM at fault but rather the school network having a loop is that you mentioned that you get these messages even with no VMs running. - Original Message - From: H. Haven Liu haven@ucla.edu To: Assaf Muller amul...@redhat.com Cc: Users@ovirt.org Sent: Wednesday, August 21, 2013 11:26:57 PM Subject: Re: [Users] received packet with own address as source address The switch is connected to the internet via the school's switch. Currently (as well as when I received the error messages last time) portfast is disabled for all ports, and STP enabled for all ports except for the port connecting my switch to the school's. On Aug 20, 2013, at 11:50 PM, Assaf Muller amul...@redhat.com wrote: The problem was also present when I just had one interface connected to the switch, connected to the Internet. How was the switch connected to the internet? Is it connected to other switches? To solve the loop you can make sure that STP is enabled on all switches and to disable portfast. - Original Message - From: H. Haven Liu haven@ucla.edu To: Assaf Muller amul...@redhat.com Cc: Users@ovirt.org Sent: Tuesday, August 20, 2013 6:09:09 PM Subject: Re: [Users] received packet with own address as source address Hello, After I reinstalled the host, the problem seems to have disappeared. This is not to say it's not going to come back, as it has done before. I know the nodes were not receiving the error message *before* I installed VDSM (which configured the bridge?), but I haven't tried uninstalling to see if the problem would go away. The problem was also present when I just had one interface connected to the switch, connected to the Internet. If the problem is indeed a classic L2 loop, how do I go about resolving it? Is it due to bridge (mis)configuration, or is it in the network switch settings? I have tried enabling and disabling STP and portfast, which didn't seem to have any effect. Thanks, Haven On Aug 20, 2013, at 12:26 AM, Assaf Muller amul...@redhat.com wrote: Hello Mr. Liu, Sounds like a classic L2 loop. Hosts getting their own packets then losing connectivity for a few minutes while the switches restart. Can you try to rule out this possibility? For example: If you uninstall the engine and VDSM from all hosts does this still happen? Can you simplify the network topology and see if the issue persists? - Original Message - From: H. Haven Liu haven@ucla.edu To: Users@ovirt.org Sent: Saturday, August 17, 2013 10:06:07 PM Subject: [Users] received packet with own address as source address Hello, I have a oVirt installation with 6 CentOS 6.4 hosts. Some (not all) hosts are receiving these error messages, at a frequency of once every other minute: [root@vhost1 ~]# grep source address /var/log/messages | tail Aug 17 11:19:20 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:21:24 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:23:29 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:25:34 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:27:39 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:29:44 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:31:49 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:33:54 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:35:59 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:38:04 vhost1 kernel: em1: received packet with own address as source address These error messages are accompanied with loss of connectivity, with duration varies between a few seconds to minutes. The loss of connectivity would start just before the above error message. I don't *think* it's hardware because the received packet with own address error message would disappear from one of the hosts after a while. These error messages are also present whether or not any VM is running on the particular host. Here are some configurations: [root@vhost1 ~]# ifconfig em1 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet6 addr: :::::eee1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37413202 errors:0
Re: [Users] oVirt and IPA (LDAP/KERBEROS) - Invalid argument ldapervers
Yair, With the latest ovirt-engine, I'm still getting the invalid argument ldapservers if I tried to use the -ldapservers in engine-manage-domains. # rpm -qa ovirt* ovirt-host-deploy-java-1.0.2-1.el6.noarch ovirt-engine-userportal-3.2.2-1.1.el6.noarch ovirt-engine-setup-3.2.2-1.1.el6.noarch ovirt-engine-3.2.2-1.1.el6.noarch ovirt-engine-sdk-3.2.0.10-1.el6.noarch ovirt-log-collector-3.2.2-1.el6.noarch ovirt-engine-backend-3.2.2-1.1.el6.noarch ovirt-engine-genericapi-3.2.2-1.1.el6.noarch ovirt-image-uploader-3.2.2-1.el6.noarch ovirt-engine-cli-3.2.0.11-1.el6.noarch ovirt-engine-restapi-3.2.2-1.1.el6.noarch ovirt-engine-dbscripts-3.2.2-1.1.el6.noarch ovirt-release-el6-7-1.noarch ovirt-host-deploy-1.0.2-1.el6.noarch ovirt-iso-uploader-3.2.2-1.el6.noarch ovirt-engine-webadmin-portal-3.2.2-1.1.el6.noarch ovirt-engine-tools-3.2.2-1.1.el6.noarch Thanks, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] received packet with own address as source address
The switch is connected to the internet via the school's switch. Currently (as well as when I received the error messages last time) portfast is disabled for all ports, and STP enabled for all ports except for the port connecting my switch to the school's. On Aug 20, 2013, at 11:50 PM, Assaf Muller amul...@redhat.com wrote: The problem was also present when I just had one interface connected to the switch, connected to the Internet. How was the switch connected to the internet? Is it connected to other switches? To solve the loop you can make sure that STP is enabled on all switches and to disable portfast. - Original Message - From: H. Haven Liu haven@ucla.edu To: Assaf Muller amul...@redhat.com Cc: Users@ovirt.org Sent: Tuesday, August 20, 2013 6:09:09 PM Subject: Re: [Users] received packet with own address as source address Hello, After I reinstalled the host, the problem seems to have disappeared. This is not to say it's not going to come back, as it has done before. I know the nodes were not receiving the error message *before* I installed VDSM (which configured the bridge?), but I haven't tried uninstalling to see if the problem would go away. The problem was also present when I just had one interface connected to the switch, connected to the Internet. If the problem is indeed a classic L2 loop, how do I go about resolving it? Is it due to bridge (mis)configuration, or is it in the network switch settings? I have tried enabling and disabling STP and portfast, which didn't seem to have any effect. Thanks, Haven On Aug 20, 2013, at 12:26 AM, Assaf Muller amul...@redhat.com wrote: Hello Mr. Liu, Sounds like a classic L2 loop. Hosts getting their own packets then losing connectivity for a few minutes while the switches restart. Can you try to rule out this possibility? For example: If you uninstall the engine and VDSM from all hosts does this still happen? Can you simplify the network topology and see if the issue persists? - Original Message - From: H. Haven Liu haven@ucla.edu To: Users@ovirt.org Sent: Saturday, August 17, 2013 10:06:07 PM Subject: [Users] received packet with own address as source address Hello, I have a oVirt installation with 6 CentOS 6.4 hosts. Some (not all) hosts are receiving these error messages, at a frequency of once every other minute: [root@vhost1 ~]# grep source address /var/log/messages | tail Aug 17 11:19:20 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:21:24 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:23:29 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:25:34 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:27:39 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:29:44 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:31:49 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:33:54 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:35:59 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:38:04 vhost1 kernel: em1: received packet with own address as source address These error messages are accompanied with loss of connectivity, with duration varies between a few seconds to minutes. The loss of connectivity would start just before the above error message. I don't *think* it's hardware because the received packet with own address error message would disappear from one of the hosts after a while. These error messages are also present whether or not any VM is running on the particular host. Here are some configurations: [root@vhost1 ~]# ifconfig em1 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet6 addr: :::::eee1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37413202 errors:0 dropped:0 overruns:0 frame:0 TX packets:17822315 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:32444347931 (30.2 GiB) TX bytes:13715272213 (12.7 GiB) Interrupt:16 em2 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2 inet6 addr: :::::eee2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21878 errors:0 dropped:0 overruns:0 frame:0 TX packets:526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1598070 (1.5 MiB) TX bytes:40526 (39.5 KiB) Interrupt:17 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:49 errors:0
Re: [Users] oVirt and IPA (LDAP/KERBEROS) - Invalid argument ldapervers
Hello, Please see below: [root@panther ~]# host -t SRV _ldap._tcp.domain.local _ldap._tcp.domain.local has SRV record 0 0 389 auth.domain.local. [root@panther ~]# engine-manage-domains -action=add -domain=domain.local -provider=ipa -user=admin -interactive -ldapservers=ldap://auth.domain.local Invalid argument ldapservers [root@panther ~]# engine-manage-domains -action=add -domain=domain.local -provider=ipa -user=admin -interactive -ldapservers=auth.domain.local Invalid argument ldapservers [root@panther ~]# cat /var/log/ovirt-engine/engine-manage-domains.log ... 2013-08-21 18:05:34,079 ERROR [org.ovirt.engine.core.domains.ManageDomains] Invalid argument ldapservers 2013-08-21 18:05:40,324 ERROR [org.ovirt.engine.core.domains.ManageDomains] Invalid argument ldapservers [root@panther ~]# Haven On Aug 21, 2013, at 5:41 PM, Yair Zaslavsky yzasl...@redhat.com wrote: I would also use the fqdn - we saw some issue with AD (yes, I saw you're using IPA, it just rang a bell). so please use -ldapServers=mymachine.example.com and not the IP address of mymachine.example.com Will it be possible to get logs if you still encounter issues? Yair - Original Message - From: Itamar Heim ih...@redhat.com To: H. Haven Liu haven@ucla.edu Cc: users@ovirt.org, Yair Zaslavsky yzasl...@redhat.com Sent: Thursday, August 22, 2013 1:31:50 AM Subject: Re: [Users] oVirt and IPA (LDAP/KERBEROS) - Invalid argument ldapervers On 08/21/2013 12:20 PM, H. Haven Liu wrote: Yair, With the latest ovirt-engine, I'm still getting the invalid argument ldapservers if I tried to use the -ldapservers in engine-manage-domains. # rpm -qa ovirt* ovirt-host-deploy-java-1.0.2-1.el6.noarch ovirt-engine-userportal-3.2.2-1.1.el6.noarch ovirt-engine-setup-3.2.2-1.1.el6.noarch ovirt-engine-3.2.2-1.1.el6.noarch ovirt-engine-sdk-3.2.0.10-1.el6.noarch ovirt-log-collector-3.2.2-1.el6.noarch ovirt-engine-backend-3.2.2-1.1.el6.noarch ovirt-engine-genericapi-3.2.2-1.1.el6.noarch ovirt-image-uploader-3.2.2-1.el6.noarch ovirt-engine-cli-3.2.0.11-1.el6.noarch ovirt-engine-restapi-3.2.2-1.1.el6.noarch ovirt-engine-dbscripts-3.2.2-1.1.el6.noarch ovirt-release-el6-7-1.noarch ovirt-host-deploy-1.0.2-1.el6.noarch ovirt-iso-uploader-3.2.2-1.el6.noarch ovirt-engine-webadmin-portal-3.2.2-1.1.el6.noarch ovirt-engine-tools-3.2.2-1.1.el6.noarch Thanks, ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users the syntaqx is a bit misleading - did you -ldapservers=xxx? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] received packet with own address as source address
Hello, After I reinstalled the host, the problem seems to have disappeared. This is not to say it's not going to come back, as it has done before. I know the nodes were not receiving the error message *before* I installed VDSM (which configured the bridge?), but I haven't tried uninstalling to see if the problem would go away. The problem was also present when I just had one interface connected to the switch, connected to the Internet. If the problem is indeed a classic L2 loop, how do I go about resolving it? Is it due to bridge (mis)configuration, or is it in the network switch settings? I have tried enabling and disabling STP and portfast, which didn't seem to have any effect. Thanks, Haven On Aug 20, 2013, at 12:26 AM, Assaf Muller amul...@redhat.com wrote: Hello Mr. Liu, Sounds like a classic L2 loop. Hosts getting their own packets then losing connectivity for a few minutes while the switches restart. Can you try to rule out this possibility? For example: If you uninstall the engine and VDSM from all hosts does this still happen? Can you simplify the network topology and see if the issue persists? - Original Message - From: H. Haven Liu haven@ucla.edu To: Users@ovirt.org Sent: Saturday, August 17, 2013 10:06:07 PM Subject: [Users] received packet with own address as source address Hello, I have a oVirt installation with 6 CentOS 6.4 hosts. Some (not all) hosts are receiving these error messages, at a frequency of once every other minute: [root@vhost1 ~]# grep source address /var/log/messages | tail Aug 17 11:19:20 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:21:24 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:23:29 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:25:34 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:27:39 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:29:44 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:31:49 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:33:54 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:35:59 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:38:04 vhost1 kernel: em1: received packet with own address as source address These error messages are accompanied with loss of connectivity, with duration varies between a few seconds to minutes. The loss of connectivity would start just before the above error message. I don't *think* it's hardware because the received packet with own address error message would disappear from one of the hosts after a while. These error messages are also present whether or not any VM is running on the particular host. Here are some configurations: [root@vhost1 ~]# ifconfig em1 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet6 addr: :::::eee1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37413202 errors:0 dropped:0 overruns:0 frame:0 TX packets:17822315 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:32444347931 (30.2 GiB) TX bytes:13715272213 (12.7 GiB) Interrupt:16 em2 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2 inet6 addr: :::::eee2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21878 errors:0 dropped:0 overruns:0 frame:0 TX packets:526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1598070 (1.5 MiB) TX bytes:40526 (39.5 KiB) Interrupt:17 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9236 (9.0 KiB) TX bytes:9236 (9.0 KiB) ovirtmgmt Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.yyy Mask:255.255.255.0 inet6 addr: :::::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22623881 errors:0 dropped:0 overruns:0 frame:0 TX packets:9990988 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:28427312067 (26.4 GiB) TX bytes:13112553784 (12.2 GiB) private_lan Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2 inet addr:10.0.1.12 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: :::::eee2/64
[Users] preauth (encrypted_timestamp) verify failure: Decrypt integrity check failed
Hello,
I tried to add a IPA directory domain following these instructions:
https://www.rvanderlinden.net/wordpress/ovirt/administrator-portal/administrator-portal-authentication-via-ipa/
It appears the domain was added successfully, but cannot be validated:
[root@vhost1 ~]# engine-manage-domains -action=add -domain=domain.local
-user=admin -provider=ipa -interactive
Enter password:
The domain domain.local has been added to the engine as an authentication
source but no users from that domain have been granted permissions within the
oVirt Manager.
Users from this domain can be granted permissions from the Web administration
interface.
oVirt Engine restart is required in order for the changes to take place
(service ovirt-engine restart).
Manage Domains completed successfully
[root@vhost1 ~]# service ovirt-engine restart
Stopping engine-service: [ OK ]
Starting engine-service: [ OK ]
[root@vhost1 ~]# engine-manage-domains -action=validate -report
Error: exception message: Integrity check on decrypted field failed (31) -
PREAUTH_FAILED
WARNING, domain: domain.local may not be functional: Failure while testing
domain domain.local. Details: Kerberos error. Please check log for further
details.
Manage Domains completed successfully
[root@vhost1 ~]#
krb5kdc.log has the following entries:
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): AS_REQ (1 etypes {23})
10.0.1.12: NEEDED_PREAUTH: admin@DOMAIN.LOCAL for
krbtgt/DOMAIN.LOCAL@DOMAIN.LOCAL, Additional pre-authentication required
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): closing down fd 10
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): AS_REQ (1 etypes {23})
10.0.1.12: ISSUE: authtime 1376950566, etypes {rep=23 tkt=18 ses=23},
admin@DOMAIN.LOCAL for krbtgt/DOMAIN.LOCAL@DOMAIN.LOCAL
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): closing down fd 10
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): TGS_REQ (6 etypes {18 17
16 23 1 3}) 10.0.1.12: ISSUE: authtime 1376950566, etypes {rep=23 tkt=18
ses=18}, admin@DOMAIN.LOCAL for ldap/auth.domain.local@DOMAIN.LOCAL
Aug 19 15:16:06 auth.domain.local krb5kdc[4572](info): closing down fd 10
Any idea?
Thanks,
Haven___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] received packet with own address as source address
Hello, I have a oVirt installation with 6 CentOS 6.4 hosts. Some (not all) hosts are receiving these error messages, at a frequency of once every other minute: [root@vhost1 ~]# grep source address /var/log/messages | tail Aug 17 11:19:20 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:21:24 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:23:29 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:25:34 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:27:39 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:29:44 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:31:49 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:33:54 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:35:59 vhost1 kernel: em1: received packet with own address as source address Aug 17 11:38:04 vhost1 kernel: em1: received packet with own address as source address These error messages are accompanied with loss of connectivity, with duration varies between a few seconds to minutes. The loss of connectivity would start just before the above error message. I don't *think* it's hardware because the received packet with own address error message would disappear from one of the hosts after a while. These error messages are also present whether or not any VM is running on the particular host. Here are some configurations: [root@vhost1 ~]# ifconfig em1 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet6 addr: :::::eee1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37413202 errors:0 dropped:0 overruns:0 frame:0 TX packets:17822315 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:32444347931 (30.2 GiB) TX bytes:13715272213 (12.7 GiB) Interrupt:16 em2 Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2 inet6 addr: :::::eee2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21878 errors:0 dropped:0 overruns:0 frame:0 TX packets:526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1598070 (1.5 MiB) TX bytes:40526 (39.5 KiB) Interrupt:17 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:49 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9236 (9.0 KiB) TX bytes:9236 (9.0 KiB) ovirtmgmt Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f1 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.yyy Mask:255.255.255.0 inet6 addr: :::::/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22623881 errors:0 dropped:0 overruns:0 frame:0 TX packets:9990988 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:28427312067 (26.4 GiB) TX bytes:13112553784 (12.2 GiB) private_lan Link encap:Ethernet HWaddr aa:bb:cc:dd:ee:f2 inet addr:10.0.1.12 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: :::::eee2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:19771 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1080512 (1.0 MiB) TX bytes:468 (468.0 b) [root@vhost1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE=em1 ONBOOT=yes HWADDR=aa:bb:cc:dd:ee:f2 BRIDGE=ovirtmgmt NM_CONTROLLED=no UUID=c25b1ad1-9646-4126-9149-be5f68bae36c DNS2=www.www.www.www DNS1=www.www.www.www HOSTNAME=vhost1.mydomain.com MTU=1500 IPV6INIT=no [root@vhost1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=xxx.xxx.xxx.xxx NETMASK=255.255.255.0 GATEWAY=xxx.xxx.xxx.1 BOOTPROTO=none NM_CONTROLLED=no UUID=c25b1ad1-9646-4126-9149-be5f68bae36c DNS2=www.www.www.www DNS1=www.www.www.www HOSTNAME=vhost1.mydomain.com MTU=1500 IPV6INIT=no [root@vhost1 ~]# Any help is appreciated. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] ovirt-hosted-engine CentOS
Hello, Is there anyway to install self hosted engine on CentOS 6.4? The package ovirt-hosted-engine isn't available in the el6-ovirt, CentOS ovirt-test repositories. Thanks, Haven ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
