![]() ![]() ![]() However, nothing could be found anywhere on how to remove it on the internet. Assuming this was vRA, I was beginning to think it would be some sort of command line action to remove the entry. No place in the documentation discusses how to remove an IaaS server from the appliance database. The answer is pretty straightforward then. Considering this is a Linux appliance, two totally unique names for the environment.Īt some point in my lab, I must have rebuilt the IaaS server, but had changed the name from a more complex upper/lower case one to a simple lower case one. When I took a look at the general vRA Setting – Host Settings, I was baffled to see that I had two IaaS servers with the same name, only spelled different through capitalization. It then displayed a single IaaS server from my lab. ![]() Make sure the Management Agent is up and running on them and that it has connectivity to the VA. The VMware certificate was not installed on the nodes listed below. When I attempted to upgrade the vRA appliance to 7.3, I received an error in the Upgrade panel stating the following: Perhaps a lack of understanding on my part, but I think it was more of a lack of documentation from VMware on vRealize Automation. This time was different and the solution, was frankly disappointing. However, typically I can figure these things out pretty quickly and go along my way. It had been a while since I had last used my vRA deployment, so I naturally assumed I was probably bound for some sort of issue due to neglect. ![]() Recently in my lab, I was frustrated over an attempted upgrade to version 7.3 from version 7.2 of vRealize Automation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |