Bug 713254 - unable to delete kernel options added in Install Options tab
Summary: unable to delete kernel options added in Install Options tab
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.6
Hardware: All
OS: Linux
unspecified
medium vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-14 19:46 UTC by Clark Williams
Modified: 2019-05-22 13:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-30 05:41:54 UTC


Attachments (Terms of Use)

Description Clark Williams 2011-06-14 19:46:39 UTC
Description of problem:

Unable to delete system specific Kernel Options while in the Install Options tab

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

[root@beaker ~]# rpm -q beaker
beaker-0.6.12-1.el5

How reproducible:
always

Steps to Reproduce:
1. add a Kernel Option for x86_64
2. add a Kernel Option Post for RedHatEnterpriseLinux6 family
3. attempt to delete Kernel Option Post for RedHatEnterpriseLinux6
  
Actual results:
HTTPD server error:

500 Internal error
The server encountered an unexpected condition which prevented it from fulfilling the request.


Expected results:
Deleted Kernel Options Post

Comment 1 Raymond Mancy 2011-06-14 22:52:52 UTC
it's dying on a key constraint failure in the db, but the code will actually need to be changed to get this to work properly.

Comment 2 Dan Callaghan 2011-06-20 03:31:53 UTC
I just saw a similar exception when deleting a system:

sqlalchemy.exceptions.OperationalError: (OperationalError) (1452, 'Cannot add or update a child row: a foreign key constraint fails (`beaker/provision_family`, CONSTRAINT `provision_family_ibfk_3` FOREIGN KEY (`provision_id`) REFERENCES `provision` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)') u'UPDATE provision_family SET provision_id=%s WHERE provision_family.id = %s' [None, 3836L]


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