On 05/16/2014 04:12 PM, Dan Callaghan wrote:
Excerpts from Amit Saha's message of 2014-05-16 16:02:21 +1000:
> We have had some discussion on the bugzilla entry for this bug [1].
> So, just to make sure all of us are on the same page, as opposed to my first
> plan to implement a "--force" switch, the forced provisioning will always
> be the default. Thus, bkr machine-test system1.fqdn.name will provision the system
> even if it is manual or broken.
Now that I think about this again, I'm not so sure... Certainly for bkr
machine-test it is a useful improvement, but I wonder if it would be bad
for the --machine option to behave differently in bkr machine-test than
in other workflow commands?
Yeah, that's a good point - consistency across commands is worth taking
into account here.
And we wouldn't want to *always* ignore the system status, as in many
cases you *want* it to fail immediately if Beaker thinks the system is
currently Broken or it has been removed from the Scheduler's control.
If we did have a switch to opt in to force="" it should be
called
something like "--ignore-system-status", since "--force" is a bit too
general.
+1
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
Testing Solutions Team Lead