We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
was hoping to try this out but the provider fails to bring up the controller with the following error events:
events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 87s default-scheduler Successfully assigned crossplane-system/provider-jet-vra-c14af35f7654-8cd84f889-9k564 to tap-17-rc-cls-md-0-7922j-856b4c9ddfxbsjp4-664hj Normal Pulling 87s kubelet Pulling image "xpkg.upbound.io/ankasoftco/provider-jet-vra:v0.0.2" Normal Pulled 84s kubelet Successfully pulled image "xpkg.upbound.io/ankasoftco/provider-jet-vra:v0.0.2" in 2.90331347s (2.903325053s including waiting) Warning Failed 84s kubelet Error: failed to generate container "c8ecdfb82f7dc3fee0cb9abe23a5cb5409f2e4f9fd1eee3f73ca29e6270b56ad" spec: failed to generate spec: no command specified Warning Failed 83s kubelet Error: failed to generate container "34b0d5aad5efe9032df1adde3ed060fc84f180a7e259ce7aadacf0f89191d39b" spec: failed to generate spec: no command specified Warning Failed 69s kubelet Error: failed to generate container "f18db5fa8090b3eb4adc050067def7a11a11189e73bc3ede1a58adddd5169589" spec: failed to generate spec: no command specified Warning Failed 56s kubelet Error: failed to generate container "fa6f6814a4a7bde6f889aab5bf840143e29324e8c9038338a1c4ed26685b349b" spec: failed to generate spec: no command specified Warning Failed 41s kubelet Error: failed to generate container "0f10752ed5db521ae7c72d9bc1650e9cd1e44a1598cd710f4f7c033478c25907" spec: failed to generate spec: no command specified Warning Failed 30s kubelet Error: failed to generate container "4d43be32ed96a29ea052c1ab8565e324a95a8272071524b9aa8ba2702b2986b5" spec: failed to generate spec: no command specified Warning Failed 17s kubelet Error: failed to generate container "d398f75c4195cb0c28bfbb3af3248fdda07ac089e5adcf9581e678b95264e85e" spec: failed to generate spec: no command specified Normal Pulled 3s (x7 over 83s) kubelet Container image "xpkg.upbound.io/ankasoftco/provider-jet-vra:v0.0.2" already present on machine Warning Failed 3s kubelet Error: failed to generate container "a5531aa9bd5fa5d8a8e1fbb8519b8020236ee9cd6eb792ef56963af37cac8af4" spec: failed to generate spec: no command specified
The text was updated successfully, but these errors were encountered:
I encountered the same issue.
Sorry, something went wrong.
Think it's the same issue you had with provider-vsphere, could we have the same fix here please.
New version released. The current version is v0.1.0
can it be used directly with esxi?
No branches or pull requests
was hoping to try this out but the provider fails to bring up the controller with the following error events:
The text was updated successfully, but these errors were encountered: