Enable bootstrap container for CentOS Stream 10

[carlwgeorge]

Since CentOS Stream 10 hasn't been released yet, the container image exists but is using the tag stream10-development instead of stream10. At some point (probably the release announcement) it will start using the stream10 tag. This image is "ready" (i.e. dnf builddep is pre-installed).

cc: @tdawson

[packit-as-a-service]

We were not able to find or create Copr project packit/rpm-software-management-mock-1451 specified in the config with the following error:

Packit received HTTP 500 Internal Server Error from Copr Service. Check the Copr status page: https://copr.fedorainfracloud.org/status/stats/, or ask for help in Fedora Build System matrix channel: https://matrix.to/#/#buildsys:fedoraproject.org.

---

Unless the HTTP status code above is >= 500, please check your configuration for:

1. typos in owner and project name (groups need to be prefixed with @)
2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
3. whether the project itself exists (Packit creates projects only in its own namespace)
4. whether Packit is allowed to build in your Copr project
5. whether your Copr project/group is not private

[praiskup]

Nice! Thank you. Can you mark #1442 Fixed in the commit message?

[carlwgeorge]

Of course, amended the commit.

[praiskup]

Two more things preferably in the same commit... would you please remove the temporary hack from behave config:

diff --git a/behave/features/isolated-build.feature b/behave/features/isolated-build.feature
index ffd623f5..ae22eb9a 100644
--- a/behave/features/isolated-build.feature
+++ b/behave/features/isolated-build.feature
@@ -12,9 +12,6 @@ Feature: Mock 5.7+ supports isolated builds
     @isolated_build
     Scenario: Isolated build against a DNF4 distribution
         Given an unique mock namespace
-        # Temporary image, until we resolve https://issues.redhat.com/browse/CS-2506
-        And next mock call uses --config-opts=bootstrap_image=quay.io/mock/behave-testing-c9s-bootstrap option
-        And next mock call uses --config-opts=bootstrap_image_ready=True option
         When deps for mock-test-bump-version-1-0.src.rpm are calculated against centos-stream+epel-9-x86_64
         And a local repository is created from lockfile
         And an isolated build is retriggered with the lockfile and repository

And provide a release note snippet? (towncrier create c10s-bootstrap-ready.config)

[praiskup]

These are small things, let me know if you prefer me to do that in a separate commit...

[praiskup]

Oh, taking back ... that is not a c10s test-case! And actually, the issue #1442 is related to CentOS Stream 8+, not just 10 - we we are not fixing the issue right now.

Can you please keep the issue open, i.e., s/Fixes/Relates/, keep the test-case as-is, but provide the release notes snippet?

[carlwgeorge]

No problem at all, if it makes sense in the same commit then that's how we should do it. I've amended again with those adjustments, let me know if there are any other tweaks needed.

[praiskup]

PASSED: centos-stream+epel-10-x86_64.cfg (tmpfs)
PASSED: centos-stream+epel-10-x86_64.cfg

[praiskup]

LGTM