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 1524366 - Upgrade from 6.2 ->6.3 snap28 w/ customer db failed at upgrade step: correct_puppet_environments
Summary: Upgrade from 6.2 ->6.3 snap28 w/ customer db failed at upgrade step: correct_...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Andrew Kofink
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-11 10:55 UTC by Sachin Ghai
Modified: 2020-04-28 16:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-28 19:35:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
foreman-debug (10.52 MB, application/x-xz)
2017-12-11 11:02 UTC, Sachin Ghai 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21969 0 Normal Rejected upgrade katello fail 2020-06-02 17:01:29 UTC

Description Sachin Ghai 2017-12-11 10:55:09 UTC 
Description of problem:


out: Upgrade Step: correct_puppet_environments (this may take a while) ...
[sat63_Server] out: rake aborted!
[sat63_Server] out: Not all the services have been started. Check the status report above and try again.
[sat63_Server] out: /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.4.5.35/lib/katello/tasks/reimport.rake:10:in `block (2 levels) in <top (required)>'
[sat63_Server] out: Tasks: TOP => katello:correct_puppet_environments => katello:check_ping
[sat63_Server] out: (See full trace by running task with --trace)
[sat63_Server] out: {:services=>
[sat63_Server] out:   {:pulp=>{:status=>"ok", :duration_ms=>"38"},
[sat63_Server] out:    :pulp_auth=>{:status=>"ok", :duration_ms=>"26"},
[sat63_Server] out:    :candlepin=>{:status=>"ok", :duration_ms=>"19"},
[sat63_Server] out:    :candlepin_auth=>{:status=>"ok", :duration_ms=>"29"},
[sat63_Server] out:    :foreman_tasks=>
[sat63_Server] out:     {:status=>"FAIL",
[sat63_Server] out:      :message=>
[sat63_Server] out:       "some executors are not responding, check /foreman_tasks/dynflow/status"}},
[sat63_Server] out:  :status=>"FAIL"}
[sat63_Server] out: foreman-rake katello:correct_puppet_environments COMMIT=true failed! Check the output for error!
[sat63_Server] out: Upgrade step correct_puppet_environments failed. Check logs for more information.
[sat63_Server] out:

Version-Release number of selected component (if applicable):
sat6.2 -> 6.3 snap28

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Upgrade should complete successfully

Additional info:
on re-running foreman-rake katello:correct_puppet_environments --trace didn't see above issue.
Comment 1 Sachin Ghai 2017-12-11 11:02:02 UTC 
Created attachment 1365922 [details]
foreman-debug
Comment 6 Sachin Ghai 2018-01-19 17:08:11 UTC 
@Brad: Hey I had a word with Andrew on IRC and it seems to be a intermittent issue as I was not able to reproduce with while upgrading same db to 6.3 snap32
Comment 7 Sachin Ghai 2018-01-19 17:11:00 UTC 
(In reply to Sachin Ghai from comment #6)
> @Brad: Hey I had a word with Andrew on IRC and it seems to be a intermittent
> issue as I was not able to reproduce with while upgrading same db to 6.3
> snap32

s/snap32/snap31.
Comment 10 Bryan Kearney 2019-02-07 12:09:24 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 11 Bryan Kearney 2019-02-28 19:35:04 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Note You need to log in before you can comment on or make changes to this bug.