The bugzilla URL says that's a private/internal only bug.
You are not authorized to access bug #1016535.
Most likely the bug has been restricted for internal development processes and
we cannot grant access.
If you are a Red Hat customer with an active subscription, please visit the Red
Hat Cu
Are you on OVS or legacy bridge networks for oVirt?
If OVS, you need to move to OVN to continue to use OVS, else regress back to
legacy.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: h
Sverker,
Can you share the hook you created for VDSM?
thanks,
thomas
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
ht
Do I even tell you how I do the conversion from legacy to OVS?
It does use ansible, and creates the vdsm nework configuration in /var/lib/vdsm
for an OVS/OVN based network.
It works great, the nodes join right up to oVirt engine with no configuration
needed.
But I know that's unsupported. :)
The answer is..
OVN replaced OVS as the networking technology. You cannot switch back to
legacy, they disabled switching between ovs and legacy in the default (1st)
datacenter using the gui. You can however, use Ansible to switch it.
Remove the VDSM ovs setting, it will just mess you up, and
5 matches
Mail list logo
