Bug 1437586 - Activation Key / Content View information always asking for content view
Summary: Activation Key / Content View information always asking for content view
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.7.0
Hardware: All
OS: All
medium
medium
Target Milestone: 6.10.0
Assignee: Jonathon Turel
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-30 15:27 UTC by Waldirio M Pinheiro
Modified: 2021-11-16 14:08 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:08:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32225 0 Normal New Activation key details page - bizzare behavior 2021-03-29 17:38:52 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:08:40 UTC

Description Waldirio M Pinheiro 2017-03-30 15:27:44 UTC
Description of problem:
When accessing one AK or just creating a new one, we define the Content View and then we click on Save, after alter tabs *Subscriptions,Product Content, Host Collections or Associations*, when we come back to Details tab, we are asked again to select the Content View. We can see the text info as *You must select a content view in order to save your environment.*

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

How reproducible:
100%

Steps to Reproduce:
1. Create AK
2. Define CV
3. Alter TAB
4. Come back to Details tab

Actual results:
Always asking for save the CV

Expected results:
CV saved.

Additional info:

Comment 2 Brad Buckingham 2017-04-03 15:53:14 UTC
Note: this issue also exists on upstream nightly.

Comment 3 Brad Buckingham 2017-04-03 15:56:33 UTC
Created redmine issue http://projects.theforeman.org/issues/19137 from this bug

Comment 4 Satellite Program 2018-02-27 17:05:41 UTC
Upstream bug assigned to ehelms

Comment 5 Bryan Kearney 2018-10-03 19:17:53 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 7 Bryan Kearney 2020-03-04 14:08:15 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 8 Bryan Kearney 2020-04-02 12:33:01 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 10 Mike McCune 2020-12-09 22:17:16 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in approximately a month. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 12 Mike McCune 2021-01-19 21:25:32 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.

Comment 14 Mike McCune 2021-03-11 18:51:08 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in one month's time. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 15 Partha Aji 2021-03-29 17:38:51 UTC
Connecting redmine issue https://projects.theforeman.org/issues/32225 from this bug

Comment 16 Bryan Kearney 2021-05-09 16:21:34 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32225 has been resolved.

Comment 23 errata-xmlrpc 2021-11-16 14:08:26 UTC
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702


Note You need to log in before you can comment on or make changes to this bug.