kyma: skr-aws-svcat-migration-dev job fails all the time

Description

The tests fails on smctl login:

  1) SKR SVCAT migration test
       Should provision new ServiceManager platform:
     Error: failed "smctl login -a https://service-manager.cfapps.sap.hana.ondemand.com --param subdomain=e2etestingscmigration --auth-flow client-credentials": Error: could not login
Reason: auth error: Client Authentication failed.
      at Object.provisionPlatform (skr-svcat-migration-test/test-helpers.js:202:15)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async Context.<anonymous> (skr-svcat-migration-test/skr-svcat-migration-test.js:44:21)

Job history: https://status.build.kyma-project.io/job-history/gs/kyma-prow-logs/logs/skr-aws-svcat-migration-dev Sample failed test log: https://storage.googleapis.com/kyma-prow-logs/logs/skr-aws-svcat-migration-dev/1470302568000262144/build-log.txt

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 22 (22 by maintainers)

Most upvoted comments

currently, the failure is related to the btp-operator selfsigned cert. There was a request to move btp-operator to a different namespace which was done in https://github.tools.sap/kyma/management-plane-config/pull/1304, but the self-signed cert was not adjusted.

binding 'func-sb-svcat-html5-apps-repo-1' in namespace 'default' failed: 'Internal error occurred: failed calling webhook "mservicebinding.kb.io": Post "https://sap-btp-operator-webhook-service.kyma-system.svc:443/mutate-services-cloud-sap-com-v1alpha1-servicebinding?timeout=10s": x509: certificate is valid for sap-btp-operator-webhook-service.sap-btp-operator.svc, sap-btp-operator-webhook-service.sap-btp-operator.svc.cluster.local, not sap-btp-operator-webhook-service.kyma-system.svc'

fwiw, the sc-removal was supposed to be deprecated by sc-migration reconciler but constant shift in priorities slowed down that development. I don’t think it is worth the effort at the moment to work on addressing all other issues with sc-removal chart and rather we should finish the sc-migration reconciler task.

wozniakjan on Jan 12, 2022

Resolving sc-removal issues will require additional work with custom reconciler, but it does not block Kyma 2.0 release, only the service management migration (cc: @wozniakjan )

Problems with ClusterServiceBrokers being unavailable on the clusters in tests were mitigated by adding initContainer to service-manager-proxy and will be cherry-picked here:

Regarding those, I am removing release-blocker label from this one.

ksputo on Jan 10, 2022

One of the root issue was that service-manager-proxy with concurrent installation by reconciler was trying to create ClusterServiceBrokers when service-catalog components were not ready yet:

time="2021-12-30T09:45:54Z" level=error msg="Internal error occurred: failed calling webhook \"mutating.clusterservicebrokers.servicecatalog.k8s.io\": Post \"https://service-catalog-catalog-webhook.kyma-system.svc:443/mutating-clusterservicebrokers?timeout=30s\": no endpoints available for service \"service-catalog-catalog-webhook\"" component="reconcile/task_scheduler.go:43" correlation_id=0293c363-71ef-4222-a4ef-5faf97ad4bd3

This one was resolved in: https://github.com/kyma-project/kyma/pull/12959

ksputo on Dec 30, 2021

Status: ticket created for SM team, still noone assigned on their side. Bumped NGPBUG ticket priority to critical.

PK85 on Dec 20, 2021