Bug #22250
Updated by Martin Bacovsky almost 7 years ago
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1526828 *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