Restraint 0.4.5

What's Changed

• Enable Fedora38 in checks, COPR Builds, container scripts by @cbouchar in #298
• Drop Fedora36/Add Fedora39 to release file by @cbouchar in #299
• point new Rawhide to Fedora 40 by @lulinqing in #304
• Extend task_fetch retries by @lulinqing in #293
• Fixes for broken builds by @StykMartin in #308
• Add support for CentOS Stream containers by @danrodrig in #311
• Fixes for valgrind and rawhide static builds by @danrodrig in #315
• Update GitHub Actions and Packit to run against the latest distributions available by @StykMartin in #318
• Release Notes 0.4.5 by @StykMartin in #319

New Contributors

• @lulinqing made their first contribution in #304

Full Changelog: restraint-0.4.4...restraint-0.4.5

Restraint 0.4.0

restraint-0.4.0

Tagging package [restraint] version [restraint-0.4.0] in directory [./].

Restraint 0.3.3

restraint-0.3.3

Tagging package [restraint] version [restraint-0.3.3] in directory [./].

Restraint 0.3.2

restraint-0.3.2

Tagging package [restraint] version [restraint-0.3.2] in directory [./].

Restraint 0.3.0

restraint-0.3.0

Tagging package [restraint] version [restraint-0.3.0] in directory [./].

Restraint 0.2.3

restraint-0.2.3

Tagging package [restraint] version [restraint-0.2.3] in directory [./].

Restraint 0.2.2

restraint-0.2.2

Tagging package [restraint] version [restraint-0.2.2] in directory [./].

Restraint 0.2.1

What’s New

• Add ability to select restraintd instance by port to restraint commands.
  When running commands outside of jobs on the local host, some restraint commands require manually setting up environment variables or constructing long URLs before running. This can be issue if you are trying to extend the watchdog in a timely fashion. A new option was added which requires the argument –port . Commands affected are rstrnt-report-log, rstrnt-report-result, rstrnt-abort, and rstrnt-watchdog.
• Restore ability to specify restraintd port
  Add the -p, –port option back to Restraint daemon and client to specify the port where restraind will be listening to.
• Document how to remove RHTS from Jobs
  Added new section Guide to removing RHTS from Jobs detailing substitutes for RHTS scripts, environment variables, and testinfo.desc file and associated variables.

Bug Fixes

• Redirect task STDIN back to /dev/null
  In release 0.2.0, the task STDIN was redirected to a pipe shared with the server. This breaks ausearch command when the input is not explicitly specified, as by default, if STDIN is a pipe, it will read from it, instead of system logs. As the pipe is closed when the task is running, tests expecting matches failed, and tests expecting no matches were unreliable. Restoring redirect of task STDIN back to /dev/null ensures that ausearch reads from system logs by default.
• Restore default port for restraind system service
  In release 0.2.0 the port for restraintd system service is chosen dynamically, breaking workflows where the port was expected to persist between reboots. When restraintd runs as a system service, the port defaults to 8081.
• Restraintd killed by SIGTRAP
  It was discovered that an error logging function (g_error) introduced in 0.2.0 also performed aborts. The function was replaced with one which logs without undesirable side effects.
• Restraintd fails to start if both, IPv4 and IPv6, are not available on the loopback interface
  In this release, restraintd will not fail if it’s able to listen on at least one protocol, IPv4 or IPv6, although it will still try to listen on both.
• Fix use of uninitialized FD for STDIN when PTY is requested
  When PTY was requested, the FD for the task STDIN was left uninitialized. The value, set to 0, was still used in a close call, closing the parent STDIN FD and causing unexpected behavior in task execution. In this release, the FD for STDIN is not used when PTY is requested.

Restraint 0.2.0

Upgrades:

• Removed libssh from restraint-client. If using the restraint-client, refer to restraint documentation for changes to executing the client as ports to server are no longer static. --port option can not be used anymore, nor restraint-client doesn't need port when it is trying to connect to restraintd.
• Replaced rhts-sync-* with rstrnt-sync-* cmds. This changeset creates rstrnt-sync- commands and links rhts-sync-* commands to it. The multihost plugin now uses rstrnt-sync- commands.
• Upgraded libxml2 to version 2.9.10.

Bug Fixes:

• Removed execute permission from systemd service file. There is a warning message in the systemd logs about the file being executable.

Restraint 0.1.45

• FIXED: RHBZ#1795781: Multihost sync hangs on remote reboot. Users multihost synchronization task hangs on block operation when remote host reboots. This is a corner case difficult to reproduce.
  (Contributed by Carol Bouchard)
• FIXED: RHBZ#1792466: Restraint segfault during labcontroller timeout. On error when gathering peer roles from the lab controller, a double free of the error structure causes bad behavior in glib memory management. Eventually this causes restraint server to crash on a segfault.
  (Contributed by Carol Bouchard)
• FIXED: RHBZ#1691485: Rstrnt Client not provide task vers in job.xml. This change affects rpm tasks only. Restraint server gets the version number from the rpm and returns it in ‘Completed/Aborted’ status message sent to restraint client. The restraint client writes it out in the job.xml.
  (Contributed by Carol Bouchard)
• FIXED: RHBZ#1793114: Wrong file permission on 30_dmesg_clear plugin. The new 30_dmesg_clear plugin does not have execute file permission. However, other scripts add execution permission so it is correct in the rpm. This is being fixed in repo to prevent chasing it as an issue.
  (Contributed by Carol Bouchard)