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.
Bug 1400028 - New container and New registry buttons are no longer buttons
Summary: New container and New registry buttons are no longer buttons
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Adam Ruzicka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-30 10:11 UTC by Peter Ondrejka
Modified: 2019-09-25 20:34 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman_docker-3.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:08:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
new_registry (9.86 KB, image/png)
2016-11-30 10:12 UTC, Peter Ondrejka
no flags Details
verification screenshot (30.80 KB, image/png)
2017-08-30 08:16 UTC, Adam Ruzicka
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 18021 0 None None None 2017-06-21 08:15:58 UTC

Description Peter Ondrejka 2016-11-30 10:11:37 UTC
Description of problem:

Buttons for creating a Container (Containers > All containers) and a Registry (Containers > Registries -- see the attached screenshot) no longer appear as buttons as it was in Satellite 6.2

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

Satellite 6.3 snap 6:
satellite-6.3.0-6.1.beta.el7sat.noarch
foreman-1.13.1-1.el7.noarch
katello-3.2.0-3.rc3.el7.noarch

Expected results:

Container UI should be consistent with the rest of Satellite UI and with previous versions.

Comment 1 Peter Ondrejka 2016-11-30 10:12:36 UTC
Created attachment 1226227 [details]
new_registry

Comment 4 Daniel Lobato Garcia 2017-06-21 07:48:51 UTC
This was already fixed upstream by http://projects.theforeman.org/issues/18021. I will link the issues, mark for 6.3 and put in POST.

Comment 5 Daniel Lobato Garcia 2017-06-21 08:15:56 UTC
Connecting redmine issue http://projects.theforeman.org/issues/18021 from this bug

Comment 6 Brad Buckingham 2017-08-08 20:13:32 UTC
Confirmed that the version of tfm-rubygem-foreman_docker included with the latest Satellite 6.3 snap includes the code for the referenced issue.

Comment 7 Adam Ruzicka 2017-08-30 08:16:55 UTC
Created attachment 1319909 [details]
verification screenshot

Comment 8 Adam Ruzicka 2017-08-30 08:17:16 UTC
Verified.
Version Tested: Satellite-6.3 Snap 13
Package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch
tfm-rubygem-foreman_docker-3.1.0-1.fm1_15.el7sat.noarch

Created a docker compute resource, navigated to Containers > All containers and Containers > Registries, Create container and Create registry links were styled as buttons, see verification image in #7

Comment 9 Bryan Kearney 2018-02-21 17:08:47 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.