search

kabanero-io / kabanero-operator

The Kabanero Operator. This repo will be archived soon.
Apache License 2.0
43 stars 26 forks source link

Installation fails on OCP 4.3 #404

Closed csantanapr closed 4 years ago

csantanapr commented 4 years ago

Environment:

Steps to reproduce:

Results:

The InstallPlan status is 'Failed'. There might a problem that is preventing the InstallPlan installation from completing, or additional time might be required to complete.

Run the following commands to examine the status of the InstallPlan:
oc -n "kabanero" describe InstallPlan "install-htgqh"

Once the problem is resolved or the status of the InstallPlan becomes 'Complete', re-run the installer to complete the installation process.

oc -n "kabanero" describe InstallPlan "install-htgqh"

After running the command to describe the first failed components contains

Name:         install-htgqh
Namespace:    kabanero
Labels:       <none>
Annotations:  <none>
API Version:  operators.coreos.com/v1alpha1
Kind:         InstallPlan
Metadata:
  Creation Timestamp:  2020-01-21T20:13:46Z
  Generate Name:       install-
  Generation:          1
  Owner References:
    API Version:           operators.coreos.com/v1alpha1
    Block Owner Deletion:  false
    Controller:            false
    Kind:                  Subscription
    Name:                  ibm-cp-applications-kabanero
    UID:                   3a5eabd4-ded9-4071-9c69-60c34003ec87
  Resource Version:        266732
  Self Link:               /apis/operators.coreos.com/v1alpha1/namespaces/kabanero/installplans/install-htgqh
  UID:                     1bcef018-a7fa-47a8-8507-57e2660ad37f
Spec:
  Approval:  Automatic
  Approved:  true
  Cluster Service Version Names:
    kabanero-operator.v0.3.4
Status:
  Catalog Sources:
    ibm-cp-applications-catalog
  Conditions:
    Last Transition Time:  2020-01-21T20:13:47Z
    Last Update Time:      2020-01-21T20:13:47Z
    Message:               CustomResourceDefinition.apiextensions.k8s.io "collections.kabanero.io" is invalid: spec.versions: Invalid value: []apiextensions.CustomResourceDefinitionVersion{apiextensions.CustomResourceDefinitionVersion{Name:"v1alpha1", Served:true, Storage:true, Schema:(*apiextensions.CustomResourceValidation)(0xc02201c0a8), Subresources:(*apiextensions.CustomResourceSubresources)(nil), AdditionalPrinterColumns:[]apiextensions.CustomResourceColumnDefinition(nil)}}: per-version schemas may not all be set to identical values (top-level validation should be used instead)
    Reason:                InstallComponentFailed
    Status:                False
    Type:                  Installed
  Phase:                   Failed
  Plan:
    Resolving:  kabanero-operator.v0.3.4
    Resource:
      Group:     operators.coreos.com
      Kind:      ClusterServiceVersion

If you need the full result output ping me on Slack to share

kaczyns commented 4 years ago

@csantanapr Thanks for blazing the trail here :-) We understand that there are issues installing right now on OCP 4.3. This specific issue relates to the CRD schema validation - when there is just one version of the schema, it is supposed to be declared at the "top level", outside of the versions array. The version of operator-sdk that we used to generate this specific schema did not do this. We have to make it compatible with Kube 1.16, then make sure that's still valid with Kube 1.14, then move on to the next problem.

kaczyns commented 4 years ago

@csantanapr starting with Kabanero 0.5.0 we are using operator-sdk 0.11.0 which generates CRDs which are compatible with Kube 1.16. Would you mind trying to install Kabanero 0.5.0-rc.3?

marikaj123 commented 4 years ago

@kaczyns - Greg raised concern at Ann's release delivery scrum meeting today. Who can help with testing/reproducing this issue?

kaczyns commented 4 years ago

@marikaj123 there is no need to reproduce this issue. We understand that Kabanero 0.5.0 is the first release of Kabanero that supports OCP 4.3.

It looks like the version of ICPA that Carlos is using, was based on Kabanero 0.3.4. ICPA can move up to Kabanero 0.5.0 to fix their issue. Or, if ICPA requires a new release of Kabanero 0.3.x that supports OCP 4.3, then ICPA can request that.

kaczyns commented 4 years ago

I've spoken to Carlos and Marika, and we agreed to close this issue since Kabanero release 0.5.0 supports OCP 4.3. The ICPA matter will be handled separately in ICPA's repository.

arobinson7532 commented 4 years ago

CP4Apps 4.0.0 uses Kabenero 0.4 release which has this issue.

kaczyns commented 4 years ago

@arobinson7532 Hi - I thought that ICPA and CP4Apps were the same thing.

marikaj123 commented 4 years ago

Based on the schedule, the content for Kabanero 0.4.0, 0.5.0 and 0.6.0 are going into v4.1.0. In 4Q19, we published Kabanero v0.3.0.

arobinson7532 commented 4 years ago

I agree with closing this issue and tracking it in the other github issue