Release 1.32.2

[lukaszachy]

Release checklist

• [x] Create a pull request with the commit, ensure tests pass, merge it

Release a new package to Fedora and EPEL repositories:

• [x] Move the fedora branch to point to the new release
• [x] Tag the commit with x.y.0, push tags git push --tags
• [x] Create a new github release__ based on the tag above
• [x] Check Fedora pull requests__, make sure tests pass and merge

Finally, if everything went well:

• [x] Close the corresponding release milestone
• [x] Once the non development copr build__ is completed, move the quay branch to point to the release commit as well to build fresh container images.

[lukaszachy]

and once again with proper quotes in docs/releases.rst

[lukaszachy]

/packit test --identifier full

[lukaszachy]

/packit test --identifier extended-unit-tests

[lukaszachy]

/packit test --identifier provision

[lukaszachy]

/packit test --identifier internal-wow

[lukaszachy]

/packit test --identifier internal-plugins

[lukaszachy]

Test failures:

/tests/run/permissions

My fault, should have wait on full testsuite as this test asserts rpm ownership :: [ 16:15:52 ] :: [ FAIL ] :: Owned by tmt (Assert: 'file /var/tmp/tmt is not owned by any package' should equal 'tmt')

I'll fix the test.

/tests/discover/distgit

Failed to clone test repo.

:: [ 16:02:01 ] :: [  BEGIN   ] :: Running 'git clone https://src.fedoraproject.org/rpms/tmt.git /tmp/tmp.3xHGZ99yan/tmt'
Cloning into '/tmp/tmp.3xHGZ99yan/tmt'...
error: RPC failed; curl 55 Failed sending data to the peer
fatal: the remote end hung up unexpectedly

Let's ignore, at least one other job passed for this test.

/tests/test/check/avc

Just on rawhide but second time in row.

@happz could you take a look? Should I create new issue? https://artifacts.dev.testing-farm.io/79667362-e80d-4054-9ec1-cf63e37959f3/work-local2hn7yq3y/plans/provision/local/execute/data/guest/default-0/tests/test/check/avc-8/output.txt

[happz]

/tests/test/check/avc

Just on rawhide but second time in row.

@happz could you take a look? Should I create new issue? https://artifacts.dev.testing-farm.io/79667362-e80d-4054-9ec1-cf63e37959f3/work-local2hn7yq3y/plans/provision/local/execute/data/guest/default-0/tests/test/check/avc-8/output.txt

I will look into it. No need for an issues, we will see this one pop up everywhere, no chance we might forget about it...

[lukaszachy]

Test failures in last round:

/tests/prepare/multihost

Third Guest VM didn't boot in time: Failed to connect in 300s. - Just a single job (f-39)

/tests/test/check/avc

On Rawhide

I believe we are OK to go.