Red Hat Bugzilla – Bug 1009583
reserve workflow should not default to filtering by STABLE tag
Last modified: 2018-02-05 19:41:31 EST
Description of problem:
Select RedHatEnterpriseLinux7, but the "distro" and "tag" fields are not set, and no systems are listed in the lab field.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Rhel7 builds are listed, and system architectures are listed.
To be able to reserve a rhel7 machine
This is because the reserve workflow defaults to tag STABLE and no RHEL7 distros have been tagged stable.
You can change the tag to "None Selected" and you will then get a list.
(In reply to Bill Peck from comment #2)
> This is because the reserve workflow defaults to tag STABLE and no RHEL7
> distros have been tagged stable.
> You can change the tag to "None Selected" and you will then get a list.
Yup, you're correct. I don't recall having to do that the last time I reserved a rhel7 machine, so that's what threw me off.
I'm guessing we don't have any distros that RTT considers STABLE.
Bill, you might be thinking of RTT_ACCEPTED which is the tag added by RTT.
STABLE is supposed to be set by addDistro.d/updateDistro when the distro has been installed successfully. But that only happens if add_distro=1 is set in /etc/sysconfig/beaker_lab_import and if --run-jobs is passed to beaker-import. It looks like our crusty old Perl script to invoke beaker-import does not pass --run-jobs. I'm not sure if/when that regressed, but it must have been a long time ago, judging by the fact that no distros have been tagged STABLE since we added tag auditing.
Defaulting to STABLE tag in the reserve workflow is probably not wise since it assumes the Beaker administrator has got that working properly (and that they actually want to run those jobs). We might be better off defaulting to no tag filtering in reserve workflow.
For 0.15.1, we'll switch the reserve workflow to not care about the distro tags by default.
For 0.16 and later, bug 958590 should mean distros start getting tagged more reliably, but that won't directly impact the resolution of this issue.
beaker 0.15.1 has been released.