Satellite 6.1.x - Bugs/issues
I have been working through several bugs/issues with Satellite 6.1.x and I was hoping other people could list issues they have found to confirm it's not just the installation (have confirmed these in multiple installations).
Host Groups
My primary issue is when cloning host groups, the basic bugs are.
1. If you clone a host group, any config groups included in that host group are not cloned
2. If you clone a host group, any overrides for parameters set are not maintained (so host group level overrides need to be re-created after clone)
Strangely, if you have assigned classes directly to the host group (not through config groups) these appear to clone OK.
Another issue I have found is that if you specify a parameter override in the global scope of a Host Group, when you clone that Host Group it will generate the following error (when clicking submit):
Host Group Not Found
Please try to update your request
When removing the parameter the Host Group will clone again ok.
Access Insights
If you disable Access Insights under the following menu
Access Insights -> Manage
All pages under the 'Access Insights' menu return '403 - Permission Denied' errors, rather than a meaningul message such as "Access Insights is currently disabled'
Has anyone seen these same issues? Is there anything else I should be looking out for? Is the Satellite 6.2 beta going to be open?
Responses
Red Hat
Pro
755 points
The parameters issue is being tracked at https://bugzilla.redhat.com/show_bug.cgi?id=1253655. It is already fixed, and will be included in the 6.2 release. I am asking folks to look at the other issues as well.
Red Hat
Pro
755 points
My understanding is that it is disabled by default. Machines should not be sending data. Your subscription should allow you 10 machines to try it out, but you would need to enabkle it. You need to follow the steps at
https://access.redhat.com/insights/getting-started/direct/
In order to enable it per machine.
Red Hat
Guru
2300 points
regarding this
Currently doesn't resolve the UID's of VMware ESX hosts retrieved
through executing virt-who to hostnames. I know this is a known bug
but it really needs to be resolved. In environments with 100+ ESX hosts,
renaming hosts in Satellite 6 by hand is extremely tedious.
newer virt-who does in fact do this. You'll find newer virt-who in the Satellite Tools repo. Add the following to your virt-who config.
hypervisor_id=hostname
Regarding Red Hat (formerly Access) Insights, whilst the server-side is enabled, the clients are NOT by default. They are explicitly enabled when one includes the access_insights puppet class on a host group. You need both before data is sent to the portal.
Red Hat
Pro
755 points
On Content Views:
Not really arbitrary. Rather, it is because each repo can only be consumed one time so have different versions of the same repo seemed odd.
On LIfecycle Environments:
I though we had an RFE for this, I will ask and add it if not there
On ISO Download:
We are testing the 6.1.5 version right now.
I agree with the issue around keeping a history of content filters. One workaround for date-based errata filters I have been using is to add them, rather than replace them but that does rely on systems administrators all doing the right thing. This wouldn't work when filtering things out in later versions that were included in earlier versions.
Search seems to inconsistent in Satellite and I'm not sure if content host filtering is the only case in which you need wildcards. I'd be happier with one or the other -- filtering as you type or having to use wildcards -- because it makes it easier when training others and writing doco!
We have the same issue with dates and would also like this fixed.
I can confirm that upping the entries_per_page setting does up the time to render significantly. I changed mine to 50 and, while it did not slow down as dramatically as it did for you (presumably you set it to ~100), it slowed down the extent that it would have been much quicker for me to use entries_per_page=20 and use the scroll bar to scroll down for the additional hosts.
What we need most of all in 6.2, though, is the ability to run arbitrary commands on content hosts, particularly the ability to reboot. We are fairly happy with the rest of 6.1.x but we only use it for patching so far.
Doug,
Regarding "...the ability to run arbitrary commands on content hosts", this is will be available in Red Hat Satellite 6.2 and known as "remote execution". It is available now in the Red Hat Satellite 6.2 Beta. For details of how to use it and examples, refer to https://access.redhat.com/documentation/en/red-hat-satellite/version-6.2-beta/host-configuration-guide/#chap-Host_Configuration_Guide-Running_Remote_Jobs_on_Satellite_Hosts.
PixelDrift.NET Support,
Regarding the issues noted on 14 January 2016, I think these would best be dealt with via bug tickets. Are you OK with that, or would you prefer they continue here? At a minimum, I would suggest raising the search RFE as an actual RFE, rather than leaving it here.
Discussion threads are great for just that, but to drive changes to the product, I think a bug report is best.
Red Hat
25369 points
I discussed this with Russell today. Better visibility on bug and RFE ticket progress and resolution is something we're going to look into. I definitely understand the frustration of trying to track progress on an issue that is being worked on in a non-public BZ.
Thanks again for your feedback. What happens with feedback, whether it comes from inside or outside Red Hat, should be transparent. There are times BZ tickets contain sensitive customer information, in which case their content must be kept private.
We are working to improve the handling of feedback, both on the product and documentation.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.