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

403 error when not subscribed is confusing

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

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhel-9.4.z, rhel-10.0
    • subscription-manager
    • None
    • No
    • None
    • subs-client-tools-2
    • None
    • False
    • False
    • Hide

      None

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

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

      {}I have a fresh rhel-10.0 toolbox on my system. I needed to dnf install a package in the container. Here is the error I get:

      $ sudo dnf install container-tools -y
      Updating Subscription Management repositories.
      subscription-manager is operating in container mode.
      Red Hat Enterprise Linux 10 for x86_ 531  B/s | 468  B     00:00    
      Errors during downloading metadata for repository 'rhel-10-for-x86_64-appstream-rpms':
        - Status code: 403 for https://cdn.redhat.com/content/dist/rhel10/10/x86_64/appstream/os/repodata/repomd.xml (IP: 173.222.140.251)
      Error: Failed to download metadata for repo 'rhel-10-for-x86_64-appstream-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
      I know that 403 is a permissions error, but nowhere does the error state in plain terms that there's a permission error. It makes it look like an outage of the CDN. Furthermore, the subscription manager says it is operating in "container mode" (whatever that means) and that makes it sound as if it's legit / subscribed / etc. 

      Nowhere is there an error to help me understand I need to register the system to install packages. Or if the host system isn't RHEL (it isn't, it's Fedora) that it's not possible to register the system at all with rhsm. 

      What is the impact of this issue to you?

      Took a while to figure out what the problem was - I'm not familiar with subscription-manager. It made for a rough experience since I had to research the issue. Now, in order to develop an application using RHEL 10 as a base, I will have to make a new container on centos-stream to develop it :-/ 

      I found a note in the access.redhat.com forum showing that several others were confused by this issue, and it's not limited to containers - stated OP was a RHEL VM.

      (See https://access.redhat.com/discussions/b77fe50d-f505-446e-8dd7-a9240e1ac86f )

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

      subscription-manager-1.30.6.1-1.el10_0.x86_64

      How reproducible is this bug?:

      Reproduces every time on UBI containers. 
      I couldn't reproduce it on a RHEL 9 VM. But there's reports of it happening in that env.

      Steps to reproduce (on UBI container)

      1. Install a RHEL system (container) on a non-RHEL host
      2. Don't register the system.
      3. Attempt to install a package via dnf.
      4. Get 403 error messages.

      Expected results

      Receive an error message that explains that my system isn't registered and gives me instructions or pointers on how to register it.

      Actual results

      Error message listed above.

              jhnidek@redhat.com Jiri Hnidek
              duffy@redhat.com Máirín Duffy
              CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
              CSI Client Tools Bugs Bot CSI Client Tools Bugs Bot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: