Bug 1361993 - Listing product content for an activation key does not show default state in Hammer
Summary: Listing product content for an activation key does not show default state in ...
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-01 06:41 UTC by jalviso
Modified: 2019-04-01 20:27 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2018-02-21 16:49:54 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 16000 None None None 2016-08-10 14:33 UTC

Description jalviso 2016-08-01 06:41:18 UTC
Description of problem:

In Hammer, listing product content for an activation key does not show default state (whether it is Yes/No). It only shows "Enabled?" column as "default" but it does not show the actual status.

In SatWEBUI, the Product Content status is shown as defaulted to Yes or No.


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


How reproducible: Always


Steps to Reproduce:

1. List product content of activation key in Hammer:

# hammer activation-key product-content --id 2 --organization "Red Hat"
----|----------------------------------------------------|----|---|-------|------------------------------|--------
ID  |NAME                                                |TYPE|URL|GPG KEY| LABEL                        |ENABLED?
----|----------------------------------------------------|----|---|-------|------------------------------|--------
4425|Red Hat Enterprise Virtualization Manager 3.6 (RPMs)|    |   |       | rhel-6-server-rhevm-3.6-rpms |default 
2455|Red Hat Enterprise Linux 7 Server (Kickstart)       |    |   |       | rhel-7-server-kickstart      |default 
2456|Red Hat Enterprise Linux 7 Server (RPMs)            |    |   |       | rhel-7-server-rpms           |default 
----|----------------------------------------------------|----|---|-------|------------------------------|--------

2. In Satellite WEBUI, Content> Activation Key> Product Content>

each repo/product-content is shown if enabled or not (Enabled Yes/No)


Actual results:

Hammer output does not contain information as the WEBUI provides.


Expected results:

Hammer output to show product-content enabled status as Yes/No

Additional info:

Comment 3 Bryan Kearney 2016-08-10 16:17:29 UTC
Upstream bug component is Content Management

Comment 4 Bryan Kearney 2016-08-10 16:17:32 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/16000 has been closed

Comment 7 Peter Ondrejka 2016-10-21 11:33:01 UTC
Verified in Satellite 6.3 snap 5, enabled status is now present in the output of hammer command:

# hammer activation-key product-content --id 1
-----|----------------------------------------------------------|------|-----|---------|------------------------------------------|----------|---------
ID   | NAME                                                     | TYPE | URL | GPG KEY | LABEL                                    | ENABLED? | OVERRIDE
-----|----------------------------------------------------------|------|-----|---------|------------------------------------------|----------|---------
4751 | Red Hat Satellite Capsule 6.2 (for RHEL 7 Server) (RPMs) |      |     |         | rhel-7-server-satellite-capsule-6.2-rpms | no       | default 
4831 | Red Hat Satellite Tools 6.2 (for RHEL 7 Server) (RPMs)   |      |     |         | rhel-7-server-satellite-tools-6.2-rpms   | no       | default 
2456 | Red Hat Enterprise Linux 7 Server (RPMs)                 |      |     |         | rhel-7-server-rpms                       | yes      | default 
-----|----------------------------------------------------------|------|-----|---------|------------------------------------------|----------|---------

Comment 8 pm-sat@redhat.com 2018-02-21 16:49:54 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, 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-2018:0336


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