Bug 573131 - Unable to successfully change system FQDN in Beaker and return system to Beaker
Summary: Unable to successfully change system FQDN in Beaker and return system to Beaker
Keywords:
Status: CLOSED DUPLICATE of bug 670912
Alias: None
Product: Beaker
Classification: Retired
Component: inventory
Version: 0.5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-12 22:38 UTC by PaulB
Modified: 2014-08-12 04:35 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-02 03:21:19 UTC
Embargoed:

Attachments (Terms of Use)

Description PaulB 2010-03-12 22:38:18 UTC 
The following system name was changed:
amd-lisbon-01.lab.bos.redhat.com

New FQDN:
amd-pence-01.lab.bos.redhat.com

Re ticket:
https://engineering.redhat.com/rt3/Ticket/Display.html?id=59735 

I was able to change the name to amd-pence-01.lab.bos.redhat.com
in Beaker and "save the change". However, when I try to return the system to Beaker I get the following:
500 Internal error

I was advised that the old record for amd-lisbon-01.lab.bos.redhat.com must be deleted from cobbler.

Thank you,
-pbunyan
Comment 1 Paul Baumgardner 2010-03-15 17:41:33 UTC 
amd-lisbon-01.lab.bos.redhat.com has been removed from cobbler.
Comment 2 PaulB 2010-04-01 15:15:51 UTC 
This issue has been resolved...

As part of my procedure for changing a systems FQDN:
I have made a note to request the Cobbler entry be deleted for the former FQDN, in my RT ticket.

Thanks you, Eng-Ops,
-pbunyan
Comment 3 Matt Brodeur 2010-08-10 19:28:52 UTC 
I'd like to see Beaker handling this directly.  At a minimum a meaningful error message should be produced.  Preferably Beaker would catch the error and purge the old cobbler system record.

Since we have a workaround, this is pretty low on the list for us.
Comment 4 Dan Callaghan 2011-02-02 03:21:19 UTC 

*** This bug has been marked as a duplicate of bug 670912 ***
Note You need to log in before you can comment on or make changes to this bug.