Automatic update for pykickstart-3.44-1.fc38.
* Wed Feb 15 2023 Brian C. Lane <bcl@redhat.com> - 3.44-1
- Add DNS handling options to the network command (vslavik)
Related: rhbz#1656662
- Fix the coverage report (vponcova)
- whitelist_externals has changed to allowlist_externals (bcl)
- Update %post example for DNS problems (bcl)
- deps: Move dependencies into requirements.txt (bcl)
- Fix syntax of a code sample (ewoud)
* Mon Jan 30 2023 Brian C. Lane <bcl@redhat.com> - 3.43-3
- SPDX migration
Please login to add feedback.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
the test failures here unfortunately always happen with pykickstart updates, because we do messy things with the pykickstart package as part of those tests (it just happened to get chosen as the sacrificial package). I need to figure out a workaround. I've waived the failures.
I'm no expert on this thing, but the one remaining test failure seems to be an unrelated infra problem. The jenkins log has this:
ERROR: Artemis API call failed: Condition 'api_call' failed to pass within given time
...and the Testing Farm logs show an ansible playbook ending with error SSHing into the host after a bunch of operations.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'waiting'.
This update has been obsoleted by pykickstart-3.46-1.fc38.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'passed'.