Project

General

Profile

Bug #22811

incremental update propagate-all-composites does not respect lifecycle-environment

Added by Daniel Kimsey about 4 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

hammer content-view version incremental-update@ incorrectly propagates ccv's to all environments even if --lifecycle-environment is set.

Katello 3.4.

Given

cv-app-foo

Version Lifecycle Environment Description
1.0 development // staging

ccv-something

Version Lifecycle Environment Description
1.0 development // staging cv-app-foo-v1 added

Do

The following command will cause ccv-something to promoted to all lifecycles rather than just the expected one. cv-app-foo will correctly only be propagated to development.

$ hammer content-view version incremental-update --content-view-version-id=1337 --package-ids=... --description='new build' --lifecycle-environments=development --propagate-all-composites=true
[.............................................................................................................................................] [100%]
Content View: cv-app-foo version 1.1
Added Content:
  Packages:
        ...

Content View: ccv-something version 1.1
Added Content:

Becomes

cv-app-foo

Version Lifecycle Environment Description
1.1 development new build // packages: ...
1.0 staging

ccv-something

Version Lifecycle Environment Description
1.1 development // staging new build
1.0 cv-app-foo-v1 added

Notice ccv-something v1.1 was deployed to both the development and staging lifecycles. I'd expect only the development lifecycle to be affected. This may not have an effect since the cv isn't deployed to staging. But it strikes me as a bit odd, and potentially concerning.

History

#1 Updated by Andrew Kofink about 4 years ago

  • Legacy Backlogs Release (now unused) set to 339

#2 Updated by Andrew Kofink about 4 years ago

  • Legacy Backlogs Release (now unused) changed from 339 to 351

#3 Updated by Jonathon Turel over 2 years ago

  • Triaged set to Yes
  • Target version changed from Katello 3.5.3 to Katello Backlog

Moving this to the general backlog since we are long past 3.5.1

Also available in: Atom PDF