Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When VDSM is installed it should remove libvirt's default network.
We do not want to have another bridge with a configured IP address, dnsmasq etc
Question : Should we also delete/remove any other libvirt managed networks or just leave this to documentation?
On Sat, Jan 15, 2011 at 12:59:24AM +0200, Barak Azulay wrote:
> Danken don't forget to think about RHEVH as well ... the code that does the
> removal should probably reside in bootstrap/registration
> > Danken don't forget to think about RHEVH as well ...
/etc/libvirt/qemu/networks/autostart/default.xml is removed in rhevh image
i.e. default libvirt network is not undefined but it won't start automatically with libvirtd.
(In reply to comment #2)
> /etc/libvirt/qemu/networks/autostart/default.xml is removed
Mimicking this on RHEL when vdsm is installed/first run sound fine.
(In reply to comment #0)
> Question : Should we also delete/remove any other libvirt managed networks or
> just leave this to documentation?
I guess we should not. If someone went into the trouble of defining a network via libvirt, let's hope he knows what he's doing and not ruin his work.
(In reply to comment #4)
> /etc/libvirt/qemu/networks/autostart/default.xml still exists.
How does that make it VERIFIED then? Summary says it should be removed.
Alan,
default.xml file will be exist until the next reboot (after rebooting the machine the file was removed)
virbr0 interface is no longer exist after rebooting the machine.
thx