Comments

9 Comments

Hi @adamwill,

how to re-trigger tests?

Selinux policy was updated so tests should be green now.

looks like SELinux policy update has been queued. Didn't check whether it includes a fix for sssd.

It does contain fix for SSSD. We'll re-push the build once selinux policy update in the compose.

Maybe the config file had 0600 before and is now 0640, which upsets the previous version.

Right: https://github.com/SSSD/sssd/commit/8472777ec472607ea450ddb4c4666017bd0de704

Some looks like infra failure?

(12:36:28): [be_resolve_server_process] (0x0200): Found address for server ipa001.test.openqa.fedoraproject.org: [172.16.2.100] TTL 1109
(12:36:28): [sssd_async_socket_init_send] (0x4000): Using file descriptor [22] for the connection.
(12:36:28): [sssd_async_socket_init_send] (0x0400): Setting 6 seconds timeout [ldap_network_timeout] for connecting
(12:36:34): [sssd_async_connect_timeout] (0x0100): The connection timed out [ldap_network_timeout]
(12:36:34): [sssd_async_socket_init_done] (0x0040): sdap_async_sys_connect request failed: [110]: Connection timed out [ldap_network_timeout].

I'm not familiar with those tests, but clicking around:

(2024-12-10 11:35:37): [be[test.openqa.fedoraproject.org]] [selinux_child_done] (0x0020): [RID#8] Error in selinux_child: [1][Operation not permitted]

at least some of those tests are due to https://github.com/fedora-selinux/selinux-policy/issues/2455