Skip to content
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

add vsphere-ipi-ovn-dualstack-ipsec #44742

Closed
wants to merge 6 commits into from

Conversation

rbbratta
Copy link
Contributor

We need to test all networking features on dualstack and dualstack-primaryipv6

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@rbbratta: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-vsphere-ipi-ovn-dualstack-privmaryv6-ipsec-f28-destructive N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.15-amd64-nightly-vsphere-ipi-ovn-dualstack-ipsec-f28 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.15-amd64-nightly-vsphere-ipi-ovn-dualstack-privmaryv6-ipsec-f28 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-vsphere-ipi-ovn-dualstack-privmaryv6-ipsec-f28 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-vsphere-ipi-ovn-dualstack-ipsec-f28-destructive N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.15-amd64-nightly-vsphere-ipi-ovn-dualstack-privmaryv6-ipsec-f28-destructive N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.15-amd64-nightly-vsphere-ipi-ovn-dualstack-ipsec-f28-destructive N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-vsphere-ipi-ovn-dualstack-ipsec-f28 N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@rbbratta
Copy link
Contributor Author

rbbratta commented Oct 23, 2023

Testing for combined SDN-3604 and OPNET-230

IPsec with DualStack.

@rbbratta
Copy link
Contributor Author

/cc @anuragthehatter

@rbbratta
Copy link
Contributor Author

Testing with the cluster-network-03-config.yml manifest is different than runtime IPsec enablement because CNO automatically decrements the Cluster MTU for IPsec at install time.

@rbbratta
Copy link
Contributor Author

@anuragthehatter
Copy link
Contributor

Looks ok to me @rbbratta Thanks
@zhaozhanqi probably check cron values to make sure.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: anuragthehatter, rbbratta
Once this PR has been reviewed and has the lgtm label, please assign liangxia for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@zhaozhanqi
Copy link
Contributor

cron value should be generated by scripts I guess
this looks good to me
/assign @jianlinliu

@@ -3819,6 +3819,48 @@ tests:
test:
- chain: openshift-e2e-test-qe-destructive
workflow: cucushift-installer-rehearse-vsphere-ipi-ovn-ipsec
- as: vsphere-ipi-ovn-dualstack-ipsec-f28
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on already have some other vsphere-ipi-ovn-dualstack and vsphere-ipi-ovn-dualstack-privmaryv6 ci jobs, can we across-cover them to save some vsphere slice quota (we only have a small number of vsphere slice quota).

E.g: non-destructive testing run on vsphere-ipi-ovn-dualstack, destructive testing run on vsphere-ipi-ovn-dualstack-ipsec.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or if we can only do base health check and do not run openshift-e2e tests on vsphere-ipi-ovn-dualstack
since vsphere-ipi-ovn-dualstack-privmaryv6-ipsec-f28 should be able to cover all tests (with or w/o ipsec cases)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather drop IPv4 only tests like vsphere-ipi-ovn-ipsec-f28. The single stack IPv4 tests are less useful.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still have almost a whole matrix test on the Dualstacks.

  • ipi-ovn-shared-to-local-gw-migration
  • ipi-proxy-fips
  • ipi-proxy-workers-rhel8 (we haven't tested DualStack with RHEL workers?)
  • ipi-external-lb
  • ipi-disk-encryption-tang-fips

All these need testing on the DualStacks.

Ideally DualStack IPv4 would become the default and replace SingleStack IPv4.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#44812

It looks like we have a bunch of OpenShiftSDN tests as well, those need to be switched to OVN DualStack for 4.15

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for Privmaryv6 #44813

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather drop IPv4 only tests like vsphere-ipi-ovn-ipsec-f28

I am okay with that, beside that, I still have concern about vsphere slice quota, especially after vsphere vpn migration, any install which need a bastion (e.g: proxy and disconnected mirror) would consume 2 slice quota at least.

if we double (dualstack and dualstack-privmaryv6) all the configurations, slice quota would definitely become a bottleneck for ci testing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rbbratta I think we can mix all related feature with dualstack to one job. eg

ipi-ovn-dualstack-ipsec-fips
ipi-ovn-dualstack-ipsec-ipv6primary-fips
ipi-disk-encryption-tang-fips --> for this one, I'm not sure it's related to dualstack,
for RHEL worker on dualstack I think it's low priority.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we get more quota? DualStack is an important feature.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we have to send request to SPLAT team.

Copy link
Contributor

openshift-ci bot commented Nov 16, 2023

@rbbratta: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 16, 2023
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 31, 2023
@openshift-bot
Copy link
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jan 15, 2024
Copy link
Contributor

openshift-ci bot commented Jan 15, 2024

@openshift-bot: Closed this PR.

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
6 participants