Chores: bump up f8 dep #3553
Chores: bump up f8 dep #3553
Conversation
|
@strimzi-ci run tests |
|
/azp run acceptance |
|
Commenter does not have sufficient privileges for PR 3553 in repo strimzi/strimzi-kafka-operator |
|
/azp run regression |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Regarding the regression failures: |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
|
/azp run acceptance |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@strimzi-ci run tests |
|
/azp run regression |
|
Azure Pipelines successfully started running 1 pipeline(s). |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
sknot-rh
force-pushed
the
f8-4.11.x
branch
4 times, most recently
from
b274655 to
bc3b006
Compare
|
@strimzi-ci run tests |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
|
@strimzi-ci run tests |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
|
@strimzi-ci run tests false profile=acceptance testcase=io.strimzi.systemtest.kafka.ListenersST#testCustomSoloCertificatesForRoute,io.strimzi.systemtest.connect.ConnectS2IST#testKafkaConnectorWithConnectS2IAndConnectWithSameName |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
|
@strimzi-ci run tests false profile=acceptance testcase=io.strimzi.systemtest.kafka.ListenersST#testCustomSoloCertificatesForRoute,io.strimzi.systemtest.connect.ConnectS2IST#testKafkaConnectorWithConnectS2IAndConnectWithSameName |
❌ Test Summary ❌TEST_PROFILE: acceptance ❗ Test Failures ❗
Re-run command: |
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
…to /oapi URLs This commit reverts 293ab9d which was added in order to fix fabric8io#2373. This behavior was causing problems with Strimzi's Kubernetes Client upgrade: strimzi/strimzi-kafka-operator#3553 . On bisecting the failing test, I found this commit as culprit. Handling OpenShift old /oapi requests seem to be handled in OpenShiftOperation where we check `config.isOpenshiftApiGroupsEnabled()` to modify OperationContext. However, fabric8io#2373 can be fixed by adding apiVersion in OpenShiftOperation.
|
@strimzi-ci run tests |
|
/azp run regression |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi guys, How much time do these tests usually take to complete? I see two workflows are already failing 😰 . Are these related to fabric8? |
|
AFAIK these tests are not related to f8 but to Azure environment. @Frawless ^ |
✔️ Test Summary ✔️TEST_PROFILE: acceptance ❗ Test Failures ❗
|
|
@stanlyDoge Yeah, the host alias tests should be fixed in #3737 |
|
@strimzi/maintainers The test look good and the code to me as well. Could you please review so that we can move forward with this and merge it? |
Signed-off-by: Stanislav Knot sknot@redhat.com
Type of change
Description
Upgrade fabric8 dependency 4.10.x -> 4.11.x
Checklist