Packit: remove el8 and add centos stream 10

[lsm5]

EL8 will go EOL soon and centos stream 10 is now available in copr.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed on RHEL. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[packit-as-a-service[bot]]

Ephemeral COPR build failed. @containers/packit-build please check.

[lsm5]

@rhatdan the latest tag pushed was 2.231.0 but we need v2.231.0. Could you please push this tag as well? Also need the github release created to get packit builds going.

[packit-as-a-service[bot]]

podman system tests failed. @containers/packit-build please check.

[lsm5]

@edsantiago PTAL at centos-stream-10 failures

[edsantiago]

Looking at one of those I see red:

Errors during downloading metadata for repository 'baseos':
  - Curl error (28): Timeout was reached for https://odcs.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/x86_64/os/repodata/repomd.xml [Failed to connect to odcs.stream.centos.org port 443 after 30001 ms: Timeout was reached]
  - Curl error (28): Timeout was reached for https://odcs.stream.centos.org/stream-10/production/latest-CentOS-Stream/compose/BaseOS/x86_64/os/repodata/repomd.xml [Failed to connect to odcs.stream.centos.org port 443 after 30000 ms: Timeout was reached]
Error: Failed to download metadata for repo 'baseos': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

...which doesn't look like anything related to anything on our end. Is there a re-run button for these?

[packit-as-a-service[bot]]

podman e2e tests failed. @containers/packit-build please check.

[lsm5]

Is there a re-run button for these?

@edsantiago Yes, click Details to see the re-run button against the test. Anyway, I reran it and that flake has gone away, now there are some real failures.

[edsantiago]

Flakes galore:

  Error: initializing source docker://registry.fedoraproject.org/fedora-toolbox:36: \
     pinging container registry registry.fedoraproject.org: \
     Get "https://registry.fedoraproject.org/v2/": \
     dial tcp: lookup registry.fedoraproject.org: Temporary failure in name resolution

[lsm5]

Flakes galore:

  Error: initializing source docker://registry.fedoraproject.org/fedora-toolbox:36: \
     pinging container registry registry.fedoraproject.org: \
     Get "https://registry.fedoraproject.org/v2/": \
     dial tcp: lookup registry.fedoraproject.org: Temporary failure in name resolution

ugh, rerunning

[edsantiago]

Oooh, the system test looks unpleasant:

# [14:48:00.647461654] Error: netavark: unable to append rule '! -d 224.0.0.0/4 -j MASQUERADE' to table 'nat': code: 4, msg: Warning: Extension MASQUERADE revision 0 not supported, missing kernel module?
# iptables v1.8.10 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain NETAVARK-1D8721804F16F

@Luap99 does that look familiar?

[Luap99]

Oooh, the system test looks unpleasant:

# [14:48:00.647461654] Error: netavark: unable to append rule '! -d 224.0.0.0/4 -j MASQUERADE' to table 'nat': code: 4, msg: Warning: Extension MASQUERADE revision 0 not supported, missing kernel module?
# iptables v1.8.10 (nf_tables):  RULE_APPEND failed (No such file or directory): rule in chain NETAVARK-1D8721804F16F

@Luap99 does that look familiar?

yes, I am on my other PC now but there is Jira issue. Basically RHEL 10 dropped support for iptables so we have to default to nftables there in netavark, work is still TODO.

[lsm5]

yes, I am on my other PC now but there is Jira issue. Basically RHEL 10 dropped support for iptables so we have to default to nftables there in netavark, work is still TODO.

@Luap99 thanks, I'll leave the centos-stream-10 tests commented out for now in that case.

[lsm5]

@rhatdan PTAL

[rhatdan]

LGTM thanks @lsm5