Bug 1015034 - [cli] "Resource not found on the server" creating content definition for the org with "." (dot)
Summary: [cli] "Resource not found on the server" creating content definition for the ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 10:49 UTC by Garik Khachikyan
Modified: 2015-01-04 22:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-10 04:31:29 UTC
Target Upstream Version:


Attachments (Terms of Use)
logs (617.55 KB, application/gzip)
2013-10-03 10:49 UTC, Garik Khachikyan
no flags Details

Description Garik Khachikyan 2013-10-03 10:49:14 UTC
Created attachment 807006 [details]
logs

Description of problem:
My tries to create a content definition for my org "Garik and co." (notice the dot at the end) all failing with "Resource not found on the server"

Version-Release number of selected component (if applicable):
candlepin-0.8.25-1.el6sam.noarch
candlepin-cert-consumer-artemis.usersys.redhat.com-1.0-1.noarch
candlepin-scl-1-5.el6_4.noarch
candlepin-scl-quartz-2.1.5-5.el6_4.noarch
candlepin-scl-rhino-1.7R3-1.el6_4.noarch
candlepin-scl-runtime-1-5.el6_4.noarch
candlepin-selinux-0.8.25-1.el6sam.noarch
candlepin-tomcat6-0.8.25-1.el6sam.noarch
createrepo-0.9.9-21.2.pulp.el6sat.noarch
elasticsearch-0.19.9-8.el6sat.noarch
katello-1.4.6-15.el6sat.noarch
katello-agent-1.4.4-2.el6sat.noarch
katello-all-1.4.6-15.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-certs-tools-1.4.4-1.el6sat.noarch
katello-cli-1.4.3-15.el6sat.noarch
katello-cli-common-1.4.3-15.el6sat.noarch
katello-common-1.4.6-15.el6sat.noarch
katello-configure-1.4.5-8.el6sat.noarch
katello-configure-foreman-1.4.5-8.el6sat.noarch
katello-configure-foreman-proxy-1.4.5-8.el6sat.noarch
katello-foreman-all-1.4.6-15.el6sat.noarch
katello-glue-candlepin-1.4.6-15.el6sat.noarch
katello-glue-elasticsearch-1.4.6-15.el6sat.noarch
katello-glue-pulp-1.4.6-15.el6sat.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-selinux-1.4.4-4.el6sat.noarch
m2crypto-0.21.1.pulp-8.el6sat.x86_64
mod_wsgi-3.4-1.pulp.el6sat.x86_64
pulp-katello-plugins-0.2-1.el6sat.noarch
pulp-nodes-common-2.3.0-0.14.alpha.el6sat.noarch
pulp-nodes-parent-2.3.0-0.14.alpha.el6sat.noarch
pulp-puppet-plugins-2.3.0-0.14.alpha.el6sat.noarch
pulp-rpm-handlers-2.3.0-0.14.alpha.el6sat.noarch
pulp-rpm-plugins-2.3.0-0.14.alpha.el6sat.noarch
pulp-selinux-2.3.0-0.14.alpha.el6sat.noarch
pulp-server-2.3.0-0.14.alpha.el6sat.noarch
python-isodate-0.5.0-1.pulp.el6sat.noarch
python-oauth2-1.5.170-3.pulp.el6sat.noarch
python-pulp-agent-lib-2.3.0-0.14.alpha.el6sat.noarch
python-pulp-bindings-2.3.0-0.14.alpha.el6sat.noarch
python-pulp-common-2.3.0-0.14.alpha.el6sat.noarch
python-pulp-puppet-common-2.3.0-0.14.alpha.el6sat.noarch
python-pulp-rpm-common-2.3.0-0.14.alpha.el6sat.noarch
python-qpid-0.18-5.el6_4.noarch
qpid-cpp-client-0.14-22.el6_3.x86_64
qpid-cpp-client-ssl-0.14-22.el6_3.x86_64
qpid-cpp-server-0.14-22.el6_3.x86_64
qpid-cpp-server-ssl-0.14-22.el6_3.x86_64
ruby193-rubygem-foreman-katello-engine-0.0.8-6.el6sat.noarch
ruby193-rubygem-katello-foreman-engine-0.0.5-2.el6sat.noarch
ruby193-rubygem-katello_api-0.0.3-4.el6sat.noarch
ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch
signo-katello-0.0.20-3.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1.org create --name "your.org"
2.content definition create --name "cd1" --org "your.org"
3.

Actual results:
Resource not found on the server

Expected results:
no issues, content definition should get created... OR we disable completely creating orgs with dots. I am fine with either solution there.

Additional info:
logs attached.

Comment 2 Mike McCune 2013-10-10 04:31:29 UTC
you have to use the label in that case

content definition create --name "cd1" --org "your_org"

sorta confusing but that is how the labeling mechanism works is for situations with orgs with non standard chars


Note You need to log in before you can comment on or make changes to this bug.