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

Upgrade to HPE CSI Operator v2.4.0 on OpenShift 4.12 Fail #355

Open
birminghamz opened this issue Jan 16, 2024 · 3 comments
Open

Upgrade to HPE CSI Operator v2.4.0 on OpenShift 4.12 Fail #355

birminghamz opened this issue Jan 16, 2024 · 3 comments

Comments

@birminghamz
Copy link

The operator gets stuck 'pending' when upgrading the HPE CSI operator on OpenShift 4.12.46 from 2.3.0 to 2.4.0:

status:
cleanup: {}
conditions:

  • lastTransitionTime: '2024-01-16T17:08:53Z'
    lastUpdateTime: '2024-01-16T17:08:53Z'
    message: requirements not yet checked
    phase: Pending
    reason: RequirementsUnknown
  • lastTransitionTime: '2024-01-16T17:08:53Z'
    lastUpdateTime: '2024-01-16T17:08:53Z'
    message: one or more requirements couldn't be found
    phase: Pending
    reason: RequirementsNotMet
    lastTransitionTime: '2024-01-16T17:08:53Z'
    lastUpdateTime: '2024-01-16T17:08:53Z'
    message: one or more requirements couldn't be found
    phase: Pending
    reason: RequirementsNotMet
    requirementStatus:
  • group: operators.coreos.com
    kind: ClusterServiceVersion
    message: CSV minKubeVersion (1.25.0) less than server version (v1.25.16+a4e782e)
    name: hpe-csi-operator.v2.4.0
    status: Present
    version: v1alpha1
  • group: apiextensions.k8s.io
    kind: CustomResourceDefinition
    message: CRD is present and Established condition is true
    name: hpecsidrivers.storage.hpe.com
    status: Present
    uuid: 4ec67ce1-dd11-4a79-b166-d57a53dcbb2b
    version: v1
  • group: ''
    kind: ServiceAccount
    message: Service account does not exist
    name: hpe-csi-operator-sa
    status: NotPresent
    version: v1
@datamattsson
Copy link
Collaborator

  1. Uninstall all instances of the Operator 2.3.0
  2. Uninstall the Operator 2.3.0
  3. Install 2.4.0

Details: https://scod.hpedev.io/partners/redhat_openshift/index.html#upgrading

@birminghamz
Copy link
Author

Just attempted a full uninstall & Install of v2.4.0 but recieving this error when attempting to create the HPECSIDriver:

failed to install release: rendered manifests contain a resource that
already exists. Unable to continue with install: CSIDriver "csi.hpe.com"
in namespace "" exists and cannot be imported into the current release:
invalid ownership metadata; annotation validation error: key
"meta.helm.sh/release-namespace" must equal "hpe-storage": current value
is "hpe-csi-driver"

@datamattsson
Copy link
Collaborator

Seems to be conflicting namespaces with residual resources. Did you install the Operator and subsequently the driver instance in the same namespace?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants