RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1338680 - [RFE] Provide a way to fill activation key and Organization when subscribe to Satellite&SAM in node ng
Summary: [RFE] Provide a way to fill activation key and Organization when subscribe to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: pre-dev-freeze
: 7.3
Assignee: Dominik Perpeet
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
 
Reported: 2016-05-23 09:12 UTC by wanghui
Modified: 2016-08-05 09:12 UTC (History)
8 users (show)

Fixed In Version: cockpit-0.114-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-04 13:47:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
subscriptions page (36.26 KB, image/png)
2016-05-23 09:12 UTC, wanghui
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1442 0 normal SHIPPED_LIVE cockpit bug fix and enhancement update 2016-08-04 17:45:50 UTC

Description wanghui 2016-05-23 09:12:55 UTC
Created attachment 1160482 [details]
subscriptions page

Description of problem:
It should provide a way to to fill activation key and Organization when subscribe to Satellite/SAM.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-3.6-20160518.0
imgbased-0.6-0.1.el7ev.noarch
cockpit-0.103-1.el7.x86_64
cockpit-ovirt-dashboard-0.9.1-0.0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install node ng
2. Check subscription page

Actual results:
1. There is no options to fill the activation key and organization when subscribe to Satellite and SAM.

Expected results:
1. It should provide a way to to fill activation key and Organization when subscribe to Satellite/SAM.

Additional info:

Comment 2 Stef Walter 2016-07-11 08:17:54 UTC
Work upstream here: https://github.com/cockpit-project/cockpit/pull/4697

Comment 4 Stef Walter 2016-07-14 12:17:18 UTC
Basic test of this upstream here: https://github.com/cockpit-project/cockpit/blob/master/test/verify/check-subscriptions#L118

Comment 7 errata-xmlrpc 2016-08-04 13:47:56 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://rhn.redhat.com/errata/RHBA-2016-1442.html


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