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

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	jkonecny, jstodola, xzhou, yoyang
Target Milestone:	rc	Keywords:	MigratedToJIRA, Reopened, Triaged
Target Release:	8.0	Flags:	pm-rhel: mirror+
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-09-18 15:30:03 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.

Comment 15 RHEL Program Management 2023-09-18 15:00:58 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 16 RHEL Program Management 2023-09-18 15:30:03 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.