ArnoKattenpoelO's Posts

Indeed, the problem got worse though, I can't even download the image with http or with the scp method seems like the entire image isn't generated anymore. Haven't tested 8.0 will give it a try when ... See more...
Indeed, the problem got worse though, I can't even download the image with http or with the scp method seems like the entire image isn't generated anymore. Haven't tested 8.0 will give it a try when I have time in my homelab.
Hi @vFouad ,   Running into the same issue with a clean install of vsphere 7.0.3f and vreplication8.5.0.4. Hosts can ping\resolve each other + vcenter. Port 31031 is accessible, services are runni... See more...
Hi @vFouad ,   Running into the same issue with a clean install of vsphere 7.0.3f and vreplication8.5.0.4. Hosts can ping\resolve each other + vcenter. Port 31031 is accessible, services are running. Only thing is we are using local datastores so your question if all the hosts can see all the datastores, no they cannot. Documentation said this should be possible. Only thing I notice is that as soon as I setup replication for the vcenter it tries to install a certain vib, Or so I assume, but the install fails everytime. There is only a indication in the logs about accessing port 80 with a certificate which fails its handshake. What would be weird since normally services on 80 are http and do not require ssl\tls.
Think I might have found the issue. After deploying the appliance, and before starting it, please have a look at configure --> "vApp options" on the VM. If you press EDIT and check the options, the I... See more...
Think I might have found the issue. After deploying the appliance, and before starting it, please have a look at configure --> "vApp options" on the VM. If you press EDIT and check the options, the IP allocation scheme should be OVF environment. So none of the options in the template regarding to IP setting will be applied if left unchecked. And its nice to know the commands for manually adjusting them but it should not be necessary after changing this setting. Poorly tested OVA template... shame on you VMware.
Hi Experts :), So I setup single image autodeployment for a cluster, added a host profile to the cluster itself and configured all the thing necessary for the ipxe boot. ESXi hosts with an empty par... See more...
Hi Experts :), So I setup single image autodeployment for a cluster, added a host profile to the cluster itself and configured all the thing necessary for the ipxe boot. ESXi hosts with an empty partition have no issue at all. However when I already have a provisioned host and try to re-provision it. Then after a while I get a friendly greeting with this message:     Error (see log for more info): An error has ocurred while paring the installation script Error: https://xx.x.x.x:6501/vmw/rbd/host/longidentifier/boot.ks:line 8: Install --overwritevmfs not specified but naa.longdiskidentiefier contains a VMFS partition. Press <Enter> to continue       Tried searching the VCSA server for the default boot.ks file to work around this issue but came up empty handed. Only work around is to recreate the raid1 to wipe the disks before deployment. Which in turn defeats its purpose to make deployment easier.  Does anyone have any suggestions to fixing this?   Edit: ok I found the default file: "/etc/vmware-rbd/DefaultStatefulInstallHostProfile.vpf" on the VCSA. Only this is a workaround, the real issue needs to be fixed and it seems that after a hostprofile change the entire autodeploy cannot find the previous version of the host profile, which one must follow the wizard again to setup autodeploy for a cluster. And still then it does not work and the host stays stateless. Made a support ticket. For now going back to the normal autodeploy.
A year later, problem still exists. Did you guys do any bug report about this issue?   And thanks for the workaround!