CORENET-6130, CORENET-6261, CORENET-6092: Implement PreconfiguredUDNAddresses API changes #2743
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@kyrtapz: This pull request references CORENET-6130 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 story to target the "4.20.0" version, but no target version was set. In 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. |
openshift-ci
bot
added
the
approved
kyrtapz
force-pushed
the
default_net_annot_vap
branch
from
1390e6b to
77084fb
Compare
openshift-merge-robot
added
the
needs-rebase
kyrtapz
force-pushed
the
default_net_annot_vap
branch
from
77084fb to
b7cf7ff
Compare
openshift-merge-robot
removed
the
needs-rebase
kyrtapz
force-pushed
the
default_net_annot_vap
branch
4 times, most recently
from
affd6d6 to
9b2b372
Compare
|
@kyrtapz could you rebase, now that #2770 was merged ? I see these warnings being logged in the ovnkube control plane pods: I think it's a red herring, but still, it would give us a cleaner signal. Thanks in advance |
kyrtapz
force-pushed
the
default_net_annot_vap
branch
2 times, most recently
from
d5c2f3a to
781728a
Compare
Add the new API fields to both CUDN and UDN CRDs behind the PreconfiguredUDNAddresses featuregate. Signed-off-by: Patryk Diak <[email protected]>
kyrtapz
force-pushed
the
default_net_annot_vap
branch
from
781728a to
ad73589
Compare
kyrtapz
changed the title
v1.multus-cni.io/default-network updates
|
@kyrtapz: This pull request references CORENET-6130 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6261 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6092 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 story to target the "4.20.0" version, but no target version was set. In 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. |
|
@kyrtapz: This pull request references CORENET-6130 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6261 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6092 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 story to target the "4.20.0" version, but no target version was set. In 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. |
|
/test e2e-gcp-ovn-techpreview |
kyrtapz
force-pushed
the
default_net_annot_vap
branch
from
ad73589 to
fbd111c
Compare
|
/test e2e-gcp-ovn-techpreview |
|
@kyrtapz: This pull request references CORENET-6130 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6261 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 story to target the "4.20.0" version, but no target version was set. This pull request references CORENET-6092 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 story to target the "4.20.0" version, but no target version was set. In 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. |
|
/test e2e-gcp-ovn-techpreview |
|
/retest-required |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw In 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. |
|
/tide refresh |
|
/override e2e-metal-ipi-ovn-dualstack-bgp-local-gw |
|
@tssurya: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In 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. |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw |
|
@tssurya: Overrode contexts on behalf of tssurya: ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw In 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. |
|
/tide refresh |
|
/shrug |
|
Changes in this PR are TechPreview specific and should not affect this job, will re-run it anyway once tide kicks of the other 20 jobs... |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec In 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. |
|
/test e2e-metal-ipi-ovn-ipv6-ipsec |
|
Metal jobs are timing out, this change is techpreview specific and not affecting ipsec. /override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec In 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. |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw |
|
/retest-required |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw In 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. |
|
/test e2e-gcp-ovn-techpreview |
|
@kyrtapz: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
This PR only affects techpreview, metal jobs are perma-failing (timeout) across the board: gcp techpreview failed on CSI test which is unrelated: |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-gcp-ovn-techpreview, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw, ci/prow/e2e-metal-ipi-ovn-ipv6 In 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. |
openshift-merge-bot
bot
merged commit 2b0fd30
into
openshift:master
|
[ART PR BUILD NOTIFIER] Distgit: cluster-network-operator |
Introduce the following changes behind the featuregate: