[Ovirt-devel] [PATCH]: Allow the WUI to manage the hardware it is running on

[Chris Lalancette]

    Two last fixes.  Since we are currently hardcoding ovirtbr0 in taskomatic,
    we have to call the bridge on the host ovirtbr0 to allow guests to start.
    This limitation should go away fairly soon with Darryl's network discovery
    work, but we need it for now.
    
    Signed-off-by: Chris Lalancette <clalance at redhat.com>

diff --git a/ovirt-managed-node/ovirt-listen-awake/ovirt-convert-host b/ovirt-managed-node/ovirt-listen-awake/ovirt-convert-host
index 98e695d..45351b1 100755
--- a/ovirt-managed-node/ovirt-listen-awake/ovirt-convert-host
+++ b/ovirt-managed-node/ovirt-listen-awake/ovirt-convert-host
@@ -45,7 +45,7 @@ backup_file /etc/sasl2/libvirt.conf
 ovirt_setup_libvirtd
 
 backup_file /etc/sysconfig/iptables
-/usr/sbin/lokkit -n -t ovirtbr
+/usr/sbin/lokkit -n -t ovirtbr0
 
 echo "Setup complete.  To make the changes take effect, shut down any running
 guests and reboot the host"
diff --git a/wui-appliance/create-wui-appliance.sh b/wui-appliance/create-wui-appliance.sh
index b81ed68..e1857b9 100755
--- a/wui-appliance/create-wui-appliance.sh
+++ b/wui-appliance/create-wui-appliance.sh
@@ -10,7 +10,7 @@ RAM=768
 IMGDIR_DEFAULT=/var/lib/libvirt/images
 NAME_DEFAULT=ovirt-appliance
 NET_SCRIPTS=/etc/sysconfig/network-scripts
-BRIDGENAME=ovirtbr
+BRIDGENAME=ovirtbr0
 
 imgdir=$IMGDIR_DEFAULT
 name=$NAME_DEFAULT