[et-mgmt-tools] no longer can create shared network

[Cole Robinson]

Mark Chaney wrote:
> You mean something like this?
> 
> [Fri, 11 Jul 2008 14:48:02 virt-manager 28541] ERROR (connection:175) Unable
> to connect to HAL to list network devices: '%s'dbus_bindings.DBusException
> Could not get owner of name 'org.freedesktop.Hal': no such name
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/connection.py", line 155, in
> __init__
>     self.hal_iface.connect_to_signal("DeviceAdded",
> self._net_phys_device_added)
>   File "/usr/lib64/python2.4/site-packages/dbus/_dbus.py", line 291, in
> connect_to_signal
>     self._obj.connect_to_signal(signal_name, handler_function,
> dbus_interface, **keywords)
>   File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 151, in
> connect_to_signal
>     path=self._object_path,
>   File "/usr/lib64/python2.4/site-packages/dbus/_dbus.py", line 179, in
> add_signal_receiver
>     named_service = bus_object.GetNameOwner(named_service,
> dbus_interface='org.freedesktop.DBus')
>   File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in
> __call__
>     ret = self._proxy_method (*args, **keywords)
>   File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in
> __call__
>     reply_message = self._connection.send_with_reply_and_block(message,
> timeout)
>   File "dbus_bindings.pyx", line 455, in
> dbus_bindings.Connection.send_with_reply_and_block
> DBusException: Could not get owner of name 'org.freedesktop.Hal': no such
> name
>

Yeah that would do it. I don't know if it would be a simple fix or not:
you can try pulling down the current upstream and see if that produces
any different results. Chances are though that things would require
a bit of backporting to work on the rhel stack.

 
> Also, how in the world can RHEL 5.2 be considered old?

The entire point of RHEL is a release with a mostly stable set of major
components that is maintained with bug fixes. We don't pull in the latest
and greatest versions of every piece in the stack for an update release.
As a result, dbus in 5.2 is probably just a patched version of dbus from
5.0 (haven't checked) making it essentially over a year old.

- Cole