Bug 1386340

Summary: Changing a host's Content View to "Default Organization View" does not make new content available
Product: Red Hat Satellite Reporter: German Pulido <gpulido>
Component: Content ViewsAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED NOTABUG QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.2.2CC: bbuckingham, gpulido, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-21 18:07:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description German Pulido 2016-10-18 17:38:13 UTC
Description of problem:
I have 2 test hosts on a new Satellite 6.2.2 installation. Hosts were registered to Satellite via Activation Keys, everything worked fine. Custom Content Views were created for each host. Some days later, when new content was available, instead of publishing a new content view version for the hosts, I changed the content view of the hosts to "Default Organization View" (this was done only as a test.). But running again a "yum update" on the hosts does not get the new content available, they keep saying there are no updates available (I am 100% positive there are available updates).

I even tried using the procedure here: https://access.redhat.com/solutions/1752493 which threw no error at all, but still the hosts see no new content. Satellite also says there are no errata available for the hosts, but as I said, there are.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Register a host to a custom Content View
2. Wait until there are availabe updates
3. Change the Content View to "Default Organization View".
4. Try to update the host

Actual results:
1. Host says there are no available updates.

Expected results:
1. Host picks the updates available on the new selected Content View

Additional info:

Comment 1 Brad Buckingham 2016-10-25 15:26:46 UTC
Hi, did you happen to run 'subscription-manager refresh' from the client?

When a content hosts environment or content view is changed from the server, the client is not currently aware that it changed.  As a result, the 'refresh' is needed.

Comment 2 German Pulido 2016-11-01 14:29:58 UTC
I did run subscription-manager refresh, but it did not seem to work, the client still said there were no updates. So far, I have had to unregister the server and register it again (with the same Activation Key) for it to take the changed content view correctly.



[root@rhel7 ~]# subscription-manager refresh
All local data refreshed
[root@rhel7 ~]#
[root@rhel7 ~]#
[root@rhel7 ~]# yum update
Loaded plugins: package_upload, product-id, search-disabled-repos, subscription-manager
rhel-7-server-rpms                                                                                                                               | 2.0 kB  00:00:00
rhel-7-server-satellite-tools-6.2-rpms                                                                                                           | 2.1 kB  00:00:00
No packages marked for update
[root@rhel7 ~]# 


Thanks!!

Comment 3 Brad Buckingham 2016-11-02 19:17:47 UTC
Thanks for the feedback.  

When you mentioned that you changed the Content View to the 'Default Organization View', was that change on the content host (UI: Hosts->Content Host) or the activation key (UI: Content->Activation Key)?

It will need to be on the Content Host, since changes to the Activation Key only affect hosts at registration time.  I assume that the change was to the Content Host based upon the description, but wanted to confirm.

Also, it would be great if we could get a foreman-debug (from satellite server) and the client logs (e.g. /var/log/messages) that cover the full scenario, as I have been unable to reproduce the scenario on my configuration.  Or if your configuration is accessible, I'd be happy to log in to take a look.

Comment 4 Brad Buckingham 2016-11-04 14:03:15 UTC
Clearing the NEEDINFO.  I have a reproducer.  Thanks!

Comment 6 Brad Buckingham 2016-11-04 14:38:33 UTC
It turns out that this is different than the upstream issue; therefore, will have to continue to work towards a reproducer.

Comment 8 Brad Buckingham 2016-11-08 22:01:00 UTC
So far, I am unable to reproduce this with 6.2.3.

This may be a yum caching issue.  Can you try the following?

subscription-manager refresh
yum clean all
yum repolist
yum update

Does the above 'yum update' show the content expected from the Default Organization View?

Comment 9 German Pulido 2016-11-16 14:26:48 UTC
Hi

Sorry for the delay, I have not been able to work with the customer for some time, so no updates here, but I will be able to work with them tomorrow so I hope to have more information by then.

Thanks!!

Comment 10 German Pulido 2016-11-21 16:35:56 UTC
Tested again with the customer, suggestion form comment 3 (changing the CV in the content host) along with "subscription-manager refresh" did the trick. I think this bug can be closed.

Thanks!

Comment 11 Brad Buckingham 2016-11-21 18:07:32 UTC
Thanks for the update!  For now, I'll close out the bugzilla; however, please feel free to re-open later if needed.