search

vmware-archive / ansible-role-vcsa

Other
27 stars 8 forks source link

vCSA OVF install doesn't return the correct status code when successfully complete #6

Open richardboswell opened 7 years ago

richardboswell commented 7 years ago

I deployed an OOB vCenter and the Ansible task did not receive a return code for successful completion due to error below. Therefore the Ansible task has been waiting for the last 12 hours or so, searching for the monitor file. The ovftool deploy log is below, it looks like the rpmInstall.json file that should have been created on the vCSA was not found.

2017-05-24T21:27:35.288Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Parsing URL 2017-05-24T21:27:35.302Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Using file size as progress measure 2017-05-24T21:27:35.302Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] OvfPackageSourceBase getting file source 2017-05-24T21:27:35.544Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] HttpWriterFactory web request : https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-0.vmdk 2017-05-24T21:27:35.544Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Initializing new curl session 2017-05-24T21:27:35.546Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Parsing URL 2017-05-24T21:27:35.546Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-0.vmdk is redirected to https://esxoob01.corp.local/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-0.vmdk 2017-05-24T21:27:35.546Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Changing HttpWriterFactory path to https://esxoob01.corp.local/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470 2017-05-24T21:28:07.403Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Closing writer. Locator: https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-0.vmdk (Written bytes: 523656704) 2017-05-24T21:28:07.403Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Curl session torn down 2017-05-24T21:28:07.403Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] OvfPackageSourceBase getting file source 2017-05-24T21:28:07.403Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] HttpWriterFactory web request : https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-1.vmdk 2017-05-24T21:28:07.403Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Initializing new curl session 2017-05-24T21:28:07.405Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Parsing URL 2017-05-24T21:28:07.405Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-1.vmdk is redirected to https://esxoob01.corp.local/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-1.vmdk 2017-05-24T21:28:07.405Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Changing HttpWriterFactory path to https://esxoob01.corp.local/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470 2017-05-24T21:29:25.279Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Closing writer. Locator: https://esxoob01.corp.local:443/ha-nfc/52c81d59-c416-ea6f-51b4-6169e22ad470/disk-1.vmdk (Written bytes: 1492460032) 2017-05-24T21:29:25.280Z verbose -[7F7913FB8700] [Originator@6876 sub=Default] Curl session torn down 2017-05-24T21:29:25.280Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Ovf convertion finished 2017-05-24T21:29:25.311Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Vi4Target::Complete: Unexpected number of tasks running on target: 0 2017-05-24T21:29:26.378Z verbose -[7F7914000700] [Originator@6876 sub=Default] Caught exception while sending lease progress: vmodl.fault.SystemError 2017-05-24T21:30:56.470Z verbose -[7F79140027C0] [Originator@6876 sub=Default] OutputFilePath : /tmp/vcsa-cli-installer-progress-6916527.json 2017-05-24T21:30:56.470Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Start monitoring : file://root:********@/var/log/firstboot/rpmInstall.json 2017-05-24T21:30:56.492Z verbose -[7F79140027C0] [Originator@6876 sub=Default] Monitor path: /var/log/firstboot/rpmInstall.json ... 2017-05-24T21:37:33.150Z verbose -[7F79134C5700] [Originator@6876 sub=Default] Keeping VI session alive

richardboswell commented 7 years ago

I checked the vCSA and both files that are monitored (/var/log/firstboot/rpmInstall.json and /var/log/firstboot/fbInstall.json) exist. I need to determine the connection path of ovftool for monitoring, the X:waitForIp argument is required and that leads me to believe that the connection is over IP.