search

crossplane-contrib / provider-mongodbatlas

MongoDB Atlas Provider based on Terrajet
Apache License 2.0
14 stars 11 forks source link

Fix pipeline #13

Closed Henni closed 1 year ago

Henni commented 1 year ago

WIP

Description of your changes

updating pipeline(s) to work again

Henni commented 1 year ago

I need some help with the e2e tests here: When running make e2e USE_HELM3=true locally, the provider is not starting up. The pod fails with the status executable file not found

  Warning  Failed     15m (x5 over 17m)     kubelet            Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "crossplane-provider": executable file not found in $PATH: unknown

This is after I modified the ControllerConfig to not contain any args. With the initial ControllerConfig it tried to execute the binary -d which for obvious reasons doesn't work. So it seems like the entrypoint (crossplane-provider) isn't executing as expected. I also tried to run the provider manually. I created my own pod config, derived from the e2e generated one, but I passed in a sleep command:

  command: [ "/bin/sh", "-c", "--" ]
  args: [ "while true; do sleep 30; done;" ]

This failed with a "unknown command: /bin/sh". So the whole Docker image inside kind seems to be malfunctioning. Just executing the image with docker run works fine (at least it starts up to tell me that the provider needs an env variable to be set).

I don't understand the whole build pipeline (the makefiles in upbound/build are black magic to me). So I'd highly appreciate some input what might be going on here and why the e2e environment seems to be using a wrong Docker image.