Could not find instance 425596b8-7d39-4f94-b501-7b676491f203 associated with job state

Question

Could not find instance 425596b8-7d39-4f94-b501-7b676491f203 associated with job state

cmoulliard opened this issue 4 years ago · 12 comments

Issue

When we create a serviceInstance of by example the serviceclass = dh-postgresql-apb

apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  name: postgresql
spec:
  clusterServiceClassExternalName: dh-postgresql-apb
  clusterServicePlanExternalName: dev
  parameters:
    postgresql_user: "luke"
    postgresql_password: "secret"
    postgresql_database: "my_data"
    postgresql_version: "9.6"

then we got the following error reported within the log of the automation-broker

[2020-04-03T13:42:39.3Z] [INFO] - Request: "PUT /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203?accepts_incomplete=true HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nContent-Length: 475\r\nContent-Type: application/json\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n{\"service_id\":\"1dda1477cace09730bd8ed7a6505607e\",\"plan_id\":\"7f4a5e35e4af2beb70076e72fab0b7ff\",\"organization_guid\":\"c65cf603-8cdd-4067-9812-544e8b733f50\",\"space_guid\":\"1f946bd9-f56b-4be9-81f2-8b9f19881d8c\",\"parameters\":{\"postgresql_database\":\"admin\",\"postgresql_password\":\"admin\",\"postgresql_user\":\"admin\",\"postgresql_version\":9.6},\"context\":{\"clusterid\":\"c65cf603-8cdd-4067-9812-544e8b733f50\",\"instance_name\":\"postgresql1\",\"namespace\":\"cf-workloads\",\"platform\":\"kubernetes\"}}"
[2020-04-03T13:42:39.301Z] [DEBUG] - Auto Escalate has been set to true, we are escalating permissions
[2020-04-03T13:42:39.301Z] [DEBUG] - get spec: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:39.306Z] [DEBUG] - Injecting PlanID as parameter: { _apb_plan_id: dev }
[2020-04-03T13:42:39.306Z] [DEBUG] - Injecting ServiceClassID as parameter: { _apb_service_class_id: 1dda1477cace09730bd8ed7a6505607e }
[2020-04-03T13:42:39.306Z] [DEBUG] - Injecting ServiceInstanceID as parameter: { _apb_service_instance_id: 425596b8-7d39-4f94-b501-7b676491f203 }
[2020-04-03T13:42:39.306Z] [DEBUG] - Injecting lastRequestingUserKey as parameter: { _apb_last_requesting_user: system:serviceaccount:catalog:service-catalog-controller-manager }
[2020-04-03T13:42:39.306Z] [DEBUG] - get service instance: 425596b8-7d39-4f94-b501-7b676491f203
[2020-04-03T13:42:39.309Z] [DEBUG] - set service instance: 425596b8-7d39-4f94-b501-7b676491f203
[2020-04-03T13:42:39.317Z] [INFO] - ASYNC provisioning in progress
10.244.0.1 - - [03/Apr/2020:13:42:39 +0000] "PUT /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203?accepts_incomplete=true HTTP/1.1" 202 58
time="2020-04-03T13:42:39Z" level=info msg="============================================================"
time="2020-04-03T13:42:39Z" level=info msg="                       PROVISIONING                         "
time="2020-04-03T13:42:39Z" level=info msg="============================================================"
time="2020-04-03T13:42:39Z" level=info msg="Spec.ID: 1dda1477cace09730bd8ed7a6505607e"
time="2020-04-03T13:42:39Z" level=info msg="Spec.Name: dh-postgresql-apb"
time="2020-04-03T13:42:39Z" level=info msg="Spec.Image: docker.io/ansibleplaybookbundle/postgresql-apb:v3.10"
time="2020-04-03T13:42:39Z" level=info msg="Spec.Description: SCL PostgreSQL apb implementation"
time="2020-04-03T13:42:39Z" level=info msg="============================================================"
time="2020-04-03T13:42:39Z" level=info msg="Checking if namespace %s exists.cf-workloads"
[2020-04-03T13:42:39.317Z] [DEBUG] - JobStateSubscriber Notify : msg state {7b53b814-c981-444c-8157-8038a1c1555d in progress  provision  action started}
[2020-04-03T13:42:39.318Z] [DEBUG] - set job state for instance: 425596b8-7d39-4f94-b501-7b676491f203 token: 7b53b814-c981-444c-8157-8038a1c1555d
time="2020-04-03T13:42:39Z" level=info msg="Creating RoleBinding apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7"
time="2020-04-03T13:42:39Z" level=info msg="Creating RoleBinding apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7"
time="2020-04-03T13:42:39Z" level=info msg="Successfully created apb sandbox: [ %s ], with %s permissions in namespace %sapb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7editdh-postgresql-apb-prov-2mzx8"
time="2020-04-03T13:42:39Z" level=info msg="Running post create sandbox fuctions if defined."
time="2020-04-03T13:42:39Z" level=info msg="Creating pod \"apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7\" in the dh-postgresql-apb-prov-2mzx8 namespace"
[2020-04-03T13:42:40.324Z] [DEBUG] - user found, returning true
[2020-04-03T13:42:40.324Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:42:40.324Z] [INFO] - Request: "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:42:40.324Z] [DEBUG] - service_id: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:40.324Z] [DEBUG] - plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff
[2020-04-03T13:42:40.324Z] [DEBUG] - operation:  7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:40.33Z] [DEBUG] - state: in progress
[2020-04-03T13:42:40.33Z] [DEBUG] - description: action started
10.244.0.1 - - [03/Apr/2020:13:42:40 +0000] "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 200 64
[2020-04-03T13:42:42.337Z] [DEBUG] - user found, returning true
[2020-04-03T13:42:42.338Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:42:42.338Z] [INFO] - Request: "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:42:42.338Z] [DEBUG] - service_id: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:42.338Z] [DEBUG] - plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff
[2020-04-03T13:42:42.338Z] [DEBUG] - operation:  7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:42.349Z] [DEBUG] - state: in progress
[2020-04-03T13:42:42.349Z] [DEBUG] - description: action started
10.244.0.1 - - [03/Apr/2020:13:42:42 +0000] "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 200 64
[2020-04-03T13:42:46.356Z] [DEBUG] - user found, returning true
[2020-04-03T13:42:46.357Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:42:46.357Z] [INFO] - Request: "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:42:46.357Z] [DEBUG] - service_id: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:46.357Z] [DEBUG] - plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff
[2020-04-03T13:42:46.357Z] [DEBUG] - operation:  7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:46.362Z] [DEBUG] - state: in progress
[2020-04-03T13:42:46.363Z] [DEBUG] - description: action started
10.244.0.1 - - [03/Apr/2020:13:42:46 +0000] "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 200 64
time="2020-04-03T13:42:46Z" level=error msg="Provision or Update action failed - Pod [ apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7 ] failed with exit code [2]"
time="2020-04-03T13:42:46Z" level=info msg="Destroying APB sandbox..."
time="2020-04-03T13:42:46Z" level=info msg="Successfully deleted rolebinding apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7, namespace dh-postgresql-apb-prov-2mzx8"
time="2020-04-03T13:42:46Z" level=info msg="Successfully deleted rolebinding apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7, namespace cf-workloads"
time="2020-04-03T13:42:46Z" level=error msg="Provision APB error: Pod [ apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7 ] failed with exit code [2]"
[2020-04-03T13:42:46.517Z] [ERROR] - broker::provision error occurred. Pod [ apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7 ] failed with exit code [2]
[2020-04-03T13:42:46.517Z] [DEBUG] - closing channel for job 7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:46.517Z] [DEBUG] - JobStateSubscriber Notify : msg state {7b53b814-c981-444c-8157-8038a1c1555d failed  provision Pod [ apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7 ] failed with exit code [2] Error occurred during provision. Please contact administrator if the issue persists.}
[2020-04-03T13:42:46.517Z] [DEBUG] - set job state for instance: 425596b8-7d39-4f94-b501-7b676491f203 token: 7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:54.374Z] [DEBUG] - user found, returning true
[2020-04-03T13:42:54.374Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:42:54.374Z] [INFO] - Request: "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:42:54.375Z] [DEBUG] - service_id: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:54.375Z] [DEBUG] - plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff
[2020-04-03T13:42:54.375Z] [DEBUG] - operation:  7b53b814-c981-444c-8157-8038a1c1555d
[2020-04-03T13:42:54.381Z] [DEBUG] - state: failed
[2020-04-03T13:42:54.381Z] [DEBUG] - description: Error occurred during provision. Please contact administrator if the issue persists.
[2020-04-03T13:42:54.381Z] [DEBUG] - job state has an error. Assuming that any error here is human readable. err - Pod [ apb-18e33c3a-e28a-4b4c-ba94-1a6b1705b1f7 ] failed with exit code [2]
10.244.0.1 - - [03/Apr/2020:13:42:54 +0000] "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=7b53b814-c981-444c-8157-8038a1c1555d&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 200 129
[2020-04-03T13:42:54.402Z] [DEBUG] - user found, returning true
[2020-04-03T13:42:54.402Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:42:54.402Z] [INFO] - Request: "DELETE /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203?accepts_incomplete=true&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:42:54.402Z] [DEBUG] - get service instance: 425596b8-7d39-4f94-b501-7b676491f203
[2020-04-03T13:42:54.405Z] [DEBUG] - get spec: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:42:54.41Z] [DEBUG] - Auto Escalate has been set to true, we are escalating permissions
[2020-04-03T13:42:54.414Z] [INFO] - All Jobs for instance: 425596b8-7d39-4f94-b501-7b676491f203 in state:  in progress -
[]apb.JobState{}
time="2020-04-03T13:42:54Z" level=error msg="Unable to load secret '425596b8-7d39-4f94-b501-7b676491f203' from namespace 'automation-broker'"
time="2020-04-03T13:42:54Z" level=error msg="unable to get secret data for 425596b8-7d39-4f94-b501-7b676491f203, in namespace: automation-broker"
[2020-04-03T13:42:54.416Z] [INFO] - ASYNC deprovision in progress
10.244.0.1 - - [03/Apr/2020:13:42:54 +0000] "DELETE /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203?accepts_incomplete=true&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 202 58
time="2020-04-03T13:42:54Z" level=info msg="============================================================"
time="2020-04-03T13:42:54Z" level=info msg="                      DEPROVISIONING                        "
time="2020-04-03T13:42:54Z" level=info msg="============================================================"
time="2020-04-03T13:42:54Z" level=info msg="ServiceInstance.Id: 1dda1477cace09730bd8ed7a6505607e"
time="2020-04-03T13:42:54Z" level=info msg="ServiceInstance.Name: dh-postgresql-apb"
time="2020-04-03T13:42:54Z" level=info msg="ServiceInstance.Image: docker.io/ansibleplaybookbundle/postgresql-apb:v3.10"
time="2020-04-03T13:42:54Z" level=info msg="ServiceInstance.Description: SCL PostgreSQL apb implementation"
time="2020-04-03T13:42:54Z" level=info msg="============================================================"
[2020-04-03T13:42:54.417Z] [DEBUG] - JobStateSubscriber Notify : msg state {ef26e68b-94df-4215-873a-d867ba6009a5 in progress  deprovision  action started}
[2020-04-03T13:42:54.417Z] [DEBUG] - set job state for instance: 425596b8-7d39-4f94-b501-7b676491f203 token: ef26e68b-94df-4215-873a-d867ba6009a5
time="2020-04-03T13:42:54Z" level=info msg="Creating RoleBinding apb-af3134e5-3d27-41b6-9b77-adf7cb368ce8"
time="2020-04-03T13:42:54Z" level=info msg="Creating RoleBinding apb-af3134e5-3d27-41b6-9b77-adf7cb368ce8"
time="2020-04-03T13:42:54Z" level=info msg="Successfully created apb sandbox: [ %s ], with %s permissions in namespace %sapb-af3134e5-3d27-41b6-9b77-adf7cb368ce8editdh-postgresql-apb-depr-5pxm8"
time="2020-04-03T13:42:54Z" level=info msg="Running post create sandbox fuctions if defined."
time="2020-04-03T13:42:54Z" level=info msg="Creating pod \"apb-af3134e5-3d27-41b6-9b77-adf7cb368ce8\" in the dh-postgresql-apb-depr-5pxm8 namespace"
time="2020-04-03T13:43:00Z" level=info msg="Destroying APB sandbox..."
[2020-04-03T13:43:00.971Z] [DEBUG] - closing channel for job ef26e68b-94df-4215-873a-d867ba6009a5
[2020-04-03T13:43:00.971Z] [DEBUG] - JobStateSubscriber Notify : msg state {ef26e68b-94df-4215-873a-d867ba6009a5 succeeded  deprovision  deprovision job completed}
[2020-04-03T13:43:00.971Z] [DEBUG] - set job state for instance: 425596b8-7d39-4f94-b501-7b676491f203 token: ef26e68b-94df-4215-873a-d867ba6009a5
[2020-04-03T13:43:00.98Z] [DEBUG] - JobStateSubscriber handleSucceeded : msg state {ef26e68b-94df-4215-873a-d867ba6009a5 succeeded  deprovision  deprovision job completed}
[2020-04-03T13:43:00.98Z] [DEBUG] - JobStateSubscriber cleanupAfterDeprovision : msg state {ef26e68b-94df-4215-873a-d867ba6009a5 succeeded  deprovision  deprovision job completed}
[2020-04-03T13:43:00.98Z] [DEBUG] - Dao::DeleteServiceInstance -> [ 425596b8-7d39-4f94-b501-7b676491f203 ]
time="2020-04-03T13:43:00Z" level=info msg="Successfully deleted rolebinding apb-af3134e5-3d27-41b6-9b77-adf7cb368ce8, namespace dh-postgresql-apb-depr-5pxm8"
time="2020-04-03T13:43:00Z" level=info msg="Successfully deleted rolebinding apb-af3134e5-3d27-41b6-9b77-adf7cb368ce8, namespace cf-workloads"
[2020-04-03T13:43:10.401Z] [DEBUG] - user found, returning true
[2020-04-03T13:43:10.401Z] [DEBUG] - We found one. HOORAY!
[2020-04-03T13:43:10.401Z] [INFO] - Request: "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=ef26e68b-94df-4215-873a-d867ba6009a5&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1\r\nHost: broker.automation-broker.svc:1338\r\nAccept-Encoding: gzip\r\nAuthorization: Basic YWRtaW46YWRtaW4=\r\nUser-Agent: Go-http-client/1.1\r\nX-Broker-Api-Originating-Identity: kubernetes eyJ1c2VybmFtZSI6InN5c3RlbTpzZXJ2aWNlYWNjb3VudDpjYXRhbG9nOnNlcnZpY2UtY2F0YWxvZy1jb250cm9sbGVyLW1hbmFnZXIiLCJ1aWQiOiI5NjdlOWQ0NS05OWJmLTQ4OWUtOGVlZS05NzYzNzIyMTM2MWQiLCJncm91cHMiOlsic3lzdGVtOnNlcnZpY2VhY2NvdW50cyIsInN5c3RlbTpzZXJ2aWNlYWNjb3VudHM6Y2F0YWxvZyIsInN5c3RlbTphdXRoZW50aWNhdGVkIl19\r\nX-Broker-Api-Version: 2.13\r\n\r\n"
[2020-04-03T13:43:10.401Z] [DEBUG] - service_id: 1dda1477cace09730bd8ed7a6505607e
[2020-04-03T13:43:10.401Z] [DEBUG] - plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff
[2020-04-03T13:43:10.401Z] [DEBUG] - operation:  ef26e68b-94df-4215-873a-d867ba6009a5
[2020-04-03T13:43:10.407Z] [ERROR] - Could not find instance 425596b8-7d39-4f94-b501-7b676491f203 associated with job state ef26e68b-94df-4215-873a-d867ba6009a5 - bundleinstances.automationbroker.io "425596b8-7d39-4f94-b501-7b676491f203" not found
[2020-04-03T13:43:10.407Z] [WARNING] - unable to find job state: [425596b8-7d39-4f94-b501-7b676491f203]. error: [bundleinstances.automationbroker.io "425596b8-7d39-4f94-b501-7b676491f203" not found]
10.244.0.1 - - [03/Apr/2020:13:43:10 +0000] "GET /ansible-service-broker/v2/service_instances/425596b8-7d39-4f94-b501-7b676491f203/last_operation?operation=ef26e68b-94df-4215-873a-d867ba6009a5&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 410 37

and serviceinstance dont at all provision a service

kc get serviceinstance/postgresql -n cf-workloads -o yaml
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"servicecatalog.k8s.io/v1beta1","kind":"ServiceInstance","metadata":{"annotations":{},"name":"postgresql","namespace":"cf-workloads"},"spec":{"clusterServiceClassExternalName":"dh-postgresql-apb","clusterServicePlanExternalName":"dev","parameters":{"postgresql_database":"my_data","postgresql_password":"secret","postgresql_user":"luke","postgresql_version":"9.6"}}}
  creationTimestamp: "2020-04-03T14:00:03Z"
  finalizers:
  - kubernetes-incubator/service-catalog
  generation: 2
  labels:
    servicecatalog.k8s.io/spec.clusterServiceClassRef.name: 7cc0b384c5e60c0bf9a73dcb722e607526f659e10f5b7db8d47d65f1
    servicecatalog.k8s.io/spec.clusterServicePlanRef.name: a48e95350ffc705453e1b5048a69d9df9181df32990cba0726394a07
  name: postgresql
  namespace: cf-workloads
  resourceVersion: "239864"
  selfLink: /apis/servicecatalog.k8s.io/v1beta1/namespaces/cf-workloads/serviceinstances/postgresql
  uid: 09df082a-189e-4b6e-a68f-47b98cfd9dfc
spec:
  clusterServiceClassExternalName: dh-postgresql-apb
  clusterServiceClassRef:
    name: 1dda1477cace09730bd8ed7a6505607e
  clusterServicePlanExternalName: dev
  clusterServicePlanRef:
    name: 7f4a5e35e4af2beb70076e72fab0b7ff
  externalID: d423b78c-dcd0-4428-8b40-99096f30d21a
  parameters:
    postgresql_database: my_data
    postgresql_password: secret
    postgresql_user: luke
    postgresql_version: "9.6"
  updateRequests: 0
  userInfo:
    groups:
    - system:serviceaccounts
    - system:serviceaccounts:catalog
    - system:authenticated
    uid: 967e9d45-99bf-489e-8eee-97637221361d
    username: system:serviceaccount:catalog:service-catalog-controller-manager
status:
  asyncOpInProgress: true
  conditions:
  - lastTransitionTime: "2020-04-03T14:00:04Z"
    message: The instance is being deprovisioned asynchronously
    reason: Deprovisioning
    status: "False"
    type: Ready
  - lastTransitionTime: "2020-04-03T14:00:11Z"
    message: 'Provision call failed: Error occurred during provision. Please contact
      administrator if the issue persists.'
    reason: ProvisionCallFailed
    status: "True"
    type: Failed
  - lastTransitionTime: "2020-04-03T14:00:11Z"
    message: 'Provision call failed: Error occurred during provision. Please contact
      administrator if the issue persists.'
    reason: ProvisionCallFailed
    status: "True"
    type: OrphanMitigation
  currentOperation: Provision
  deprovisionStatus: Required
  inProgressProperties:
    clusterServicePlanExternalID: 7f4a5e35e4af2beb70076e72fab0b7ff
    clusterServicePlanExternalName: dev
    parameterChecksum: f5626b04b46be0949a4f84c4940b3f79c8e58d5138d15c1595600e1dfa54679e
    parameters:
      postgresql_database: my_data
      postgresql_password: secret
      postgresql_user: luke
      postgresql_version: "9.6"
    userInfo:
      groups:
      - system:serviceaccounts
      - system:serviceaccounts:catalog
      - system:authenticated
      uid: 967e9d45-99bf-489e-8eee-97637221361d
      username: system:serviceaccount:catalog:service-catalog-controller-manager
  lastConditionState: OrphanMitigation
  lastOperation: 60f8153d-de2b-4887-9900-1fe0a45e7017
  observedGeneration: 2
  operationStartTime: "2020-04-03T14:00:04Z"
  orphanMitigationInProgress: true
  provisionStatus: ""
  reconciledGeneration: 0
  userSpecifiedClassName: ClusterServiceClass/dh-postgresql-apb
  userSpecifiedPlanName: dev

