Description of problem: if you have repo defined with just hostname hammer import repository refuses to import it and shows msg about invalid source_url, e.g. "Skipping proxy560-rhel6-x86_64 repository import, invalid source_url." Version-Release number of selected component (if applicable): rubygem-hammer_cli_import-0.8.0-1.el6.noarch How reproducible: 100% Steps to Reproduce: 1. @sat5: have defined a repository using just hostname (not fqdn) 2. spacewalk-export 3. hammer import repository --csv-file /tmp/exports/repositories.csv Actual results: it refuses to import repos with urls just made of hostname (not fqdn) Expected results: it should import repos even with such urls Additional info: /tmp/exports/repositories.csv: 66,620,proxy560-rhel6-x86_64,yum,http://download/released/Proxy-5.6-RHEL-6/x86_64/tree/RHNProxy/,,,,,,,,,
hammer-cli-import.git: b4cf49ea9e9a0c86cd1c4442d7a10c9d2a2e8a5f
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
VERIFIED. rubygem-hammer_cli_import-0.10.1-1.el6.noarch # cat /tmp/exports/repositories.csv org_id,id,repo_label,repo_type,source_url,client_key_descr,client_key_type,client_key,client_cert_descr,client_cert_type,client_cert,ca_descr,ca_type,ca_key 66,620,proxy560-rhel6-x86_64,yum,http://download/released/Proxy-5.6-RHEL-6/x86_64/tree/RHNProxy/,,,,,,,,, # hammer import repository --csv-file /tmp/exports/repositories.csv Summary Created 1 repository. Created 1 product.
Unless csv (or at least hostname) that this fails on is provided I can not do anything about it as I am unable to reproduce it with data provided in comment #0
Providing traceback would also not hurt.
Unable to reproduce, moving back to ON_QA. Please open a new BZ if you can find a reproducer and mention there this bug.
Can't reproduce, already VERIFIED by QE - returning to VERIFIED, which is where we were when this started.
This was delivered with Satellite 6.0 which was released on 10 September 2014.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days