Add ec2authtoken credentials to default.conf#625
Add ec2authtoken credentials to default.conf#625openshift-merge-bot[bot] merged 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
|
This won't work without the tests being fixed to use HEAT_SIGNAL. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c94b1625a01d451a8967947792170091 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 11s |
After OSSA-2025-002, Keystone's ec2tokens API requires authentication. This breaks CFN_SIGNAL-based software deployment signaling since the [ec2authtoken] section lacks the required auth credentials. Add authentication credentials to the [ec2authtoken] section so that ec2tokens API calls are properly authenticated, fixing CFN_SIGNAL-based signaling. jira: OSPCIX-1214 Change-Id: I63a05c2a08d68d5346c5edd0cbe90662bd4c2ca5 Signed-off-by: rabi <ramishra@redhat.com>
|
/test functional |
|
/cherry-pick 18.0-fr5 |
|
@rabi: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
karelyatin
left a comment
There was a problem hiding this comment.
/lgtm
matches to config what worked locally last i tested this issue
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abays, karelyatin, rabi 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 |
771b160
into
openstack-k8s-operators:main
|
@rabi: new pull request created: #626 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
After OSSA-2025-002, Keystone's ec2tokens API requires authentication. This breaks CFN_SIGNAL-based software deployment signaling since the [ec2authtoken] section lacks the required auth credentials.
Add authentication credentials to the [ec2authtoken] section so that ec2tokens API calls are properly authenticated, fixing CFN_SIGNAL-based signaling.
jira: OSPCIX-1214