Project

General

Profile

Actions

Bug #8547

closed

Promoting CVs with hammer results in error when referencing environment by name

Added by Partha Aji about 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Hammer
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1165642
Description of problem:
When promoting a content view version using hammer, if the lifecycle environment to which we are promoting is referenced by name, we get an error. If we promote by lifecycle environment ID, then the promotion works correctly.

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

How reproducible:
Every time

Steps to Reproduce:
1. Check what lifecycle environments we have available:
  1. lifecycle-environment list --organization "Default_Organization"
    ---|---------|--------
    ID | NAME | PRIOR
    ---|---------|--------
    2 | Crash | Library
    1 | Library |
    ---|---------|--------
2. Promote a CV version by name:
  1. hammer content-view version promote --content-view "acme-7.0.0" --organization "Default_Organization" --lifecycle-environment "Crash" --id 7

Actual results:
Could not promote the content view:
Error: environment found more than once

Expected results:
Correct promotion.

Additional info:
Promotion by lifecycle environment ID works fine:
  1. hammer content-view version promote --content-view "acme-7.0.0" --organization "Default_Organization" --lifecycle-environment-id 2 --id 7
    [.....................................................................................................................................................] [100%]
    Task 09187308-173c-4aff-8d46-4b4c6a1c8f49: success
Actions

Also available in: Atom PDF