Description of problem: The current way the hotplug scripts report errors is sub-optimal, rarely giving the user enough information to diagnose the problem. This is particularly true of the networking scripts whose typical failure mode is very obsecure. eg, if I configure a guest to use bridge7 which does not exist, I will be told: # xm create demo ....60 seconds passes... Error: Device 0 (vif) could not be connected. Hotplug scripts not working. How reproducible: Always Additional info: A fix is upstream (see URL field) and in FC-6.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Built as xen-3.0.3-30.el5 into dist-5E-qu-candidate * Tue Jun 26 2007 Daniel P. Berrange <berrange> - 3.0.3-30.el5 - Hotplug scripts error reporting (rhbz 233433)
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2007-0635.html