Stretch Deploy Troubleshooting – Part II


Some interesting progress that may be useful to the broader audience…  In trying to trouble-shoot my vCHS disconnect, I decided to stretch deploy a VM from my vCenter to my private vCD to get a better sense of what each task is.  I discovered that each “getting tasks” entry in the log represents a discrete step.  If you remember, my vCHS DCE fails at 10% and 2% for the two primary tasks.  Well this is the full set of steps for a successful stretch deploy:

  1. create folder – in dest org
  2. deploy ovf template – stretched_vapp_network
  3. reconfigure vm – stretched_vapp_network
  4. reconfigure cluster – vcenter
  5. power on vm – stretched_vapp_network
  6. reconfigure autostart – host (at this point the tasks were at 40% and 8% completion.  This means the vCHS DCE is never reaching this far along)
  7. update opaque data for set of entities – no real detail in the event view on these “update opaque data for set of entities” entries.  Assume they are reconfiguration of recently created/modified resources
  8. reconfigure distributed port group – destination
  9. reconfigure dvport
  10. update opaque data for set of entities
  11. update opaque data for set of entities
  12. reconfigure distributed port group
  13. reconfigure dvport
  14. update opaque data for set of entities
  15. export OVFtemplate
  16. create folder – destination
  17. deploy OVFtemplate – destination
  18. rename virtual machine
  19. reconfigure virtual machine
  20. reconfigure virtual machine
  21. create folder
  22. create virtual machine snapshot
  23. clone virtual machine
  24. reconfigure virtual machine
  25. create virtual machine snapshot
  26. clone virtual machine
  27. remove snapshot
  28. reconfigure virtual machine
  29. delete virtual machine
  30. unregister and delete – tempvApp
  31. reconfigure virtual machine
  32. rename virtual machine
  33. delete virtual machine
  34. unregister and delete
  35. set virtual machine custom value
  36. set virtual machine custom value

I’ve included some entity descriptions on the steps above, but most of them make sense based on name and most of them take place on the destination side of the move after the copy has been completed.

The SSL VPN tunnel connection happens early, steps 2-5, so that’s the point where I believe my vCHS DCE experiment is failing.  Now the only question is why!  Stay tuned!

 

EDIT: in taking a closer look at some fresh logs, this error appears to be the culprit (still now sure how/why though):

2013-09-09 02:46:11.420 EDT [tomcat-http--15] WARN  o.s.web.client.RestTemplate - GET request for "https://p1v14-vcd.vchs.vmware.com:8443/cloud/org/Massimo/agent/api/v2/transferprotocol" resulted in 404 (Not Found); invoking error handler
"stretch deploy" via SSL VPN between two virtual edges that live on the same physical VLAN! Mind... blown!
“stretch deploy” via SSL VPN between two virtual edges that live on the same physical VLAN! Mind… blown!
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s