Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
@anazmy can you elaborate on:
"Actual results:
After a while the vm will loose the subscription. This happens to all VMs using this sub, not only one."
Sure, my point this is not affecting just one vm, but multiple vms, maybe all vms using derived subscriptions. Though I did not investigate the whole environment, but the impact was prominent.
(In reply to Ahmed Nazmy from comment #3)
> Sure, my point this is not affecting just one vm, but multiple vms, maybe
> all vms using derived subscriptions. Though I did not investigate the whole
> environment, but the impact was prominent.
I think a concern of QE for the z-stream are verification steps they can use once a resolution is presented.
Note: while testing the upgrade to the candlepin version for this bug the first time it started, the Candlepin service took 4-5 minutes to start on one of my lab hosts.
After a restart, Candlepin came up fast as normal but if you see a failure in the upgrade to 6.8.5 that includes this error in the installer:
[DEBUG 2021-03-25T13:43:53 main] Foreman_smartproxy[sat-r220-10.lab.eng.rdu2.redhat.com](provider=rest_v3): Received response 500 from request to https://sat-r220-10.lab.eng.rdu2.redhat.com/api/v2/smart_proxies?search=name=%22sat-r220-10.lab.eng.rdu2.redhat.com%22
[ERROR 2021-03-25T13:43:53 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[sat-r220-10.lab.eng.rdu2.redhat.com]: Could not evaluate: Proxy sat-r220-10.lab.eng.rdu2.redhat.com cannot be retrieved: unknown error (response 500)
[ERROR 2021-03-25T13:43:53 main] /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in `proxy'
it may be because Candlepin's startup was slow. If this happens, please let us in Engineering know so we can track down the cause if this is a general issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Satellite 6.8.5 Async Bug Fix Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:1057