What’s New in Beaker 0.12?¶

Noteworthy changes¶

def run(self, *args, **kwargs):
    self.set_hub(**kwargs)
    ...

<ks_append>
%post
echo 'Custom script begins here'
%end
</ks_append>

New features¶

<disk>
    <sector_size op="&gt;" value="512" />
</disk>

<not>
    <disk>
        <sector_size op="=" value="512" />
    </disk>
</not>

Other enhancements¶

• The scheduler tries to pick systems with more than one CPU core before systems with only one CPU core, as the latter are rarer. (Contributed by Raymond Mancy in #%s824534.)

• The netboot configuration for a system can be cleared from the Commands tab on the system page. (Contributed by Raymond Mancy in #%s559332.)

• A new command, bkr update-prefs, lets you update your user preferences in Beaker. In this first release, it only supports updating your email address. (Contributed by Qixiang Wan in #%s832937.)

• The beaker-sync-tasks command is a new server side tool to sync the task RPMs on a local Beaker instance with those on a remote Beaker instance. It overwrites tasks of the same name on the local instance with that from the remote Beaker instance if they are of different versions. Tasks which are only present on the remote instance are added to the local instance.

  See copying tasks to learn more about how to use this tool. (Contributed by Amit Saha in #%s912205.)

• The bkr job-list command no longer prints the number of jobs found. It now accepts a --format option to control its output format. Currently, the two supported formats are list (newline-separated) and json (JSON array). The list format can be used as input to other command line utilities, for example: bkr job-list --mine --format list | wc -l would print the number of jobs found for the user invoking the command. (Contributed by Amit Saha in #%s907658.)

• Custom repositories are now made available at install time, using the Anaconda repo command in the kickstart, for Red Hat Enterprise Linux 5 and Fedora. This was already being done for Red Hat Enterprise Linux 6 and above. (Contributed by Amit Saha in #%s902390 and #%s912234.)

• You can now set unsupported_hardware in kickstart metadata to provision systems with Red Hat Enterprise Linux 6 on unsupported hardware. It can be set on a per-system basis in the Install Options tab (see System details tabs) or in the ks_meta attribute of the recipe element (see Recipes). Beaker will automatically add the unsupported_hardware command to the kickstart and provision the system, avoiding the need for manual user intervention during installation. (Contributed by Amit Saha in #%s907636.)

• The bkr client now accepts a --hub option (for all subcommands), to override the hub URL specified in the configuration file. This can be used to submit jobs against a testing Beaker instance, for example. (Contributed by Dan Callaghan in #%s903865.)

• You can now limit the distro tree import process to specific arches and variants, by passing the --arch and --variant options to beaker-import. Support for importing trees outside of their compose has also been improved. (Contributed by Raymond Mancy in #%s880933.)

• The beaker-proxy daemon now uses gevent instead of SimpleXMLRPCServer. This means beaker-proxy can efficiently handle many concurrent connections using a single process. Previously, a new handler process was forked for every request. (Contributed by Dan Callaghan.)

• The name prefix for oVirt virtual machines created by Beaker is now configurable through the guest_name_prefix setting. A lab controller can now have multiple oVirt data centers associated with it. (Contributed by Dan Callaghan.)

• oVirt integration is now enabled for Red Hat Enterprise Linux 3 and i386 recipes. (Contributed by Qixiang Wan in #%s884898 and #%s884901.)

• The special handling for kernel types when importing armhfp distro trees is now activated for arm distro trees as well. (Contributed by Bill Peck in #%s903709.)

Documentation improvements¶

• The Beaker Makefile section was updated to describe the Provides field. (Contributed by Amit Saha in #%s910725.)
• The various job XML–related sections were rearranged into a new page, Job XML. This page now includes examples of searching for specific hardware. (Contributed by Amit Saha in #%s887746.)
• The Releases section was updated for clarity. (Contributed by Dan Callaghan in #%s743579.)
• The bkr(1) man page was updated to accurately reflect all the options supported by workflow commands. (Contributed by Amit Saha in #%s916351.)
• Beaker’s documentation now includes release notes for each new version. The release notes describe any significant changes, new features, and bug fixes which are included in that release. They also contain upgrade instructions for Beaker administrators, supplanting the previous SchemaUpgrades directory.

Bug fixes¶

The following bugs were fixed in Beaker 0.12.0:

• #%s691666: guestname attribute of guestrecipe should not be required in job XML
• #%s745971: beaker-wizard should provide ‘None’ as possible value for attachment download
• #%s768381: No Fedora repos in kickstart
• #%s805791: Typo in beaker-wizard: MaxLenghtTestName should be MaxLengthTestName
• #%s807237: Job still running when all of its parts are completed
• #%s807991: Unexpected package definition: -readahead
• #%s839888: Leading and trailing whitespace is not stripped in search boxes
• #%s855703: Storing logs on the lab controller should be possible even without an archive server
• #%s855716: beaker-transfer stuck in while loop, when disabling cache with untransferred logs
• #%s858944: “autopick” element is not documented in job XML schema
• #%s872187: Recipes can become deadlocked if a system becomes free during the scheduling loop
• #%s874385: beaker_expire_distros does not enforce timeouts for HTTP and FTP requests
• #%s879991: Client should allow interrupt power command
• #%s880497: User column is always empty on Recipe Systems page
• #%s881387: Order in which recipes are displayed on the job page depends on their database ID
• #%s888959: rhts_post snippet doesn’t handle duplicate EFI entries
• #%s890261: “like” op in CPU flag filtering does not work
• #%s893878: bkr machine-test can submit an invalid job if no matching distro is found
• #%s903935: Guest recipes remain stuck in Waiting even though their host recipe is finished
• #%s906214: Check image status before starting VM on RHEV 3.1
• #%s906715: Invalid vmtype (for RHEV 3.1) specified in VirtManager
• #%s906803: bkr watchdog-extend and watchdogs-extend commands are too similar
• #%s907650: bkr job-list --mine lists all jobs if authentication fails
• #%s912159: Changes to beaker.base_mac_addr not taking effect
• #%s912242: Trailing spaces in distro tree URL should be removed
• #%s915549: Task table is missing a unique constraint on ‘name’ field
• #%s915695: NoSuchElementException is raised for some Selenium tests occasionally
• #%s917745: Internal error (500) when adding system to a group twice
• #%s917933: Users can delete jobs not owned by themselves
• #%s920433: createrepo output is not captured
• #%s922721: Notify CC list should be visible to non-admins

The following bugs were fixed in Beaker 0.12.1:

• #%s889065: Scheduling deadlock for multihost tests
• #%s950922: Upgrade instructions for 0.12 may lead to a long outage
• #%s951283: Role environment variables have duplicate FQDNs if recipe role and task role are the same
• #%s951309: beaker-provision sometimes runs commands twice
• #%s951981: Cannot import naked distro tree
• #%s952948: CLIENTS role in a guest recipe halts /distribution/install task of host recipe