Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 913449 - CLI - error creating architecture by long name
Summary: CLI - error creating architecture by long name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: Nightly
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: Unspecified
Assignee: Tomas Strachota
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On: 1120271
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-21 09:38 UTC by Hayk Hovsepyan
Modified: 2019-09-26 17:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:21:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Hayk Hovsepyan 2013-02-21 09:38:13 UTC 
Description of problem:

When creating Architecture by specifying name longer than 10 characters: ('architecture create --name poiuytrdsadsadsad'),
 it shows error in CLI:

'{"error":{"message":"PGError: ERROR:  value too long for type character varying(10)\n: INSERT INTO \"architectures\" (\"updated_at\", \"created_at\", \"name\") VALUES ('2013-02-21 09:23:17.048325', '2013-02-21 09:23:17.048325', 'poiuytrdsadsadsad') RETURNING \"id\""}}'


Version-Release number of selected component (if applicable):
katello-configure-1.3.6-1.git.660.a33726a.el6.noarch
katello-common-1.3.14-1.git.659.105fb89.el6.noarch
katello-1.3.14-1.git.659.105fb89.el6.noarch
katello-selinux-1.3.1-1.el6.noarch
katello-repos-1.3.2-1.el6.noarch
katello-cli-common-1.3.4-1.git.651.edf5d46.el6.noarch
katello-glue-elasticsearch-1.3.14-1.git.659.105fb89.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-cli-1.3.4-1.git.651.edf5d46.el6.noarch
katello-glue-pulp-1.3.14-1.git.659.105fb89.el6.noarch
katello-glue-foreman-1.3.14-1.git.659.105fb89.el6.noarch
katello-glue-candlepin-1.3.14-1.git.659.105fb89.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-certs-tools-1.1.9-1.el6.noarch
katello-all-1.3.14-1.git.659.105fb89.el6.noarch
rubygem-foreman_api-0.1.1-1.el6.noarch
foreman-postgresql-1.0.2-17.e0d9186.el6.noarch
katello-glue-foreman-1.3.14-1.git.659.105fb89.el6.noarch
foreman-1.0.2-17.e0d9186.el6.noarch
Comment 1 Mike McCune 2013-04-03 15:22:08 UTC 
When we build our unified CLI we need to address this
Comment 4 sthirugn@redhat.com 2014-08-08 20:04:53 UTC 
Now I am able to create architecture with name upto 255 characters. Attempting to create architecture with 256 characters throws error.

Version Tested:
GA Snap 4 - Satellite-6.0.4-RHEL-6-20140806.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.19-1.el6_5.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.9.19-1.el6_5.noarch
* candlepin-tomcat6-0.9.19-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.38-1.el6sat.noarch
* foreman-compute-1.6.0.38-1.el6sat.noarch
* foreman-gce-1.6.0.38-1.el6sat.noarch
* foreman-libvirt-1.6.0.38-1.el6sat.noarch
* foreman-ovirt-1.6.0.38-1.el6sat.noarch
* foreman-postgresql-1.6.0.38-1.el6sat.noarch
* foreman-proxy-1.6.0.23-1.el6sat.noarch
* foreman-selinux-1.6.0.4-1.el6sat.noarch
* foreman-vmware-1.6.0.38-1.el6sat.noarch
* katello-1.5.0-28.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.57-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.30.beta.el6sat.noarch
* pulp-server-2.4.0-0.30.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
* sssd-ldap-1.11.5.1-3.el6.x86_64
Comment 6 Bryan Kearney 2014-09-11 12:21:44 UTC 
This was delivered with Satellite 6.0 which was released on 10 September 2014.
Note You need to log in before you can comment on or make changes to this bug.