Bug #27397: Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable - Docker - Foreman

Actions

Copy link

Bug #27397

closed

Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable

Added by Martin Bacovsky almost 6 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Martin Bacovsky

Category:

CLI

Target version:

Difficulty:

Triaged:

Bugzilla link:

1730026

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

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

Actions

Copy link

Updated by Martin Bacovsky almost 6 years ago

Subject changed from Some hammer commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable to Some hammer docker commands fail with uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable
Category changed from Hammer to Container
Assignee set to Martin Bacovsky