Bug 1430799
| Summary: | Create script to restore original network configuration of removed vdsm host | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Jiri Belka <jbelka> |
| Component: | vdsm | Assignee: | Petr Horáček <phoracek> |
| Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | danken, edwardh, jbelka, lsurette, mburman, phoracek, rbalakri, srevivo, trichard, ycui, ykaul, ylavi |
| Target Milestone: | ovirt-4.2.0 | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
vdsm-tool now provides commands for VDSM network cleanup, such as `vdsm-tool clear-nets` and `vdsm-tool dummybr-remove`. You can remove networks configured by VDSM following the steps below. Note that the VDSM service does not need to be running:
1. To prevent loss of connectivity, it might be necessary to exclude the default route network from the cleanup. Look for a network providing the default route (ovirtmgmt by default):
# vdsm-tool list-nets
...
ovirtmgmt (default route)
...
2. Remove all networks configured by VDSM except for the default network:
# vdsm-tool clear-nets --exclude-net ovirtmgmt
3. Remove the libvirt dummy bridge ;vdsmdummy;
# vdsm-tool dummybr-remove
4. Now that the host is clean, you can remove VDSM.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-15 17:50:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jiri Belka
2017-03-09 15:44:35 UTC
Do you have a flow to share on how to do this? Who can help us with getting this content? Petr, please provide a script to remove all vdsm networks (apart of one, ovirtmgmt). Just to clarify, we will not be able to restore the node to the "original" state, for that we need to "remember" the original state, which we do not. The suggested "cleaning" may even be wrong, as it may remove acquired configuration (like pre existing bridges, bonds, IP/s.. etc). If we bring NM in the picture, after this "cleaning", it will not control the previously acquired devices, manual intervention is needed to do so. I guess the documentation needs to reflect all this, suggests way to continue manually patching things after the "automatic" step is finished. INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: rhv-devops Verified on - vdsm-4.20.7-37.gitfb0d1c3.el7.centos.x86_64 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:1489 BZ<2>Jira Resync |