Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stabilization: Add a Playbook name to Ansible Playbooks #10712

Conversation

jan-cerny
Copy link
Collaborator

Description:

In the stabilization GitHub Action CI runs all the tests ansible-playbook-per-profile-ansible-lint-check-.* fail due to a missing name. This can be easily fixed by assigning a name to all the playbooks.

Addressing:
name[play]: All plays should be named.

Rationale:

docs/release_process.md says:

There is a GitHub Action hooked up with stabilization-vX.Y.Z branch that will run a set of
tests on every push.
Make sure that all these tests are passing before moving on with the release process.

Review Hints:

review the results of ansible-playbook-per-profile-ansible-lint-check CTest tests

@jan-cerny jan-cerny added BLOCKER Impediments to release, like failure to build content, or content built is out of standard's syntax Ansible Ansible remediation update. labels Jun 14, 2023
@github-actions
Copy link

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment
Open in Gitpod

Oracle Linux 8 Environment
Open in Gitpod

@jan-cerny jan-cerny changed the title Add a Playbook name to Ansible Playbooks Stabilization: Add a Playbook name to Ansible Playbooks Jun 14, 2023
In the stabilization GitHub Action CI runs all the tests
ansible-playbook-per-profile-ansible-lint-check-.*
fail due to a missing name. This can be easily fixed by
assigning a name to all the playbooks.

Addressing:
name[play]: All plays should be named.
@jan-cerny
Copy link
Collaborator Author

The CI fail on CS 9 looks unrelated:

fatal: [localhost]: FAILED! => {"changed": false, "failures": [], "msg": "Depsolve Error occurred: \n Problem: package qemu-guest-agent-17:8.0.0-4.el9.x86_64 from @System requires liburing.so.1()(64bit), but none of the providers can be installed\n - package qemu-guest-agent-17:8.0.0-4.el9.x86_64 from @System requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed\n - cannot install both liburing-2.3-2.el9.x86_64 from testing-farm-tag-repository and liburing-0.7-7.el9.x86_64 from @System\n - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.3-2.el9.x86_64 from testing-farm-tag-repository\n - cannot install the best update candidate for package qemu-guest-agent-17:8.0.0-4.el9.x86_64\n - cannot install the best update candidate for package liburing-0.7-7.el9.x86_64", "rc": 1, "results": []}

@Mab879 Mab879 self-assigned this Jun 14, 2023
@Mab879 Mab879 added this to the 0.1.68 milestone Jun 14, 2023
@Mab879
Copy link
Member

Mab879 commented Jun 14, 2023

Waving CentOS Stream 9 tests as that error is unrelated.

@Mab879 Mab879 merged commit 513280d into ComplianceAsCode:stabilization-v0.1.68 Jun 14, 2023
25 of 26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ansible Ansible remediation update. BLOCKER Impediments to release, like failure to build content, or content built is out of standard's syntax
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants