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

OCPBUGS-1554: Bump vendored k8s libraries to 1.25 #829

Merged
merged 1 commit into from
Sep 30, 2022

Conversation

gcs278
Copy link
Contributor

@gcs278 gcs278 commented Sep 20, 2022

Update k8s.io/api, k8s.io/apimachinery, k8s.io/apiserver, and k8s.io/client-go to v0.25.0 as well as sigs.k8s.io/controller-runtime to v0.13.0 which maps to the overall 1.25 kubernetes release. Also bump github.com/openshift/library-go for its 1.25 support. All other vendor updates were automatically included as a part of these updates.

pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock" and added utilclocktesting "k8s.io/utils/clock/testing" as that where NewFakeClock moved into.
pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/ingress/status.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/status/controller.go: Moved utilclock to "k8s.io/utils/clock"

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Sep 20, 2022
@openshift-ci-robot
Copy link
Contributor

@gcs278: This pull request references Jira Issue OCPBUGS-1554, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Update k8s.io/api, k8s.io/apimachinery, k8s.io/apiserver, and k8s.io/client-go to v0.25.0, which maps to the overall 1.25 kubernetes release. Also bump github.com/openshift/library-go for its 1.25 support. All other vendor updates were automatically included as a part of these updates.

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.

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 20, 2022

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 20, 2022

/hold
E2E build failure I missed regarding NewFakeClock missing.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 20, 2022
@gcs278
Copy link
Contributor Author

gcs278 commented Sep 20, 2022

/unhold
NewFakeClock moved to k8s.io/utils/clock/testing

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 20, 2022
@openshift-ci-robot
Copy link
Contributor

@gcs278: This pull request references Jira Issue OCPBUGS-1554, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

In response to this:

Update k8s.io/api, k8s.io/apimachinery, k8s.io/apiserver, and k8s.io/client-go to v0.25.0, which maps to the overall 1.25 kubernetes release. Also bump github.com/openshift/library-go for its 1.25 support. All other vendor updates were automatically included as a part of these updates.

pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock" and added utilclocktesting "k8s.io/utils/clock/testing" as that where NewFakeClock moved into.

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.

@openshift-ci-robot
Copy link
Contributor

@gcs278: This pull request references Jira Issue OCPBUGS-1554, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.0) matches configured target version for branch (4.12.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

In response to this:

Update k8s.io/api, k8s.io/apimachinery, k8s.io/apiserver, and k8s.io/client-go to v0.25.0, which maps to the overall 1.25 kubernetes release. Also bump github.com/openshift/library-go for its 1.25 support. All other vendor updates were automatically included as a part of these updates.

pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock" and added utilclocktesting "k8s.io/utils/clock/testing" as that where NewFakeClock moved into.
pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/ingress/status.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/status/controller.go: Moved utilclock to "k8s.io/utils/clock"

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.

@frobware
Copy link
Contributor

You have some .idea and .envrc files committed here.

A [.envrc](https://github.com/openshift/cluster-ingress-operator/pull/829/files#diff-d33e979799a45c7c51752e9c8d96a3e452015d1a40b1e4b6ec6a98e92c4d8430) (1)
A [.idea/.gitignore](https://github.com/openshift/cluster-ingress-operator/pull/829/files#diff-21610973868a98feff98dd0460438a8a32cca1447bc8701537ec5048e0c5faeb) (8)
A [.idea/cluster-ingress-operator.iml](https://github.com/openshift/cluster-ingress-operator/pull/829/files#diff-3cc7c2f38630ac52dcd6b7a2cd0b31ba4b1ac4050d2827792eb489aee98b69c2) (9)
A [.idea/modules.xml](https://github.com/openshift/cluster-ingress-operator/pull/829/files#diff-0aae258f1732eac2acd4fcdd1af6d0737b4ec8d233136c3ba7c40b6d49aeda50) (8)
A [.idea/vcs.xml](https://github.com/openshift/cluster-ingress-operator/pull/829/files#diff-a6dab70bd0e9ffc91d8419ad52225baff3a3e7c9d8e1724f7ed6d96b661d804a) (6)

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 21, 2022

You have some .idea and .envrc files committed here.

@frobware I did have .idea and .envrc checked in by accident, but they have since been removed. Are you still seeing them in the commit? I can't find them.

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 21, 2022

Tons of CI failures, looks like ingress is not working. Will investigate.

@frobware
Copy link
Contributor

You have some .idea and .envrc files committed here.

@frobware I did have .idea and .envrc checked in by accident, but they have since been removed. Are you still seeing them in the commit? I can't find them.

I was reading changes via email. Looking again, I don't see them in the commit.

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 21, 2022

/retest
Maybe this was fluke?

@candita
Copy link
Contributor

candita commented Sep 21, 2022

/assign @frobware
/assign @brandisher

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 21, 2022

CI Failures happened again:
{Operator unavailable (IngressDoesNotHaveAvailableCondition): The "default" ingress controller is not reporting an Available status condition. Operator unavailable (IngressDoesNotHaveAvailableCondition): The "default" ingress controller is not reporting an Available status condition.}

Investigating

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. and removed jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. labels Sep 21, 2022
@gcs278
Copy link
Contributor Author

gcs278 commented Sep 26, 2022

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 26, 2022

I don't think related, others are seeing this issue: ingress-to-oauth-server-new-connections was unreachable during disruption testing
/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 26, 2022

/retest

3 similar comments
@suleymanakbas91
Copy link
Contributor

/retest

@suleymanakbas91
Copy link
Contributor

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 27, 2022

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 27, 2022

The install failed...
/retest

@suleymanakbas91
Copy link
Contributor

/retest

2 similar comments
@suleymanakbas91
Copy link
Contributor

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 28, 2022

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 28, 2022

OVNKubernetesControllerDisconnectedSouthboundDatabase failure again, and now a new pods should keep the assigned EgressIPs when being rescheduled to another node connection timeout failure, which I don't believe to be affected by cluster-ingress-operator.
/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 28, 2022

Both OVN and the ingress-to-oauth-server-new-connections was unreachable during disruption testing type testing.
Supposedly the disruption tests are fixed, so:
/retest

@suleymanakbas91
Copy link
Contributor

/retest

1 similar comment
@suleymanakbas91
Copy link
Contributor

/retest

@brandisher
Copy link
Contributor

ingress-to-XXX issues again
/test e2e-gcp-ovn-serial

@brandisher
Copy link
Contributor

etcd and ovn issues
/retest e2e-gcp-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2022

@brandisher: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test e2e-aws-operator
  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-upgrade
  • /test e2e-gcp-ovn-serial
  • /test images
  • /test unit
  • /test verify

The following commands are available to trigger optional jobs:

  • /test e2e-aws-ovn-single-node
  • /test e2e-azure-operator
  • /test e2e-azure-ovn
  • /test e2e-gcp-operator

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-operator
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-single-node
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-upgrade
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-azure-ovn
  • pull-ci-openshift-cluster-ingress-operator-master-e2e-gcp-ovn-serial
  • pull-ci-openshift-cluster-ingress-operator-master-images
  • pull-ci-openshift-cluster-ingress-operator-master-unit
  • pull-ci-openshift-cluster-ingress-operator-master-verify

In response to this:

etcd and ovn issues
/retest e2e-gcp-ovn-serial

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.

@brandisher
Copy link
Contributor

/test e2e-gcp-ovn-serial

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 29, 2022

/unhold
I think we've gotten enough CI runs in. It's just stuck on know problems (OVN and disruption).

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 29, 2022
@Miciah
Copy link
Contributor

Miciah commented Sep 29, 2022

/override ci/prow/e2e-gcp-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 29, 2022

@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-gcp-ovn-serial

In response to this:

/override ci/prow/e2e-gcp-ovn-serial

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD fbe157d and 2 for PR HEAD be08afc in total

@suleymanakbas91
Copy link
Contributor

/retest

@Miciah
Copy link
Contributor

Miciah commented Sep 30, 2022

/override ci/prow/e2e-gcp-ovn-serial

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2022

@Miciah: Overrode contexts on behalf of Miciah: ci/prow/e2e-gcp-ovn-serial

In response to this:

/override ci/prow/e2e-gcp-ovn-serial

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 30, 2022

@gcs278: 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-robot openshift-merge-robot merged commit dbefffe into openshift:master Sep 30, 2022
@openshift-ci-robot
Copy link
Contributor

@gcs278: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-1554 has been moved to the MODIFIED state.

In response to this:

Update k8s.io/api, k8s.io/apimachinery, k8s.io/apiserver, and k8s.io/client-go to v0.25.0 as well as sigs.k8s.io/controller-runtime to v0.13.0 which maps to the overall 1.25 kubernetes release. Also bump github.com/openshift/library-go for its 1.25 support. All other vendor updates were automatically included as a part of these updates.

pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock" and added utilclocktesting "k8s.io/utils/clock/testing" as that where NewFakeClock moved into.
pkg/operator/controller/dns/controller.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/ingress/status.go: Moved utilclock to "k8s.io/utils/clock"
pkg/operator/controller/status/controller.go: Moved utilclock to "k8s.io/utils/clock"

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants