Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1801779

Summary:	Disable Autoconf only option for rhel8 host and above
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.0	CC:	bugs, dholler
Target Milestone:	ovirt-4.4.0	Flags:	pm-rhel: ovirt-4.4+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine 4.4.0-27 22b6f82	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:01:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Burman 2020-02-11 16:02:04 UTC

Description of problem:
Disable Autoconf only option for rhel8 host and above

We decided to disable/grayout the Autoconf option for IPv6 bootprotocol as it's not supported in NetworkManager on rhel8 hosts.

libnmstate.error.NmstateNotImplementedError: Autoconf without DHCP is not supported yet

NM doesn't accept by attention autoconf without dhcpv6, it accepts none, static IPv6 address, poly(DHCPv6 + autocnf) or dhcpv6 only.
So this option should disabled for rhel8 hosts, but enabled for rhel7 hosts.

When adding a fresh rhel 8.2 host to RHV 4.4 and it's a dual stack host with RA(autoconf) configured, RHV will set it as poly and host will be in sync(ovirtmgmt will be in sync).

Version-Release number of selected component (if applicable):
rhvm-4.4.0-0.19.master.el7.noarch

Comment 1 Dominik Holler 2020-02-17 09:29:26 UTC

I set the target milestone of this bug to 4.4.0, because after 4.4.0 we should avoid the introduction of new limitations.

Comment 2 Dominik Holler 2020-03-09 11:22:13 UTC

*** Bug 1785382 has been marked as a duplicate of this bug. ***

Comment 3 Michael Burman 2020-03-29 11:19:58 UTC

Verified on - rhvm-4.4.0-0.29.master.el8ev.noarch

Comment 4 Sandro Bonazzola 2020-05-20 20:01:49 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.