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.

Description of problem:

When IPv6 is disabled using recommended method:

  /etc/sysctl.conf:

  net.ipv6.conf.all.disable_ipv6 = 1
  net.ipv6.conf.default.disable_ipv6 = 1

ipa-server-upgrade fails trying to connect to port 8080 tcp on ::1 and time out (Checking if a service was started)

  /var/log/ipaupgrade.log:

  Failed to connect to port 8080 tcp on ::1

Reenabling IPv6 solves the upgrade, but if it is disabled again after upgrade, ipactl start fails with long wait times too and related services don't start.


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

ipa-server-4.5.0-21.el7

How reproducible:

Always when IPv6 is disabled

Steps to Reproduce:
1. Disable IPv6
2. run ips-server-upgrade

According to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/installing-ipa.html#prerequisites
IPv6 must be enabled on the system.

(In reply to Florence Blanc-Renaud from comment #2)
> According to
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/
> html/Linux_Domain_Identity_Authentication_and_Policy_Guide/installing-ipa.
> html#prerequisites
> IPv6 must be enabled on the system.

Fair, but it could be better to detect it and show a message. I know rpm updates should run unattended, but printing a message about how the IPA installation will not be upgraded and will remain down until IPV6 is reenabled and ipa-server-upgrade is run again could help a lot.

This case was a small customer that when the updated was installed was dumbfounded to find the server not working at all, did not understood the problem with the long timeouts.

Upgrade now checks for IPv6 

https://pagure.io/freeipa/c/f05afa4813f425e9fc9960f63100431a78310638

*** This bug has been marked as a duplicate of bug 1477367 ***