Host provisioned with Satellite and activation key does not "set release"
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
Responses
Brian, do you have the release set in the activation key in the following location?
Content -> Activation Keys -> <select activation key> -> Details Tab -> Activation Key Content -> Release Version
Also, you want to use either 'yum install package_name' or 'yum update', executing 'yum install update' is attempting to install a package called 'update' which doesn't exist.
I have the same problem, even weirder.
I have two activation keys, where the only difference is that they point to a different environment within the same life cycle (one points to 'development' step, the other to 'production'). Both activation keys have the 'Release version' properly set. Now, servers using the 'development' activation key work as expected but the ones using the 'production' activation key don't set the release version when subscribing. If I go to the 'content hosts' screen, find those hosts and set the release version by hand, everything goes OK (after a subscription manager refresh && subscription manager repos --list).
Why could this be happening?
Oh, by the way, I'm using Satellite 6.1.10.
More info about this issue: this only happens when I copy an activation key to create another that is a clone of the former but for the environment (i.e. mykey-development versus mykey-production).
If I create the second key anew, the host's release version gets assigned as expected. Is it a known bug on Satellite 6.1.x?
I've run into this issue a few times as well, and have found a few ways to resolve the issue:
Modify the host directly to enable the release version, after the host has been provisioned
Hosts > Content Hosts > (select Host) Then select the correct Release Version from the drop-down- Modify The activation Key used to subscribe the system using a specific release version (as described by PixelDrift.NET Support above)
Modify the subscription snippet host provisioning template to include a dynamic configuration based upon the host information. This requires ensuring the snippet is included in the post-configuration of your kickstart. Some example code you could add to your registration snippet is below:
<% if @host.operatingsystem.name == "RedHat" %> <% if @host.operatingsystem.major.to_i == 5 %> subscription-manager release --set=5Server <% end %> <% if @host.operatingsystem.major.to_i == 6 %> subscription-manager release --set=6Server <% end %> <% if @host.operatingsystem.major.to_i == 7 %> subscription-manager release --set=7Server <% end %> <% end %>
I have started using method #3 as my preferred option, due to the dynamic control of it offers. In the particular case identified here, since '7Server' was the default selected - you could simply modify the snippet to set the version to '7.1' instead.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.