1:10 p.m.
This is a multi-part message in MIME format.
--------------080204010900060200040902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi all,
I'm testing the bootstrapping of host without reboot on Fedora 18. After
host's bootstrap,
Ifconfig output returns this:
ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.70.37.219 netmask 255.255.254.0 broadcast 10.70.37.255
<snipped>
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast
192.168.122.255
<snipped>
Running*glusterHostsList* vdsm verb, returns the ip address
192.168.122.1, whereas my host has been added with ip address 10.70.37.219
If I reboot the host, the virbr0 bridge is removed, and there's no issue.
The vdsm verb glusterHostsList - returns ipAddress of host + output of
gluster peer probe. This is needed because a periodic sync job needs to
make sure that the hosts added in engine are in sync with the gluster
cli (hosts could also be added/removed from gluster cli).
How can we make sure glusterHostsList picks the correct ipAddress?
Reading the inetinfo based on bridge has been vetoed as we are doing
away with bridges.
It would also work if virbr0 was updated in vds_interfaces table. Since
this is not happening either - we have an issue.
thanks
sahina
--------------080204010900060200040902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<pre><font face="sans-serif">Hi all,
I'm testing the bootstrapping of host without reboot on Fedora 18. After
host's bootstrap,
Ifconfig output returns this:
ovirtmgmt: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.70.37.219 netmask 255.255.254.0 broadcast 10.70.37.255
<snipped>
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast
192.168.122.255
<snipped>
Running <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>glusterHostsList<span
class="moz-txt-tag">*</span></b> vdsm verb, returns the ip
address
192.168.122.1, whereas my host has been added with ip address 10.70.37.219
If I reboot the host, the virbr0 bridge is removed, and there's no
issue.</font>
<font face="sans-serif">
</font></pre>
<font face="sans-serif">The vdsm verb glusterHostsList - returns
ipAddress of host + output of gluster peer probe. This is needed
because a periodic sync job needs to make sure that the hosts added
in engine</font> are in sync with the gluster cli (hosts could
also be added/removed from gluster cli).<br>
<br>
How can we make sure glusterHostsList picks the correct ipAddress?
Reading the inetinfo based on bridge has been vetoed as we are doing
away with bridges.<br>
<br>
It would also work if virbr0 was updated in vds_interfaces table.
Since this is not happening either - we have an issue.<br>
<br>
thanks<br>
sahina<br>
<br>
</body>
</html>
--------------080204010900060200040902--