-
Notifications
You must be signed in to change notification settings - Fork 114
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
nutanix_image: long running image create completes successfully at 10 minutes, without getting success call from API #20
Labels
Comments
Merged
yannickstruyf3
pushed a commit
to yannickstruyf3/terraform-provider-nutanix
that referenced
this issue
Nov 9, 2021
abhimutant
added a commit
that referenced
this issue
Dec 9, 2024
* Feat/1.9.3 (#633) Co-authored-by: Abhishekism9450 <[email protected]> Co-authored-by: Deepak Muley <[email protected]> Co-authored-by: Abhishek <[email protected]> * Feat/1.9.4 (#645) Co-authored-by: Frederic M <[email protected]> Co-authored-by: ArtemProt <[email protected]> Co-authored-by: Abhishekism9450 <[email protected]> * new tf design * import changes * package name change for fc * package name for fc is foundationCentral * package name to foundationcentral * fixes around acctest * examples folder * v4 design * some fixes after merging * datasource for subnets,vpcs, fips * datasource for pbrs * lint fixes. go error (gomnd, gosimple, golint) * go checks, magic numbers(gomnd) * fix config testcase as base client will differ in sdks * datadource for clusters * lint fixes * host datasource * lint fixes * resource for user * adding flatten funcs * resource for subnets * adding go mod for public repo * lint fixes * lint fix * lint fix for client name * test config as client will be different for sdks * adding crud for fips * address groups v4 * service groups * resource for service groups * crud for service groups * CRUD for address groups * data source for network security * CRUD for network security * microseg sdk pointing to internals * datasource for directory services * CRUD for directory service * datasource for saml * CRUD for idp * CRUD auth policy * delete Operation for directory service * CRUD for user groups * Roles info +CRUD logic * change err check logic * acc test for roles * Docs & examples * fix err message * test_roles_config file for Testing * d9ocs and examples for user groups * setup and write test cases for user groups, Test is in progress * fix user group destroy(If-Match header required for delete API) and change 'distinguished_name' attribute to required bcs we can not create user group without `distinguished_name` * Skipping test as it requires a valid user group configuration, and setup test_config_v4.json file * fix test configuration v4 file * fix test configuration v4 file * fix test cases to use test_config_v4 * TestAccRolesV4Resource_Basic remove double check on client_name * fix docs * Docs and examples * Add test configuration file and test cases for directory services, Skipping tests as configurations is not available yet * add secondary_urls to directory service schema * fix idp_metadata in datasource, add If-Match Header on delete resource and fix delete response, API just return response code * add SamlIdpV4 to resource Map * write acc test cases, datasorce test cases verified, resource test cases blocked bcs of idp_metadata.error_url issue * fix error url issue, update resource test case , write docs * test_config_v4 for nutanix_saml_identity_providers_v4 * update sdk to v4.0.2-beta.1, users info done, test cases need to be verified * acc test cases for resource_users_v4 * fix username mistype * docs for users_v4 * fix user resource * fix CRUD and info for auth policies, there is a bug in CRUD , and info . identities.reserved and entities.reserved treated as JSONString * fix bug on update auth policy * acc test for authorization policy * authorization policy v4 docs * fix acc test cases, add more test cases to cover more scenarios in create user, test cases not verified duo to sdk upgrade issue * update provider, add "nutanix_user_v4" to resource and datasource Map * merge feat/v4-permissions into v4-iam * merge feat/v4-user-groups into v4-iam * remove all other modules, add sdk, fix operation module name update provider resource/data maps, fix the structure of test_config_v4.json file * add more roles test cases * fix user test cases * fix user test cases for data sources * remove unnecessary temp folder * remove unnecessary vendor folder * exclude vendor * exclude vendor * add more acc tests cases, change the module name from v4 to v2, * change the user module name from v4 to v2, * change the roles module name from v4 to v2, * change the operations module name from v4 to v2, * change the authorization policy module name from v4 to v2, add examples, update acc test for acps * change the operation module files name from permissions to operations * fix authorization_policy_v2 data_source acc test case * change the saml idp module name from v4 to v2, add examples, update acc * change the directory_service module name from v4 to v2, add and check acc tests, fix some bugs, add examples * change the v2 iam package from iam to iamv2 * change the Roles, User Groups functions names from v4 to v2 * change the test configuration file name from v4 to v2 * Revert "exclude vendor" This reverts commit 14c9f4c. --------- Co-authored-by: Abhishek Chaudhary <[email protected]> Co-authored-by: Abhishekism9450 <[email protected]> Co-authored-by: Deepak Muley <[email protected]> Co-authored-by: Abhishek <[email protected]> Co-authored-by: Frederic M <[email protected]> Co-authored-by: ArtemProt <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When an image create call runs longer than 10 minutes, terraform stops at 10m1s and calls the configuration complete; however, the state file is invalid because it does not get the computed values from the API, since the API has not finished processing the async API creation.
In the case we looked at today, for whatever reason, an ISO creation took ~22-ish minutes on the Prism Central in a particular customers environment. The call ended up succeeding, but not before terraform called it complete.
Prism Central was PC 5.9.1
Expected behavior
P0. Regardless of API version, long-running API calls should FAIL if their time out was reached.
P1. There should be a way to configure the polling timeout if we know a particular call may take a very long time.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: