Bug 1523702

Summary: The foreman-maintain upgrade check --target-version 6.3 version hammer admin password does not work if the original admin password on 6.2.12 was auto-generated
Product: Red Hat Satellite Reporter: amaliver
Component: Satellite MaintainAssignee: Anurag Patel <apatel>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: ajoseph, amaliver, apatel, bbuckingham, inecas, kgaikwad, mbacovsk, sabnave
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-10 12:47:06 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:

Description amaliver 2017-12-08 16:08:09 UTC
Description of problem:
I upgrading from Satellite 6.2.12 to 6.3-Beta and when I initially installed my Satellite 6 server I used auto-generated password instead of initially assigning the admin account a password. The foreman-maintain upgrade check --target-version 6.3 version hammer password states Invalid Credentials even though I can use that same credential to login to the Satellite GUI.

Version-Release number of selected component (if applicable):


How reproducible:
Cory and I were able to reproduce the same error

Steps to Reproduce:
1. Install satellite 6.2 without specifying initial admin password nor username: satellite-installer --scenario satellite

2. Followed section 2.2.1 on the Satellite 6.3 Upgrade document:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/html-single/upgrading_and_updating_red_hat_satellite/#upgrading_a_connected_satellite_server

3. Fails on step 10
Actual results:

Hammer username [admin]: admin
Hammer password: 

Expected results:

To move forward with upgrade

Additional info:
manually change the admin password and the script will work.

Comment 2 Kavita 2017-12-11 12:10:39 UTC
(In reply to amaliver from comment #0)
> Description of problem:
> I upgrading from Satellite 6.2.12 to 6.3-Beta and when I initially installed
> my Satellite 6 server I used auto-generated password instead of initially
> assigning the admin account a password. The foreman-maintain upgrade check
> --target-version 6.3 version hammer password states Invalid Credentials even
> though I can use that same credential to login to the Satellite GUI.
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> Cory and I were able to reproduce the same error
> 
> Steps to Reproduce:
> 1. Install satellite 6.2 without specifying initial admin password nor
> username: satellite-installer --scenario satellite
> 
> 2. Followed section 2.2.1 on the Satellite 6.3 Upgrade document:
> 
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3-beta/
> html-single/upgrading_and_updating_red_hat_satellite/
> #upgrading_a_connected_satellite_server
> 
> 3. Fails on step 10
> Actual results:
> 
> Hammer username [admin]: admin
> Hammer password: 
> 
> Expected results:
> 
> To move forward with upgrade
> 
> Additional info:
> manually change the admin password and the script will work.

This issue might be related to BZ https://bugzilla.redhat.com/show_bug.cgi?id=1513599
Auto-generated password string may contains upper-case letters.

Please confirm if this is the scenario that you are facing.
Otherwise, it would be great if you have reproducer so that we can debug further.

Comment 3 Anto P Joseph 2017-12-27 03:07:05 UTC
Workaround:

update hammer/cli_config.yml with new/working admin password.

and update the same in /etc/foreman-maintain/foreman-maintain-hammer.yml

**issue: admin password with Uppercase gets converted to Lowecase.

Comment 4 Anurag Patel 2018-01-10 12:47:06 UTC

*** This bug has been marked as a duplicate of bug 1513599 ***

Comment 5 Red Hat Bugzilla 2023-09-14 04:13:31 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days