Skip to content
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

get_networks and set_network does not use the same source #165

Open
sigbjornaib opened this issue Mar 11, 2020 · 1 comment
Open

get_networks and set_network does not use the same source #165

sigbjornaib opened this issue Mar 11, 2020 · 1 comment

Comments

@sigbjornaib
Copy link
Contributor

When the get_networks (/ RedHatConsulting_Utilities / Service / Provisioning / DynamicDialogs / get_networks) method is used to display available networks for a new provision request for RHV/OVIRT, it uses the Network name (Network -> Networks in RHV-M) to find available networks to display to the end user.

When the provisioning request is executing, and the set_network (/ RedHatConsulting_Utilities / Infrastructure / VM / Provisioning / StateMachines / Methods / set_network) method is used to update the vlan for the provisioning request, the vNIC Profile ID is used. (Network -> vNIC Profiles in RHV-M).

The result is when a Network name is set to "my_network", and the vNIC Profile is set to "my-network", the provisioning dialog displays a selectable VM network, however the provisioning request fails during the set_network stage:

[workernode1] VM [myvmname.domain] Step [PreProvision_2] Status [Error setting network: State=<PreProvision_2> running raised exception: <Method exited with rc=Unknown RC: [1]>] Message [Setting Network]

The issue is with the get_networks method, as the vNIC profile name should be used for matching to allow selecting different vNIC profiles.

@itewk
Copy link
Collaborator

itewk commented Mar 11, 2020

@sigbjornaib pull requests welcome.

@A-Beck FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants