-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip "none" vApp network when inventoring #198
Conversation
With this commit we prevent NetworkManager from crashing is case when there is a special network "none" listed in vApp network configuration section. This "none" network is a reserved vApp network name which is for some reason present in case when at least one NIC of the vApp VMs is not connected to any network. Following XML is present for such "none" networks: ``` <vcloud:NetworkConfig networkName="none"> <vcloud:Description>This is a special place-holder used for disconnected network interfaces.</vcloud:Description> <vcloud:Configuration> <vcloud:IpScopes> <vcloud:IpScope> <vcloud:IsInherited>false</vcloud:IsInherited> <vcloud:Gateway>196.254.254.254</vcloud:Gateway> <vcloud:Netmask>255.255.0.0</vcloud:Netmask> <vcloud:Dns1>196.254.254.254</vcloud:Dns1> </vcloud:IpScope> </vcloud:IpScopes> <vcloud:FenceMode>isolated</vcloud:FenceMode> </vcloud:Configuration> <vcloud:IsDeployed>false</vcloud:IsDeployed> </vcloud:NetworkConfig> ``` and it must be ignored when inventoring. Signed-off-by: Miha Pleško <[email protected]>
@agrare playing with networking customization via vApp template provisioning I just discovered that our NetworkManager inventoring crashes hard in case there is a VM with NIC that is not connected to any network. Turns out it's because vCD then automatically includes a special placeholder "none" which should just be ingored by our refresher. @miq-bot add_label gaprindashvili/yes |
Checked commit miha-plesko@5fd5d12 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 **
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM
Skip "none" vApp network when inventoring
Skip "none" vApp network when inventoring (cherry picked from commit a0417bb) https://bugzilla.redhat.com/show_bug.cgi?id=1552673
Gaprindashvili backport details:
|
@miha-plesko @agrare Assume this needs to be |
@miha-plesko I asked because #161 is set to |
Skip "none" vApp network when inventoring (cherry picked from commit a0417bb) https://bugzilla.redhat.com/show_bug.cgi?id=1552675
Looks I accidentally had the backport pushed to Fine branch a few days ago... reverted now. |
Update for Sprint 71
With this commit we prevent NetworkManager from crashing is case when there is a special network "none" listed in vApp network configuration section. This "none" network is a reserved vApp network name which is for some reason present in case when at least one NIC of the vApp VMs is not connected to any network.
Following XML is present for such "none" networks:
and it must be ignored when inventoring.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1520372
@miq-bot add_label enhancement
@miq-bot assign @agrare