-
Notifications
You must be signed in to change notification settings - Fork 24
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
GetNic Will return "not found" wrongly #32
Comments
@Smithx10 what type of image/instance is this (e.g. Ubuntu distro, LX, SmartOS, KVM)? |
@Smithx10 I'm having trouble reproducing this (I don't get the "unable to get machine NIC: ResourceNotFound: nic not found" error, I just get nic states "provisioning" and "running"). What nics are on the machine after the instance.Create step? I.e. |
@twhiteman @mgerdts, I am going to test this with another machine image. Currently the workflow job for addinging the NIC is running into the "vmadam shutdown not exiting 0" bug that @mgerdts addressed earlier in the week. Perhaps that failure in the workflow is causing this condition? Todd are you having any errors in your workflow job? The following task timed out after 90s.
|
Oh, my add_nics workflow job failed:
so it failed to reboot correctly and prematurely ended the add_nics workflow (so the workflow then runs the on_error handler chain). The add_nics on_error workflow is meant to run the More digging is needed. |
@twhiteman What is the reasoning for rebooting an instance for a nic add and delete? I thought SmartOS could add NICs without bounce. |
Adding or removing a NIC has always needed a bounce, as far as I remember. I'm not sure of the reasoning, but it's mentioned in the CloudAPI docs: |
After updating my platform (for the reboot bug, aka OS-5176), I'm now getting successful workflow jobs, but still no sign of the issue you've seen:
and the jobs:
|
While Extending https://github.com/terraform-providers/terraform-provider-triton to accept NetworkObjects I discovered some intermittent behavior here. I created the following test to demonstrate what was occuring.
The following test demonstrates:
A NIC is added to a newly created running Instance.
We begin polling for a state of "running"
We find the NIC that we added with the state of "provisioning" for awhile
The NIC is no longer found for awhile
We find the NIC that we added with the state of "running"
Test:
Result:
The text was updated successfully, but these errors were encountered: