alcaron2k2's Posts

Oh look, upgrading to LCM 8.3 and VROPS 8.3 it works and sets the hostname correctly now...quality. Of course what I actually mean is download the binary for VROPS 8.3, no love, upgrade LCM to 8.3, ... See more...
Oh look, upgrading to LCM 8.3 and VROPS 8.3 it works and sets the hostname correctly now...quality. Of course what I actually mean is download the binary for VROPS 8.3, no love, upgrade LCM to 8.3, get told there is no mapping for VROPS 8.3, delete VROPS 8.3, re-download it, be told three times you aren't entitled to it, fourth time it works, now it so far is deploying fine. Qua...li..tee...
I'm going to put this out there...I am starting to think vRSLCM isn't a finished product...good thing we didn't pay for it! oh... So running vROPS deployment it always fails on the same thing. Host... See more...
I'm going to put this out there...I am starting to think vRSLCM isn't a finished product...good thing we didn't pay for it! oh... So running vROPS deployment it always fails on the same thing. Hostname ip check. Error Code: LCMVSPHERECONFIG1000072   IP address assignment check failed. Check if the network details are correct and retry.   Exception occured while validating the Hostname and IP of vm : mynode of product : vrops. Failed to find a VA with name : 'mynode', ip : 'myip', hostname : 'mynode.domain'.   The hostname in vcenter is localhost, rebooting it does nothing to resolve that. I can nslookup the IP and get the correct hostname, I can deploy VRA and log insight without issue. The certs are correct, the DNS entries are created well in advance, I have restarted the dns resolver on the LCM, I have upgraded the LCM to 8.3.   I feel like there is a word for saying something is done and charging money for it and it's really, really, not done...
This leads to something I have searched high and low for an answer to and never found an explanation. "Custom resource with the same external type already exists. Use a different external type... See more...
This leads to something I have searched high and low for an answer to and never found an explanation. "Custom resource with the same external type already exists. Use a different external type." So lets say my output type is a string right, I create a custom resource for a workflow that outputs a string, and now I go create another workflow that also spits out a string...and then I go to create a custom resource that...oh wait no you can't because you can only create ONE custom resource for each external type without getting that error. Which seems...insane...
I have been pulling my hair out only to find out that the issue isn't woth my workflows, it is with ANY custom resource Destroy lifecycle action. The Create lifecycle action runs just find, th... See more...
I have been pulling my hair out only to find out that the issue isn't woth my workflows, it is with ANY custom resource Destroy lifecycle action. The Create lifecycle action runs just find, the Destroy always gives this error. ALWAYS. I am using the embedded vRO instance if that matters.