vsphere: Failed deployments potentially related to network issues

[akutz]

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

• K8s
  • v1.11.0
• Prometheus
  • v2.3.1
  • f32acc0
• CoreDNS
  • v1.1.4
  • a5fe423
• Fluentd
  • v1.2.2
  • 029bb4b
• Linkerd
  • v1.4.3
  • 0280009
• ONAP
  • v1.1.1
  • 8169f18

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]

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]

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

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

[akutz]

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

pd22411

pd22412

pd21943 (the outlier)

[lixuna]

@akutz re: comment https://github.com/crosscloudci/cross-cloud/issues/161#issuecomment-405325305:

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

Please see https://github.com/crosscloudci/cross-cloud/issues/164 for greenlight on destroying pd21943 and pd21944.