Bug #27397
Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1730026
Some hammer commands fail with:
Error: uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Did you mean? HammerCLIKatello::LifecycleEnvironmentNameMapping
This definitely happens on `hammer docker manifest list`, but I am yet to discover full scope of the problem.
Version:
Satellite 6.6.0 snap 11
pulp-server-2.19.1-1.el7sat.noarch
satellite-6.6.0-5.beta.el7sat.noarch
katello-3.12.0-1.el7sat.noarch
foreman-1.22.0.9-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.18.0.2-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.17.1-2.el7sat.noarch
Associated revisions
History
#1
Updated by Martin Bacovsky over 3 years ago
Updated by - Assignee set to Martin Bacovsky
- Category changed from Hammer to Container
- Subject changed from Some hammer commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable to Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
#2
Updated by Martin Bacovsky over 3 years ago
- Category changed from Container to CLI
- Project changed from Katello to Docker
#3
Updated by Martin Bacovsky over 3 years ago
- Status changed from New to Closed
Applied in changeset hammer_cli_foreman_docker|6f92ac63eaa8c6cc863de1af0cbfc130eb1d03a9.
Fixes #27397 - lifecycle environments
Rename --environment options to --lifecycle-environment
to be consistent with rest of the CLI. --environment
is preserved and deprecated.