-
Notifications
You must be signed in to change notification settings - Fork 479
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
PHYDEV should not be mandatory for ovswitch #2241
Milestone
Comments
I found #1807 and I'm more confused. I think the
But the Regards. |
Plus the documentation says it's optional for ovswitch:
Regards. |
baby-gnu
changed the title
PHYDEV is mandatory for ovswitch
Jun 29, 2018
PHYDEV
is mandatory for ovswitch
baby-gnu
changed the title
PHYDEV is mandatory for ovswitch
PHYDEV should not be mandatory for ovswitch
Jun 29, 2018
abelCoronado93
pushed a commit
to abelCoronado93/one
that referenced
this issue
Jul 4, 2018
rsmontero
pushed a commit
that referenced
this issue
Jul 4, 2018
Fix for 5.6 oned and Sunstone. |
rsmontero
pushed a commit
that referenced
this issue
Jul 21, 2022
rsmontero
pushed a commit
that referenced
this issue
Jul 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Version of OpenNebula
Component
Description
An incompatible change is made to
ovswitch
driver : thePHYDEV
attribute is now mandatory.Here is the vnet template I used for ONE 5.4:
Expected Behavior
I can create completely isolated vnet without the
PHYDEV
attribute.Actual Behavior
I can't create the vnet with the following error:
How to reproduce
Progress Status
The text was updated successfully, but these errors were encountered: