Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-135111

Registration to insights fails for bootc installations

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • rhel-anaconda
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      When installing RHEL-10 with registration to Insights (rhsm --connect-to-insights), the registration to Insights fails:

      09:37:09,012 WARNING org.fedoraproject.Anaconda.Modules.Subscription:INFO:program:requests.exceptions.ConnectionError:
       HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/v1/syste
      ms (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f90e3035640>: Failed to establish a
       new connection: [Errno -2] Name or service not known'))
      

      However, if the registration is done manually (insights-client --register, either from chroot in installation environment or in installed system, it is successful on the first attempt. The failure happens both with stage and prod CDN, I've tested the registration also with package mode installation (which works OK) to rule out an infrastructure issue.

      What is the impact of this issue to you?

      UX impact in bootc installation mode.

      Please provide the package NVR for which the bug is seen:

      anaconda-40.22.3.39-1.el10

      How reproducible is this bug?:

      100%

      Steps to reproduce

      1.  Prepare kickstart file using bootc command together with rhsm ... --connect-to-insights.
      2.  Start installation of RHEL-10.2 using the kickstart file.

      Expected results

      Registration to Insights is successful.

      Actual results

      Registration to Insights fails.

      Additional notes

      I don't know if I should directly blame insights-client rather than Anaconda, but I believe the failure might be caused by some configuration of the installation environment - because the manual registration, as mentioned above, works fine. Therefore I'm setting the component to anaconda right now, with the prospect of moving it to insights if we find out everything is OK on Anaconda's side.

              anaconda-maint-list anaconda-maint-list
              rhn-support-jikortus Jiri Kortus
              anaconda-maint-list anaconda-maint-list
              Release Test Team Release Test Team
              Sagar Dubewar Sagar Dubewar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: