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

Release 0.7.0 breaks selection of multiple services #944

Closed
nastacio opened this issue Apr 9, 2021 · 2 comments · Fixed by #955
Closed

Release 0.7.0 breaks selection of multiple services #944

nastacio opened this issue Apr 9, 2021 · 2 comments · Fixed by #955
Labels
kind/bug Something isn't working
Milestone

Comments

@nastacio
Copy link

nastacio commented Apr 9, 2021

What is the environment (Minikube, Openshift)?

OpenShift 4.6.22, on IBM Cloud

What is the SBO version used?

0.7.0

(this example was working in 0.6.0 and stopped working in 0.7.0)

What are the steps to reproduce this issue?

  1. Create one application and two services
  2. Create a service binding request between the application and the two services
  3. Reference the service fields in the mappings section of the binding request
  4. Apply the resulting YAML to the cluster
oc new project sbo
oc new-app https://github.com/openshift/ruby-hello-world#beta4 -n sbo
oc apply sb-original.yaml
oc apply sb-reverse.yaml

What is the expected behaviour?

All mapped values should be present in the final Secret objects created from the binding.

What is the actual behaviour?

Only the mapped values from the one of the services (last in file?) appear in the secrets.
The mapped values from the other services are empty.

See two outputs:

oc get secret binding-original-f999dd17  -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq .
{
  "Values": [
    {
      "HOST": "ruby-hello-world.sbo.svc.cluster.local",
      "SOURCE": "<no value>"
    }
  ]
}
root@6d37c76e5d2e:/tools/scripts# oc get secret binding-reverse-18a1300e   -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq .
{
  "Values": [
    {
      "HOST": "<no value>.<no value>.svc.cluster.local",
      "SOURCE": "beta4"
    }
  ]
}

Service Binding Operator Logs

operator-logs.txt

Additional Information (Screenshots, etc)

sb-example-archive.zip
(contains sb-reverse.yaml and sb-original.yaml)

I rolled back the operator to 0.6.0 and saw the correct results again:

 oc get secret binding-original-6f93c924eb98fbd528c74b610b632229352734c1  -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq .
{
  "Values": [
    {
      "HOST": "ruby-hello-world.sbo.svc.cluster.local",
      "SOURCE": "beta4"
    }
  ]
}

oc get secret binding-reverse-6f93c924eb98fbd528c74b610b632229352734c1 -n sbo -o jsonpath='{.data.env\.json}' | base64 -d | jq .
{
  "Values": [
    {
      "HOST": "ruby-hello-world.sbo.svc.cluster.local",
      "SOURCE": "beta4"
    }
  ]
}

@nastacio nastacio added the kind/bug Something isn't working label Apr 9, 2021
@pedjak
Copy link
Contributor

pedjak commented Apr 13, 2021

thanks for the report, I am looking for sb-reverse.yaml and sb-original.yaml but it seems they are not attached?

@nastacio
Copy link
Author

thanks for the report, I am looking for sb-reverse.yaml and sb-original.yaml but it seems they are not attached?

My mistake, ugh, apologies.

I just attached an archive file containing both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants