Bug 786110 - Removal of system template fails if Repo added
Summary: Removal of system template fails if Repo added
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
: 786591 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-31 13:52 UTC by Kedar Bidarkar
Modified: 2019-09-26 13:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:23:39 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kedar Bidarkar 2012-01-31 13:52:42 UTC
Description of problem:

Upon removal of system template, it throws an error saying 

"undefined method `eq' for nil:NilClass" 

"An error has occurred while communicating with the server"

Not sure if any logs I could provide here, as it's not able to communicate with the server.


Version-Release number of selected component (if applicable):
katello-201

How reproducible:
Adding a repo to system template via UI is must.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Cannot Remove a System Template if Repo is added

Expected results:
Should be possible to remove the System TEmplate 

Additional info:

Comment 1 Kedar Bidarkar 2012-02-02 07:10:13 UTC
*** Bug 786591 has been marked as a duplicate of this bug. ***

Comment 2 Brad Buckingham 2012-02-02 14:20:16 UTC
commit - c41ec4f9f55bcf4c9036bef07208fcae5c16d08c

This change required adding an id column to the system_templates_repositories table.  As a result, developers need to run 'clear-all.sh' to regenerate the schema.

Comment 3 Mike McCune 2012-03-07 23:44:06 UTC
mass move ON_QA after brewing

Comment 4 Corey Welton 2012-03-15 17:16:58 UTC
QA verified.

Comment 6 Mike McCune 2013-08-16 17:56:52 UTC
getting rid of 6.0.0 version since that doesn't exist


Note You need to log in before you can comment on or make changes to this bug.