Bug 1006312
| Summary: | Add support for unicode strings to repository IDs | ||
|---|---|---|---|
| Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | John Matthews <jmatthew> |
| Component: | Dev-Tools | Assignee: | RHUI Bug List <rhui-bugs> |
| Status: | CLOSED WORKSFORME | QA Contact: | mkovacik |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1.2 | CC: | cduryee, dgao, tsanders |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-28 18:19:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
pulp is being rebased to 2.8, closing bz. |
Description of problem: Pulp v1 (official from github.com/pulp, branch 'pulp_v1') has several extra commits related to handling unicode support in repository id's that did not get cherry picked into the 'rhui' branch at (github.com/splice/pulp). Version-Release number of selected component (if applicable): RHUI 2.1.2 How reproducible: We saw this problem showing up as an intermittent problem from test_repo_cloning.py:TestRepoSyncSchedule.test_repo_clone_with_i18n_id The problem expresses itself as a random from of the above test fails. This leaves a task snapshot in mongodb: db.task_snapshots.find() { "_id" : "3d6026c5-8ee5-420e-9c53-6d1dc361ef80", "synchronizer_class" : "cpulp.server.api.synchronizers\nYumSynchronizer\np0\n.", "weight" : 1, "class_name" : null, "hooks" : "(dp0\nS'enqueue'\np1\n(lp2\nccopy_reg\n_reconstructor\np3\n(cpulp.server.auth.authorization\nGrantPermissionsForTask\np4\nc__builtin__\nobject\np5\nNtp6\nRp7\n(dp8\nS'user_name'\np9\nVSYSTEM\np10\nsbasS'dequeue'\np11\n(lp12\ng3\n(cpulp.server.auth.authorization\nRevokePermissionsForTask\np13\ng5\nNtp14\nRp15\n(dp16\ng9\ng10\nsbas.", "start_time" : "N.", "args" : "(lp0\nV\\u0938\\u093e\np1\na.", "callable" : "cpulp.server.api.repo_sync\n_clone\np0\n.", "clone_id" : "सा", "result" : "N.", "timeout_delta" : "N.", "id" : "435e73a1-197c-11e3-bace-000c2948fd1c", "_ns" : "task_snapshots", "method_name" : "_clone", "exception" : "N.", "job_id" : null, "cancel_attempts" : 0, "schedule_threshold" : "cdatetime\ntimedelta\np0\n(I0\nI300\nI0\ntp1\nRp2\n.", "traceback" : "N.", "task_class" : "cpulp.server.api.repo_clone_task\nRepoCloneTask\np0\n.", "finish_time" : "N.", "state" : "waiting", "failure_threshold" : null, "_progress_callback" : "cpulp.server.api.synchronizers\nlocal_progress_callback\np0\n.", "kwargs" : "(dp0\nS'feed'\np1\nS'parent'\np2\nsS'groupid'\np3\n(lp4\nsS'filters'\np5\n(lp6\nsS'id'\np7\nV\\u0938\\u093e\\u092f\\u0932\\u0940\np8\nsS'clone_name'\np9\nS'clone-publish-false'\np10\nsS'relative_path'\np11\nV\\u0938\\u093e\np12\ns.", "progress" : null, "consecutive_failures" : 0 } }$ nosetests test_repo_cloning.py Exception in thread Thread-33: Traceback (most recent call last): File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner self.run() File "/usr/lib64/python2.6/threading.py", line 484, in run self.__target(*self.__args, **self.__kwargs) File "/mnt/hgfs/jmatthews/git/RHUI/pulp/test/common/../../src/pulp/server/tasking/task.py", line 437, in run self.failed(e) File "/mnt/hgfs/jmatthews/git/RHUI/pulp/test/common/../../src/pulp/server/tasking/task.py", line 475, in failed self.exception = str(exception) UnicodeEncodeError: 'ascii' codec can't encode characters in position 15-16: ordinal not in range(128) Once this problematic task snapshot is in pulp_unittest, the majority of unit tests then fail. They fail when the async.initialize() To fix this we need to drop pulp_unittest in mongoDB Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: