Created attachment 988848 [details] traceback 500ISE for repo_syncs Description of problem: syncing content the second time throws traceback in production.log with 500 ISE Version-Release number of selected component (if applicable): Beta-Snap1-compose3 How reproducible: always Steps to Reproduce: 1. create a docker repo 2. sync content 3. now create another docer repo with same content or re-sync the existing docker repo to find 500ISE message errors in foreman/production.log Actual results: [root@yyyy yum.repos.d]# hammer -u admin -p changeme repository synchronize --id 6 --organization-id 1 /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.4/lib/hammer_cli/./apipie/../abstract.rb:68: warning: already initialized constant DEFAULT_LABEL_INDENT [ ] [0%] Task 4c0130f9-ae18-4ab0-a8d4-801b5d7c6c99: pending Processing metadata Could not synchronize the repository: 203: unexpected token at 'NaN,"progress_weight":10}' Expected results: Should be handled properly, for scenarios mentioned in step 3) of Reproduce. Additional info:
Created redmine issue http://projects.theforeman.org/issues/11183 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/11183 has been closed ------------- Partha Aji Applied in changeset commit:katello|9cb7ac3c33c84b605602efb83b1076c8aab5006f.
FAILEDQA: # rpm -qa | grep foreman foreman-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.1-1.el7sat.noarch foreman-vmware-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-postgresql-1.7.2.33-1.el7sat.noarch foreman-debug-1.7.2.33-1.el7sat.noarch foreman-gce-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.19-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-compute-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.4-1.el7sat.noarch foreman-libvirt-1.7.2.33-1.el7sat.noarch [root@hp-z600-01 ~]# clear [3;J [root@hp-z600-01 ~]# rpm -qa | grep foreman foreman-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.1-1.el7sat.noarch foreman-vmware-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-postgresql-1.7.2.33-1.el7sat.noarch foreman-debug-1.7.2.33-1.el7sat.noarch foreman-gce-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.19-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.33-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-compute-1.7.2.33-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.4-1.el7sat.noarch foreman-libvirt-1.7.2.33-1.el7sat.noarch steps: 1. create a docker repo 2. sync content 3. re-sync the existing docker repo 4. # hammer -u admin -p changeme repository synchronize --id 6 --organization-id 1 [................................................... ] [72%] getaddrinfo: Name or service not known
VERIFIED: # rpm -qa | grep foreman foreman-proxy-1.7.2.5-1.el6_6sat.noarch foreman-1.7.2.33-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch foreman-postgresql-1.7.2.33-1.el6_6sat.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_docker-1.2.0.18-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el6_6sat.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-libvirt-1.7.2.33-1.el6_6sat.noarch foreman-ovirt-1.7.2.33-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.15.4-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch foreman-debug-1.7.2.33-1.el6_6sat.noarch foreman-vmware-1.7.2.33-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.19-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch cloud-qe-9.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch foreman-gce-1.7.2.33-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el6_6sat.noarch foreman-compute-1.7.2.33-1.el6_6sat.noarch steps: 1. create a docker repo 2. sync content 3. re-sync the existing docker repo # hammer -u admin -p changeme repository synchronize --id 41 --organization-id 1 [......................................................................] [100%]
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.