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 1746792 - Incorrect error handling for Update all packages via Remote Execution
Summary: Incorrect error handling for Update all packages via Remote Execution
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Collections
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Ondřej Pražák
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-29 09:42 UTC by Stephen Wadeley
Modified: 2019-10-22 19:49 UTC (History)
2 users (show)

Fixed In Version: rubygem-katello-3.12.0.21-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:49:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 27768 0 None None None 2019-09-03 12:27:27 UTC

Description Stephen Wadeley 2019-08-29 09:42:52 UTC 
Description of problem:

When on the Hosts Collection page, and selecting "Package Installation, Removal, and Update", and then "Update all packages" and select "via Remote Execution" option, this error was displayed:

 Oops, we're sorry but something went wrong No hosts have been specified.


Version-Release number of selected component (if applicable):
On a new install of 6.6 fro latest snap while testing BZ#1728289

~]# rpm -q tfm-rubygem-katello
tfm-rubygem-katello-3.12.0.18-1.el7sat.noarh

How reproducible:


Steps to Reproduce:
1. Create three or more hosts and add them to a Host Collection
2. Create custom Product and repo with packages, add to an activation key.
4. Register the hosts and use auto attach to add product to hosts
5. Navigate Host Collections > TestHC and select "Package Installation, Removal, and Update" 
6. Try to "Update all packages" and select "via Remote Execution"

Actual results:

error is displayed.

 Oops, we're sorry but something went wrong No hosts have been specified.

Clicking the Back button takes me to the Overview page, not the Host Collection page.

Expected results:


Command works or gives more accurate error and useful error message


Clicking the Back button takes me to the Host Collection page.


Additional info:

If I select "via Remote Execution -- customize first", I see this error:


 Oops, we're sorry but something went wrong ERF42-4995 [Foreman::Exception]: Invalid authenticity token


Clicking the Back button takes me to the Overview page, not the Host Collection page as I expect.
Comment 2 Ondřej Pražák 2019-09-03 12:27:26 UTC 
Created redmine issue https://projects.theforeman.org/issues/27768 from this bug
Comment 3 Bryan Kearney 2019-09-03 14:01:26 UTC 
Upstream bug assigned to oprazak
Comment 4 Bryan Kearney 2019-09-03 14:01:27 UTC 
Upstream bug assigned to oprazak
Comment 5 Bryan Kearney 2019-09-09 22:01:34 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27768 has been resolved.
Comment 8 Bryan Kearney 2019-10-22 19:49:24 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.