SDN-5485: OVNLocalnetWithNoSubnets: ->4.17.[0-6] with virtualization
#6403
Conversation
openshift-ci
bot
added
the
approved
petr-muller
force-pushed
the
OVNLocalnetWithNoSubnets
branch
from
f3718a1 to
b0a6e0f
Compare
petr-muller
changed the title
OVNLocalnetWithNoSubnets: ->4.17.[0-6] with virtualizationOVNLocalnetWithNoSubnets: ->4.17.[0-6] with virtualization
openshift-ci-robot
added
the
jira/valid-reference
|
@petr-muller: This pull request references SDN-5485 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
Address SDN-5485 / OCPBUGS-43454 which affects 4.17 until 4.17.7 where it is fixed. We have not managed to identify a precise technical PromQL to identify clusters with the exact problematic networking configuration so I am proposing to use a coarse approximation of what clusters are *likely* (based on the information available) to have such config (OpenShift Virtualization installations identified by the hyperconverged-cluster-operator CSV presence, which at the same time have at least one `network-attachment-definitions.k8s.cni.cncf.io` resource instance. Given the impact of the bug when hit (failure to create new workloads), it is better to steer the group of potentially affected clusters towards already available 4.17.7, even if we are not able to produce a sufficiently targeted PromQL for the actual network configuration.
petr-muller
force-pushed
the
OVNLocalnetWithNoSubnets
branch
from
b0a6e0f to
79f8eb4
Compare
|
@petr-muller: This pull request references SDN-5485 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.19.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@petr-muller: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: petr-muller, wking 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 |
3 participants
Address SDN-5485 / OCPBUGS-43454 which affects 4.17 until 4.17.7 where it is fixed. We have not managed to identify a precise technical PromQL to identify clusters with the exact problematic networking configuration so I am proposing to use a coarse approximation of what clusters are likely (based on the information available) to have such config (OpenShift Virtualization installations identified by the hyperconverged-cluster-operator CSV presence, and which at the same time have at least one
network-attachment-definitions.k8s.cni.cncf.ioresource instance.Given the impact of the bug when hit (failure to create new workloads), it is better to steer the group of potentially affected clusters towards already available 4.17.7, even if we are not able to produce a sufficiently targeted PromQL for the actual network configuration.