Bug 1490969
| Summary: | Unable to change the default Satellite username "admin-username" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Gilbert Kimetto <gkimetto> | ||||||
| Component: | Users & Roles | Assignee: | satellite6-bugs <satellite6-bugs> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 6.2.11 | CC: | dhlavacd, gkimetto, mhulan | ||||||
| Target Milestone: | 6.4.0 | Keywords: | Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-10-16 19:10:26 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Gilbert Kimetto
2017-09-12 15:54:48 UTC
Do you mean the default username "admin"? In Sat 6.2.12 the username field is disabled, the same applies to 6.2.10. I don't have the 6.2.11 at hand, would you mind uploading a screen if it's not the case in 6.2.11? Did you perhaps changed the admin name by passing to --foreman-admin-username satellite-installer? Hi Marek
I had 3 Satellite VMs with 6.2.11. I am no longer able to update the "Username" field as before and now the default user is "admin" and greyed out.
If you want to take a look around its 10.19.231.248 {admin/redhat}
So what is the issue then? In comment 0 you said you can change the username, in comment 2 you say the field is disabled. How do you try to change the username then? On instance you provided I see the text field disabled. Hi Marek This happened immediately after I did the install. I used the name "admin-username" for a while then decided to change it. I am not sure when/how the field changed to "admin" disabled. I will try to reproduce this when I do another 6.2.11 I think the only way to achieve this is to change the admin name on initial installation by doing > satellite-installer --foreman-admin-username admin-username as suggested in comment 1. If that's the case, we should change the way how we detect the default admin account when we decide whether the username field should be editable, right now we disable the field on if login == 'admin'. I'd say this is low prio though, the installer parameter is rarely used. Created attachment 1338311 [details]
After install change name
Right after the install where I used the foreman CLI command to install and create a user gk-admin. I loginto the GUI and attempt to change the name to admin. When I save the name remains as "gk-admin"
Created attachment 1338312 [details]
After Submit
Gilbert, foreman CLI is hammer, did you use hammer or satellite-installer to set a user name to gk-admin? This is the command used from my history (Following the 6.2 Install Guide): satellite-installer --scenario satellite --foreman-initial-organization "gkm8o_org" --foreman-initial-location "Kericho" --foreman-admin-username gk-admin --foreman-admin-password redhat --foreman-proxy-dns-managed=false --foreman-proxy-dhcp-managed=false Ok, thanks, so my guess in comment 1 was correct. Thanks for confirmation. Created redmine issue http://projects.theforeman.org/issues/21353 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21353 has been resolved. verified on Sat 6.3 snap 6 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. https://access.redhat.com/errata/RHSA-2018:2927 |