Use AES Ceph cipher for CentOS-9 HCI scenario - #4144
Conversation
Update scenarios/centos-9/hci_ceph_backends.yml so that jobs which depend on that file use the Ceph old AES cipher and not the new AES256k cipher. Co-authored-by: Roberto Alfieri <ralfieri@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com> Signed-off-by: John Fulton <fulton@redhat.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
fmount
left a comment
There was a problem hiding this comment.
I'm ok with this change because I think we are not going to rebuild Antelope clients to include a new ceph-common (if available) from centos storage sig. iirc Antelope goes with squid clients, and we need backports for it before switching to the new defaults, so this makes sense to me.
I was under impression that this was already covered by #4130, but I might be wrong and I might need to investigate more.
Being that said, the change of this patch makes sense and /lgtm
I changed those values as well but it's not important. I'm fine with the gradual approach. lgtm from me as well. |
|
/lgtm |
|
/approve |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fmount, Valkyrie00 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
50f35b6
into
openstack-k8s-operators:main
Update scenarios/centos-9/hci_ceph_backends.yml so that jobs which depend on that file use the Ceph old AES cipher and not the new AES256k cipher.