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 1526828 - After upgrading to 6.3 hammer credentials are not migrated to new location - Invalid username or password
Summary: After upgrading to 6.3 hammer credentials are not migrated to new location - ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Martin Bacovsky
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-17 20:02 UTC by Michal Dekan
Modified: 2021-12-10 15:30 UTC (History)
7 users (show)

Fixed In Version: katello-installer-base-3.4.5.23-1,katello-installer-base-3.4.5.24-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
foreman-debug from satellite 6.2.12 prior to upgrade (7.87 MB, application/x-xz)
2018-01-11 10:50 UTC, Michal Dekan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22250 0 High Closed After upgrading hammer credentials are not migrated to new location - Invalid username or password 2020-12-11 15:57:35 UTC
Foreman Issue Tracker 22431 0 High Closed After upgrading hammer credentials are not migrated to new location - Invalid username or password 2020-12-11 15:57:36 UTC

Description Michal Dekan 2017-12-17 20:02:55 UTC 
Description of problem:

Upgrading 6.2 -> 6.3 public beta does not migrate hammer login credentials from ~/.hammer/cli_config.yml (6.1, 6.2) to ~/.hammer/cli.modules.d/foreman.yml (new location in 6.3) which leads to error

# hammer organization list
Invalid username or password

~/.hammer/cli.modules.d/foreman.yml contained some random string as a password

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

satellite 6.2.12 upgraded to 6.3 public beta

[root@provisioning ~]# rpm -qa | egrep "satellite|hammer"
satellite-cli-6.3.0-21.0.beta.el7sat.noarch
satellite-common-6.3.0-21.0.beta.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_admin-0.0.7-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_remote_execution-0.0.6-1.fm1_15.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3.3-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.11.0.3-1.el7sat.noarch
tfm-rubygem-foreman_theme_satellite-1.0.4.11-1.el7sat.noarch
tfm-rubygem-hammer_cli_csv-2.3.0-1.el7sat.noarch
satellite-6.3.0-21.0.beta.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.6-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_discovery-1.0.0-1.el7sat.noarch
satellite-installer-6.3.0.9-1.beta.el7sat.noarch
tfm-rubygem-hammer_cli-0.11.0.1-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_openscap-0.1.5-1.fm1_15.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.11.3.1-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.12-1.fm1_15.el7sat.noarch
satellite-capsule-6.3.0-21.0.beta.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.3-1.el7sat.noarch


How reproducible:


Steps to Reproduce:
1. Upgrade to 6.3 with stored hammer credentials
2. Run hammer command

Actual results:

# hammer organization list
Invalid username or password

After satellite upgrade


Expected results:

satellite-installer will migrate previously stored login credentials to new location used in 6.3
Comment 4 Ivan Necas 2018-01-10 12:41:14 UTC 
@martin: could you have a look at this? I wonder if this could be somehow related to https://community.theforeman.org/t/hammer-username-password-not-working-after-upgrading-to-katello-3-5/7957/9
Comment 5 Martin Bacovsky 2018-01-11 09:31:24 UTC 
I was not able to reproduce yet. Do we have the machine at hand? Can I have the foreman-debug or sosreport?

Was the machine upgraded from 6.1 or was it 6.2 fresh install? Any interesting configuration tweaks?
Comment 6 Michal Dekan 2018-01-11 10:50:02 UTC 
Created attachment 1379944 [details]
foreman-debug from satellite 6.2.12 prior to upgrade
Comment 7 Martin Bacovsky 2018-01-11 11:15:50 UTC 
Thanks for the debug info.

The way to reproduce is
1/ install satellite 6.2
2/ change admin password in the UI
3/ update your hammer config to the new password
4/ upgrade to 6.3 (without specifying the --admin-password on the installer CLI)
5/ run hammer os list and see the error

The problem is that the hammer config changed the location and is created with the admin credentials stored in answer file [1].

Workaround is to run the upgrade with --admin-password <current admin password>
or changing the value in answer file prior the upgrade.

The config is not replaced later by puppet (even not when changed) so this issue is present only during upgrade.

[1] /etc/foreman-installer/scenarios.d/satellite-answers.yaml
Comment 9 Martin Bacovsky 2018-01-11 13:31:56 UTC 
Created redmine issue http://projects.theforeman.org/issues/22250 from this bug
Comment 12 Satellite Program 2018-01-26 15:08:03 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22431 has been resolved.
Comment 15 Jitendra Yejare 2018-02-15 16:18:46 UTC 
Verified !

@ Satellite 6.3 snap 35

Steps:

1. Satellite 6.2 with hammer config creds saved under ~/.hammer/cli_config.yml
2. Upgraded to satellite 6.3
3. Verify if hammer commands return results without providing the credentials


Observation:

1. Hammer commands returned correct result of command without providing credentials.
2. No errors were thrown from hammer for invalid creds
3. The cli_config.yml carry forworded to 6.3 from 6.2 as it is, so the hammer is reading credentials from that file only.
4. The new .hammer/cli.modules.d/foreman.yml file is created but its empty.
---
:foreman: {}
5. Hammer auth status post upgrade
# hammer auth status
Using configured credentials for user 'admin'.
Comment 16 Satellite Program 2018-02-21 16:54:17 UTC 
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:0336
Note You need to log in before you can comment on or make changes to this bug.