@vkadlcik There is a button here in Bodhi that people can use to restart tests. [citest] does nothing in Bodhi. Or you can use Bodhi CLI to re-trigger tests.

Do you have more info about the crash please?

It seems like there is a problem with this update (?)

 Problem 2: package python3-wtforms-sqlalchemy-0.3.0-7.fc40.noarch from updates-testing requires (python3.12dist(sqlalchemy) < 2~~ with python3.12dist(sqlalchemy) >= 0.7.10), but none of the providers can be installed
  - package python3-sqlalchemy1.3-1.3.24-11.fc40.x86_64 from fedora conflicts with python3-sqlalchemy provided by python3-sqlalchemy-2.0.28-1.fc40.x86_64 from @System
  - package python3-sqlalchemy1.4-1.4.51-1.fc40.x86_64 from fedora conflicts with python3-sqlalchemy >= 2 provided by python3-sqlalchemy-2.0.28-1.fc40.x86_64 from @System
  - package python3-sqlalchemy1.4-1.4.52-1.fc40.x86_64 from updates-testing conflicts with python3-sqlalchemy >= 2 provided by python3-sqlalchemy-2.0.28-1.fc40.x86_64 from @System
  - cannot install the best update candidate for package python3-wtforms-sqlalchemy-0.3.0-6.fc40.noarch
  - cannot install the best update candidate for package python3-sqlalchemy-2.0.28-1.fc40.x86_64

Just to close the loop here -- I reported the issue with selinux and OSB images to the owners of the Fedora Image Builder change: https://fedoraproject.org/wiki/Changes/FedoraWorkstationImageBuilder

So they are aware of the issue and they will look into it ;)

Thanks for the thorough explanation.

So, when it comes to selinux being in permissive mode by default, I tried again just now -- just to make sure that I wasn't dreaming. I don't know if this is expected or not, but these are my findings:

Fedora-Workstation-Live-osb-Rawhide-20240206.n.0.x86_64.iso -- this has the selinux policy set to permissive right after installation. I was doing the testing on this "osb" version, so maybe that's where I made the mistake?

Fedora-Workstation-Live-x86_64-Rawhide-20240206.n.0.iso -- this one indeed comes with selinux enforcing enabled by default.

Oh, wait. My freshly installed Rawhide VM is running in permissive mode by default? That's why I didn't see the problem...

For the record, this is the test bug that I successfully created from the Rawhide VM: https://bugzilla.redhat.com/show_bug.cgi?id=2263025

Hmm, I cannot reproduce the problem on a freshly installed up-to-date Rawhide VM.

This is interesting:

-   "ADVISORY" : "FEDORA-2024-617d585f1f",
-   "ADVISORY_NVRS_1" : "selinux-policy-40.11-1.fc40",
-   "ADVISORY_OR_TASK" : "FEDORA-2024-617d585f1f",
+   "ADVISORY" : "FEDORA-2024-82aa4e575f",
+   "ADVISORY_NVRS_1" : "abrt-2.17.2-1.fc40 libreport-2.17.13-1.fc40 satyr-0.43-1.fc40",
+   "ADVISORY_OR_TASK" : "FEDORA-2024-82aa4e575f",
-   "BUILD" : "Update-FEDORA-2024-617d585f1f",
+   "BUILD" : "Update-FEDORA-2024-82aa4e575f",

It seems like the new selinux-policy landed at the same time and was tested together with this update? I will try to re-push the update. The worst case scenario is that CI will keep the update blocked.

Yep, I noticed that too. That's why I quickly unpushed the update. I did not see the problem locally though, so I need to investigate more.

This update has been unpushed.

The update fixes the "KeyError: console_scripts" problem.

With python3-argcomplete-2.0.0-11.fc39:

$ /usr/bin/python3 -m argcomplete._check_console_script /usr/bin/podman-compose

...

KeyError: 'console_scripts'

With the new python-argcomplete-2.0.0-12.fc39:

$ /usr/bin/python3 -m argcomplete._check_console_script /usr/bin/podman-compose

does not appear to be a console script

fatal: RPC failed at server.  The API key you specified has been revoked by the user that created it.

Please make sure that you have a valid API key. You can generate one in https://bugzilla.redhat.com/userprefs.cgi?tab=apikey

Then in gnome-abrt, click Preferences->Events tab->Bugzilla and paste the API key there. The API key is a string that is ~40 characters long.

Thank you both for such a quick feedback ;)

New centpkg is broken as it needs the new rpkg. But the problem will be fixed once this update reaches stable: https://issues.redhat.com/browse/CS-1230

Tested:

$ cd /var/spool/abrt/Python3-2022-02-21-03:58:35-226040

$ reporter-bugzilla .

This problem was already reported to Bugzilla (see 'https://bugzilla.redhat.com/show_bug.cgi?id=2063399'). Do you still want to create a new bug? [y/N] y Checking for duplicates Creating a new bug New bug id: 2063401 Adding attachments to bug 2063401 Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=2063401

$ rpm -qf /usr/bin/reporter-bugzilla

libreport-plugin-bugzilla-2.15.2-8.fc35.x86_64