Bug 1871057

Summary: The field for manual IP address config is too short for IPv6
Product: Red Hat Satellite Reporter: Radovan Drazny <rdrazny>
Component: Discovery ImageAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: egolov, lzap, rabajaj
Target Milestone: 6.9.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-discovery-image-3.6.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-21 13:17:42 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:
Attachments:
Description Flags
FDI manual network config limit none

Description Radovan Drazny 2020-08-21 08:59:51 UTC 
Created attachment 1712146 [details]
FDI manual network config limit

Description of problem:
When you want to enter IPv6 address in FDI manually, and you need to use full-sized format of IPv6, you will hit the field limit, which is set to 30 characters.

Version-Release number of selected component (if applicable):
foreman-discovery-image-3.6.1-1

How reproducible:
always

Steps to Reproduce:
1. Boot FDI and go for the manual network setup
2. Try to enter a full-sized IPv6 address string.


Actual results:
You will hit the limit of 30 characters

Expected results:
IPv6 address can be entered.

Additional info:
Standard IPv6 address is 39 characters long - 4*8 (for hex digits) + 7 (for colon separators).
If we take this https://tools.ietf.org/html/rfc4291#section-2.5.5.2 in account, the maximum IPv6 address can be up to 45 characters long. The FDI field limit should be expanded to accept an address of this length.
Comment 1 Lukas Zapletal 2020-08-24 09:37:15 UTC 
There is a patch upstream which already fixes other issue and this one as well. https://projects.theforeman.org/issues/30662
Comment 2 Lukas Zapletal 2020-08-24 09:38:30 UTC 
Please test this build:

https://github.com/theforeman/foreman-discovery-image/pull/125

Then comment in the GH and we can close this BZ and the other one. TY.
Comment 4 Bryan Kearney 2020-09-07 08:04:32 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30662 has been resolved.
Comment 5 Roman Plevka 2021-01-07 15:59:22 UTC 
VERIFIED
on sat6.9.0-8.0

tested with value: 2607:f0d0:1002:0051:0000:0000:0000:0004
Comment 8 errata-xmlrpc 2021-04-21 13:17:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.9 Release), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2021:1313