mikedep333

Error on content prepare from sat 6.9 to 6.10

Sep 29th, 2021 (edited)
93
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.06 KB | None | 0 0
  1. [root@dhcp-3-234 server]# satellite-maintain prep-6.10-upgrade
  2. Running Preparations for the Satellite 6.10 upgrade
  3. ================================================================================
  4. Preparations for the Satellite 6.10 upgrade:
  5. prep-6.10-upgrade may take a while depending on the size of /var/lib/pulp/content
  6. | $ chown -R :pulp /var/lib/pulp/content [OK]
  7. --------------------------------------------------------------------------------
  8.  
  9. [root@dhcp-3-234 server]# satellite-maintain content prepare
  10. Running Prepare content for Pulp 3
  11. ================================================================================
  12. Start applicable services:
  13.  
  14. Starting the following service(s):
  15. rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, rh-redis5-redis, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker, dynflow-sidekiq@worker-hosts-queue, foreman-proxy
  16. / All services started [OK]
  17. --------------------------------------------------------------------------------
  18. Enable applicable services:
  19.  
  20. Enabling the following service(s):
  21. pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
  22. / enabling pulpcore-resource-manager
  23. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-api.service to /etc/systemd/system/pulpcore-api.service.
  24.  
  25. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-content.service to /etc/systemd/system/pulpcore-content.service.
  26.  
  27. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-resource-manager.service to /etc/systemd/system/pulpcore-resource-manager.service.
  28. | enabling pulpcore-worker@4
  29. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-worker@1.service to /etc/systemd/system/pulpcore-worker@.service.
  30.  
  31. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-worker@2.service to /etc/systemd/system/pulpcore-worker@.service.
  32.  
  33. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-worker@3.service to /etc/systemd/system/pulpcore-worker@.service.
  34.  
  35. Created symlink from /etc/systemd/system/multi-user.target.wants/pulpcore-worker@4.service to /etc/systemd/system/pulpcore-worker@.service.
  36. / All services enabled [OK]
  37. --------------------------------------------------------------------------------
  38. Start applicable services:
  39.  
  40. Starting the following service(s):
  41. pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
  42. / All services started [OK]
  43. --------------------------------------------------------------------------------
  44. Prepare content for Pulp 3:
  45.  
  46. Checking for valid Katello configuraton.
  47. rake aborted!
  48. The following services have not been started or are reporting errors: candlepin, foreman_tasks, pulp3
  49. /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.40/app/models/katello/ping.rb:35:in `ping!'
  50. /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.40/lib/katello/tasks/pulp3_migration.rake:13:in `block (2 levels) in <top (required)>'
  51. /opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
  52. Tasks: TOP => katello:pulp3_migration
  53. (See full trace by running task with --trace)
  54. [FAIL]
  55. Failed executing foreman-rake katello:pulp3_migration, exit status 1
  56. --------------------------------------------------------------------------------
  57. Scenario [Prepare content for Pulp 3] failed.
  58.  
  59. The following steps ended up in failing state:
  60.  
  61. [content-prepare]
  62.  
  63. Resolve the failed steps and rerun
  64. the command. In case the failures are false positives,
  65. use --whitelist="content-prepare"
  66.  
  67.  
  68. root@dhcp-3-234 server]# systemctl --failed
  69. UNIT LOAD ACTIVE SUB DESCRIPTION
  70. ● cloud-final.service loaded failed failed Execute cloud user/final scripts
  71. ● pulp_celerybeat.service loaded failed failed Pulp's Celerybeat
  72. ● rh-mongodb34-mongod.service loaded failed failed High-performance, schema-free document-oriented dat
  73. ● selinux-policy-migrate-local-changes@targeted.service loaded failed failed Migrate local SELinux policy changes from the old
  74.  
  75. LOAD = Reflects whether the unit definition was properly loaded.
  76. ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  77. SUB = The low-level unit activation state, values depend on unit type.
  78.  
  79. 4 loaded units listed. Pass --all to see loaded but inactive units, too.
  80. To show all installed unit files use 'systemctl list-unit-files'.
  81.  
  82. root@dhcp-3-234 server]# systemctl | grep -E 'pulp|candlepin|foreman'
  83. foreman-proxy.service loaded active running Foreman Proxy
  84. foreman.service loaded active running Foreman
  85. ● pulp_celerybeat.service loaded failed failed Pulp's Celerybeat
  86. pulp_resource_manager.service loaded active running Pulp Resource Manager
  87. pulp_streamer.service loaded active running The Pulp lazy content loading streamer
  88. pulp_worker-0.service loaded active running Pulp Worker #0
  89. pulp_worker-1.service loaded active running Pulp Worker #1
  90. pulp_worker-2.service loaded active running Pulp Worker #2
  91. pulp_worker-3.service loaded active running Pulp Worker #3
  92. pulp_worker-4.service loaded active running Pulp Worker #4
  93. pulp_worker-5.service loaded active running Pulp Worker #5
  94. pulp_workers.service loaded active exited Pulp Celery Workers
  95. pulpcore-api.service loaded active running Pulp API Server
  96. pulpcore-content.service loaded active running Pulp Content App
  97. pulpcore-resource-manager.service loaded active running Pulp Resource Manager
  98. pulpcore-worker@1.service loaded active running Pulp RQ Worker
  99. pulpcore-worker@2.service loaded active running Pulp RQ Worker
  100. pulpcore-worker@3.service loaded active running Pulp RQ Worker
  101. pulpcore-worker@4.service loaded active running Pulp RQ Worker
  102. system-pulpcore\x2dworker.slice loaded active active system-pulpcore\x2dworker.slice
  103. foreman.socket loaded active running Foreman HTTP Server Accept Sockets
  104. pulpcore-api.socket loaded active running Pulp API Server socket
  105. pulpcore-content.socket loaded active running Pulp Content App socket
  106.  
Add Comment
Please, Sign In to add comment