Bug 752437

Summary:	Disabling a lab controller removes that lab controller from every system
Product:	[Retired] Beaker	Reporter:	Sean Waite <swaite>
Component:	web UI	Assignee:	Raymond Mancy <rmancy>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.7	CC:	bpeck, dcallagh, ebaak, jnicolet, mbrodeur, mcsontos, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-11-10 17:28:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sean Waite 2011-11-09 13:51:47 UTC

Description of problem:
If you disable a lab controller, any system that is associated with that lab controller has the "Lab Controller" item set to "None"

This is a small problem on the less-utilized lab controllers, but on some of them this could effect thousands of systems. 

We need the lab controller setting to remain on the correct lab controller, regardless of the status of the lab controller. 

The problem I see is what behavior a system will have if it's lab controller is disabled and a test schedules, we might need some additional logic to handle this.

Comment 1 Bill Peck 2011-11-09 14:01:56 UTC

Are you sure your not removing the lab controller?

Disable should be for temporary offline and does not remove the lab controller from systems.

Comment 2 Sean Waite 2011-11-09 14:21:14 UTC

As far as I'm aware of, we didn't manually remove any lab controllers from the system. Looking through the history, there isn't any reference to the lab controllers vanishing from the system. I can see where it was re-added via CSV later.

Comment 3 Matt Brodeur 2011-11-10 17:28:19 UTC

Sorry, false alarm.  I confirmed with Wei (one of the NAY admins) that the LC was "Removed" instead of "Disabled".  Dropping the LC assignment from every host is expected behavior in that case.