In previous blog I performed the actions of converging an existing vSphere environment on it’s own as a second VCF Instance, thus being my first Management Domain for my VCF Private Cloud.
During the progress, I continued to encounter an error ”Failed to bootstrap VCF services runtime Reference Token: XXXX” This was during the VCF runtime services deployment and it was going through a failure and several retries. It would deploy the appliance and VM template, attempt it again and eventually error. Here is an example of the error.
The following is the error in the vSphere console ‘The user world daemon of bootstrap-vm-xxxx could not fault in a page. The virtual machine is terminated as further progress is impossible.
While Googling around I did come across the following Broadcom Article Failed to bootstrap VCF services runtime Reference Token: #### & there are other ones that appeared such as VCF 9.1 Deployment fails during VMSP bootstrap due to timeout and there are some additional links in there, but it did not seem to help in my case. I did attempt a re-deploy by deleting the VMs and cleaning up the SDDC Manager plugin from the vCenter. The article at first was pointing towards FQDN and object name case sensitivity, I went back and re-do the wizard steps and change everything to lowercase and could continue to get the failure.
Something got me thinking and said let me see if I can access the SDDC Manager and view the tasks in that console and found that it was pointing towards one of my DNS records unable to resolve due to a configured 127.0.0.1 name server
I still had some understanding of SDDC Interface and checked under Administration >> Network Settings and at that time my Primary DNS for some reason came configured with 127.0.0.1 as Primary and a correct one for Alternate, so I made the change within the SDDC Manager and during the Retry my convergence completed successfully.
Leave a Reply