[
https://issues.apache.org/jira/browse/GEODE-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16991976#comment-16991976
]
ASF subversion and git services commented on GEODE-7527:
--------------------------------------------------------
Commit 6773246103b60f7632518029406323797d79c768 in geode's branch
refs/heads/feature/GEODE-7536b from Scott Jewell
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6773246 ]
GEODE-7527: Correct create_instance and delete_instance zone usage (#4400)
* Correct create_instance.sh to use proper zone for delete
* Do not fail delete instance on not found
* Ensure exit 0 for delete_instance
* Improve error handling of delete instance
> Harden create_instance and delete_instance CI scripts
> -----------------------------------------------------
>
> Key: GEODE-7527
> URL: https://issues.apache.org/jira/browse/GEODE-7527
> Project: Geode
> Issue Type: Bug
> Components: ci
> Reporter: Scott Jewell
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following issues have been identified in the create_instance and
> delete_instance scripts.
> create_instance is used within a retry loop and as such attempts to clean up
> any instance
> from a previous attempt that may have failed. However, the retry attempt may
> be targeting
> a different cloud region than the previous attempt and the cleanup fails.
> delete_instance has been seen to fail due to attempting to delete a
> non-existent instance.
> It appears that the gcloud compute instances list command occasionally
> returns duplicate
> entries and when the script attempts to delete the second occurance, it will
> fail.
> delete_instance should be tolerant of a "not found" when attempting to delete
> an instnce.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
