Project

General

Profile

Bug #9799

Incremental update publishes/promotes to incorrect lifecycle environments of a composite content view

Added by Justin Sherrill about 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Web UI
Target version:
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1200540
Description of problem:
Incremental update publishes/promotes to incorrect lifecycle environments of a composite content view

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150303.0

How reproducible:
Always

Steps to Reproduce:
1. Create a content view cv1 and publish v1.0 and promote to Library, QE. Register and subscribe a content host ch1 to cv1 -> QE
2. Create a composite content view ccv2, add cv1 to it. Publish v1.0 - promote to Library, QE. Register and subscribe a content host ch2 to ccv2 -> QE
3. Go to Content -> Errata -> Select an errata which is applicable to both content hosts ch1 and ch2
4. Click Apply Errata
5. Both ch1 and ch2 will show up
6. Just select ch1, click Next
7. Click the check box to immediately apply the errata to the content host. Click confirm.

Actual results:
1 - cv1 is published with v1.1 for QE (works as expected)
2 - ch1 received the errata (works as expected)
3 - cch2 is published with v1.1 for both Library, QE (not sure why cch2 is published to both Library, QE) (Not works as expected)

Expected results:
For the 3rd item above, I really dont know the expected result, this is a design question

Additional info:

Associated revisions

Revision 3817b397 (diff)
Added by Justin Sherrill about 8 years ago

fixes #9799 - changing structure of incremental update around composites

Now when performing an incremental update, you simply pass the composites
in the "content_view_version_environments" structure as a parameter.
This gives the user control over exactly which composites are updated.
If a user passes a composite without a componenet specified an error is thrown

Revision 917a9398
Added by Justin Sherrill about 8 years ago

Merge pull request #5118 from jlsherrill/9799

fixes #9799 - changing structure of incremental update around composites

History

#1 Updated by Justin Sherrill about 8 years ago

  • Target version set to 68
  • Legacy Backlogs Release (now unused) set to 23
  • Difficulty set to medium
  • Triaged changed from No to Yes

#2 Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5118 added
  • Pull request deleted ()

#3 Updated by Justin Sherrill about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF