[skip-ci] Packit: enable c10s downstream sync

[lsm5]

This commit will enable downstream syncing to CentOS Stream 10. The centos maintainer will need to manually run packit propose-downstream and centpkg build until better centos integration is in place.

This commit also builds both rhel9 and centos9 copr rpms so we can check for things like differences in golang compiler.

What type of PR is this?

/kind other

What this PR does / why we need it:

enables downstream syncing to c10s

How to verify it

can't be verified pre-merge. After a release is cut, the centos maintainer will run packit propose downstream -p buildah-centos to trigger a centos merge request.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [lsm5]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[packit-as-a-service]

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

[packit-as-a-service]

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

[lsm5]

@nalind @rhatdan PTAL. the centos stream jobs are failing on HashSign but the change itself should be good to go.

[lsm5]

@nalind @TomSweeneyRedHat PTAL .

[TomSweeneyRedHat]

All kinds of red test unhappiness @lsm5

[lsm5]

All kinds of red test unhappiness @lsm5

Yes, those are expected because of the undefined: ecdsa.HashSign FIPS issue that's being worked on. Having both RHEL (EPEL targets) and CentOS Stream testing would mean some tests would fail at times depending on golang compiler / toolchain differences. This is actually a good thing IMHO as it provides early warnings of upcoming RHEL issues.

On the flip side, if centos stream tests pass and epel tests fail, then it's safe to say the RHEL tests will pass after sometime.

I will check with packit team if it's possible to hide / waive such tests if one includes a github comment like slash-packit ignore-foo-test

[lsm5]

This is failing on c9s because the golang update to restore the HashSign and HashVerify symbols hasn't landed in buildroot yet. The change itself should be good to go

@nalind @rhatdan @TomSweeneyRedHat PTAL

[nalind]

/lgtm

[lsm5]

/cherrypick release-1.36

[openshift-cherrypick-robot]

@lsm5: new pull request created: #5561

In response to this:

/cherrypick release-1.36

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[nalind]

This is failing on c9s because the golang update to restore the HashSign and HashVerify symbols hasn't landed in buildroot yet. The change itself should be good to go

Do we have any expectations around when golang-1.22.3-2.el9 will be showing up there?

[lsm5]

This is failing on c9s because the golang update to restore the HashSign and HashVerify symbols hasn't landed in buildroot yet. The change itself should be good to go

Do we have any expectations around when golang-1.22.3-2.el9 will be showing up there?

@nalind i'm told whenever the next compose goes out. Hard to tell the exact date I guess.