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.

Bug 1495205

Summary:

upgrade w/ customer db failed at Step: correct_repositories

Product:

Red Hat Satellite

Reporter:

Sachin Ghai <sghai>

Component:

Upgrades

Assignee:

satellite6-bugs <satellite6-bugs>

Status:

CLOSED DUPLICATE

QA Contact:

Katello QA List <katello-qa-list>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

6.2.12

CC:

bbuckingham, inecas, mbacovsk, sghai

Target Milestone:

Unspecified

Keywords:

Triaged

Target Release:

Unused

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2017-10-10 13:05:19 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

1458642

Attachments:

Description	Flags
logs from console	none
foreman-debug	none

Description Sachin Ghai 2017-09-25 13:33:39 UTC

Description of problem:

I was trying to perform db upgrade on rhel7 and db was cloned using sat-clone. Upgrade failed at step:

Upgrade Step: correct_repositories (this may take a while) ...
rake aborted!
Not all the services have been started. Check the status report above and try again.
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.144/lib/katello/tasks/reimport.rake:8:in `block (2 levels) in <top (required)>'
Tasks: TOP => katello:correct_repositories => katello:check_ping
(See full trace by running task with --trace)
{:status=>"FAIL",
 :services=>
  {:pulp=>{:status=>"ok", :duration_ms=>"56"},
   :pulp_auth=>{:status=>"ok", :duration_ms=>"39"},
   :candlepin=>{:status=>"ok", :duration_ms=>"23"},
   :candlepin_auth=>{:status=>"ok", :duration_ms=>"30"},
   :foreman_tasks=>
    {:status=>"FAIL",
     :message=>
      "some executors are not responding, check /foreman_tasks/dynflow/status"}}}

Upgrade step correct_repositories failed. Check logs for more information.



Version-Release number of selected component (if applicable):
6.2 -> 6.2.12 on rhel7

How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Sachin Ghai 2017-09-25 13:36:23 UTC

Created attachment 1330550 [details]
foreman-debug

Comment 5 Sachin Ghai 2017-09-28 12:04:11 UTC

I hit exactly same issue while performing 6.2.z -> 6.3 upgrade and at same step:

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




this time I found one more error at db:seed step. It is the step before "Correct repositories step.."

------
Success!
katello-service restart finished successfully!
Upgrade Step: db_seed...
E, [2017-09-28T07:52:59.922364 #25492] ERROR -- /client-dispatcher: Could not find an executor for Dynflow::Dispatcher::Envelope[request_id: 8, sender_id: 54608557-25e1-467c-b837-f11d59601231, receiver_id: Dynflow::Dispatcher::UnknownWorld, message: Dynflow::Dispatcher::Event[execution_plan_id: f81a3ecd-f974-497d-a2f7-f8b09ff097f3, step_id: 2, event: Actions::Candlepin::ListenOnCandlepinEvents::Reconnect[message: initialized...have not connected yet]]] (Dynflow::Error)
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/dispatcher/client_dispatcher.rb:66:in `dispatch_request'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/dispatcher/client_dispatcher.rb:38:in `block in publish_request'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/dispatcher/client_dispatcher.rb:108:in `track_request'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/dispatcher/client_dispatcher.rb:37:in `publish_request'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/actor.rb:6:in `on_message'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.3/lib/concurrent/actor/context.rb:46:in `on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.3/lib/concurrent/actor/behaviour/executes_context.rb:7:in `on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.3/lib/concurrent/actor/behaviour/abstract.rb:25:in `pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/actor.rb:26:in `on_envelope'
--------------

Comment 8 Sachin Ghai 2017-10-05 14:03:03 UTC

Another DB failed exactly at same step.

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

Comment 9 Ivan Necas 2017-10-10 13:05:19 UTC


*** This bug has been marked as a duplicate of bug 1493046 ***

Comment 10 Ivan Necas 2017-10-10 13:09:49 UTC

I'm closing because https://bugzilla.redhat.com/show_bug.cgi?id=1495205#c5 and https://bugzilla.redhat.com/show_bug.cgi?id=1495205#c8 are referring to katello-3.4.x, which means that were issues that started happening after the repositories were updated