How reproducible: always Steps to Reproduce: 1. set hostname to contain capital letters 2. katello-configure Actual results: fails in db_seed phase Expected results: everyghing works Additional info:
Proposed fix (updating katello-configure): https://github.com/Katello/katello/pull/1858
Moving to ON_QA for drop 2.
Tried to verify this issue with following satellite6 MDP1 build: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.8.9-1.el6_4.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.9-1.el6_4.noarch * candlepin-tomcat6-0.8.9-1.el6_4.noarch * elasticsearch-0.19.9-8.el6sat.noarch * foreman-1.1.10002-44.noarch * foreman-installer-puppet-concat-0-2.d776701.git.0.21ef926.el6sat.noarch * foreman-installer-puppet-dhcp-0-5.3a4a13c.el6sat.noarch * foreman-installer-puppet-dns-0-7.fcae203.el6sat.noarch * foreman-installer-puppet-foreman-0-6.568c5c4.el6sat.noarch * foreman-installer-puppet-foreman_proxy-0-8.bd1e35d.el6sat.noarch * foreman-installer-puppet-puppet-0-3.ab46748.el6sat.noarch * foreman-installer-puppet-tftp-0-5.ea6c5e5.el6sat.noarch * foreman-installer-puppet-xinetd-0-50a267b8.git.0.44aca6a.el6sat.noarch * foreman-postgresql-1.1.10002-44.noarch * foreman-proxy-1.1.10002-1.el6sat.noarch * foreman-proxy-installer-1.0.1-8.f5ae2cd.el6sat.noarch * katello-1.4.2-8.el6sat.noarch * katello-all-1.4.2-8.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.2-2.el6sat.noarch * katello-cli-1.4.2-6.el6sat.noarch * katello-cli-common-1.4.2-6.el6sat.noarch * katello-common-1.4.2-8.el6sat.noarch * katello-configure-1.4.3-12.el6sat.noarch * katello-configure-foreman-1.4.3-12.el6sat.noarch * katello-foreman-all-1.4.2-8.el6sat.noarch * katello-glue-candlepin-1.4.2-8.el6sat.noarch * katello-glue-elasticsearch-1.4.2-8.el6sat.noarch * katello-glue-pulp-1.4.2-8.el6sat.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.4.3-3.el6sat.noarch * openldap-2.4.23-31.el6.x86_64 * pulp-rpm-plugins-2.1.1-1.el6sat.noarch * pulp-selinux-2.1.1-1.el6sat.noarch * pulp-server-2.1.1-1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.1.7-3.el6sat.noarch * ruby193-rubygem-net-ldap-0.2.2-7.el6_4.noarch * signo-0.0.15-1.el6sat.noarch * signo-katello-0.0.15-1.el6sat.noarch I tried to test it with two scenarios: 1. Updated hostname to include capital letters on the existing satellite6 setup installed with above build. 2. Installed a fresh node and sets the hostname with capital letters and then ran katello-configure and foreman-proxy-configure In both ways, I didn't see any failure while running katello-configure. However while login to UI, I see the signo error as below. -- Relay Party https://host166.englab.pnq.redhat.com not trusted, consult SSO configuration. -- Host name that I set was "HOST166.englab.pnq.redhat.com", however URL using the hostname in small letters. Not sure if that's the reason. I would like to know two things: 1. I just checked the katello-configure output and it seems fine, so do I need to check any configuration file if everything is ok ? 2. Is this relay party issue is related to this bugzilla or shall I log a different bz ? Not sure if this
This is not related directly to the original issue (by the time of the BZ being created, Signo was not in place yet). Therefore I would suggest filing a new BZ, as the katello-configure went successfully, and therefore the original issue was fixed. Thank you for finding it.
As per comment4 and 5, I'm moving this bz to verified state as the reported issue is no longer reproducible during katello-configure. However for relat party issue, I've opened a new bz https://bugzilla.redhat.com/show_bug.cgi?id=972575
mass move to CLOSED:CURRENTRELEASE since MDP1 has been released.