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

aws-load-balancer: update ocp version #45653

Merged

Conversation

alebedev87
Copy link
Contributor

Update the versions of the OpenShift clusters on which the tests are run.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 14, 2023
@alebedev87
Copy link
Contributor Author

/pj-rehearse

@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-main-e2e-aws-rosa-operator

@alebedev87
Copy link
Contributor Author

openshift/aws-load-balancer-operator#120: to fix release-1.0 jobs.

@alebedev87
Copy link
Contributor Author

/pj-rehearse

@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-release-1.0-e2e-aws-operator

1 similar comment
@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-release-1.0-e2e-aws-operator

@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-release-1.0-e2e-aws-rosa-operator

@alebedev87
Copy link
Contributor Author

/retest

@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-main-e2e-aws-rosa-operator

@@ -25,12 +25,12 @@ promotion:
releases:
initial:
integration:
name: "4.12"
name: "4.14"
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be 4.15 now? Just like #45662

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done.

@alebedev87
Copy link
Contributor Author

/pj-rehearse

1 similar comment
@alebedev87
Copy link
Contributor Author

/pj-rehearse

@alebedev87
Copy link
Contributor Author

/pj-rehearse pull-ci-openshift-aws-load-balancer-operator-main-e2e-aws-operator

@alebedev87
Copy link
Contributor Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 20, 2023
@@ -1,6 +1,6 @@
base_images:
base:
name: "4.12"
name: "4.14"
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be 4.15 too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, let me fix it.

@@ -79,6 +79,7 @@ tests:
OO_INSTALL_NAMESPACE: aws-load-balancer-operator
OO_PACKAGE: aws-load-balancer-operator
OO_TARGET_NAMESPACES: '!all'
OPENSHIFT_VERSION: "4.13"
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems odd that you have OPENSHIFT_VERSION only on aws-load-balancer-operator-release-1.0.yaml. Is it needed? Why not the other files?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question, I think I ignored the other branches since they are for the TechPreview releases.

Copy link
Contributor Author

@alebedev87 alebedev87 Dec 21, 2023

Choose a reason for hiding this comment

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

I figured this out. The TechPreview branch cannot have this because they don't have the rosa test back ported. And the 1.1 release was using 4.14 at the time the PR was created. Let me update 1.1 branch too.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yea that makes sense.

I suppose the point of this is to "pin" to a specific version of OpenShift in ROSA; without this, it looks like https://steps.ci.openshift.org/reference/rosa-cluster-provision installs the latest version of OCP with ROSA, which I believe we don't want.

Shouldn't we add this to ci-operator/config/openshift/aws-load-balancer-operator/openshift-aws-load-balancer-operator-main.yaml too?

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 suppose the point of this is to "pin" to a specific version of OpenShift in ROSA; without this, it looks like https://steps.ci.openshift.org/reference/rosa-cluster-provision installs the latest version of OCP with ROSA, which I believe we don't want.

Right

Shouldn't we add this to ci-operator/config/openshift/aws-load-balancer-operator/openshift-aws-load-balancer-operator-main.yaml too?

I think it's fine to keep the main branch as development one which runs on the latest OCP candidate available. This way we are sure we start new features on the latest OCP available on ROSA.

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh yea, that's a fair point. I think the tricky part is remembering to keep the OCP versioning up-to-date with our releases (hence the reason this PR was created).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. Similar problem we have in the operator repository with the latest doc links.

@alebedev87
Copy link
Contributor Author

/pj-rehearse

Re-rehearsing as new branches were impacted.

@gcs278
Copy link
Contributor

gcs278 commented Dec 21, 2023

/approve
/lgtm

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

openshift-ci bot commented Dec 21, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87, gcs278

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

Copy link
Contributor

openshift-ci bot commented Dec 21, 2023

@alebedev87: 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-merge-bot openshift-merge-bot bot merged commit 6e27312 into openshift:master Dec 21, 2023
21 checks passed
robpblake pushed a commit to robpblake/release that referenced this pull request Jan 11, 2024
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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants