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-18131: Block upgrade to 4.13 via admin ack #171

Merged

Conversation

gnufied
Copy link
Member

@gnufied gnufied commented Sep 22, 2023

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gnufied

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 Sep 22, 2023
@gnufied gnufied changed the title Block upgrade 413 admin ack OCPBUGS-18131: Block upgrade 413 admin ack Sep 22, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 22, 2023
@openshift-ci-robot
Copy link
Contributor

@gnufied: This pull request references Jira Issue OCPBUGS-18131, which is invalid:

  • expected the bug to target the "4.12.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-18131 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

In response to this:

Fixes https://issues.redhat.com/browse/OCPBUGS-18131

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.

@gnufied
Copy link
Member Author

gnufied commented Sep 22, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@gnufied: This pull request references Jira Issue OCPBUGS-18131, which is invalid:

  • expected dependent Jira Issue OCPBUGS-18132 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@gnufied gnufied changed the title OCPBUGS-18131: Block upgrade 413 admin ack OCPBUGS-18131: Block upgrade to 4.13 via admin ack Sep 22, 2023
Copy link
Contributor

@jsafrane jsafrane left a comment

Choose a reason for hiding this comment

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

/lgtm


pvs, err := apiDependencies.ListPersistentVolumes()
if err != nil {
reason := fmt.Errorf("vsphere csi driver installed failed with %s, unable to list pvs: %v", result.Reason, err)
Copy link
Contributor

Choose a reason for hiding this comment

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

This error is IMO not related to CSI driver installation
(this applies also to the original PR, so I don't mind if we leave it as it is...)

@jsafrane
Copy link
Contributor

/label backport-risk-assessed
/retest-required

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 27, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 27, 2023
@duanwei33
Copy link

Pre-merge verified with PR: #171 and openshift/cluster-storage-operator#402.

Create cluster in vsphere 8, while ESXi version is 8.0.1.0-22088125(doesn't match the requirement) and vsphere version is 8.0.1.0-22088981 (matches the requirement)

  1. oc adm upgrade shows the CSI migration warning as below which is expected, not starting with a new line however:
$ oc adm upgrade
Cluster version is 4.12.0-0.test-2023-09-28-022513-ci-ln-58nnh9k-latest

Upgradeable=False

  Reason: AdminAckRequired
  Message: Kubernetes 1.26 and therefore OpenShift 4.13 remove several APIs which require admin consideration. Please see the knowledge article https://access.redhat.com/articles/6958394 for details and instructions. vSphere CSI migration will be enabled in Openshift-4.14. Your cluster appears to be using in-tree vSphere volumes and is on a vSphere version that has CSI migration related bugs. See - https://access.redhat.com/node/7011683 for more information, before upgrading to 4.14.
  1. Check the driver operator log which is expected:
I0928 07:16:18.276872       1 vmware.go:273] Found existing profile with same name: openshift-storage-policy-wduan-0928b-vs-k6pft
I0928 07:16:19.178787       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.178913       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.186219       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.186276       1 check_patched_vcenter.go:29] checking for patched version of vSphere for CSI migration: 8.0.1.0-22088981
I0928 07:16:19.186289       1 vsphere_environment_checker.go:90] Overall check result: UpgradeRequiresAdminAck: host host-1013 is on ESXI version 8.0.1.0-22088125, minimum required for CSI migration: > 8.0.1-22088125
I0928 07:16:19.186296       1 vspherecontroller.go:261] Scheduled the next check in 1h0m0s
I0928 07:16:19.186310       1 check_error.go:217] found vSphere in-tree persistent volumes in the cluster
I0928 07:16:19.186316       1 vspherecontroller.go:361] check status is: pass
I0928 07:16:19.186333       1 vspherecontroller.go:516] Updating admin-gates to require admin-ack for vSphere CSI migration
W0928 07:16:19.199366       1 vspherecontroller.go:496] host host-1013 is on ESXI version 8.0.1.0-22088125, minimum required for CSI migration: > 8.0.1-22088125
I0928 07:16:19.199788       1 event.go:285] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"vmware-vsphere-csi-driver-operator", UID:"4a86e840-d6e9-4af9-b1a5-8eac2ad524ea", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'ConfigMapUpdated' Updated ConfigMap/admin-gates -n openshift-config-managed:

Check admin-gates, we use ack-4.12-kube-126-vsphere-migration-in-4.14 as it has impact when upgrading to 4.14 which is expected:

$ oc get ConfigMap/admin-gates -n openshift-config-managed -o yaml
apiVersion: v1
data:
  ......
  ack-4.12-kube-126-vsphere-migration-in-4.14: vSphere CSI migration will be enabled
    in Openshift-4.14. Your cluster appears to be using in-tree vSphere volumes and
    is on a vSphere version that has CSI migration related bugs. See - https://access.redhat.com/node/7011683
    for more information, before upgrading to 4.14.

@duanwei33
Copy link

duanwei33 commented Sep 28, 2023

@gnufied Just one strange observation, the message "Scheduled the next check in 1h0m0s" which stands for the end actually came before all check finished:
(But I don't think it blocks the PER merge, we can have another PRs to fix 4.12/4.13 if needed.)

I0928 07:16:18.276872       1 vmware.go:273] Found existing profile with same name: openshift-storage-policy-wduan-0928b-vs-k6pft
I0928 07:16:19.178787       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.178913       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.186219       1 check_nodes.go:174] checking for patched version of ESXi for CSI migration: 8.0.1.0-22088125
I0928 07:16:19.186276       1 check_patched_vcenter.go:29] checking for patched version of vSphere for CSI migration: 8.0.1.0-22088981
I0928 07:16:19.186289       1 vsphere_environment_checker.go:90] Overall check result: UpgradeRequiresAdminAck: host host-1013 is on ESXI version 8.0.1.0-22088125, minimum required for CSI migration: > 8.0.1-22088125
I0928 07:16:19.186296       1 vspherecontroller.go:261] Scheduled the next check in 1h0m0s
I0928 07:16:19.186310       1 check_error.go:217] found vSphere in-tree persistent volumes in the cluster
I0928 07:16:19.186316       1 vspherecontroller.go:361] check status is: pass
I0928 07:16:19.186333       1 vspherecontroller.go:516] Updating admin-gates to require admin-ack for vSphere CSI migration
W0928 07:16:19.199366       1 vspherecontroller.go:496] host host-1013 is on ESXI version 8.0.1.0-22088125, minimum required for CSI migration: > 8.0.1-22088125
I0928 07:16:19.199788       1 event.go:285] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"vmware-vsphere-csi-driver-operator", UID:"4a86e840-d6e9-4af9-b1a5-8eac2ad524ea", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'ConfigMapUpdated' Updated ConfigMap/admin-gates -n openshift-config-managed:

@duanwei33
Copy link

/label qe-approved
/label cherry-pick-approved

@openshift-ci openshift-ci bot added qe-approved Signifies that QE has signed off on this PR cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Sep 28, 2023
@jsafrane
Copy link
Contributor

jsafrane commented Oct 2, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 2, 2023
@openshift-ci-robot
Copy link
Contributor

@jsafrane: This pull request references Jira Issue OCPBUGS-18131, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-18132 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-18132 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

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

In response to this:

/jira refresh

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 2, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 64cb29d and 2 for PR HEAD 77ab37f in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2dff285 and 1 for PR HEAD 77ab37f in total

@gnufied
Copy link
Member Author

gnufied commented Oct 2, 2023

@duanwei33 that should be okay. So we run all the expensive checks and when they are finished we run another check which takes result of previously finished checks and applies further logic. For example - if expensive checks resulted in determining an older version of vSphere then the next check verifies if cluster has intree PVs.

@gnufied
Copy link
Member Author

gnufied commented Oct 4, 2023

/retest

@openshift-ci openshift-ci bot merged commit 1271ebf into openshift:release-4.12 Oct 4, 2023
7 of 8 checks passed
@openshift-ci-robot
Copy link
Contributor

@gnufied: Jira Issue OCPBUGS-18131: All pull requests linked via external trackers have merged:

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

In response to this:

Fixes https://issues.redhat.com/browse/OCPBUGS-18131

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.12.0-0.nightly-2023-10-04-200342

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants