fail to deploy vcf 9.0.2.0

[Gary Davison]

no matter what i do i keep getting this error:-

i have tried offline, online, different version's with no luck

-------------------------------------------

[Dhruv Tyagi]

9.0.2 has been released today so the current Holodeck does not yet support its deployment. We will be validating 9.0.2 on Holodeck and releasing a new version which will support 9.0.2 deployment.

-------------------------------------------

[Gary Davison]

hi thank you for that,

i'm now trying to deploy 9.0.0.0 and keep getting this error:-

-------------------------------------------

[Dhruv Tyagi]

In the same powershell session when the error occurs, run $Error | Select * to get more details about the error. The error.log file currently only logs networking setup related errors and not deployment related errors

-------------------------------------------

[Joel Nordsving]

Any thoughts on when Holodeck 9.0.2.0 will be released?  we also are experiencing deployment issues with version 9.0.1.0, it's continuing to request NSX images for 9.0.2.0 during deployment within VCF Installer. - we've not changed our version of the 2 deployment files required. The processed seemed to break after VCF Installer is now seeing 9.0.2.0 in the available online depot, although the Holodeck script is properly downloading version 9.0.1.0.

-------------------------------------------

[Gary Davison]

Hi,

I now get this:-[cid:c055cf92-e0f8-4409-8270-385c49044d5b]
But the depot is connected and everything is downloaded:-
[cid:6eb4df7d-6b0b-485c-85c1-e662b99d1203]
Kind regards

Gary

[Dhruv Tyagi]

Holodeck 9.0.2 is now available: https://vmware.github.io/Holodeck/release_notes/#holodeck-902-maintenance-release

-------------------------------------------

[Gary Davison]

Hi thank you for that,

I've now tried to deploy it using 9.0.2.0 and get this error:-

i can ping from the SDDC to all the host via ip address, when i try and use the hostname this is what i get:-

-------------------------------------------

[Dhruv Tyagi]

Can you run nslookup esx-01a.site-a.vcf.lab from vcf installer and see if you still get connection refused?

If yes, run the same from holorouter. If still the same, run kubectl get pods and check if dnsmasq pod is running. 

-------------------------------------------

[Levi Bergmann]

I'm running into the same issue using version 9.0.2.0 and 9.0.1.0. It seems like there is an error in the dnsmasq config, screenshots are from 9.0.2.0:

ConfigMap:

-------------------------------------------

[Nikhil M Kulkarni]

Edit the /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml file and change the line server=1.1.1.1#cloudflare-dns.com to server=1.1.1.1

Then run the following commands -
kubectl apply -f /holodeck-runtime/dnsmasq/dnsmasq_configmap.yaml
kubectl delete -f /holodeck-runtime/dnsmasq/dnsmasq_deployment.yaml
kubectl apply -f /holodeck-runtime/dnsmasq/dnsmasq_deployment.yaml

-------------------------------------------

[Gary Davison]

Amazing thank you so much for this :-) it worked perfectly

-------------------------------------------

[Dhruv Tyagi]

Thanks for confirming. This has been added to the list of known issues in the documentation: https://vmware.github.io/Holodeck/release_notes/#known-issues

-------------------------------------------