Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Creation of a service fails using cf-service #44

Closed
cmoulliard opened this issue Apr 7, 2020 · 3 comments
Closed

Creation of a service fails using cf-service #44

cmoulliard opened this issue Apr 7, 2020 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@cmoulliard
Copy link

Issue

When we try to create a service or delete it , that fails and minibroker reports errors

cf create-service postgresql 10-8-0 my-postgresql
cf service my-postgresql
Showing info of service my-postgresql in org redhat.com / space demo as admin...
name:             my-postgresql
service:          postgresql
tags:
plan:             10-8-0
description:      Helm Chart for postgresql
documentation:
dashboard:
service broker:   minibroker
Showing status of last operation from service my-postgresql...
status:    create failed
message:   service instance "05c1d5e1-0907-4766-bcff-0e1c9a057f1d" failed to provision
started:   2020-04-07T16:28:37Z
updated:   2020-04-07T16:28:40Z
There are no bound apps for this service.
Upgrades are not supported by this broker.

OR

cf ds -f my-postgresql

Log of minibroker

[snowdrop@h01-116 temp]$ kc logs -n minibroker minibroker-minibroker-798cd8d755-n8bw6 -c minibroker | grep 05c1d5e1-0907-4766-bcff-0e1c9a057f1d
I0407 16:28:37.730041       1 apisurface.go:89] Received ProvisionRequest for instanceID "05c1d5e1-0907-4766-bcff-0e1c9a057f1d"
I0407 16:28:37.730081       1 broker.go:77] Provisioning 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (postgresql/postgresql-10-8-0) in minibroker
I0407 16:28:37.746937       1 broker.go:92] Successfully initiated provisioning 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (postgresql/postgresql-10-8-0) in minibroker
E0407 16:28:39.951269       1 minibroker.go:335] Failed to provision "05c1d5e1-0907-4766-bcff-0e1c9a057f1d": rpc error: code = Unknown desc = validation failed: unable to recognize "": no matches for kind "StatefulSet" in version "apps/v1beta2"
I0407 16:28:40.490011       1 apisurface.go:233] Received LastOperationRequest for instanceID "05c1d5e1-0907-4766-bcff-0e1c9a057f1d"
I0407 16:28:40.490046       1 broker.go:120] Getting last operation of 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (<nil>/<nil>)
I0407 16:28:40.492868       1 broker.go:132] Successfully got last operation of 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (<nil>/<nil>): &{State:failed Description:0xc42008e580}
I0407 16:55:09.477239       1 apisurface.go:169] Received DeprovisionRequest for instanceID "05c1d5e1-0907-4766-bcff-0e1c9a057f1d"
I0407 16:55:09.477299       1 broker.go:97] Deprovisioning 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (postgresql/postgresql-10-8-0)
I0407 16:55:09.491970       1 broker.go:114] Successfully initiated deprovisioning 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (postgresql/postgresql-10-8-0)
E0407 16:55:09.493592       1 minibroker.go:600] Failed to deprovision "05c1d5e1-0907-4766-bcff-0e1c9a057f1d": could not delete release : rpc error: code = Unknown desc = no release provided
I0407 16:55:12.711746       1 apisurface.go:233] Received LastOperationRequest for instanceID "05c1d5e1-0907-4766-bcff-0e1c9a057f1d"
I0407 16:55:12.711791       1 broker.go:120] Getting last operation of 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (<nil>/<nil>)
I0407 16:55:12.715522       1 broker.go:132] Successfully got last operation of 05c1d5e1-0907-4766-bcff-0e1c9a057f1d (<nil>/<nil>): &{State:failed Description:0xc42044fb70}
@f0rmiga
Copy link
Contributor

f0rmiga commented Jun 4, 2020

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 4, 2020
@f0rmiga
Copy link
Contributor

f0rmiga commented Jun 4, 2020

@cmoulliard Thanks for reporting this. We will investigate.

@f0rmiga
Copy link
Contributor

f0rmiga commented Jul 22, 2020

@cmoulliard The problem is with the API version used for the statefulset on the chart that the plan 10-8-0 uses:
https://github.com/helm/charts/blob/637a0bd43ded93bcb6c7ee497c2f0610fbf95a0e/stable/postgresql/templates/statefulset.yaml#L1

It's quite old. Can you go for PG 11? Another alternative (not so trivial) is to provide your own Helm registry with the chart patched to use the new API version.

@f0rmiga f0rmiga closed this as completed Aug 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants