Bug 1917169

Summary:	Invalid host name when setting IPv6 NFS server during RHEL 8.3 Install
Product:	Red Hat Enterprise Linux 8	Reporter:	vuisdaog
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	NEW ---	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	jkonecny, jstodola, xzhou, yoyang
Target Milestone:	rc	Keywords:	Reopened, Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-09 07:28:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description vuisdaog 2021-01-17 20:14:19 UTC

Description of problem:
I have an NFS server setup with a RHEL 8.3 install. When I try to setup a network source during the installation and try to put an IPv6 address as the server address, it will say invalid host name. Ex. [ff:f:f:f::f]:/nfsshare

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


How reproducible: Easily reproducible


Steps to Reproduce:
1. Start an installation of RHEL 8.3
2. Go to installation source
3. Enter an NFS url of [ipv6 address]:[share]
4. Press Done

Actual results:
Should allow the URL to be passed in and return to installation menu and connect to NFS server

Expected results:
Invalid Host Name message

Additional info:

Comment 1 Yongcheng Yang 2021-01-18 01:30:00 UTC

(In reply to vuisdaog from comment #0)
> ...
> Actual results:
> Should allow the URL to be passed in and return to installation menu and
> connect to NFS server

From my understanding, it's the installation process that can't parse the ipv6 address.

If the [ipv6 address]:[share] is available, there's no problem on the NFS side IMO.

Comment 2 vuisdaog 2021-01-18 13:18:56 UTC

(In reply to Yongcheng Yang from comment #1)
> (In reply to vuisdaog from comment #0)
> > ...
> > Actual results:
> > Should allow the URL to be passed in and return to installation menu and
> > connect to NFS server
> 
> From my understanding, it's the installation process that can't parse the
> ipv6 address.
> 
> If the [ipv6 address]:[share] is available, there's no problem on the NFS
> side IMO.

Yeah, you are correct. I just didn't know which category to put the bug in if it was an installation bug.

Comment 3 Yongcheng Yang 2021-01-18 14:01:41 UTC

I'm moving this over to the anaconda team, which probably is not correct (please feel free to re-triage it).

Comment 5 RHEL Program Management 2022-07-17 07:27:28 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 6 Jan Stodola 2022-08-09 14:17:20 UTC

Reopening, reproduced with RHEL-8.6.

1) The following format is refused as an invalid host name:
[ff:f:f:f::f]:/nfsshare


2) The following format is accepted without any errors/warnings in GUI, but not used by the installer:
ff:f:f:f::f:/nfsshare

And the following error can be found in anaconda.log:
ERR ui.gui.spokes.installation_source: ValueError: too many values to unpack (expected 2)


So, 1) should be accepted and used by the installer, 2) should be refused as an invalid host name or parsed properly.

Comment 10 RHEL Program Management 2023-02-09 07:27:47 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 13 RHEL Program Management 2023-08-09 07:28:22 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.