On 08/08/12 20:25, Trey Dockendorf wrote:
A few weeks back I started a discussion about my issues with IP/Netmask not being set on networks that weren't enabled for VM use. The bug is here, https://bugzilla.redhat.com/show_bug.cgi?id=834205.
I've since upgrade to latest ovirt / vdsm and while the issue seems to be resolved it's now failing in a different way. Looking at the logs , it looks like the correct parameters are being passed to vdsm but the ifcfg-eth* is still left with no IPADDR or NETMASK values.
Hi Trey, When you say latest ovirt/vdsm do you mean 3.1 release or build from source? We had a few issues with non-vm network and we could not fix them without changing vdsm-engine API. The change could not be pushed to the formal upstream 3.1 release because the fix came too late. This implies that the formal 3.1 release does not support non-vm network. The latest bits on the other hand already have the fix and should fully support non-vm network. but this feature is disabled by default in the engine until engine adds 3.2 cluster. a simple work around is to change false to true in the db for supporting non-vm network (this will only work if you have engine and vdsm latest bits) use the following SQL query for that - "update vdc_options set option_value='true' where option_name='SupportBridgesReportByVDSM' and version='3.1'" Thanks, Livnat
Attached are logs from when Assigning a Static IP to both eth0 / ovirtmgmt and eth1/stor0.
CentOS 6.3 on the Engine host with the following versions ovirt-engine-cli-3.1.0.2-1alpha.el6.noarch ovirt-engine-webadmin-portal-3.1.0-3.16.el6.noarch ovirt-engine-notification-service-3.1.0-3.16.el6.noarch ovirt-iso-uploader-3.1.0-16.el6.noarch ovirt-engine-sdk-3.1.0.1-1alpha.el6.noarch ovirt-engine-restapi-3.1.0-3.16.el6.noarch ovirt-engine-backend-3.1.0-3.16.el6.noarch ovirt-engine-userportal-3.1.0-3.16.el6.noarch ovirt-engine-tools-common-3.1.0-3.16.el6.noarch ovirt-engine-dbscripts-3.1.0-3.16.el6.noarch ovirt-engine-3.1.0-3.16.el6.noarch ovirt-log-collector-3.1.0-16.el6.noarch ovirt-engine-jbossas711-1-0.x86_64 ovirt-engine-setup-3.1.0-3.16.el6.noarch ovirt-engine-config-3.1.0-3.16.el6.noarch ovirt-engine-genericapi-3.1.0-3.16.el6.noarch ovirt-image-uploader-3.1.0-16.el6.noarch
CentOS 6.3 on the Node with the following versions vdsm-xmlrpc-4.10.0-0.42.12.el6.noarch vdsm-python-4.10.0-0.42.12.el6.x86_64 vdsm-cli-4.10.0-0.42.12.el6.noarch vdsm-hook-simpleqemu-0.1-1.el6.noarch vdsm-4.10.0-0.42.12.el6.x86_64
After performing the change in the web interface, this is ifcfg-eth1 (missing IPADDR and NETMASK) # cat ifcfg-eth1 DEVICE=eth1 ONBOOT=yes BOOTPROTO=none HWADDR=00:25:90:4c:91:bf NM_CONTROLLED=no MTU=9000
I've also run into an issue where in the web interface, the ovirtmgmt network always reverts back to DHCP as the boot protocol. The ifcfg on node will reflect the correct setting after I change to static, but if I go to re-edit the entry, it's back on DHCP.
Thanks - Trey
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users