MasterWayZ
Enthusiast
Enthusiast

vRealize Automation 8.0.1 installation fails on VraVaPostInstallCheck

Jump to solution

Today when I tried to deploy vRealize Automation 8.0.1 using the Easy Installer, the deployment got stuck on the VraVaPostInstallCheck step and failed this, with the following error:

- LCMVRAVACONFIG590004

- Error Code: LCMVRAVACONFIG590004

- First boot check failed on vRA. Check if all the network details provided are valid.

- vRA VA deployment Failed at First Boot check on HostName vra.internal.masterwayz.nl

com.vmware.vrealize.lcm.common.exception.EngineException: vRA VA deployment Failed at First Boot check on HostName vra.internal.masterwayz.nl    at com.vmware.vrealize.lcm.plugin.core.vra80.task.VraVaPostInstallCheckTask.execute(VraVaPostInstallCheckTask.java:104)    at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:45)    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)    at java.lang.Thread.run(Thread.java:748)

This is what /var/log/boot.log shows:

root@vra [ /var/log ]# cat boot.log

2020-05-04T16:54:46.585280+00:00 photon-machine root: vami_set_hostname, line 259: Host name has been set to 185.254.168.192.ip.internal.masterwayz.nl

2020-05-04T16:54:46.587959+00:00 photon-machine root: vami_set_hostname, line 98: Inaccessible file: vami_access -rw /etc/mailname failed.

2020-05-04T16:54:46.585270+00:00 photon-machine root[993]: vami_set_hostname, line 259: Host name has been set to 185.254.168.192.ip.internal.masterwayz.nl

2020-05-04T16:54:46.587949+00:00 photon-machine root[998]: vami_set_hostname, line 98: Inaccessible file: vami_access -rw /etc/mailname failed.

2020-05-04T16:54:52.128164+00:00 photon-machine root: vami_set_hostname, line 259: Host name has been set to vra.internal.masterwayz.nl

2020-05-04T16:54:52.130948+00:00 photon-machine root: vami_set_hostname, line 98: Inaccessible file: vami_access -rw /etc/mailname failed.

2020-05-04T16:54:52.128150+00:00 photon-machine root[1192]: vami_set_hostname, line 259: Host name has been set to vra.internal.masterwayz.nl

2020-05-04T16:54:52.130935+00:00 photon-machine root[1197]: vami_set_hostname, line 98: Inaccessible file: vami_access -rw /etc/mailname failed.

Anything that I may do wrong? I'm not sure what I may be doing wrong though. vRLCM and vIDM deployed fine.

Any ideas?

vExpert 2020
0 Kudos
1 Solution

Accepted Solutions
MasterWayZ
Enthusiast
Enthusiast

I deployed it again on an ESXi 6.7u3 host instead of 7.0, and now it works fine.

I didn't know that the ESXi version could matter that much. (or I just had a broken ESXi install on that server)

vExpert 2020

View solution in original post

0 Kudos
5 Replies
kumarsenthild
Enthusiast
Enthusiast

Its know issue.  Please follow below mentioned link , let me know if still having issue.

VMware Knowledge Base

https://kb.vmware.com/s/article/76870

Regards Senthil Kumar D
0 Kudos
MasterWayZ
Enthusiast
Enthusiast

Thank you, trying the solution out now. I also tried to install Automation 8.1, is this issue in there as well? That failed as well but I didn't look at any logs, wanted to try an older version first.

vExpert 2020
0 Kudos
kumarsenthild
Enthusiast
Enthusiast

I tested only 8.0.1 . I don't have enough resource to check 8.1

Regards Senthil Kumar D
0 Kudos
MasterWayZ
Enthusiast
Enthusiast

I set the changes of the last one, since the first one gave me an error.

Now I get this when I run deploy.sh:

Timeout expired

Deployment failed. Collecting log bundle ...

2020-05-04 18:11:36,320 [INFO] Log bundle generation started

2020-05-04 18:11:36,343 [ERROR] Error setting up Kubernetes API.

Traceback (most recent call last):

  File "/opt/python-modules/vracli/commands/log_bundle.py", line 69, in log_bundle_create_handler

    self._setup_k8s_api()

  File "/opt/python-modules/vracli/commands/base_command.py", line 34, in _setup_k8s_api

    crd = self.v1beta1.read_custom_resource_definition(CRD_NAME)

  File "/opt/python-modules/kubernetes/client/apis/apiextensions_v1beta1_api.py", line 850, in read_custom_resource_definition

    (data) = self.read_custom_resource_definition_with_http_info(name, **kwargs)

  File "/opt/python-modules/kubernetes/client/apis/apiextensions_v1beta1_api.py", line 935, in read_custom_resource_definition_with_http_info

    collection_formats=collection_formats)

  File "/opt/python-modules/kubernetes/client/api_client.py", line 321, in call_api

    _return_http_data_only, collection_formats, _preload_content, _request_timeout)

  File "/opt/python-modules/kubernetes/client/api_client.py", line 155, in __call_api

    _request_timeout=_request_timeout)

  File "/opt/python-modules/kubernetes/client/api_client.py", line 342, in request

    headers=headers)

  File "/opt/python-modules/kubernetes/client/rest.py", line 231, in GET

    query_params=query_params)

  File "/opt/python-modules/kubernetes/client/rest.py", line 222, in request

    raise ApiException(http_resp=r)

kubernetes.client.rest.ApiException: (404)

Reason: Not Found

HTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'Date': 'Mon, 04 May 2020 18:11:36 GMT', 'Content-Length': '318'})

HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"customresourcedefinitions.apiextensions.k8s.io \"vaconfigs.prelude.vmware.com\" not found","reason":"NotFound","details":{"name":"vaconfigs.prelude.vmware.com","group":"apiextensions.k8s.io","kind":"customresourcedefinitions"},"code":404}

2020-05-04 18:11:36,344 [WARNING] Falling back to VA-stored logs.

2020-05-04 18:11:36,344 [INFO] Adding fallback node support bundle...

2020-05-04 18:11:44,833 [WARNING] Falling back to VA-stored container logs

2020-05-04 18:11:45,485 [INFO] Log bundle log-bundle-1588615896.tar.xz generated with errors

Error setting up Kubernetes API

vExpert 2020
0 Kudos
MasterWayZ
Enthusiast
Enthusiast

I deployed it again on an ESXi 6.7u3 host instead of 7.0, and now it works fine.

I didn't know that the ESXi version could matter that much. (or I just had a broken ESXi install on that server)

vExpert 2020

View solution in original post

0 Kudos