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.

Description of problem:
After creation of an activation key, where a lifecycle environment and composite content view is choosen, the spinner is shown in the middle of the screen and it keeps spinning although the activation key has already been made.

Version-Release number of selected component (if applicable):
Satellite 6.1.0 GA RC 3 (SNAP8-C3)

How reproducible:


Steps to Reproduce:
1. Create activation key with lifecycle env and ccv
2. Watch spinner spin for a while
3. interrupt by choosing some menu item
4. Go back and see the act.key has been made

Actual results:


Expected results:


Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Hi Fred,  I am not seeing the same behavior on the current Sat6.1.1 GA build.  Would it be possible to capture and attach the foreman-debug for the machine when this is occurring?

Hi Brad. I am. An the third act-key I made (first test1, then test4 and then test6. On test6 it's hanging. All 3 keys have lifecycle-env and cv or ccv attached. All different.

I've add screenshot and foreman-debug

Created attachment 1049455 [details]
screenshot

Created attachment 1049456 [details]
foreman-debug as requested

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.