Project

General

Profile

Actions
Copy link

Bug #11183

closed

syncing content the second time throws traceback in production.log

Added by Partha Aji over 9 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Partha Aji
Category:
Web UI
Target version:
Katello 2.3.0
Difficulty:
Triaged:
Yes
Bugzilla link:
1190121
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1190121
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:

Actions
Copy link

Also available in: Atom PDF