jmrodri commented 4 years ago

/close

Answer 1 · 2020-04-06T14:01:16.000Z

TBH from the brokers perspective, this looks reasonable:

We attempted to create a service by running the APB, the APB failed and the service catalog attempts deprovision.

I would suggest that you look into why the APB is failing, to figure out the root cause of the issue.

Answer 2 · 2020-04-06T14:44:04.000Z

@shawn-hurley How can I then find the log about of the pod created to install the APB - Service (= PostgreSQL) ?

A pod and namespace is created but pod is terminating immediately

dh-postgresql-apb-prov-rkjjx   apb-b390a898-6dd0-4f37-9c21-f9a016032e36                       0/1     Error              0          7s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     Pending            0          0s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     Pending            0          0s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     ContainerCreating   0          0s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       1/1     Running             0          2s
dh-postgresql-apb-prov-rkjjx   apb-b390a898-6dd0-4f37-9c21-f9a016032e36                       0/1     Terminating         0          12s
dh-postgresql-apb-prov-rkjjx   apb-b390a898-6dd0-4f37-9c21-f9a016032e36                       0/1     Terminating         0          12s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     Completed           0          6s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     Terminating         0          12s
dh-postgresql-apb-depr-5nqsr   apb-0100e739-ee13-4b01-923f-7d3eb24decb4                       0/1     Terminating         0          12s

