Thank you for your bug report. This issue was evaluated for inclusion in the current release of Subscription Asset Manager (SAM). Unfortunately, we are unable to address this request. Because we are in the final stages of development in the current release, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next release of SAM.
We will allow these usernames in headpin mode only for now. Katello will remain restrictive until pulp is fixed.
Cloned the Katello bug in bz 871537
merged fix in commit: https://github.com/Katello/katello/commit/b8615f448d211fd03f02fcdf37f66a76420ad8df
*** Bug 871794 has been marked as a duplicate of this bug. ***
regressed due to commit: https://github.com/Katello/katello/commit/9c5e2918494c5e1128df82b2bbf2c3d078a8e528
a quick fix was merged [1] to keep utf8 functionality in headpin. This will be fixed correctly for both headpin and katello once some deeper changes are made to katello so that pulp will play nice with utf8 usernames. [1] https://github.com/Katello/katello/commit/6f1723b36fc9f92c4786f4c52a688f0c8553dc16
Created attachment 639077 [details] Creating user names using unicode characters VERIFIED : # rpm -qa | grep katello katello-certs-tools-1.2.1-1h.el6_3.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-cli-common-1.2.2-1h.el6_3.noarch katello-glue-candlepin-1.2.2-1h.el6_3.noarch katello-cli-1.2.2-1h.el6_3.noarch katello-selinux-1.2.1-1h.el6_3.noarch katello-headpin-all-1.2.2-1h.el6_3.noarch katello-headpin-1.2.2-1h.el6_3.noarch katello-configure-1.2.1-1h.el6_3.noarch katello-common-1.2.2-1h.el6_3.noarch
Sorry .. Changed to MODIFIED need to verify it for puddle
Created attachment 648286 [details] User name i18n VERIFIED : # rpm -qa | grep katello katello-configure-1.2.3-1h.el6_3.noarch katello-headpin-all-1.2.6-1h.el6_3.noarch katello-glue-candlepin-1.2.6-1h.el6_3.noarch katello-cli-1.2.4-1h.el6_3.noarch katello-selinux-1.2.1-1h.el6_3.noarch katello-cli-common-1.2.4-1h.el6_3.noarch katello-headpin-1.2.6-1h.el6_3.noarch katello-common-1.2.6-1h.el6_3.noarch katello-candlepin-cert-key-pair-1.0-1.noarch
I am not sure, what have You verified. I have just tried: katello-configure --deployment=sam --user-name='root' --user-pass='redhat' --org-name='Red Hat Czech, s. r. o.' 1. katello-configure did not check the parameter and started processing. 2. After the failure I tried to run katello-configure again with correct value of --org-name parameter, but it did not finished. I have not found easy way to repair the system after the previous failure and to configure katello (even uninstalling of all SAM related packages was not enough). Therefore I see no change, opening the issue again.
I just ran: $ katello-configure --deployment=sam --user-name=adprice and it configured correctly (from the latest compose). I can then use that admin user/pass to issue cli commands: $ headpin -u adprice -p admin ping -------------------------------------------------------------------------------------------------------------------------------------------------------------- Katello Status Status Service Result Duration Message -------------------------------------------------------------------------------------------------------------------------------------------------------------- OK candlepin OK 631ms candlepin_auth OK 37ms elasticsearch OK 26ms katello_jobs OK 34ms where as 'admin' does not work: $ headpin -u admin -p admin ping Invalid credentials
I do not understand You. Why did You run $ katello-configure --deployment=sam --user-name=adprice while I reported problem with # katello-configure --deployment=sam --user-name='root' --user-pass='redhat' --org-name='Red Hat Czech, s. r. o.' ?
The point is, that the application must perform input validation. Do not force me keep trying other combinations of unchecked params. Just assert that it won't run until the input is OK.
Jakub: Adam was showing you that user-names can have periods and @ symbols in them, which is the intent of this bug. There is another bug around org name validation and accepting non-validating parameters from the installer, but that is a different issue and requires a new BZ.
I tried to see if there are any workarounds for the ORG error mentioned by the user and here they are: Step 1: (Invalid ORG name) # katello-configure --deployment=sam --user-name='root' --user-pass='redhat' --org-name='Red Hat Czech, s. r. o.' This errored. The logs said unable to create first org. Step 2: (Valid ORG name) # katello-configure --deployment=sam --user-name='root' --user-pass='redhat' --org-name='Red Hat Czech' This also errored out. The logs said the user already exists. Workarounds: Workaround 1 - Running katello-configure without specifying user-name, user-pass # katello-configure --deployment=sam --org-name='Red Hat Czech' Works fine - But, a new admininstrator user called 'admin' is also created. I am able to log in both as 'root' and 'admin' users. They both have administrator privileges. WORKAROUND 2 - Running katello-configure using --reset-data # katello-configure --reset-data=YES --deployment=sam --user-name='root' --user-pass='redhat' --org-name='Red Hat Czech' Works fine. Only one administrator user called 'root' is created.
A new bug is created for tracking the Organization name issue - https://bugzilla.redhat.com/show_bug.cgi?id=902990. Jakub Dorňák: If you are okay with this, can you please review and close this bug?
Tested the following scenario as originally reported in this defect and it works fine. # katello-configure --deployment=sam --user-name=qa --user-pass=redhatqa --org-name="Red Hat" Starting Katello configuration The top-level log file is [/var/log/katello/katello-configure-20130123-144705/main.log] Creating Candlepin database user ############################################################ ... OK Creating Katello database user ############################################################ ... OK Creating Katello database ############################################################ ... OK Populating Katello database schema ############################################################ ... OK Initializing Katello data ############################################################ ... OK I was able to log in as qa in the SAM UI. Version: * candlepin-0.7.23-1.el6_3.noarch * candlepin-tomcat6-0.7.23-1.el6_3.noarch * elasticsearch-0.19.9-5.el6_3.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.2.1-1h.el6_3.noarch * katello-cli-1.2.1-12h.el6_3.noarch * katello-cli-common-1.2.1-12h.el6_3.noarch * katello-common-1.2.1-15h.el6_3.noarch * katello-configure-1.2.3-3h.el6_3.noarch * katello-glue-candlepin-1.2.1-15h.el6_3.noarch * katello-headpin-1.2.1-15h.el6_3.noarch * katello-headpin-all-1.2.1-15h.el6_3.noarch * katello-selinux-1.2.1-2h.el6_3.noarch * thumbslug-0.0.28-1.el6_3.noarch * thumbslug-selinux-0.0.28-1.el6_3.noarch Note: As per my earlier comments, for the Organization issue a separate Bug https://bugzilla.redhat.com/show_bug.cgi?id=902990 has been written. An email has been sent to the author of this Bug too.
Great, thanks!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0544.html