Sat 6 Content Views showing errata that should not be shown
I have one environment named Library and two content views in there, dev and prd.
I have set the dev content view to include everything, no filter. The prd content view is set up to include security, enhancements and bug fixes. I have the start date of this filter left blank and an end date on Dec 1st 2016. I have assigned a client to this view but under the Errata tab of the system I see some errata with a date issued after 12/1/16.
I have added another client to this prd view and I also see errata available with a date after 12/1/16.
Any ideas?
Responses
Gary,
It's not clear to me why your filter is not working as you expect, but I have some questions which may provide the necessary information.
Since you want to filter content from the Library which has an end date of December 1 2016, I think using an exclude filter, with a "Start Date" of December 2 2016 might achieve what you want. Also, are you using the "Updated On" or "Issued On" radio buttons when configuring the filter?
For more details about creating content filters, see CREATING A CONTENT FILTER.
Gary,
Thanks for your response. I'll be interested to hear the results of your next test.
One odd behaviour I found in the Satellite web UI is that when you save a change to a Content View's filter, there is no prompt given that the Content View must be published for the changes to take effect. You could happily make a number of changes, saving after making each change, but still find that the changes don't "work". I have raised a request for enhancement against the Satellite web UI, asking that some visual feedback be added when a Content View has been changed, but not published.
Gary,
I know it's a hunch, but it seems likely that if some hosts are not checking in with the Satellite Server, that this may be affecting the errata management. I suggest getting the "checkin" issue resolved in the other thread, then revisit this problem. Do you agree?
Gary,
Now that your problem, "Last Checkin date/time not updating" has been resolved, I'm curious to know if the error for which you created this discussion is resolved. I believe that, except for tweaking the content view filter's criteria a little, the problem is likely to have been resolved.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
