Thread
#general
    a

    adamant-architect-10544

    5 months ago
    I'm trying to use pulumi helm release (python based). The chart's deployment fails with a timeout. Below is the error:
    Diagnostics:
      pulumi:pulumi:Stack (test-trial2):
        Python 3.6 is approaching EOL and will not be supported in Pulumi soon. Check <https://github.com/pulumi/pulumi/issues/8131> for more details
    
        debug: registering resource: ty=pulumi:pulumi:Stack, name=test-trial2, custom=False, remote=False
        debug: registering resource: ty=pulumi:providers:kubernetes, name=my-k8s, custom=True, remote=False
        debug: registering resource: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, name=trial-edge, custom=True, remote=False
        debug: Waiting for outstanding RPCs to complete
        debug: RPCs successfully completed
        debug: Waiting for 55 outstanding tasks to complete
        debug: beginning rpc register resource
        debug: beginning rpc register resource
        debug: beginning rpc register resource
        debug: beginning rpc register resource outputs
        debug: resource registration prepared: ty=pulumi:pulumi:Stack, name=test-trial2
        debug: resource registration successful: ty=pulumi:pulumi:Stack, urn=urn:pulumi:trial2::test::pulumi:pulumi:Stack::test-trial2
        debug: resource registration prepared: ty=pulumi:providers:kubernetes, name=my-k8s
        debug: register resource outputs prepared: urn=urn:pulumi:raji-trial2::test::pulumi:pulumi:Stack::test-trial2, props=
        debug: resource registration successful: urn=urn:pulumi:raji-trial2::test::pulumi:pulumi:Stack::test-trial2, props=
        debug: resource registration successful: ty=pulumi:providers:kubernetes, urn=urn:pulumi:trial2::test::pulumi:providers:kubernetes::my-k8s
        debug: resource registration prepared: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, name=trial-edge
        error: update failed
        debug: resource registration successful: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, urn=urn:pulumi:trial2::test::kubernetes:<http://helm.sh/v3:Release::trial-edge|helm.sh/v3:Release::trial-edge>
    
      kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (trial-edge):
        warning: Helm release "trial-edge-8kchrd9c" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then retry. Reason: timed out waiting for the condition
        error: 1 error occurred:
            * Helm release "trial-edge/trial-edge-8kchrd9c" was created, but failed to initialize completely. Use Helm CLI to investigate.: failed to become available within allocated timeout. Error: Helm Release trial-edge/trial-edge-8kchrd9c: timed out waiting for the condition
    The same chart goes through fine when deploying manually (helm status shows deployed as well). All k8s objects are created properly in both the cases. How do I need to debug this further?
    b

    bright-teacher-68496

    5 months ago
    Has anyone else faced this issue, or know how to debug this further?