-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ST] Fixups for few failing tests in nightlies #9801
Conversation
…ing creation of default NP for some tests Signed-off-by: Lukas Kral <[email protected]>
Signed-off-by: Lukas Kral <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for fix. Works for me ✅
@strimzi-ci run tests --cluster-type=ocp --cluster-version=4.14 --install-type=bundle --profile=all --groups=route,bridge,networkpolicies |
|
Signed-off-by: Lukas Kral <[email protected]>
@strimzi-ci run tests --cluster-type=ocp --cluster-version=4.14 --install-type=bundle --profile=all --groups=route,bridge,networkpolicies |
|
/azp run regression |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run upgrade |
Azure Pipelines successfully started running 1 pipeline(s). |
✔️ Test Summary ✔️TEST_PROFILE: all |
/azp run kraft-regression |
Azure Pipelines successfully started running 1 pipeline(s). |
Type of change
Description
This PR fixes few failing tests in our nightlies, mainly for OCP:
route
as a listener types are sometimes failing on the length of the hostname - that is hit because of long name of the NodePools. I changed it frombroker-
,control-
, andmixed-
prefixes tob-
,c-
,m-
prefixes. In case that it will not be that readable, we can try different prefix and possibly shorter the suffix as well.my-cluster-
prefix tocluster-
ROUTE
tag to one test missing this tagSkipDefaultNetworkPolicyCreation
for tests that need skip of creation of the default NetworkPolicies -> for example testtestNPGenerationEnvironmentVariable
turns off creation of NetworkPolicies in CO -> and because the "default to deny" global network policy we would not be able to create the Kafka Pods, as it seems that the ZooKeeper throws "connection refused", but in the end it's just the default NetworkPolicies that blocks the connection requests to ZKMultipleClusterOperatorsST
Checklist