provider-vsphere Failure on Install

[noshmak78]

Hello Team,

Tried installing Provider Vsphere on cluster but its failing to create container. Below are errors recieved:

Provider Description:

Name:         provider-vsphere
Namespace:    
Labels:       <none>
Annotations:  <none>
API Version:  pkg.crossplane.io/v1
Kind:         Provider
Metadata:
  Creation Timestamp:  2024-08-08T05:51:06Z
  Generation:          1
  Resource Version:    739939420
  UID:                 48bcbbaa-42ab-4fc1-a0fc-b95d0581b828
Spec:
  Ignore Crossplane Constraints:  false
  Package:                        xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1
  Package Pull Policy:            IfNotPresent
  Revision Activation Policy:     Automatic
  Revision History Limit:         1
  Runtime Config Ref:
    API Version:               pkg.crossplane.io/v1beta1
    Kind:                      DeploymentRuntimeConfig
    Name:                      default
  Skip Dependency Resolution:  false
Status:
  Conditions:
    Last Transition Time:  2024-08-08T05:51:36Z
    Message:               post establish runtime hook failed for package: provider package deployment is unavailable with message: Deployment does not have minimum availability.
    Reason:                UnhealthyPackageRevision
    Status:                False
    Type:                  Healthy
    Last Transition Time:  2024-08-08T05:51:12Z
    Reason:                ActivePackageRevision
    Status:                True
    Type:                  Installed
  Current Identifier:      xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1
  Current Revision:        provider-vsphere-a3adebbdd27f
Events:
  Type     Reason                  Age                From                                 Message
  ----     ------                  ----               ----                                 -------
  Warning  InstallPackageRevision  20m (x3 over 21m)  packages/provider.pkg.crossplane.io  current package revision health is unknown
  Warning  InstallPackageRevision  14m (x5 over 20m)  packages/provider.pkg.crossplane.io  current package revision is unhealthy

Pod Events:

Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Pulling    25m                   kubelet            Pulling image "xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1"
  Normal   Scheduled  25m                   default-scheduler  Successfully assigned crossplane-system/provider-vsphere-a3adebbdd27f-5f8db575c7-vt8rk to ip-100-64-41-228.eu-west-1.compute.internal
  Normal   Pulled     24m                   kubelet            Successfully pulled image "xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1" in 7.999s (7.999s including waiting)
  Warning  Failed     24m                   kubelet            Error: failed to generate container "187ea807396bd5fc320ec129b30fb036d1ad771988998c223a120d479e5bfb1e" spec: failed to generate spec: no command specified
  Warning  Failed     24m                   kubelet            Error: failed to generate container "70cc9d0e57ee078905f26b0791e44e3aa0588423ee65ca90cd5b8b3c2a6fe18a" spec: failed to generate spec: no command specified
  Warning  Failed     24m                   kubelet            Error: failed to generate container "18ba14d5aaf9c62b75a8421eb4b3d9ea7f245a57ada86210b8e1522a0d519fa2" spec: failed to generate spec: no command specified
  Warning  Failed     24m                   kubelet            Error: failed to generate container "7f046f4ebac8ec9373e792447e15b323e5f6ba8ce6a7128bef5aa6f0c11793bd" spec: failed to generate spec: no command specified
  Warning  Failed     24m                   kubelet            Error: failed to generate container "910c7f84516e715d66d17db5f3373623a57dfe768efa217f1ffd24505552e3a9" spec: failed to generate spec: no command specified
  Warning  Failed     24m                   kubelet            Error: failed to generate container "46d78d7014e94b9c84d8793d982fb281a64ce4b8ee77bc0cb2c1d41bfa14ceeb" spec: failed to generate spec: no command specified
  Warning  Failed     23m                   kubelet            Error: failed to generate container "6c705fa3eb557209d4e1e6fd0a6d43cc21c4e2ecefab5a24b303c266c306f9ec" spec: failed to generate spec: no command specified
  Warning  Failed     23m                   kubelet            Error: failed to generate container "c7b5a2b6a867f4227748fb0c99e5f3af704a55bf235d9f8c9fab0b8651ed5c5c" spec: failed to generate spec: no command specified
  Warning  Failed     23m                   kubelet            Error: failed to generate container "57243baf9cb693c8b742603bd7acd12ea13dff55881ba75c29d9f1766c3dec6c" spec: failed to generate spec: no command specified
  Warning  Failed     22m (x3 over 23m)     kubelet            (combined from similar events): Error: failed to generate container "fe549f7eb51238876cef1df3e1fe9f5fddd8f60996b295839fcdcd9c8c1298fc" spec: failed to generate spec: no command specified
  Normal   Pulled     4m59s (x93 over 24m)  kubelet            Container image "xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1" already present on machine

[limlengchye]

Same here. Looks at the image does have not cmd, entrypoint, env nor arch.

$ docker inspect xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1
[
    {
        "Id": "sha256:6ad646fe108343796790a7c93cd9b37f16e769449a44bb47df5d780b43a7ccc9",
        "RepoTags": [
            "xpkg.upbound.io/ankasoftco/provider-vsphere:v0.0.1"
        ],
        "RepoDigests": [
            "xpkg.upbound.io/ankasoftco/provider-vsphere@sha256:a3adebbdd27fc34d8e394a4c5b0d9b503ac11855f55d7bb04dd34ba681d66aca"
        ],
        "Parent": "",
        "Comment": "",
        "Created": "0001-01-01T00:00:00Z",
        "DockerVersion": "",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": null,
            "Cmd": null,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": {
                "io.crossplane.xpkg:sha256:c5b690f2acc7a4e4536fac1b88502bfc9567a0b653f31bb641349722763534d4": "base"
            }
        },
        "Architecture": "",
        "Os": "linux",
        "Size": 924151,
        "GraphDriver": {
            "Data": {
                "MergedDir": "/var/lib/docker/overlay2/be203436c3025c9c5f5a5b64bbd1670dcd145a27054fbe7da1b20ab42d6eaaf4/merged",
                "UpperDir": "/var/lib/docker/overlay2/be203436c3025c9c5f5a5b64bbd1670dcd145a27054fbe7da1b20ab42d6eaaf4/diff",
                "WorkDir": "/var/lib/docker/overlay2/be203436c3025c9c5f5a5b64bbd1670dcd145a27054fbe7da1b20ab42d6eaaf4/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:2aba47554cc111ce4354285d87e9a70963f0022e67fc30ebf44aea3bcb47723c"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

[lbrigman124]

I'm getting the same issue. It looks like the XRD was uploaded in place of the provider image.
Is there a way that this can get updated in the marketplace. I see the company does have other crossplane providers that they mention on their web site.