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 1376040

Summary:	IPA client ipv6 - invalid --ip-address shows traceback
Product:	Red Hat Enterprise Linux 7	Reporter:	Pavel Picka <ppicka>
Component:	ipa	Assignee:	IPA Maintainers <ipa-maint>
Status:	CLOSED ERRATA	QA Contact:	Pavel Picka <ppicka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	mbabinsk, mbasti, pvoborni, rcritten, tkrizek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-4.5.0-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 09:39:54 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 Pavel Picka 2016-09-14 13:41:08 UTC

Description of problem:
When specify invalid ipv6 in --ip-address, ipa-client-install shows traceback

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

How reproducible:
always


Steps to Reproduce:
1. ipa-client-install --ip-address 2002:2222:: # non exist/present IPv6 

Actual results:
[root@rhel06 ~]# ipa-client-install --ip-address 2002:2244:6644:/128
WARNING: ntpd time&date synchronization service will not be configured as
conflicting service (chronyd) is enabled
Use --force-ntpd option to disable it and force configuration of ntpd

Traceback (most recent call last):
  File "/usr/sbin/ipa-client-install", line 3128, in <module>
    sys.exit(main())
  File "/usr/sbin/ipa-client-install", line 3109, in main
    rval = install(options, env, fstore, statestore)
  File "/usr/sbin/ipa-client-install", line 2306, in install
    if not check_ip_addresses(options):
  File "/usr/sbin/ipa-client-install", line 1793, in check_ip_addresses
    ipautil.CheckedIPAddress(ip, match_local=True)
  File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 138, in __init__
    super(CheckedIPAddress, self).__init__(addr)
  File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 123, in __init__
    self._net = netaddr.IPNetwork(addr, flags=self.netaddr_ip_flags)
  File "/usr/lib/python2.7/site-packages/netaddr/ip/__init__.py", line 926, in __init__
    raise AddrFormatError('invalid IPNetwork %s' % addr)
netaddr.core.AddrFormatError: invalid IPNetwork 2002:2244:6644:/128


Expected results:
error message of invalid IP specified

Comment 2 Tomas Krizek 2016-09-19 07:09:36 UTC

This is already fixed upstream.

Upstream ticket: https://fedorahosted.org/freeipa/ticket/6296

Comment 3 Martin Bašti 2016-09-19 07:57:31 UTC

This is *not* fixed. Ticket mentioned above solves only link-local addresses. This BZ is about showing traceback when incorrect address is used (e.g: 2001::db8::1). We should handle this nicely and show just error message not traceback.

Comment 4 Martin Babinsky 2016-09-21 08:27:40 UTC

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/ddf48f2fef344784b9e1918d2f2ee6feef9d4c04

Comment 6 Pavel Picka 2017-06-02 14:19:47 UTC

verified ipa-server-4.5.0-14.el7.x86_64

# ipa-client-install --ip-address 2002:2244:
Usage: ipa-client-install [options]

ipa-client-install: error: option --ip-address: invalid IP address 2002:2244:: failed to detect a valid IP address from '2002:2244:'

Comment 7 errata-xmlrpc 2017-08-01 09:39:54 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, 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/RHBA-2017:2304