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.

Sign up for GitHub

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

Jump to bottom

vsphere: Failed deployments potentially related to network issues #161

Open
akutz opened this issue Jul 16, 2018 · 4 comments
Open

vsphere: Failed deployments potentially related to network issues #161

akutz opened this issue Jul 16, 2018 · 4 comments

Comments

@akutz
Copy link
Contributor

akutz commented Jul 16, 2018

On 2018/07/16 the following items failed for vSphere:

The issues appear to be network related. An internal VMware ticket has been filed which will cross-reference this issue. Any assistance provided by the CNCF support team will be greatly appreciated. Thank you!
@akutz akutz changed the title vsphere: Failed deployments related to potential network issues vsphere: Failed deployments potentially related to network issues Jul 16, 2018
@akutz
Copy link
Contributor Author

akutz commented Jul 16, 2018

An internal, VMware JIRA ticket was filed. Please note that this ticket is not publicly accessible. It's been noted here for tracking purposes.

@akutz
Copy link
Contributor Author

akutz commented Jul 16, 2018

Hmm, it does not appear that the orphaned environments still present on the vSphere system are related to this morning's failed tests:

image

The AWS LBs for the orphaned environments were created on 7/12, four days ago. Hmmm.

@akutz
Copy link
Contributor Author

akutz commented Jul 16, 2018

Why does it appear that three environments were kicked off this morning at the scheduled time?

pd22411

create-22411

pd22412

create-22412

pd21943 (the outlier)

create-21943

@akutz akutz mentioned this issue Jul 16, 2018
Closed
akutz added a commit to akutz/cross-cloud that referenced this issue Jul 16, 2018
@akutz
provider/vSphere: Make env destroy configurable
142f1f9 
This patch introduces the environment variable
`VSPHERE_DESTROY_ENABLED`. Unless set to `true`, an environment deployed
to vSphere will not be destroyed during the deprovision step.

This PR is related to crosscloudci#161 and possibly crosscloudci#154.
@akutz akutz mentioned this issue Jul 16, 2018
Merged
@lixuna lixuna mentioned this issue Jul 16, 2018
Closed
@lixuna
Copy link
Contributor

lixuna commented Jul 16, 2018

@akutz re: comment #161 (comment):

  • pd21943 (the outlier) was one of the orphaned environments.

Please see #164 for greenlight on destroying pd21943 and pd21944.

akutz added a commit to akutz/cross-cloud that referenced this issue Jul 16, 2018
@akutz
provider/vSphere: Make env destroy configurable
1317abc 
This patch introduces the environment variable `VSPHERE_DESTROY_SKIP`.
If set to `true` the deployed environment will not be deleted during the
destroy step.

This PR fixes crosscloudci#163 and is related to crosscloudci#161; possibly crosscloudci#154.
akutz added a commit to akutz/cross-cloud that referenced this issue Jul 16, 2018
@akutz
provider/vSphere: Make env destroy configurable
4d1af8a 
This patch introduces the environment variable `VSPHERE_DESTROY_SKIP`.
If set to `true` the deployed environment will not be deleted during the
destroy step.

This PR fixes crosscloudci#162 and is related to crosscloudci#161; possibly crosscloudci#154.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@akutz @lixuna