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: On the New Container page, it is possible to click the "Next" button, when no Docker compute resource has been created. This results in an improperly formatted error page.
Version-Release number of selected component (if applicable):
Nightly RHEL6.5/7
How reproducible:
Always
Steps to Reproduce:
1. Ensure you have no Docker computer resources crated.
2. Navigate to Containers -> New container
3. You should have an error displayed on the page stating you need a Docker computer resource. If not, go to step 1.
4. Click the "Next" button.
Actual results:
User is able to click the next button and initiate the next step. However, an error page is displayed with the improperly formatted error message below.
Warning!
undefined method `[]' for nil:NilClass
Expected results:
The "Next" button is disabled unless the Docker computer resource has been created and/or a proper error message is displayed on the next page.
Comment 1RHEL Program Management
2014-11-10 17:03:02 UTC
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.
Moving to POST since upstream bug http://projects.theforeman.org/issues/8342 has been closed
-------------
Vanya Jauhal
Applied in changeset commit:foreman-docker|2fed5c014e06f2c90de96e116a10437977685128.
Verified on: Satellite-6.1.0-RHEL-7-20150303.0 and Satellite-6.1.0-RHEL-6-20150303.0
Steps to verify:
1. Ensured that no Docker-based Compute Resource was not created
2. Navigated to Containers > New Container
3. The following message was shown: "You need a Docker compute resource in order to create containers. Please add a new one and try again.". And the next button was not shown, not allowing me to proceed to next step until a Docker-based Compute Resource was created.
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-2015:1592