Bug 1709871

This bug tracks the change in the documantation.

+++ This bug was initially created as a clone of Bug #1698102 +++

Description of problem:


Version-Release number of selected component (if applicable):
rhv 4.2.8

How reproducible:
everytime

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

Actual results:
vm will fail with error below:
VM test-ovn is down with error. Exit message: Hook Error: ('',).

Expected results:
ovn services will be started on the hosts, br-int interface will be created and vm will be able to boot

Additional info:
removing and re-adding hosts workaround the issue

--- Additional comment from Michael Burman on 2019-04-10 07:28:57 UTC ---

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.

--- Additional comment from Marian Jankular on 2019-04-24 13:40:01 UTC ---

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?

--- Additional comment from Miguel Duarte Barroso on 2019-04-24 14:18:21 UTC ---

(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.

--- Additional comment from Dominik Holler on 2019-04-30 13:48:54 UTC ---

Marian, do you think the following two suggestions would be helpful:

1. We will add a sentence to
 https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3-beta/html-single/administration_guide/index#Adding_OVN_as_an_External_Network_Provider
 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.

--- Additional comment from Marian Jankular on 2019-05-02 12:20:44 UTC ---

Hi Dominik,

I think that should be enough.

Thank you in advance.

--- Additional comment from Dominik Holler on 2019-05-07 12:22:29 UTC ---

(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
>  https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3-
> beta/html-single/administration_guide/
> index#Adding_OVN_as_an_External_Network_Provider
>  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?

--- Additional comment from Yedidyah Bar David on 2019-05-14 09:34:30 UTC ---

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.