Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run engine setup and do not configure ovirt-ovn-provider
2. add host, storage
3. run engine-setup --reconfigure-optional-components and configure ovirt-ovn-provider
4, create network provided by ovirt-ovn-provider
5, create vm with ovn network and try to boot
vm will fail with error below:
VM test-ovn is down with error. Exit message: Hook Error: ('',).
ovn services will be started on the hosts, br-int interface will be created and vm will be able to boot
removing and re-adding hosts workaround the issue
If the cluster has no 'external network provider' enabled this is expected and won't work. The default is no provider, so if customer didn't changed it is expected.
In order to this to work you need:
1. Enable ovn provider on the cluster level
2. Remove and hosts again so all relevant ovn configuration and tunneling will applied on the host.
If this is the case this should be closed as not a bug.
sorry for late response,
I thought once customer runs engine-setup with "--reconfigure-optional-components" and he enables ovirt-ovn-provider engine will instruct host to create br-int interface, if not we should at least warn him either in the setup or at least in documentation that he enabled it in engine however to push this to host he needs to remove and add the host again, what do you think?
(In reply to Marian Jankular, comment#2)
I definitely agree that the current behavior is not obvious, and there's room for improvement on our docs; I think updating the documentation would suffice.
Marian, do you think the following two suggestions would be helpful:
1. We will add a sentence to
which highlights that other clusters than the Default one are not modified to use ovirt-provider-ovn as the default network provider and ovn will not work for this reason.
2. Print a warning message to engine-setup, which highlights that other clusters than the Default one are not modified to use ovirt-provider-ovn as the default network provider and ovn will not work for this reason.
I think that should be enough.
Thank you in advance.
(In reply to Dominik Holler from comment #4)
> Marian, do you think the following two suggestions would be helpful:
> 1. We will add a sentence to
> which highlights that other clusters than the Default one are not modified
> to use ovirt-provider-ovn as the default network provider and ovn will not
> work for this reason.
Didi, is adding a warning to the output of engine-setup acceptable for you?
Fine for me, but imo we should only do this if there actually are other clusters - otherwise, it will be confusing. Or, make it a info/note (not warning) and write the text so that it's clear that this is the case, if it's indeed so, also for clusters to be created in the future. Also, it wasn't clear from previous comments if it does work automatically for cluster 'Default' (and VMs already created on it prior to the latter engine-setup). Is it so? If not, we should again clarify this in the text.
1. If it's just a new warning, almost no-one will notice, IMO.
2. If it's important enough, we should prompt:
Configure ovirt-provider-ovn (Yes, No) [Yes]: yes
Please note that only the cluster 'Default' is configured to use it. Press Enter to continue.
3. If we do not want to prompt, perhaps just change the text asking whether to configure ovn. E.g.:
Configure ovirt-provider-ovn? Please note that if you do, only the cluster 'Default' is configured to use it (Yes, No) [Yes]:
Please document what message + behaviour you would like in this flow.
(In reply to eraviv from comment #9)
> Please document what message + behaviour you would like in this flow.
Currently i find the message confusing and user may think that the default cluster is the only cluster that works with OVN.
The message should improved and include that other clusters can be set with OVN after installation or something like that.
When i read it now, i understand that the default cluster is the only one who effective with OVN..
This can be moved to ON_QA
Verified on - rhvm-4.4.0-0.32.master.el8ev.noarch
Configure ovirt-provider-ovn and set the Default cluster's default network provider to ovirt-provider-ovn (non-Default clusters may be configured with an OVN provider after installation) (Yes, No) [Yes]:
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.