Project

General

Profile

Bug #10460

Prevent puppet environments from being deleted when produced by a content view

Added by Justin Sherrill over 4 years ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Currently users can delete a puppet environment that a content view publish/promote created.

When trying to republish, the user will get an error:

Validation failed: Puppet environment can't be blank

To recover from this, follow these steps: https://gist.github.com/jlsherrill/2dd11592853885643251


Related issues

Related to Katello - Bug #10459: Don't publish puppet environments for content views without puppet environmentsClosed2015-05-11
Related to Katello - Bug #10435: Publishing an existing CV with a previous deletion of Puppet Environment ends up with Error "Validation failed: Puppet environment can't be blank"Closed2015-05-09
Has duplicate Katello - Bug #9316: Puppet Environment Deletion allowed even when content view still existsDuplicate2015-02-10

History

#1 Updated by Justin Sherrill over 4 years ago

  • Related to Bug #10459: Don't publish puppet environments for content views without puppet environments added

#2 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 31 to 51

#3 Updated by Christian Ehart over 4 years ago

  • Related to Bug #10435: Publishing an existing CV with a previous deletion of Puppet Environment ends up with Error "Validation failed: Puppet environment can't be blank" added

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 51 to 55

#5 Updated by Eric Helms over 4 years ago

  • Has duplicate Bug #9316: Puppet Environment Deletion allowed even when content view still exists added

#6 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 55 to 61

#7 Updated by Eric Helms about 4 years ago

  • Legacy Backlogs Release (now unused) changed from 61 to 31

#8 Updated by Stephen Benjamin about 4 years ago

  • Legacy Backlogs Release (now unused) changed from 31 to 70

Mass move to 2.4.0

#9 Updated by Justin Sherrill almost 4 years ago

  • Legacy Backlogs Release (now unused) changed from 70 to 86

#10 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 144

#11 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#12 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 162

#13 Updated by Justin Sherrill about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 162 to 114

#14 Updated by John Mitsch about 2 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF