Skip to content

Sync caracal antelope #1235

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

Merged
merged 37 commits into from
Aug 20, 2024
Merged

Sync caracal antelope #1235

merged 37 commits into from
Aug 20, 2024

Conversation

Alex-Welsh
Copy link
Member

No description provided.

markgoddard and others added 30 commits July 23, 2024 09:03
A similar change was made for Ubuntu systems in #1119, but it did not
apply to Rocky 9 systems. This changes brings the two into line.

(cherry picked from commit ef96aa2)
These are causing changes to docker overlay filesystems with
possible unintended consequences. It is also really slow to loop
through so many files in ansible.

(cherry picked from commit 0d1dfe2)
By default the 'Run tempest' task has no_log set to avoid revealing
sensitive data. This does not apply in CI, and makes it difficult to
debug failures.

(cherry picked from commit 8384dc4)
CI: Allow logging of Rally/Tempest
Fixes CVE-2024-40767 [1] with updated container images for Nova
services.

[1] https://security.openstack.org/ossa/OSSA-2024-002.html
CI: Bump AIO root volume size to 40GB
This is necessary to address OSSA-2024-002 [1] until patches are merged
upstream.

[1] https://security.openstack.org/ossa/OSSA-2024-002.html
molly-guard can be used to prevent accidental reboots, prompting the
user to input the system's hostname before allowing a reboot. This does
not work well with automation, however.

This change adds the internal reboot executable within molly-guard to
the search path to avoid this issue.
yoga: Fix reboot hang on systems with molly-guard, add timeout variable
These can be used to enter and exit maintenance for Ceph hosts.
yoga: Stop changing permissions on files in CIS
If we have the CIS hardening hook enabled and run a command such as the
following:

  kayobe overcloud host configure -t foo

where 'cis' is not in the specified tags, we see the following error:

  PLAY [Security hardening] *****************************************
  TASK [include_role : ansible-lockdown.rhel9_cis] ******************
  fatal: [controller-01]: FAILED! =>
    msg: |-
      The conditional check 'ansible_facts.os_family == 'RedHat' and
      ansible_facts.distribution_major_version == '9'' failed. The error
      was: error while evaluating conditional (ansible_facts.os_family
      == 'RedHat' and ansible_facts.distribution_major_version == '9'):
      'dict object' has no attribute 'os_family'. 'dict object' has no
      attribute 'os_family'

      The error appears to be in 'etc/kayobe/ansible/cis.yml': line 35,
      column 7, but may be elsewhere in the file depending on the exact
      syntax problem.

      The offending line appears to be:

          - include_role:
            ^ here

This is because the include_role task has the 'always' tag, so runs
despite no facts having been gathered.

The always tag is not required for this task - specifying the 'cis' tag
causes the role to be included. This change fixes the issue by removing
the always tags from these tasks.
Defining set of special characters to omit "`" and "'" which leads to issues
More description: #1226
CIS: Remove always tag from include_role tasks
Allow reboot playbook to run with bootstrap user
@Alex-Welsh Alex-Welsh requested a review from a team as a code owner August 20, 2024 13:43
@Alex-Welsh Alex-Welsh force-pushed the sync-caracal-antelope branch 2 times, most recently from 679edee to fa2995e Compare August 20, 2024 13:47
@markgoddard markgoddard merged commit 01f7e23 into stackhpc/2024.1 Aug 20, 2024
4 of 12 checks passed
@markgoddard markgoddard deleted the sync-caracal-antelope branch August 20, 2024 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants