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

Destroy does not download plugins #8768

Closed
chainlink opened this issue Jan 14, 2022 · 7 comments
Closed

Destroy does not download plugins #8768

chainlink opened this issue Jan 14, 2022 · 7 comments
Labels
area/cli UX of using the CLI (args, output, logs) kind/bug Some behavior is incorrect or out of spec needs-repro Needs repro steps before it can be triaged or fixed resolution/no-repro This issue wasn't able to be reproduced

Comments

@chainlink
Copy link

Issue details

When I try running destroy the necessary plugins are not downloaded (Running up downloads plugins and succeeds)

Error message:

stderr: error: could not load plugin for kubernetes provider 'urn:pulumi:pulumi-preview::jupyter-test::pulumi:providers:kubernetes::k8sprovider': no resource plugin 'kubernetes' found in the workspace or on your $PATH

Steps to reproduce

Github action setup:

jobs:
  up:
    name: remove-preview
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: actions/setup-go@v2
         with:
           go-version: '^1.17.2'
      - uses: google-github-actions/setup-gcloud@master
        with:
          service_account_key: ${{ secrets.GCP_KEY }}
          project_id: ${{ env.PROJECT_ID }}
          export_default_credentials: true
      - uses: pulumi/actions@v3
        with:
          command: destroy
          stack-name: blah
          work-dir: infra

Expected: Destroy to run sucessfully
Actual: Destroy failed with above error

@mikhailshilkov
Copy link
Member

I can reproduce this with running pulumi destroy in the CLI, so this is not specific to actions. I'll move the issue to pulumi/pulumi.

@mikhailshilkov mikhailshilkov transferred this issue from pulumi/actions Jan 18, 2022
@mikhailshilkov mikhailshilkov added area/cli UX of using the CLI (args, output, logs) kind/bug Some behavior is incorrect or out of spec labels Jan 18, 2022
@lukehoban
Copy link
Member

FWIW - this is also what #5619 was tracking, it sounds like the issue described there is perhaps unique to "destroy" operations, which might be why it was not reproduced during investigation?

@mikhailshilkov mikhailshilkov added this to the 0.68 milestone Jan 24, 2022
@dixler
Copy link
Contributor

dixler commented Jan 24, 2022

@mikhailshilkov do you have CLI repro steps?

Note: I'm on a linux machine if there is any weirdness

I tried:

  • bringing up a stack from examples
  • deleting the ~/.pulumi/plugins directory
  • running destroy.
kdixler@kdixler-20xw004aus ..mples/kubernetes-ts-exposed-deployment (git)-[master] % ~/.pulumi/bin/pulumi version
v3.22.1
kdixler@kdixler-20xw004aus ..mples/kubernetes-ts-exposed-deployment (git)-[master] % pulumi up --yes; rm -rf ~/.pulumi/plugins; pulumi destroy --yes
Please choose a stack, or create a new one: issue8768
Previewing update (issue8768)

View Live: https://app.pulumi.com/kyle/exposed-deployment/issue8768/previews/df073e10-b8db-4db1-a181-a8d96d550f8c

     Type                              Name                          Plan       
 +   pulumi:pulumi:Stack               exposed-deployment-issue8768  create     
 +   ├─ kubernetes:apps/v1:Deployment  nginx                         create     
 +   └─ kubernetes:core/v1:Service     nginx                         create     
 
Resources:
    + 3 to create

Updating (issue8768)

View Live: https://app.pulumi.com/kyle/exposed-deployment/issue8768/updates/9

     Type                              Name                          Status      
 +   pulumi:pulumi:Stack               exposed-deployment-issue8768  created     
 +   ├─ kubernetes:apps/v1:Deployment  nginx                         created     
 +   └─ kubernetes:core/v1:Service     nginx                         created     
 
Outputs:
    frontendIp: "10.103.229.171"

Resources:
    + 3 created

Duration: 14s

Please choose a stack: issue8768
Previewing destroy (issue8768)

View Live: https://app.pulumi.com/kyle/exposed-deployment/issue8768/previews/84dafa29-9040-4f56-bbf8-318f9b44fc15

[resource plugin kubernetes-3.14.1] installing
Downloading plugin: 30.18 MiB / 30.18 MiB [=========================] 100.00% 8s
     Type                              Name                          Plan       
 -   pulumi:pulumi:Stack               exposed-deployment-issue8768  delete     
 -   ├─ kubernetes:core/v1:Service     nginx                         delete     
 -   └─ kubernetes:apps/v1:Deployment  nginx                         delete     
 
Outputs:
  - frontendIp: "10.103.229.171"

Resources:
    - 3 to delete

Destroying (issue8768)

View Live: https://app.pulumi.com/kyle/exposed-deployment/issue8768/updates/10

     Type                              Name                          Status      
 -   pulumi:pulumi:Stack               exposed-deployment-issue8768  deleted     
 -   ├─ kubernetes:core/v1:Service     nginx                         deleted     
 -   └─ kubernetes:apps/v1:Deployment  nginx                         deleted     
 
Outputs:
  - frontendIp: "10.103.229.171"

Resources:
    - 3 deleted

Duration: 2s

The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained. 
If you want to remove the stack completely, run 'pulumi stack rm issue8768'.

@mikhailshilkov
Copy link
Member

Hmm, yeah, that's what I did - I deleted all files from ~/.pulumi/plugins (empty dir) and then ran pulumi destroy. It failed for me...

@mikhailshilkov
Copy link
Member

I tried again but I can't reproduce it this time. Odd. I must have done something differently or my state was somewhat different but I can't figure out what that was yet.

@dixler
Copy link
Contributor

dixler commented Jan 25, 2022

Failed to repro using the pulumi/actions repo by stripping down the entrypoint. It still destroyed. This was after a couple of runs so my environment might be dirty or it may be looking somewhere else for plugins

The following test used AWS resources. The logs are commented in the gist.

https://gist.github.com/dixler/2ea418da0dab0b561f4e9e670e8c983f

@mikhailshilkov mikhailshilkov added the needs-repro Needs repro steps before it can be triaged or fixed label Jan 26, 2022
@mikhailshilkov mikhailshilkov removed this from the 0.68 milestone Jan 26, 2022
@dixler dixler removed their assignment Mar 4, 2022
@justinvp justinvp added the resolution/no-repro This issue wasn't able to be reproduced label Jul 27, 2023
@justinvp
Copy link
Member

Closing as no repro. If you're running into this, please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cli UX of using the CLI (args, output, logs) kind/bug Some behavior is incorrect or out of spec needs-repro Needs repro steps before it can be triaged or fixed resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

5 participants