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

SDN-4776: add e2e-aws-ovn-subnet-configs job #51970

Merged
merged 1 commit into from
Jun 4, 2024

Conversation

jluhrsen
Copy link
Contributor

  • adds new step to do day-2 config for internalTransitSwitchSubnet
  • adds new step to do day-2 config for internalJoinSubnet
  • job uses a clusternetwork manifest so that the cluster install will have a configured internalMasqueradeSubnet
  • the job will run periodically using the CNO repo

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented May 13, 2024

@jluhrsen: This pull request references SDN-4776 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.16.0" version, but no target version was set.

In response to this:

  • adds new step to do day-2 config for internalTransitSwitchSubnet
  • adds new step to do day-2 config for internalJoinSubnet
  • job uses a clusternetwork manifest so that the cluster install will have a configured internalMasqueradeSubnet
  • the job will run periodically using the CNO repo

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.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen jluhrsen changed the title SDN-4776: add e2e-aws-ovn-subnet-configs SDN-4776: add e2e-aws-ovn-subnet-configs job May 21, 2024
@anuragthehatter
Copy link
Contributor

@jluhrsen I believe we should be ok now as https://issues.redhat.com/browse/OCPBUGS-33728 was merged yesterday

@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 29, 2024
@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 29, 2024
@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Comment on lines 18 to 30
internalTransitSwitchSubnet=$(oc get network.operator.openshift.io -o jsonpath='{.items[0].spec.defaultNetwork.ovnKubernetesConfig.ipv4.internalTransitSwitchSubnet}')

# first wait for the network operator to move to Progressing=True
wait_for_operator_to_be_progressing network

# make sure all operators and nodes are good
wait_for_operators_and_nodes 300

if [[ "$internalTransitSwitchSubnet" != "100.69.0.0/16" ]]; then
echo "Error: internalTransitSwitchSubnet is misconfigured. Expected internalTransitSwitchSubnet of 100.69.0.0/16, but got:"
oc get network.operator.openshift.io -o jsonpath='{.items[0].spec.defaultNetwork}'
exit 1
fi
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't really understand why you check internalTransitSwitchSubnet. Either at all (since it would mean that the patch command that did not fail didn't work, so testing the patch command?) and also why you do it after the operators stabilize but with the value you got before they did.

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess the same comment would apply for the internalJoinSubnet.

Probably missing something that could be clarified through a comment

Copy link
Contributor Author

Choose a reason for hiding this comment

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

great catch here. the intention was to do the patch, then let the operator to progress and settle, then validate that
it's present in network.opertor.

I just updated the PR to do that with a small comment.

Thanks for this.

internalMasqueradeSubnet: 100.254.169.0/29
EOF

cat ${SHARED_DIR}/manifest_cluster-network-03-config.yml
Copy link
Contributor

Choose a reason for hiding this comment

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

Out of curiosity, are all manifests in ${SHARED_DIR} among all the other files in there, picked up for installation? or is there any more specific criteria?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

great question. I don't actually know the answer, just following the pattern that was there since the beginning for me :)

internalMasqueradeSubnet: 100.254.169.0/29
EOF

cat ${SHARED_DIR}/manifest_cluster-network-03-config.yml
Copy link
Contributor

Choose a reason for hiding this comment

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

A lot of the files don't end with an empty new line, unsure if that's an issue

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no, I don't think it's an issue as the jobs work as expected. I've seen both with and without I think. not sure if we have a standard to follow on this.

- adds new step to do day-2 config for internalTransitSwitchSubnet
- adds new step to do day-2 config for internalJoinSubnet
- job uses a clusternetwork manifest so that the cluster install will
  have a configured internalMasqueradeSubnet
- adds a step post-install that will check that the internalMasqueradeSubnet
  route is configured in every node's route table
- the job will run periodically using the CNO repo

Signed-off-by: Jamo Luhrsen <jluhrsen@gmail.com>
@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@jluhrsen: 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
pull-ci-openshift-cluster-network-operator-release-4.14-e2e-aws-ovn-clusternetwork-cidr-expansion-presubmit openshift/cluster-network-operator presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.17-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.16-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.15-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-clusternetwork-cidr-expansion openshift/ovn-kubernetes presubmit Registry content changed
periodic-ci-openshift-cluster-network-operator-release-4.15-e2e-aws-ovn-clusternetwork-cidr-expansion N/A periodic Registry content changed
periodic-ci-openshift-cluster-network-operator-release-4.14-e2e-aws-ovn-clusternetwork-cidr-expansion N/A periodic Registry content changed
periodic-ci-openshift-cluster-network-operator-release-4.13-e2e-aws-ovn-clusternetwork-cidr-expansion N/A periodic Registry content changed
periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-clusternetwork-cidr-expansion N/A periodic Registry content changed
periodic-ci-openshift-cluster-network-operator-release-4.16-e2e-aws-ovn-clusternetwork-cidr-expansion N/A periodic Registry content changed
periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 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 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 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.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse periodic-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-subnet-configs

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Copy link
Contributor

openshift-ci bot commented May 31, 2024

@jluhrsen: 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-sigs/prow repository. I understand the commands that are listed here.

@jluhrsen
Copy link
Contributor Author

@jcaamano , I think this is good now if you could check please.

@jluhrsen
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@jluhrsen: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 31, 2024
@jcaamano
Copy link
Contributor

jcaamano commented Jun 4, 2024

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2024
Copy link
Contributor

openshift-ci bot commented Jun 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcaamano, jluhrsen

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 4, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit fce426b into openshift:master Jun 4, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
4 participants