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: Can we remove the completed 7/12 VMware testing environment? #164

Closed
lixuna opened this issue Jul 16, 2018 · 3 comments
Closed

vsphere: Can we remove the completed 7/12 VMware testing environment? #164

lixuna opened this issue Jul 16, 2018 · 3 comments

Comments

@lixuna
Copy link
Contributor

lixuna commented Jul 16, 2018

Follow-up ticket from #161 (comment):

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

The following environments are still online and were not destroyed properly:

  1. pd21943
  2. pd21944
@lixuna
Copy link
Contributor Author

lixuna commented Jul 16, 2018

@akutz,

Yes, greenlight on vmware destroying these environments

@lixuna lixuna mentioned this issue Jul 16, 2018
Open
@akutz
Copy link
Contributor

akutz commented Jul 16, 2018

Hi @lixuna,

Grazzie!

pd21943

$ docker run \
>   --rm \
>   --dns 147.75.69.23 --dns 8.8.8.8 \
>   -v $(pwd)/data:/cncf/data \
>   -e VSPHERE_SERVER=$VSPHERE_SERVER \
>   -e VSPHERE_USER=$VSPHERE_USER \
>   -e VSPHERE_PASSWORD=$VSPHERE_PASSWORD \
>   -e VSPHERE_AWS_ACCESS_KEY_ID=$VSPHERE_AWS_ACCESS_KEY_ID \
>   -e VSPHERE_AWS_SECRET_ACCESS_KEY=$VSPHERE_AWS_SECRET_ACCESS_KEY \
>   -e VSPHERE_AWS_REGION=$VSPHERE_AWS_REGION \
>   -e CLOUD=vsphere \
>   -e BACKEND=file \
>   -e NAME=pd21943 \
>   -e COMMAND=destroy \
>   -e VSPHERE_DESTROY_FORCE=true \
>   -ti provisioning
# deleting DNS entries for master node(s)
  - pd21943-master-1.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-1","modifiedIndex":25468,"createdIndex":24393},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-1","value":"{\"host\":\"192.168.1.175\"}","modifiedIndex":24393,"createdIndex":24393}}
  - pd21943-master-2.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-2","modifiedIndex":25469,"createdIndex":24394},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-2","value":"{\"host\":\"192.168.1.174\"}","modifiedIndex":24394,"createdIndex":24394}}
  - pd21943-master-3.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-3","modifiedIndex":25470,"createdIndex":24392},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-master-3","value":"{\"host\":\"192.168.1.176\"}","modifiedIndex":24392,"createdIndex":24392}}

# deleting DNS entries for worker node(s)
  - pd21943-master-1.pd21943.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21943/pd21943-worker-1","modifiedIndex":25471,"createdIndex":24391},"prevNode":{"key":"/skydns/local/vsphere/pd21943/pd21943-worker-1","value":"{\"host\":\"192.168.1.173\"}","modifiedIndex":24391,"createdIndex":24391}}

# deleting AWS load balancer(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:loadbalancer/net/xapi-20180712204306658100000002/748b108df78b7054

# waiting for deletion of AWS load balancer(s)

# deleting AWS load balancer target group(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:targetgroup/xapi-20180712204304878800000001/249022a72adda676

# deleting AWS elastic IP address(es)
  - eipalloc-04448dfd1687e73ca ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...

# deleting vSphere VM(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-2
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-master-3
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943/pd21943-worker-1

# deleting vSphere folder(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21943

# deleting vSphere resource pool(s)
  - /SDDC-Datacenter/host/Cluster-1/Resources/Compute-ResourcePool/CNCF Cross-Cloud/pd21943

# deleting Terraform state

real	2m39.319s
user	0m16.580s
sys	0m2.190s

pd21944

$ docker run \
>   --rm \
>   --dns 147.75.69.23 --dns 8.8.8.8 \
>   -v $(pwd)/data:/cncf/data \
>   -e VSPHERE_SERVER=$VSPHERE_SERVER \
>   -e VSPHERE_USER=$VSPHERE_USER \
>   -e VSPHERE_PASSWORD=$VSPHERE_PASSWORD \
>   -e VSPHERE_AWS_ACCESS_KEY_ID=$VSPHERE_AWS_ACCESS_KEY_ID \
>   -e VSPHERE_AWS_SECRET_ACCESS_KEY=$VSPHERE_AWS_SECRET_ACCESS_KEY \
>   -e VSPHERE_AWS_REGION=$VSPHERE_AWS_REGION \
>   -e CLOUD=vsphere \
>   -e BACKEND=file \
>   -e NAME=pd21944 \
>   -e COMMAND=destroy \
>   -e VSPHERE_DESTROY_FORCE=true \
>   -ti provisioning
# deleting DNS entries for master node(s)
  - pd21944-master-1.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-1","modifiedIndex":25472,"createdIndex":24430},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-1","value":"{\"host\":\"192.168.1.182\"}","modifiedIndex":24430,"createdIndex":24430}}
  - pd21944-master-2.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-2","modifiedIndex":25473,"createdIndex":24432},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-2","value":"{\"host\":\"192.168.1.184\"}","modifiedIndex":24432,"createdIndex":24432}}
  - pd21944-master-3.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-3","modifiedIndex":25474,"createdIndex":24431},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-master-3","value":"{\"host\":\"192.168.1.181\"}","modifiedIndex":24431,"createdIndex":24431}}

# deleting DNS entries for worker node(s)
  - pd21944-master-1.pd21944.vsphere.local
{"action":"delete","node":{"key":"/skydns/local/vsphere/pd21944/pd21944-worker-1","modifiedIndex":25475,"createdIndex":24429},"prevNode":{"key":"/skydns/local/vsphere/pd21944/pd21944-worker-1","value":"{\"host\":\"192.168.1.183\"}","modifiedIndex":24429,"createdIndex":24429}}

# deleting AWS load balancer(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:loadbalancer/net/xapi-20180712204423284700000002/0f31cb7bb30b2d35

# waiting for deletion of AWS load balancer(s)

# deleting AWS load balancer target group(s)
  - arn:aws:elasticloadbalancing:us-west-2:571501312763:targetgroup/xapi-20180712204421432200000001/6cdd67ac5ae591c0

# deleting AWS elastic IP address(es)
  - eipalloc-02a87e539046d61af ... ... ... ... ... ... ... ... ...

# deleting vSphere VM(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-2
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-worker-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-1
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944/pd21944-master-3

# deleting vSphere folder(s)
  - /SDDC-Datacenter/vm/Workloads/CNCF Cross-Cloud/pd21944

# deleting vSphere resource pool(s)
  - /SDDC-Datacenter/host/Cluster-1/Resources/Compute-ResourcePool/CNCF Cross-Cloud/pd21944

# deleting Terraform state

real	1m10.669s
user	0m7.330s
sys	0m1.150s

@akutz
Copy link
Contributor

akutz commented Jul 16, 2018

Hi @lixuna,

From my perspective this issue can be closed. However, the S3 buckets with the TF state may still need to be cleaned up. I imagine there's an auto-expiring lease on those, so it may not be an issue.

@lixuna lixuna closed this as completed Jul 26, 2018
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