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

No way to catch error/exception #94

Closed
nhi-vanye opened this issue Jun 10, 2020 · 2 comments
Closed

No way to catch error/exception #94

nhi-vanye opened this issue Jun 10, 2020 · 2 comments
Assignees
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced

Comments

@nhi-vanye
Copy link

Using the same example in #92 - but using a Ubuntu-14 template (as opposed to Ubuntu-20) getting an error that I can't trap

However the VMs are created - but there's no way to capture the error/exception and handle the IP address lookup myself.

Do you want to perform this update? yes
Updating (testing):
     Type                             Name              Status                  Info
     pulumi:pulumi:Stack              XXXX-testing  **failed**              1 error
 ~   ├─ vsphere:index:VirtualMachine  rmo-su-1          **updating failed**     [diff: ~vapp];
 ~   ├─ vsphere:index:VirtualMachine  rmo-cc-1          **updating failed**     [diff: ~vapp];
 
Diagnostics:
  pulumi:pulumi:Stack (labminds-testing):
    error: update failed

  vsphere:index:VirtualMachine (rmo-su-1):
    error: 1 error occurred:
    	* updating urn:pulumi:testing::XXXX::vsphere:index/virtualMachine:VirtualMachine::rmo-su-1: timeout waiting for an available IP address
@leezen
Copy link

leezen commented Jun 11, 2020

If this is due to a get then I think this is the same as pulumi/pulumi#3364

@mikhailshilkov mikhailshilkov added the kind/bug Some behavior is incorrect or out of spec label Aug 9, 2023
@mjeffryes
Copy link
Member

Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it? (Commenting will bump it back into our triage queue.)

@mjeffryes mjeffryes added the awaiting-feedback Blocked on input from the author label Sep 26, 2024
@mjeffryes mjeffryes added the resolution/no-repro This issue wasn't able to be reproduced label Oct 25, 2024
@mjeffryes mjeffryes self-assigned this Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting-feedback Blocked on input from the author kind/bug Some behavior is incorrect or out of spec resolution/no-repro This issue wasn't able to be reproduced
Projects
None yet
Development

No branches or pull requests

4 participants