Answer 3 · 2020-04-06T16:56:55.000Z

If I look to the log of the ansible broker, there is an exit 2 error but I have no idea how we could get more info ...

10.244.0.1 - - [06/Apr/2020:16:53:12 +0000] "GET /ansible-service-broker/v2/service_instances/9dddb9b5-b972-4448-b205-9567a93f9f88/last_operation?operation=6b5dc602-6ac2-4df9-ae9c-7c8e112c00ae&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 200 64
time="2020-04-06T16:53:16Z" level=error msg="Provision or Update action failed - Pod [ apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc ] failed with exit code [2]"
time="2020-04-06T16:53:16Z" level=info msg="Destroying APB sandbox..."
time="2020-04-06T16:53:16Z" level=info msg="Successfully deleted rolebinding apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc, namespace dh-postgresql-apb-prov-mczr9"
time="2020-04-06T16:53:16Z" level=info msg="Successfully deleted rolebinding apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc, namespace demo"
time="2020-04-06T16:53:16Z" level=error msg="unable to delete the network policy object - networkpolicies.networking.k8s.io \"apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc\" not found"
time="2020-04-06T16:53:16Z" level=error msg="Provision APB error: Pod [ apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc ] failed with exit code [2]"
[2020-04-06T16:53:16.621Z] [ERROR] - broker::provision error occurred. Pod [ apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc ] failed with exit code [2]
[2020-04-06T16:53:16.621Z] [DEBUG] - closing channel for job 6b5dc602-6ac2-4df9-ae9c-7c8e112c00ae
[2020-04-06T16:53:16.621Z] [DEBUG] - JobStateSubscriber Notify : msg state {6b5dc602-6ac2-4df9-ae9c-7c8e112c00ae failed  provision Pod [ apb-be57e0a6-e40d-4a4a-882d-e84ae3965ddc ] failed with exit code [2] Error occurred during provision. Please contact administrator if the issue persists.}

Answer 4 · 2020-04-06T16:57:28.000Z

Can you get the logs of the APB pod?

Answer 5 · 2020-04-06T17:13:15.000Z

Is the APB pod that you refers this one dh-postgresql-apb-depr-5nqsr by example ? If your answer is yes, then I cannot provide you the log as the pod and temporary namespace have been deleted directly.
@shawn-hurley

kc get pods -A
NAMESPACE                      NAME                                                           READY   STATUS      RESTARTS   AGE
dh-postgresql-apb-depr-259mm   apb-b3f9aa9b-2767-49ea-afa4-492b215dc4f0                       1/1     Running     0          5s
$ kubectl logs -n dh-postgresql-apb-depr-259mm apb-b3f9aa9b-2767-49ea-afa4-492b215dc4f0
Error from server (NotFound): namespaces "dh-postgresql-apb-depr-259mm" not found

Answer 6 · 2020-04-07T05:26:29.000Z

I think that I know the reason which is perhaps due to a RBAC problem.

I'm nevertheless still surprised to see that the namespace is terminating. Here is error reported within the controller --> kubectl logs -n kube-system pod/kube-controller-manager-h01-116 | grep apb-b3f9aa9b

E0406 17:15:56.229525       1 tokens_controller.go:260] error 
synchronizing serviceaccount dh-postgresql-apb-depr-259mm/apb-b3f9aa9b-2767-49ea-afa4-492b215dc4f0: 
secrets "apb-b3f9aa9b-2767-49ea-afa4-492b215dc4f0-token-9qwx2" is forbidden: 
unable to create new content in namespace dh-postgresql-apb-depr-259mm 
because it is being terminated

Answer 7 · 2020-04-07T07:29:56.000Z

I installed the tool stern in order to try to capture the log of the pod created and here is the outcome

stern --all-namespaces -l apb-fqname=dh-postgresql-apb
+ dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 › apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb PLAY [Deploy rhscl-postgresql-apb to "kubernetes"] *****************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [ansible.kubernetes-modules : Install latest openshift client] ************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [ansibleplaybookbundle.asb-modules : debug] *******************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : Find pod we need to update] ***********************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : Find dc we will clean up] *************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : Find deployment we will clean up] *****************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : Create db backup directory] ***********************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : Backup source database] ***************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : rsync db backup to apb] ***************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb skipping: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : set service state to present] *********************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb changed: [localhost]
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : include_tasks] ************************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb included: /opt/ansible/roles/rhscl-postgresql-apb/tasks/dev.yml for localhost
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : set development deployment config state to present] ***
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb fatal: [localhost]: FAILED! => {"changed": false, "error": 404, "msg": "Failed to create object: the server could not find the requested resource"}
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb PLAY RECAP *********************************************************************
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb localhost                  : ok=2    changed=1    unreachable=0    failed=1
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb
+ dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a › apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb PLAY [Deploy rhscl-postgresql-apb to "kubernetes"] *****************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [ansible.kubernetes-modules : Install latest openshift client] ************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [ansibleplaybookbundle.asb-modules : debug] *******************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Find pod we need to update] ***********************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Find dc we will clean up] *************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Find deployment we will clean up] *****************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Create db backup directory] ***********************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Backup source database] ***************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : rsync db backup to apb] ***************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : set service state to absent] **********************
- dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb changed: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : include_tasks] ************************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb included: /opt/ansible/roles/rhscl-postgresql-apb/tasks/dev.yml for localhost
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : set development deployment config state to absent] ***
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb ok: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : set development deployment config state to absent] ***
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : include_tasks] ************************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Wait for postgres to come up] *********************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Find pod we need to restore] **********************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : rsync db backup to new pod] ***********************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Restore database] *********************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Remove deployment config] *************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : Remove deployment] ********************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : ensure production volume is absent] ***************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost] => (item=9.4)
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost] => (item=9.5)
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost] => (item=9.6)
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb TASK [rhscl-postgresql-apb : encode bind credentials] **************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb skipping: [localhost]
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb PLAY RECAP *********************************************************************
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb localhost                  : ok=3    changed=1    unreachable=0    failed=0
dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a apb
- dh-postgresql-apb-depr-5nftr apb-0729e971-cda1-4e4f-a78e-90c744e0611a

Is the problem related to this error ?

dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb TASK [rhscl-postgresql-apb : set development deployment config state to present] ***
dh-postgresql-apb-prov-jmr24 apb-74603300-da82-4c7e-ab67-fb3dbbecae33 apb fatal: [localhost]: FAILED! => {"changed": false, "error": 404, "msg": "Failed to create object: the server could not find the requested resource"}

Can the apb playbook be executed on a plain kubernetes cluster and not okd ?

@shawn-hurley @camilamacedo86 @jmontleon

Answer 8 · 2020-04-07T19:00:14.000Z

Probably not, it Looks like it is attempting to create a deployment config which will not be an api that is available on k8s.

Answer 9 · 2020-04-08T12:16:20.000Z

deployment config

I dont think so because if you look to the template part of the apb, then there is if/else condition.

Answer 10 · 2020-04-08T12:16:55.000Z

FYI: The problem has been fixed after moving to the latest/canary image of the postgresql APB.

Answer 11 · 2020-09-20T01:20:04.000Z

@jmrodri: Closing this issue.

In response to this:

/close

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.