HI Everyone,
My setup has two capsule in two different DataCenter,
Today we update some rpm and did a new publish.
After the publish we did promotion from Library to DEV.
Since doing the Promote the green bar is just setting there and say
pending.
Version is 1.6.3 Katello 2.0
Let me know where to look.
Question will hammer give me a status on what it is waiting for.
12/23/14 2:43 PM 2 Promoted to DEV admin pending 12/23/14 2:31 PM 2 Published
new version admin success
Thanks Al Johnson
I found this task in dynoflow.
Started at: 2014-12-23 20:53:41 UTC
Ended at: 2014-12-24 06:14:59 UTC
Real time: 33678.23s
Execution time (excluding suspended state): 117.98s
Input:
···
---
consumer_uuid: ecd0628f-4d70-4f5c-b5d1-e1c2ffda02c9
skip_content: true
remote_user: admin-71dd069e
remote_cp_user: admin
locale: en
Output:
pulp_tasks:- exception:
task_type:
_href: /pulp/api/v2/tasks/89d6cb99-d305-4d31-b86b-67187c287713/
task_id: 89d6cb99-d305-4d31-b86b-67187c287713
tags:
- pulp:consumer:ecd0628f-4d70-4f5c-b5d1-e1c2ffda02c9
- pulp:action:unit_update
finish_time:
_ns: task_status
start_time:
traceback:
spawned_tasks: []
progress_report: {}
queue: agent
state: accepted
result:
error:
_id:
$oid: 5499d6552fc65a32713f809b
id: 5499d6552fc65a32713f809b
poll_attempts:
total: 2066
failed: 0
Error:
StandardError
Abnormal termination (previous state: suspended)
---- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
`block in assigns’
- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
`tap’
- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
assigns'- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in
match_value’
- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
`block in match’
- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
each'- /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
match’
- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/execution_plan/steps/error.rb:12:in
`new’
- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/world.rb:174:in
block (2 levels) in consistency_check'- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/world.rb:172:in
each’
- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/world.rb:172:in
`block in consistency_check’
- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/world.rb:163:in
each'- /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/world.rb:163:in
consistency_check’
- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow.rb:48:in
`block in initialize!’
- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow.rb:38:in
tap'- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow.rb:38:in
initialize!’
- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/engine.rb:71:in
`block in class:Engine’
- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in
instance_exec'- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in
run’
- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:55:in
`block in run_initializers’
- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in
each'- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in
run_initializers’
- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:136:in
`initialize!’
- /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:in
method_missing'- /usr/share/foreman/config/environment.rb:5:in
<top (required)>’
- /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require’
- /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
require'- /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
block in require’
- /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in
`load_dependency’
- /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
require'- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow/daemon.rb:15:in
run’
- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow/daemon.rb:50:in
`block in run_background’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:249:in
call'- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:249:in
block in start_proc’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/daemonize.rb:197:in
`call’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/daemonize.rb:197:in
call_as_daemon'- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:253:in
start_proc’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:293:in
`start’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/controller.rb:70:in
run'- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons.rb:195:in
block
in run_proc’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/cmdline.rb:109:in
`call’
- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/cmdline.rb:109:in
catch_exceptions'- /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons.rb:194:in
run_proc’
- /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.10/lib/foreman_tasks/dynflow/daemon.rb:43:in
`run_background’
- /usr/bin/foreman-tasks:5:in `’
On Tuesday, December 23, 2014 11:04:19 PM UTC-6, Alvin Johnson wrote:
HI Everyone,
My setup has two capsule in two different DataCenter,
Today we update some rpm and did a new publish.
After the publish we did promotion from Library to DEV.
Since doing the Promote the green bar is just setting there and say
pending.
Version is 1.6.3 Katello 2.0
Let me know where to look.
Question will hammer give me a status on what it is waiting for.
12/23/14 2:43 PM 2 Promoted to DEV admin pending 12/23/14 2:31 PM 2 Published
new version admin success
Thanks Al Johnson