Description of problem: [root@preethi ~]# pulp-admin repo clone --id=f13_test_relative --clone_id=clone_f13_test_relative --clone_name=clone_f13_test_relative --feed=origin --relativepath=/tmp/clone/ --groupid=test-grp Repository [f13_test_relative] is being cloned as [clone_f13_test_relative] Use "repo status" to check on the progress see that in the above command --relativepath is specified as /tmp/clone and so the repo should be created as var/lib/pulp/repos/tmp/clone/clone_f13_test_relative instead the following is created [root@preethi repos]# ls -l /var/lib/pulp/repos/ total 1196 drwxr-sr-x. 3 apache apache 905216 Nov 1 12:16 clone_f12 drwxr-sr-x. 3 apache apache 4096 Nov 1 14:52 clone_f13_test_relative drwxr-sr-x. 4 apache apache 290816 Oct 29 14:38 clone_nofeed drwxr-sr-x. 3 apache apache 4096 Oct 27 14:57 content drwxr-sr-x. 3 apache apache 4096 Oct 27 11:53 pub drwxr-sr-x. 3 apache apache 4096 Oct 28 09:09 repos drwxr-sr-x. 4 apache apache 4096 Nov 1 14:52 tmp [root@preethi repos]# [root@preethi repos]# ls -l /var/lib/pulp/repos/tmp/clone/ total 0
We have decided not to support specifying different relative_path for repo clones unless there is specific usecase in mind. It defaults to clone_id right now. I have removed --relativepath option from cli.
Fixed in build 0.78.
verified [root@preethi ~]# pulp-admin repo clone --help Usage: pulp-admin <options> repo clone <options> Options: -h, --help show this help message and exit --id=ID repository id (required) --clone_id=CLONE_ID id of cloned repo --clone_name=CLONE_NAME common repository name for cloned repo --feed=FEED feed of cloned_repo: parent/origin/none --groupid=GROUPID a group to which the repository belongs; this is just a string identifier --timeout=TIMEOUT repository clone timeout -F, --foreground clone repository in the foreground
Closing with community release pulp-0.0.139-1.fc14.noarch