Project

General

Profile

Actions
Copy link

Bug #10460

closed

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

Added by Justin Sherrill over 9 years ago. Updated over 5 years ago.

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

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 3 (0 open — 3 closed)

Related to Katello - Bug #10459: Don't publish puppet environments for content views without puppet environmentsClosed05/11/2015Actions
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"ClosedJustin Sherrill05/09/2015Actions
Has duplicate Katello - Bug #9316: Puppet Environment Deletion allowed even when content view still existsDuplicate02/10/2015Actions
Actions
Copy link
 #1

Updated by Justin Sherrill over 9 years ago

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

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release changed from 31 to 51
Actions
Copy link
 #3

Updated by Christian Ehart over 9 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
Actions
Copy link
 #4

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release changed from 51 to 55
Actions
Copy link
 #5

Updated by Eric Helms over 9 years ago

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

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release changed from 55 to 61
Actions
Copy link
 #7

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release changed from 61 to 31
Actions
Copy link
 #8

Updated by Stephen Benjamin over 9 years ago

  • Translation missing: en.field_release changed from 31 to 70

Mass move to 2.4.0

Actions
Copy link
 #9

Updated by Justin Sherrill about 9 years ago

  • Translation missing: en.field_release changed from 70 to 86
Actions
Copy link
 #10

Updated by Eric Helms over 8 years ago

  • Translation missing: en.field_release changed from 86 to 144
Actions
Copy link
 #11

Updated by Eric Helms over 8 years ago

  • Translation missing: en.field_release changed from 144 to 168
Actions
Copy link
 #12

Updated by Eric Helms over 8 years ago

  • Translation missing: en.field_release changed from 168 to 162
Actions
Copy link
 #13

Updated by Justin Sherrill over 8 years ago

  • Translation missing: en.field_release changed from 162 to 114
Actions
Copy link
 #14

Updated by John Mitsch over 5 years ago

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

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.

Actions
Copy link

Also available in: Atom PDF