You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
The ibm_pi_instance update in-place action should complete once the VM status
is no longer 'RESIZE', whether the new state is 'ACTIVE', 'SHUTOFF', or
possibly others (I'm not familiar with all possible states, anything other than
error type states should be OK).
Actual Behavior
The ibm_pi_instance update in-place action times out polling for the VSI state
to be 'ACTIVE'.
2022-12-22T09:22:43.450-0600 [WARN] Provider "registry.terraform.io/ibm-cloud/ibm" produced an unexpected new value for ibm_pi_instance.resize-test during refresh.
- .status: was cty.StringVal("ACTIVE"), but now cty.StringVal("SHUTOFF")
2022-12-22T09:22:43.453-0600 [WARN] Provider "registry.terraform.io/ibm-cloud/ibm" produced an invalid plan for ibm_pi_instance.resize-test, but we are tolerating it because it is using the legacy plugin SDK.
Community Note
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
Debug Output
Note: The gist include output from both the working scenario (VSI in 'ACTIVE'
state) and hang scenario (VSI in 'SHUTOFF' state).
https://gist.github.com/jaywcarman/2dde2d72483861250b668aac7e9d78e6
Panic Output
No panic occurs.
Expected Behavior
The ibm_pi_instance update in-place action should complete once the VM status
is no longer 'RESIZE', whether the new state is 'ACTIVE', 'SHUTOFF', or
possibly others (I'm not familiar with all possible states, anything other than
error type states should be OK).
Actual Behavior
The ibm_pi_instance update in-place action times out polling for the VSI state
to be 'ACTIVE'.
Steps to Reproduce
The Terraform code required to recreate is available here:
https://github.com/jaywcarman/terraform-provider-ibm/tree/ibm-power-resize/examples/ibm-power-resize
Create a PowerVS VSI. See project above. I set variables in a
var.tfvars
file, export
IBMCLOUD_API_KEY
as an env var and apply via:Shutdown the PowerVS VSI using
ibmcloud
cli or https://cloud.ibm.com web GUI.Modify the
ibm_pi_instance
'spi_memory
and/orpi_processors
attributes. We want to update the VSI in place.
Wait an hour for the operation to time out☹️
Important Factoids
The resize action is successful in all cases, even when Terroform exits with
Error: context deadline exceeded
.References
The text was updated successfully, but these errors were encountered: