Bug 1956640 - HyperConverged deployment should not require "multinetwork functionality" from install-config.yaml
Summary: HyperConverged deployment should not require "multinetwork functionality" fro...
Keywords:
Status: NEW
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 2.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Petr Horáček
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 06:37 UTC by Patrik Martinsson
Modified: 2021-05-06 13:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Patrik Martinsson 2021-05-04 06:37:09 UTC
Description of problem:

When creating a "HyperConverged" deployment from the operator "OpenShift Virtualization" one is required to have set the "disableMultiNetwork: false" in the install-config.yaml. 
This in turn will enable the multus-deployment that will enable pods to have multiple networks attached. If you have "disableMultiNetork: true" in the install-config.yaml, the installation of "HyperConverged" will fail with a message telling you that you need to "enable multinetwork functionality". 

I don't see why this should be a requiremnt, we are running "OpenShift Virtualization" and have successfully created an "Hyperconverged" deployment and can successfully run VM's - without a "multinetwork functionality" (ie. we have set "disableMultiNetork: true" in our install-config.yaml). We had to temporary enable it though to get the installation of HyperConverged to continue, but once the installation finished, we removed it again.

In other words, it seems to me that one *is not needed* to have a multus deployment (disableMultiNetwork: false) to successfully have running VM's and hence it should not be required. 

Version-Release number of selected component (if applicable):
OpenShift                : 4.7.6
OpenShift Virtualization : 2.6.1 

How reproducible:
Always.


Steps to Reproduce:
1. Install an OpenShift 4.7 cluster with "disableMultiNetwork: true" 

2. Install the Virtualization Operator

3. Create a hyperconverged deployment. 


Actual results:
Deployment of hyperconverged should suceed. 


Expected results:
Deployment of hyperconverged should fails with a message similar to "you need to enable multinetwork functionality to be able to install hyperconverged"


Additional info:
In order to change an installation from "disableMultiNetork: true" to "disableMultiNetork: false" one is needed to "trick" the network operator by changing its applied state, otherwise the operator will tell you that you can't change the parameter after install. This is of course unsupported, but that's not the point here. 

The point is simply, a working hyperconverged deployment doesn't seem to need "disableMultiNetwork: false" and hence should not require it at installation. 

I hope I made sense and please tell me if I'm missing something.


Ps. 
I'm not able to create a bug under the product "Container Native Virtualization (CNV)" (this product is simply not shown in the list of all products for me). And when trying to clone an existing one, ie. https://bugzilla.redhat.com/show_bug.cgi?id=1952509 I get a page saying that "Sorry, either the product Container Native Virtualization (CNV) does not exist or you aren't authorized to enter a bug into it.". That's why I need to create it here - maybe there is something wrong with the permissions for that product? I'm logged in as a regular user. 


Best regards,
Patrik,
Sweden


Note You need to log in before you can comment on or make changes to this bug.