I used these under 2.1, but no action appears to be taken with my current
install.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of the
sync-plan/association with a product. But I can't find anything else under
/var/log using the sync-plan name.
Can anyone help? Cheers.
Let's try to verify that these sync plans are known to Pulp. If you take
the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:
foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp to
see if there is possibly a mismatch between what we think and what Pulp
thinks.
[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
I used these under 2.1, but no action appears to be taken with my current
install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of the
sync-plan/association with a product. But I can’t find anything else under
/var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Cheers Eric. OK, so…
# vi /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# chmod u+x /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# ll /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
-rwx------. 1 root root 989 May 29 15:43
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# foreman-rake list_active_sync_schedules
rake aborted!
Don't know how to build task 'list_active_sync_schedules'
(See full trace by running task with --trace)
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don't know how to build task 'list_active_sync_schedules'
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in []' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun'
/opt/rh/ruby193/root/usr/bin/rake:32:in `<main>'
Not sure whether this should complete without a problem, but I thought I
would also try:
# foreman-rake --trace
** Invoke default (first_time)
** Invoke test (first_time)
** Execute test
** Invoke test:run (first_time)
** Execute test:run
** Invoke test:units (first_time)
** Invoke test:prepare (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
API controllers newer than Apipie cache! Run apipie:cache rake task to
regenerate cache.
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment
** Invoke db:load_config
** Execute db:test:purge
** Execute db:test:load
** Invoke db:test:load_schema (first_time)
** Invoke db:test:purge
** Execute db:test:load_schema
rake aborted!
Please install the sqlite3 adapter: gem install activerecord-sqlite3-adapter (Could not find sqlite3 (~> 1.3.5) amongst
[actionmailer-3.2.8, actionpa
ck-3.2.8, activemodel-3.2.8,
activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8,
addressable-2.3.6, algebrick-0.4.0, ancestry-2.0.0, anemone
-0.7.2, angular-rails-templates-0.1.2, ansi-1.4.3, apipie-params-0.0.3,
apipie-rails-0.2.6, archive-tar-minitar-0.5.2, arel-3.0.2, audited-3.0.0,
audit
ed-activerecord-3.0.0, autoparse-0.3.3, bastion-0.3.3,
bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, bundler_ext-0.3.0,
coffee-rails-3.2.2, coffee-sc
ript-2.2.0,
coffee-script-source-1.3.3, commonjs-0.2.7, daemons-1.1.4,
deep_cloneable-2.0.2, deface-0.7.2, diff-lcs-1.1.3, docker-api-1.17.0,
dynflow-0
.7.8, erubis-2.7.0, excon-0.43.0, execjs-1.4.0,
extlib-0.9.16, faraday-0.9.1, fast_gettext-0.9.2, fog-1.29.0,
fog-aws-0.1.0, fog-core-1.29.0, fog-json-
1.0.0, fog-xml-0.1.1,
foreigner-1.7.1, foreman-tasks-0.6.13, foreman_bootdisk-5.0.0,
foreman_discovery-3.0.0, foreman_docker-1.3.1, foreman_gutterball-
0.0.1, foreman_hooks-0.3.7, formatador-0.2.1, friendly_id-4.0.10.1,
gettext_i18n_rails-1.2.1, google-api-client-0.8.2, haml-4.0.6,
haml-rails-0.4, hash
r-0.0.22, hike-1.2.1, hooks-0.2.2,
hpricot-0.8.6, i18n-0.6.0, i18n_data-0.2.7, io-console-0.3,
ipaddress-0.8.0, journey-1.0.4, jquery-ui-rails-4.1.2, j
son-1.5.5, justified-0.0.4, jwt-1.2.0, katello-2.2.0, launchy-2.4.3,
ldap_fluff-0.3.4, less-2.5.1, less-rails-2.5.0, little-plugger-1.1.3,
logging-1.8.
1, mail-2.4.4, mime-types-1.19, minitest-2.5.1,
multi_json-1.10.1, multipart-post-1.2.0, net-http-persistent-2.7,
net-ldap-0.10.0, net-scp-1.1.0, net-s
sh-2.6.7, netrc-0.7.7,
nokogiri-1.5.11, oauth-0.4.7, passenger-4.0.18, pg-0.12.2, polyglot-0.3.3,
qpid_messaging-0.30.0, rabl-0.11.4, rack-1.4.1, rack-
cache-1.2,
rack-jsonp-1.3.1, rack-protection-1.2.0, rack-ssl-1.3.2, rack-test-0.6.1,
rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbovirt-0.0.35, rbvmomi
-1.8.2, rdoc-3.9.5, rest-client-1.6.7, retriable-1.4.1, robotex-1.0.0,
ruby-libvirt-0.5.2, ruby2ruby-2.1.3, ruby_parser-3.6.3, runcible-1.3.1,
safemode
-1.2.2, sass-3.4.9, scoped_search-2.7.1,
secure_headers-1.4.1, sequel-4.17.0, sexp_processor-4.4.4, signet-0.6.0,
sinatra-1.3.2, sprockets-2.12.3, sshk
ey-1.6.0,
strong_parameters-0.2.1, thor-0.15.4, tilt-1.3.3, tire-0.6.2,
treetop-1.4.10, trollop-2.0, turbolinks-2.5.3, tzinfo-0.3.33,
validates_lengths
_from_database-0.4.0, wicked-1.1.0,
will_paginate-3.0.2])
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in
to_specs' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:into_spec'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:in gem' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3:in<top (required)>'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require' /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock 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:inrequire'
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:in
resolve_h ash_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:29:inspec'
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:129:in
establis h_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:477:inblock (3 levels) in <top (required)>'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke'
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:459:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in block in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in mon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in invoke' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:524:inblock (3 levels) in <top (required)>'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:61:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:incollect'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:in
block (2 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in block in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in mon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in invoke' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:50:inblock in <top (required)>'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:in block in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in invoke_task' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in each' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in block in run' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in run' /opt/rh/ruby193/root/usr/bin/rake:32:in<main>'
Tasks: TOP => db:test:load_schema
Let’s try to verify that these sync plans are known to Pulp. If you take
the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp to
see if there is possibly a mismatch between what we think and what Pulp
thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie.caldwell@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my current
install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of
the sync-plan/association with a product. But I can’t find anything else
under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Jamie.
OK, here we go:
# foreman-rake list_active_sync_schedules
'EPEL' in Product 'CentOS7' with product ID '4' has 1 sync plans attached
to them
'OS' in Product 'CentOS7' with product ID '4' has 1 sync plans attached to
them
'Updates' in Product 'CentOS7' with product ID '4' has 1 sync plans
attached to them
Need more coffee… that should be sync_schedule_tasks.rake (not .rb).
Eric
Cheers Eric. OK, so…
# vi /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# chmod u+x /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# ll /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
-rwx------. 1 root root 989 May 29 15:43
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# foreman-rake list_active_sync_schedules
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
(See full trace by running task with --trace)
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in
run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’Not sure whether this should complete without a problem, but I thought I
would also try:# foreman-rake --trace
** Invoke default (first_time)
** Invoke test (first_time)
** Execute test
** Invoke test:run (first_time)
** Execute test:run
** Invoke test:units (first_time)
** Invoke test:prepare (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
API controllers newer than Apipie cache! Run apipie:cache rake task to
regenerate cache.
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment
** Invoke db:load_config
** Execute db:test:purge
** Execute db:test:load
** Invoke db:test:load_schema (first_time)
** Invoke db:test:purge
** Execute db:test:load_schema
rake aborted!
Please install the sqlite3 adapter:gem install activerecord-sqlite3-adapter(Could not find sqlite3 (~> 1.3.5) amongst
[actionmailer-3.2.8, actionpa
ck-3.2.8, activemodel-3.2.8,
activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8,
addressable-2.3.6, algebrick-0.4.0, ancestry-2.0.0, anemone-0.7.2, angular-rails-templates-0.1.2, ansi-1.4.3, apipie-params-0.0.3,
apipie-rails-0.2.6, archive-tar-minitar-0.5.2, arel-3.0.2, audited-3.0.0,
audit
ed-activerecord-3.0.0, autoparse-0.3.3, bastion-0.3.3,
bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, bundler_ext-0.3.0,
coffee-rails-3.2.2, coffee-sc
ript-2.2.0,
coffee-script-source-1.3.3, commonjs-0.2.7, daemons-1.1.4,
deep_cloneable-2.0.2, deface-0.7.2, diff-lcs-1.1.3, docker-api-1.17.0,
dynflow-0
.7.8, erubis-2.7.0, excon-0.43.0, execjs-1.4.0,
extlib-0.9.16, faraday-0.9.1, fast_gettext-0.9.2, fog-1.29.0,
fog-aws-0.1.0, fog-core-1.29.0, fog-json-
1.0.0, fog-xml-0.1.1,
foreigner-1.7.1, foreman-tasks-0.6.13, foreman_bootdisk-5.0.0,
foreman_discovery-3.0.0, foreman_docker-1.3.1, foreman_gutterball-0.0.1, foreman_hooks-0.3.7, formatador-0.2.1, friendly_id-4.0.10.1,
gettext_i18n_rails-1.2.1, google-api-client-0.8.2, haml-4.0.6,
haml-rails-0.4, hash
r-0.0.22, hike-1.2.1, hooks-0.2.2,
hpricot-0.8.6, i18n-0.6.0, i18n_data-0.2.7, io-console-0.3,
ipaddress-0.8.0, journey-1.0.4, jquery-ui-rails-4.1.2, json-1.5.5, justified-0.0.4, jwt-1.2.0, katello-2.2.0, launchy-2.4.3,
ldap_fluff-0.3.4, less-2.5.1, less-rails-2.5.0, little-plugger-1.1.3,
logging-1.8.
1, mail-2.4.4, mime-types-1.19, minitest-2.5.1,
multi_json-1.10.1, multipart-post-1.2.0, net-http-persistent-2.7,
net-ldap-0.10.0, net-scp-1.1.0, net-s
sh-2.6.7, netrc-0.7.7,
nokogiri-1.5.11, oauth-0.4.7, passenger-4.0.18, pg-0.12.2, polyglot-0.3.3,
qpid_messaging-0.30.0, rabl-0.11.4, rack-1.4.1, rack-
cache-1.2,
rack-jsonp-1.3.1, rack-protection-1.2.0, rack-ssl-1.3.2, rack-test-0.6.1,
rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbovirt-0.0.35, rbvmomi-1.8.2, rdoc-3.9.5, rest-client-1.6.7, retriable-1.4.1, robotex-1.0.0,
ruby-libvirt-0.5.2, ruby2ruby-2.1.3, ruby_parser-3.6.3, runcible-1.3.1,
safemode
-1.2.2, sass-3.4.9, scoped_search-2.7.1,
secure_headers-1.4.1, sequel-4.17.0, sexp_processor-4.4.4, signet-0.6.0,
sinatra-1.3.2, sprockets-2.12.3, sshk
ey-1.6.0,
strong_parameters-0.2.1, thor-0.15.4, tilt-1.3.3, tire-0.6.2,
treetop-1.4.10, trollop-2.0, turbolinks-2.5.3, tzinfo-0.3.33,
validates_lengths
_from_database-0.4.0, wicked-1.1.0,
will_paginate-3.0.2])
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in
to_specs' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:into_spec’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:ingem' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3:in<top (required)>’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require' /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock 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:inrequire’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:in
resolve_h ash_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:29:inspec’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:129:in
establis h_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:477:inblock (3 levels) in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:459:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:524:inblock (3 levels) in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:61:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:incollect’
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:in
block (2 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:50:inblock in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in
invoke_task' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun' /opt/rh/ruby193/root/usr/bin/rake:32:in'
Tasks: TOP => db:test:load_schemaOn 29 May 2015 at 15:28, Eric D Helms ericdhelms@gmail.com wrote:
Let’s try to verify that these sync plans are known to Pulp. If you take
the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp to
see if there is possibly a mismatch between what we think and what Pulp
thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie.caldwell@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my
current install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of
the sync-plan/association with a product. But I can’t find anything else
under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Jamie.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Ahh. Will try on Monday as I've already escaped for the weekend. Enjoy
the coffee and the break! Cheers for your time.
Need more coffee… that should be sync_schedule_tasks.rake (not .rb).
Eric
On Fri, May 29, 2015 at 10:56 AM, Jamie Caldwell < > mr.jamie.caldwell@gmail.com> wrote:
Cheers Eric. OK, so…
# vi /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# chmod u+x /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# ll /usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
-rwx------. 1 root root 989 May 29 15:43
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb
# foreman-rake list_active_sync_schedules
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
(See full trace by running task with --trace)
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in
run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’Not sure whether this should complete without a problem, but I thought I
would also try:# foreman-rake --trace
** Invoke default (first_time)
** Invoke test (first_time)
** Execute test
** Invoke test:run (first_time)
** Execute test:run
** Invoke test:units (first_time)
** Invoke test:prepare (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
API controllers newer than Apipie cache! Run apipie:cache rake task to
regenerate cache.
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment
** Invoke db:load_config
** Execute db:test:purge
** Execute db:test:load
** Invoke db:test:load_schema (first_time)
** Invoke db:test:purge
** Execute db:test:load_schema
rake aborted!
Please install the sqlite3 adapter:gem install activerecord-sqlite3-adapter(Could not find sqlite3 (~> 1.3.5) amongst
[actionmailer-3.2.8, actionpa
ck-3.2.8, activemodel-3.2.8,
activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8,
addressable-2.3.6, algebrick-0.4.0, ancestry-2.0.0, anemone-0.7.2, angular-rails-templates-0.1.2, ansi-1.4.3, apipie-params-0.0.3,
apipie-rails-0.2.6, archive-tar-minitar-0.5.2, arel-3.0.2, audited-3.0.0,
audit
ed-activerecord-3.0.0, autoparse-0.3.3, bastion-0.3.3,
bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, bundler_ext-0.3.0,
coffee-rails-3.2.2, coffee-sc
ript-2.2.0,
coffee-script-source-1.3.3, commonjs-0.2.7, daemons-1.1.4,
deep_cloneable-2.0.2, deface-0.7.2, diff-lcs-1.1.3, docker-api-1.17.0,
dynflow-0
.7.8, erubis-2.7.0, excon-0.43.0, execjs-1.4.0,
extlib-0.9.16, faraday-0.9.1, fast_gettext-0.9.2, fog-1.29.0,
fog-aws-0.1.0, fog-core-1.29.0, fog-json-
1.0.0, fog-xml-0.1.1,
foreigner-1.7.1, foreman-tasks-0.6.13, foreman_bootdisk-5.0.0,
foreman_discovery-3.0.0, foreman_docker-1.3.1, foreman_gutterball-0.0.1, foreman_hooks-0.3.7, formatador-0.2.1, friendly_id-4.0.10.1,
gettext_i18n_rails-1.2.1, google-api-client-0.8.2, haml-4.0.6,
haml-rails-0.4, hash
r-0.0.22, hike-1.2.1, hooks-0.2.2,
hpricot-0.8.6, i18n-0.6.0, i18n_data-0.2.7, io-console-0.3,
ipaddress-0.8.0, journey-1.0.4, jquery-ui-rails-4.1.2, json-1.5.5, justified-0.0.4, jwt-1.2.0, katello-2.2.0, launchy-2.4.3,
ldap_fluff-0.3.4, less-2.5.1, less-rails-2.5.0, little-plugger-1.1.3,
logging-1.8.
1, mail-2.4.4, mime-types-1.19, minitest-2.5.1,
multi_json-1.10.1, multipart-post-1.2.0, net-http-persistent-2.7,
net-ldap-0.10.0, net-scp-1.1.0, net-s
sh-2.6.7, netrc-0.7.7,
nokogiri-1.5.11, oauth-0.4.7, passenger-4.0.18, pg-0.12.2, polyglot-0.3.3,
qpid_messaging-0.30.0, rabl-0.11.4, rack-1.4.1, rack-
cache-1.2,
rack-jsonp-1.3.1, rack-protection-1.2.0, rack-ssl-1.3.2, rack-test-0.6.1,
rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbovirt-0.0.35, rbvmomi-1.8.2, rdoc-3.9.5, rest-client-1.6.7, retriable-1.4.1, robotex-1.0.0,
ruby-libvirt-0.5.2, ruby2ruby-2.1.3, ruby_parser-3.6.3, runcible-1.3.1,
safemode
-1.2.2, sass-3.4.9, scoped_search-2.7.1,
secure_headers-1.4.1, sequel-4.17.0, sexp_processor-4.4.4, signet-0.6.0,
sinatra-1.3.2, sprockets-2.12.3, sshk
ey-1.6.0,
strong_parameters-0.2.1, thor-0.15.4, tilt-1.3.3, tire-0.6.2,
treetop-1.4.10, trollop-2.0, turbolinks-2.5.3, tzinfo-0.3.33,
validates_lengths
_from_database-0.4.0, wicked-1.1.0,
will_paginate-3.0.2])
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in
to_specs' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:into_spec’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:ingem' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3:in<top (required)>’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require’
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require' /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock 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:inrequire’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:in
resolve_h ash_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:29:inspec’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/connection_specification.rb:129:in
establis h_connection' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:477:inblock (3 levels) in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:459:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:524:inblock (3 levels) in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:61:in
block (3 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:incollect’
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:59:in
block (2 levels) in <top (required)>' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in
invoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:ininvoke_with_call_chain’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/test_unit/testing.rake:50:inblock in <top (required)>’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:incall' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:inblock in invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize’
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain' /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in
invoke_task' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun' /opt/rh/ruby193/root/usr/bin/rake:32:in'
Tasks: TOP => db:test:load_schemaOn 29 May 2015 at 15:28, Eric D Helms ericdhelms@gmail.com wrote:
Let’s try to verify that these sync plans are known to Pulp. If you take
the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp
to see if there is possibly a mismatch between what we think and what Pulp
thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie.caldwell@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my
current install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of
the sync-plan/association with a product. But I can’t find anything else
under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Jamie.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
for
Eric/All - I've since rebuilt, but still have the same problem. Worse, I
can't even get you script to run. Can you help?
# cd /var/log
*# grep -Ri Daily8am **
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{"interval"=>"hourly", "startDate"=>"2015-07-31T06:44:22.013Z",
"name"=>"Daily8am", "startTime"=>"2015-07-31T07:00:22.128Z",
"sync_date"=>"Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight Time)",
"api_version"=>"v2", "organization_id"=>"1",
"sync_plan"=>{"name"=>"Daily8am", "sync_date"=>"Fri Jul 31 2015 08:00:00
GMT+0100 (GMT Daylight Time)", "interval"=>"hourly"}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters: {"id"=>"2",
"organization_id"=>"1", "name"=>"Daily8am", "description"=>nil,
"sync_date"=>"2015-07-31T07:00:00Z", "interval"=>"daily",
"next_sync"=>"2015-07-31T07:00:00Z", "created_at"=>"2015-07-31T06:44:35Z",
"updated_at"=>"2015-07-31T06:44:35Z", "enabled"=>true,
"products"=>[{"id"=>3, "cp_id"=>"1438165438810", "name"=>"CentOS5",
"label"=>"CentOS5", "description"=>nil, "sync_state"=>"finished",
"last_sync"=>"2015-07-30 07:35:26 UTC", "last_sync_words"=>"about 23
hours", "repository_count"=>5}], "permissions"=>{"view_sync_plans"=>true,
"edit_sync_plans"=>true, "destroy_sync_plans"=>true}, "api_version"=>"v2",
"sync_plan"=>{"id"=>"2", "name"=>"Daily8am", "description"=>nil,
"sync_date"=>"2015-07-31T07:00:00Z", "interval"=>"daily",
"organization_id"=>"1", "created_at"=>"2015-07-31T06:44:35Z",
"updated_at"=>"2015-07-31T06:44:35Z", "enabled"=>true}}
# ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman
-rw-r–r--. 1 root root 639 Jun 15 13:20 foreman.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 middleware
drwxr-xr-x. 4 root root 4096 Jul 28 15:25 net
-rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54 sync_schedule_tasks.rake
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 tasks
-rw-r–r--. 1 root root 1211 Jun 15 13:20 timed_cached_store.rb
-rw-r–r--. 1 root root 2098 Jun 15 13:20 ws_proxy.rb
# grep list_active_sync_schedules sync_schedule_tasks.rake
task :list_active_sync_schedules => :environment do
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don't know how to build task 'list_active_sync_schedules'
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in []' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun'
/opt/rh/ruby193/root/usr/bin/rake:32:in `<main>'
Try adding the code in the rake tasks directly to
/use/share/foreman/Rakefile
Eric/All - I’ve since rebuilt, but still have the same problem. Worse, I
can’t even get you script to run. Can you help?# cd /var/log
*# grep -Ri Daily8am **
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight Time)”,
“api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015 08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters: {“id”=>“2”,
“organization_id”=>“1”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“next_sync”=>“2015-07-31T07:00:00Z”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”, “name”=>“CentOS5”,
“label”=>“CentOS5”, “description”=>nil, “sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about 23
hours”, “repository_count”=>5}], “permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true}, “api_version”=>“v2”,
“sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“organization_id”=>“1”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}# ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman
-rw-r–r--. 1 root root 639 Jun 15 13:20 foreman.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 middleware
drwxr-xr-x. 4 root root 4096 Jul 28 15:25 net
-rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54 sync_schedule_tasks.rake
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 tasks
-rw-r–r--. 1 root root 1211 Jun 15 13:20 timed_cached_store.rb
-rw-r–r--. 1 root root 2098 Jun 15 13:20 ws_proxy.rb
# grep list_active_sync_schedules sync_schedule_tasks.rake
task :list_active_sync_schedules => :environment do
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in
run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
# foreman-rake list_active_sync_schedules
’EPEL’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans attached
to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans attached
to them
’Updates’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If you take
the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp
to see if there is possibly a mismatch between what we think and what Pulp
thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my
current install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of
the sync-plan/association with a product. But I can’t find anything else
under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Thanks. Bingo.
'EPEL' in Product 'CentOS5' with product ID '3' has 1 sync plans attached
to them
'KatelloAgent' in Product 'CentOS5' with product ID '3' has 1 sync plans
attached to them
'OS' in Product 'CentOS5' with product ID '3' has 1 sync plans attached to
them
'SubscriptionAgent' in Product 'CentOS5' with product ID '3' has 1 sync
plans attached to them
'Updates' in Product 'CentOS5' with product ID '3' has 1 sync plans
attached to them
This tallys with my action. I created a plan and assigned it to the
CentOS5 product.
Try adding the code in the rake tasks directly to
/use/share/foreman/Rakefile
On Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:Eric/All - I’ve since rebuilt, but still have the same problem. Worse, I
can’t even get you script to run. Can you help?# cd /var/log
*# grep -Ri Daily8am **
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight Time)”,
“api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015 08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters: {“id”=>“2”,
“organization_id”=>“1”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“next_sync”=>“2015-07-31T07:00:00Z”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”, “name”=>“CentOS5”,
“label”=>“CentOS5”, “description”=>nil, “sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about 23
hours”, “repository_count”=>5}], “permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true}, “api_version”=>“v2”,
“sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“organization_id”=>“1”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}# ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman
-rw-r–r--. 1 root root 639 Jun 15 13:20 foreman.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 middleware
drwxr-xr-x. 4 root root 4096 Jul 28 15:25 net
-rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54 sync_schedule_tasks.rake
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 tasks
-rw-r–r--. 1 root root 1211 Jun 15 13:20 timed_cached_store.rb
-rw-r–r--. 1 root root 2098 Jun 15 13:20 ws_proxy.rb
# grep list_active_sync_schedules sync_schedule_tasks.rake
task :list_active_sync_schedules => :environment do
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in
run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
# foreman-rake list_active_sync_schedules
’EPEL’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans attached
to them
’Updates’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If you
take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in Pulp
to see if there is possibly a mismatch between what we think and what Pulp
thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my
current install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation of
the sync-plan/association with a product. But I can’t find anything else
under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
A couple of screen grabs…
I don't suppose anyone has any further thoughts on this? I'm getting close
to delivering the Katello server into live service and really need to iron
out the last few issues… Thanks.
JC,
Was this the issue we were discussing in Redmine? I just wanted to clarify
on the list if this had been addressed or not.
Eric
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really need to
iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules
‘EPEL’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans
attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans
attached to them
’OS’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached
to them
’SubscriptionAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them
’Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans
attached to themThis tallys with my action. I created a plan and assigned it to the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms ericdhelms@gmail.com wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/Rakefile
On Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?# cd /var/log
*# grep -Ri Daily8am **
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight Time)”,
“api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015 08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“next_sync”=>“2015-07-31T07:00:00Z”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”, “name”=>“CentOS5”,
“label”=>“CentOS5”, “description”=>nil, “sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about 23
hours”, “repository_count”=>5}], “permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true}, “api_version”=>“v2”,
“sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”, “description”=>nil,
“sync_date”=>“2015-07-31T07:00:00Z”, “interval”=>“daily”,
“organization_id”=>“1”, “created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}# ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman
-rw-r–r--. 1 root root 639 Jun 15 13:20 foreman.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 middleware
drwxr-xr-x. 4 root root 4096 Jul 28 15:25 net
-rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54 sync_schedule_tasks.rake
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 tasks
-rw-r–r--. 1 root root 1211 Jun 15 13:20 timed_cached_store.rb
-rw-r–r--. 1 root root 2098 Jun 15 13:20 ws_proxy.rb
# grep list_active_sync_schedules sync_schedule_tasks.rake
task :list_active_sync_schedules => :environment do
# foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock
in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
# foreman-rake list_active_sync_schedules
’EPEL’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them
’Updates’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If you
take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules in
Pulp to see if there is possibly a mismatch between what we think and what
Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with my
current install.
- I create a sync plan - for example, hourly. The tasks completes
successfully.- I apply that plan to product. The update completes successfully.
Nothing happens.
/var/log/foreman/production.log contains a record for the creation
of the sync-plan/association with a product. But I can’t find anything
else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe
.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University
Yup, it was. Thanks.
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs again?
Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms ericdhelms@gmail.com wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC mr.jamie.caldwell@gmail.com wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms ericdhelms@gmail.com wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Marcus - I wish I had a better answer for you. It now works for me, but I
have no idea why. It has been a problem for four weeks and I have not
performed any updates. It just started working after a weekend. The only
thing I have noticed is that when I create a new plan, the time defaults
the actual time (which I would expect), where as before it would be one
hour forward from the current time. Thus, my theory was that there was
some sort of timezone mismatch.
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs
again?-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com]
Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work
(anymore)Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms ericdhelms@gmail.com wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC mr.jamie.caldwell@gmail.com wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms ericdhelms@gmail.com wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then
run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com > wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users
.For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visithttps://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Hi JC,
thanks for your replay. I´ve to admit that this is a pity. I´ve created a new sync plan and applied it to all repos but things didn´t change. Well that´s something I need to get fixed before more employees start working with this fantastic tool 
Marcus - I wish I had a better answer for you. It now works for me, but I have no idea why. It has been a problem for four weeks and I have not performed any updates. It just started working after a weekend. The only thing I have noticed is that when I create a new plan, the time defaults the actual time (which I would expect), where as before it would be one hour forward from the current time. Thus, my theory was that there was some sort of timezone mismatch.
On 14 August 2015 at 10:52, <Markus.Moj@mc.ingenico.commailto:Markus.Moj@mc.ingenico.com> wrote:
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs again?
-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.commailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC <mr.jamie...@gmail.commailto:mr.jamie...@gmail.com> wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.commailto:foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.commailto:forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com<mailto:foreman-users%2Bunsubscribe@googl
Have you run Eric's rake code to check that the plan is really stored? It
only confirmed that it was, but it is a first step…
Hi JC,
thanks for your replay. I´ve to admit that this is a pity. I´ve created a
new sync plan and applied it to all repos but things didn´t change. Well
that´s something I need to get fixed before more employees start working
with this fantastic tool JVon: foreman-users@googlegroups.com [mailto:
foreman-users@googlegroups.com] *Im Auftrag von *Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:18
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to
work (anymore)Marcus - I wish I had a better answer for you. It now works for me, but I
have no idea why. It has been a problem for four weeks and I have not
performed any updates. It just started working after a weekend. The only
thing I have noticed is that when I create a new plan, the time defaults
the actual time (which I would expect), where as before it would be one
hour forward from the current time. Thus, my theory was that there was
some sort of timezone mismatch.On 14 August 2015 at 10:52, Markus.Moj@mc.ingenico.com wrote:
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs
again?-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com]
Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work
(anymore)Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms ericdhelms@gmail.com wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC mr.jamie.caldwell@gmail.com wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms ericdhelms@gmail.com wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then
run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com > wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users
.For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visithttps://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
Hi JC,
no I didn´t run the rake code. But I´ll give it a try …
Have you run Eric’s rake code to check that the plan is really stored? It only confirmed that it was, but it is a first step…
On 14 August 2015 at 11:25, <Markus.Moj@mc.ingenico.commailto:Markus.Moj@mc.ingenico.com> wrote:
Hi JC,
thanks for your replay. I´ve to admit that this is a pity. I´ve created a new sync plan and applied it to all repos but things didn´t change. Well that´s something I need to get fixed before more employees start working with this fantastic tool
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.commailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:18
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Marcus - I wish I had a better answer for you. It now works for me, but I have no idea why. It has been a problem for four weeks and I have not performed any updates. It just started working after a weekend. The only thing I have noticed is that when I create a new plan, the time defaults the actual time (which I would expect), where as before it would be one hour forward from the current time. Thus, my theory was that there was some sort of timezone mismatch.
On 14 August 2015 at 10:52, <Markus.Moj@mc.ingenico.commailto:Markus.Moj@mc.ingenico.com> wrote:
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs again?
-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.commailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC <mr.jamie...@gmail.commailto:mr.jamie...@gmail.com> wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.commailto:foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.commailto:forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.commailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
Hi @all,
to me it looks ok. Here is an example output of foreman rake run.
{"next_run"=>"2015-08-14T19:00:00Z", "remaining_runs"=>nil, "last_updated"=>1438246052.161148, "first_run"=>"2015-07-07T19:00:00Z", "total_run_count"=>36, "schedule"=>"2015-07-30T18:45:00Z/PT24H", "kwargs"=>{"overrides"=>{}}, "args"=>["Red_Hat_Software_Collections__for_RHEL_Server_-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server"], "enabled"=>true, "last_run_at"=>"2015-08-13T19:00:01Z", "task"=>"pulp.server.tasks.repository.sync_with_auto_publish", "failure_threshold"=>nil, "resource"=>"pulp:importer:Red_Hat_Software_Collections__for_RHEL_Server_-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server:yum_importer", "_id"=>"559e0aba4755ea9c1a0663fd", "consecutive_failures"=>0, "href"=>"/pulp/api/v2/repositories/Red_Hat_Software_Collections__for_RHEL_Server-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server/importers/yum_importer/schedules/sync/559e0aba4755ea9c1a0663fd/"}
'Red Hat Software Collections Source RPMs for Red Hat Enterprise Linux 7 Server x86_64 7Server' in Product 'Red Hat Software Collections for RHEL Server' with product ID '8' has 1 sync plans attached to them
But I´d to run the sync of alle repos manualy.
Hi JC,
no I didn´t run the rake code. But I´ll give it a try …
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:27
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Have you run Eric’s rake code to check that the plan is really stored? It only confirmed that it was, but it is a first step…
On 14 August 2015 at 11:25, <Markus.Moj@mc.ingenico.commailto:Markus.Moj@mc.ingenico.com> wrote:
Hi JC,
thanks for your replay. I´ve to admit that this is a pity. I´ve created a new sync plan and applied it to all repos but things didn´t change. Well that´s something I need to get fixed before more employees start working with this fantastic tool
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.commailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:18
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Marcus - I wish I had a better answer for you. It now works for me, but I have no idea why. It has been a problem for four weeks and I have not performed any updates. It just started working after a weekend. The only thing I have noticed is that when I create a new plan, the time defaults the actual time (which I would expect), where as before it would be one hour forward from the current time. Thus, my theory was that there was some sort of timezone mismatch.
On 14 August 2015 at 10:52, <Markus.Moj@mc.ingenico.commailto:Markus.Moj@mc.ingenico.com> wrote:
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs again?
-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.commailto:foreman-users@googlegroups.com] Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.commailto:foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work (anymore)
Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms <ericdhelms@gmail.commailto:ericdhelms@gmail.com> wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” <mr.jamie.caldwell@gmail.commailto:mr.jamie.caldwell@gmail.com> wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC <mr.jamie...@gmail.commailto:mr.jamie...@gmail.com> wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.commailto:foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.commailto:forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.commailto:foreman-users%2Bunsubscribe@googlegroups.com.
T
If you look through /var/log/messages around the time you'd expect the
syncs to have occurred do you see any Pulp activity?
Hi @all,
to me it looks ok. Here is an example output of foreman rake run.
{“next_run”=>“2015-08-14T19:00:00Z”, “remaining_runs”=>nil,
“last_updated”=>1438246052.161148, “first_run”=>“2015-07-07T19:00:00Z”,
“total_run_count”=>36, “schedule”=>“2015-07-30T18:45:00Z/PT24H”,
“kwargs”=>{“overrides”=>{}},
“args”=>[“Red_Hat_Software_Collections__for_RHEL_Server_-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server”],
“enabled”=>true, “last_run_at”=>“2015-08-13T19:00:01Z”,
“task”=>“pulp.server.tasks.repository.sync_with_auto_publish”,
“failure_threshold”=>nil,
“resource”=>“pulp:importer:Red_Hat_Software_Collections__for_RHEL_Server_-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server:yum_importer”,
"_id"=>“559e0aba4755ea9c1a0663fd”, “consecutive_failures”=>0,
“href"=>"/pulp/api/v2/repositories/Red_Hat_Software_Collections__for_RHEL_Server-Red_Hat_Software_Collections_Source_RPMs_for_Red_Hat_Enterprise_Linux_7_Server_x86_64_7Server/importers/yum_importer/schedules/sync/559e0aba4755ea9c1a0663fd/”}‘Red Hat Software Collections Source RPMs for Red Hat Enterprise Linux 7
Server x86_64 7Server’ in Product ‘Red Hat Software Collections for RHEL
Server’ with product ID ‘8’ has 1 sync plans attached to themBut I´d to run the sync of alle repos manualy.
Von: foreman-users@googlegroups.com [mailto:
foreman-users@googlegroups.com] *Im Auftrag von *Moj, Markus
Gesendet: Freitag, 14. August 2015 13:24
An: foreman-users@googlegroups.com
Betreff: AW: [foreman-users] [Katello 2.2] Sync plans don’t appear to
work (anymore)Hi JC,
no I didn´t run the rake code. But I´ll give it a try …
Von: foreman-users@googlegroups.com [
mailto:foreman-users@googlegroups.com foreman-users@googlegroups.com] *Im
Auftrag von *Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:27
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to
work (anymore)Have you run Eric’s rake code to check that the plan is really stored? It
only confirmed that it was, but it is a first step…On 14 August 2015 at 11:25, Markus.Moj@mc.ingenico.com wrote:
Hi JC,
thanks for your replay. I´ve to admit that this is a pity. I´ve created a
new sync plan and applied it to all repos but things didn´t change. Well
that´s something I need to get fixed before more employees start working
with this fantastic tool JVon: foreman-users@googlegroups.com [mailto:
foreman-users@googlegroups.com] *Im Auftrag von *Jamie Caldwell
Gesendet: Freitag, 14. August 2015 12:18
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to
work (anymore)Marcus - I wish I had a better answer for you. It now works for me, but I
have no idea why. It has been a problem for four weeks and I have not
performed any updates. It just started working after a weekend. The only
thing I have noticed is that when I create a new plan, the time defaults
the actual time (which I would expect), where as before it would be one
hour forward from the current time. Thus, my theory was that there was
some sort of timezone mismatch.On 14 August 2015 at 10:52, Markus.Moj@mc.ingenico.com wrote:
Hi @all,
I´m facing the same issue, is there any fix to enable scheduled repo syncs
again?-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com]
Im Auftrag von Jamie Caldwell
Gesendet: Mittwoch, 12. August 2015 09:35
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2] Sync plans don’t appear to work
(anymore)Yup, it was. Thanks.
On 12 August 2015 at 00:57, Eric D Helms ericdhelms@gmail.com wrote:
JC,
Was this the issue we were discussing in Redmine? I just wanted to
clarify on the list if this had been addressed or not.Eric
On Mon, Aug 3, 2015 at 3:46 AM, JC mr.jamie.caldwell@gmail.com wrote:
I don’t suppose anyone has any further thoughts on this? I’m getting
close to delivering the Katello server into live service and really
need to iron out the last few issues… Thanks.On Friday, 31 July 2015 12:37:32 UTC+1, JC wrote:
A couple of screen grabs…
On Friday, 31 July 2015 12:32:44 UTC+1, JC wrote:
Thanks. Bingo.
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to them
’KatelloAgent’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to them ‘OS’ in Product ‘CentOS5’ with product ID
’3’ has 1 sync plans attached to them ‘SubscriptionAgent’ in
Product ‘CentOS5’ with product ID ‘3’ has 1 sync plans attached to
them ‘Updates’ in Product ‘CentOS5’ with product ID ‘3’ has 1 sync
plans attached to themThis tallys with my action. I created a plan and assigned it to
the
CentOS5 product.On 31 July 2015 at 12:24, Eric D Helms ericdhelms@gmail.com wrote:
Try adding the code in the rake tasks directly to
/use/share/foreman/RakefileOn Jul 31, 2015 4:58 AM, “JC” mr.jamie.caldwell@gmail.com wrote:
Eric/All - I’ve since rebuilt, but still have the same problem.
Worse, I can’t even get you script to run. Can you help?cd /var/log
grep -Ri Daily8am *
foreman/production.log:2015-07-31 07:44:35 [I] Parameters:
{“interval”=>“hourly”, “startDate”=>“2015-07-31T06:44:22.013Z”,
“name”=>“Daily8am”, “startTime”=>“2015-07-31T07:00:22.128Z”,
“sync_date”=>“Fri Jul 31 2015 08:00:00 GMT+0100 (GMT Daylight
Time)”, “api_version”=>“v2”, “organization_id”=>“1”,
“sync_plan”=>{“name”=>“Daily8am”, “sync_date”=>“Fri Jul 31 2015
08:00:00
GMT+0100 (GMT Daylight Time)”, “interval”=>“hourly”}}
foreman/production.log:2015-07-31 07:45:37 [I] Parameters:
{“id”=>“2”, “organization_id”=>“1”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “next_sync”=>“2015-07-31T07:00:00Z”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true,
“products”=>[{“id”=>3, “cp_id”=>“1438165438810”,
“name”=>“CentOS5”, “label”=>“CentOS5”, “description”=>nil,
“sync_state”=>“finished”,
“last_sync”=>“2015-07-30 07:35:26 UTC”, “last_sync_words”=>“about
23 hours”, “repository_count”=>5}],
“permissions”=>{“view_sync_plans”=>true,
“edit_sync_plans”=>true, “destroy_sync_plans”=>true},
“api_version”=>“v2”, “sync_plan”=>{“id”=>“2”, “name”=>“Daily8am”,
“description”=>nil, “sync_date”=>“2015-07-31T07:00:00Z”,
“interval”=>“daily”, “organization_id”=>“1”,
“created_at”=>“2015-07-31T06:44:35Z”,
“updated_at”=>“2015-07-31T06:44:35Z”, “enabled”=>true}}ll
total 52
-rw-r–r--. 1 root root 3970 Jun 15 13:20 core_extensions.rb
drwxr-xr-x. 3 root root 4096 Jul 28 15:25 foreman -rw-r–r--. 1
root root 639 Jun 15 13:20 foreman.rb drwxr-xr-x. 2 root root
4096 Jul 28 15:25 middleware drwxr-xr-x. 4 root root 4096 Jul 28
15:25 net -rw-r–r--. 1 root root 875 Jun 15 13:20 net.rb
drwxr-xr-x. 2 root root 4096 Jul 28 15:25 proxy_api
-rw-r–r--. 1 root root 72 Jun 15 13:20 proxy_api.rb
-rw-r–r--. 1 root root 427 Jun 15 13:20 regexp_extensions.rb
-rwxr-xr-x. 1 root root 982 Jul 31 09:54
sync_schedule_tasks.rake drwxr-xr-x. 2 root root 4096 Jul 28
15:25 tasks -rw-r–r--. 1 root root 1211 Jun 15 13:20
timed_cached_store.rb -rw-r–r--. 1 root root 2098 Jun 15 13:20
ws_proxy.rb # grep list_active_sync_schedules
sync_schedule_tasks.rake task :list_active_sync_schedules =>
:environment do # foreman-rake list_active_sync_schedules --trace
rake aborted!
Don’t know how to build task ‘list_active_sync_schedules’
/opt/rh/ruby193/root/usr/share/ruby/rake/task_manager.rb:49:in[]' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:115:ininvoke_task’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block (2 levels) in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:ineach’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in
block in top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in
top_level' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:inblock in run’
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling' /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:inrun’
/opt/rh/ruby193/root/usr/bin/rake:32:in `’On Monday, 1 June 2015 08:57:54 UTC+1, JC wrote:
OK, here we go:
foreman-rake list_active_sync_schedules ‘EPEL’ in Product
‘CentOS7’ with product ID ‘4’ has 1 sync plans attached to them
’OS’ in Product ‘CentOS7’ with product ID ‘4’ has 1 sync plans
attached to them ‘Updates’ in Product ‘CentOS7’ with product ID
’4’ has 1 sync plans attached to themOn Friday, 29 May 2015 15:28:12 UTC+1, Eric Helms wrote:
Let’s try to verify that these sync plans are known to Pulp. If
you take the contents of [1] and put them in a file at
/usr/share/foreman/lib/tasks/sync_schedule_tasks.rb you can then
run:foreman-rake list_active_sync_schedules
This will tell us what repositories have active sync schedules
in Pulp to see if there is possibly a mismatch between what we
think and what Pulp thinks.[1] https://gist.github.com/ehelms/52405ed3e75ec54ed91f
On Fri, May 29, 2015 at 5:04 AM, JC mr.jamie...@gmail.com > wrote:
I used these under 2.1, but no action appears to be taken with
my current install.
- I create a sync plan - for example, hourly. The tasks
completes successfully.- I apply that plan to product. The update completes
successfully.Nothing happens.
/var/log/foreman/production.log contains a record for the
creation of the sync-plan/association with a product. But I
can’t find anything else under /var/log using the sync-plan name.Can anyone help? Cheers.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from
it, send an email to foreman-user...@googlegroups.com.
To post to this group, send email to forema...@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users
.For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the
Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
.Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in
the Google Groups “Foreman users” group.
To unsubscribe from this topic, visithttps://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/sRuZvzQcJh0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.–
You received this message because you are subscribed to a topic in the
G