Fix test_rgw_kafka_notifications#13688
Conversation
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
|
/cherry-pick release-4.19 |
|
@sagihirshfeld: 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. |
|
/cherry-pick release-4.18 |
|
@sagihirshfeld: 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. |
|
/cherry-pick release-4.17 |
|
@sagihirshfeld: 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. |
ocs-ci
left a comment
There was a problem hiding this comment.
PR validation on existing cluster
Cluster Name: shirshfe-20vs11
Cluster Configuration: conf/deployment/vsphere/ipi_1az_rhcos_vsan_3m_3w.yaml
PR Test Suite:
PR Test Path: tests/functional/workloads/app/amq/test_rgw_kafka_notifications.py::TestRGWAndKafkaNotifications::test_rgw_kafka_notifications
Additional Test Params: --skip-rpm-go-version-collection
OCP VERSION: 4.20
OCS VERSION: 4.20
tested against branch: master
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: PrasadDesala, sagihirshfeld, vkathole The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@sagihirshfeld: #13688 failed to apply on top of branch "release-4.17": 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. |
|
@sagihirshfeld: #13688 failed to apply on top of branch "release-4.19": 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. |
|
@sagihirshfeld: #13688 failed to apply on top of branch "release-4.18": 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. |
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Signed-off-by: Sagi Hirshfeld <shirshfe@redhat.com>
Changes made
Use a custom fork of the notify tool, where we drop the forced use of the old S3 signature. See my PR at the notify repo for details.
The use of Zookeeper in the setup is deprecated, and was updated elsewhere in Update AMQ Kafka deployment to latest Strimzi (KRaft, no ZooKeeper) #12966. This PR also updates the relevant part in
test_rgw_kafka_notifications.Make sure we run with a uniqe (random) topic name each run. This is mainly for quality of life when running multiple times locally for debugging.
Fixes: #13527