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.
Created attachment 1233935[details]
Status of remote execution jobs before attempting re-run
Description of problem: Remote execution job service rhsmcertd ran on 835 hosts. When customer tried to rerun the failed jobs, the error message "Oops, we're sorry but something went wrong stack level too deep" appeared.
Version-Release number of selected component (if applicable): Satellite 6.2.6. Was occurring with 6.2.4 as well.
How reproducible: Attempt to re-run failed remote execution jobs with more than a handful of hosts
Actual results:
Error page
Expected results:
Jobs re-run
Additional info:
From the 6.2.7 notes:
* Remote Execution against many hosts was causing errors to appear. This
case is now handled correctly. (BZ#1367606, BZ#1372708)
Customer is upgrading to 6.2.7 this Friday. I'm curious to see if the errors go away.
Verification steps:
1. prepare large amount of fake hosts
cat <<END | bundle exec rails console
User.current = User.first
group = Hostgroup.unscoped.find_or_create_by(:name => 'fakes')
group.save
location = Location.first
organization = Organization.first
group.locations << location
group.organizations << organization
1000.times do |i|
i = i+11
puts i
h = Host.new(:name => "host-#{i+10}.sat.test")
h.hostgroup_id = group.id
h.organization = organization
h.location = location
h.save!
end
END
2. run any job against the `~ test` hosts
3. wait until it fails
4. use 'Rerun failed'
5. form is displayed properly and running the job works (after selecting the type of query, that we track in https://bugzilla.redhat.com/show_bug.cgi?id=1481981
Comment 21Satellite Program
2018-02-21 16:54:37 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
Created attachment 1233935 [details] Status of remote execution jobs before attempting re-run Description of problem: Remote execution job service rhsmcertd ran on 835 hosts. When customer tried to rerun the failed jobs, the error message "Oops, we're sorry but something went wrong stack level too deep" appeared. Version-Release number of selected component (if applicable): Satellite 6.2.6. Was occurring with 6.2.4 as well. How reproducible: Attempt to re-run failed remote execution jobs with more than a handful of hosts Actual results: Error page Expected results: Jobs re-run Additional info: