Project

General

Profile

Bug #6871

Capsule happily syncs when invalid environment requested

Added by Brad Buckingham about 5 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Category:
API
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1125397
Description of problem:

Assuming a capsule (id:1) has only the dev (id:2) lifecycle environment attached, attempting to perform a synchronize with the prod (id:4) lifecycle environment will attempt to perform the synchonize.

Scenario:

hammer capsule synchronize --id 1 --environment-id 4

Actual Result:

the server will attempt to sync environment 4, even if it is not associated with the capsule

Expected Result:

the server should return an error to the user indicating that it is an invalid environment

Associated revisions

Revision 5ee5f52d (diff)
Added by Brad Buckingham about 5 years ago

fixes #6871 / BZ 1125397 - capsule - add error case for content sync

If the user attempts to sync a lifecyle environment that isn't attached
to the capsule, generate an error to the user.

Revision f551c009
Added by Brad Buckingham about 5 years ago

Merge pull request #4514 from bbuckingham/issue-6871

fixes #6871 / BZ 1125397 - capsule - add error case for content sync

History

#1 Updated by The Foreman Bot about 5 years ago

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

#2 Updated by Eric Helms about 5 years ago

  • Assignee set to Brad Buckingham
  • Triaged changed from No to Yes

#3 Updated by Brad Buckingham about 5 years ago

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

#4 Updated by Eric Helms about 5 years ago

  • Legacy Backlogs Release (now unused) set to 13

Also available in: Atom PDF