Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1284577

Summary:	New RHSM repos do not appear as expected
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	Release	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED DEFERRED	QA Contact:	libra bugs <libra-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.1.0	CC:	aos-bugs, bcourt, bleanhar, candlepin-bugs, crog, dmcphers, dstadiem, erich, jokerman, kurktchiev, mmccomas, pep, sdodson, sgraf
Target Milestone:	---	Keywords:	Triaged, UpcomingRelease
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1297059 (view as bug list)		Environment:
Last Closed:	2016-04-08 15:29:08 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1297059

Description Scott Dodson 2015-11-23 15:46:01 UTC

Description of problem:
Last Thursday a new channel in RHSM was created, 'rhel-7-server-ose-3.1-rpms', without re-registering a system this channel does not show up.


Version-Release number of selected component (if applicable):
subscription-manager-1.15.9-15.el7.x86_64

How reproducible:
Seems like 100% though it's hard to test because you have to have a system that was registered prior to the new channel being created so if you register a system now it won't show up.

Steps to Reproduce:
1. Register a system via rhsm
2. Have a new repo created
3. Attempt to attach to that repo

Actual results:
New repo doesn't show up

Expected results:
new repo shows up

Additional info:
Remove and attach seems to work as a workaround but does remove free up the entitlement in RHSM?

subscription-manager remove --serial=###
subscription-manager attach --pool=###

Comment 2 Scott Dodson 2015-11-23 15:47:16 UTC

subscription-manager refresh has no effect

Comment 3 Brenton Leanhardt 2015-12-03 14:46:22 UTC

We're still hearing reports of customers hitting this.  Can this be given some priority?  I suspect we'll hit this problem for every OpenShift release.

Comment 4 Chris "Ceiu" Rog 2016-01-14 15:49:42 UTC

Having a bit of trouble reproducing this. The only thing I could do to generate a similar situation was adding a subscription to a backing pre-2.0 Candlepin instance after a consumer had registered with subman (so far this sounds about right). I was able to resolve the issue by performing a refresh_pools operation on Candlepin directly. At that point, the new subscription started showing up in `subscription-manager list --available` and clients were able to attach to it fine.

Where I think we're deviating a bit is that it looks like you already have a pool ID, which implies a refresh had already been done to cause the new pool to be generated.

Comment 5 Scott Dodson 2016-01-25 14:37:10 UTC

Sorry, I really don't have a good idea of the candlepin side of things here, just that as an end user of RHSM managed system I had to remove and attach subscriptions. I believe this is a new repo added to an existing subscription.

Comment 8 David Stadiem 2016-01-25 15:56:19 UTC

This is not a sku issue. I would recommend looping in the Candlepin team. They would be able to provide insight into the issue with registering systems while introducing a new repo.