Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
    • Tags

    Host provisioned with Satellite and activation key does not "set release"

    Posted on

    when ever I provision a host from satellite it seems to register , but the set release command is not evoked.

    So I get errors ( below ) when I do a "yum install update" but if I run the command "subscription-manager release --set=7.1" before I run the "yum install update" it works fine , how and where can I automate the "subscription-manager release --set=7.1" command??

    ( see attached file for more detail)

    [root@puppettest1 ~]# yum install update
    Loaded plugins: product-id, subscription-manager
    https://satprod.int.xxxxxxxxxxxxxx.com/pulp/repos/satprod/Devel/SOE-PCI/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
    Trying other mirror.

    One of the configured repositories failed (Red Hat Enterprise Linux 7 Server (RPMs)),
    and yum doesn't have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.
    
     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).
    
     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:
    
            yum-config-manager --disable rhel-7-server-rpms
    
     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:
    
            yum-config-manager --save --setopt=rhel-7-server-rpms.skip_if_unavailable=true
    

    failure: repodata/repomd.xml from rhel-7-server-rpms: [Errno 256] No more mirrors to try.
    https://satprod.int.aaaaari.com/pulp/repos/satprod/Devel/SOE-PCI/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

    Attachments

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2025 Red Hat