vCF 3.x – SDDC-Manager Precheck Fails: LCM Directories Permission Check

Problem Summary

For a customer, I was doing the prechecks for his VCF environments, since we wanted to upgrade the environments from 3.9.1. to 3.10. Unfortunately the following error appeared on all 3 environments.

Afbeelding met schermafbeelding Automatisch gegenereerde beschrijving

 

Error Description:
LCM does not have read/write permission to /opt/vmware/vcf/lcm/lcm-app/conf/jpa-prod.properties.bak

Proposed Remediation:
Make sure LCM App user (vrack) has read & write permissions to all files & directories involved in LCM self-upgrade


Troubleshooting

*********************Precaution************************

Before you start with this procedure, please make a snapshot of your SDDC-Manager first.
If you make mistakes, you can easily revert back.

**********************************************************

 

So the folder were we need to be is:

/opt/vmware/vcf/lcm/lcm-app/conf/

Here, there will be a few files that we need to change the permission from.
As you see below, these are the permissions before the change.

In the precheck error, it stated that it couldn’t access the file “jpa-prod.properties”.
For all the coming precheck file errors, we will be changing the permissions of the “Group” & “Other Users”.

If correct, the Owner already has the highest permissions (7). The following command will change the permission to:

776 otherwise known As
Owner: Full Permissions (7), Group: Full Permissions (7), Others: Read & Execute Permissions (6)

So the first file we’re going to change with the command is the “jpa-prod.properties” file.

Chmod 776 jpa-prod.properties

After that the precheck still failed, but if you look closely, this time it fails on a different file.

Afbeelding met schermafbeelding Automatisch gegenereerde beschrijving

Error:
LCM does not have read/write permission to /opt/vmware/vcf/lcm/lcm-app/conf/application.properties

Chmod 776 application.properties

After that Change the last precheck error came along

Afbeelding met schermafbeelding Automatisch gegenereerde beschrijving

So for we change the permissions one more time with

Chmod 776 VersionAlias.yml.old

After that the Issue was solved and the Precheck Succeeded.

Afbeelding met schermafbeelding Automatisch gegenereerde beschrijving

The File Permissions in the End looked like this.

Hope that this was helpfull for you.
If you have any questions, let me know in the comments below.

↑↑ Follow me on my Socialz ↑↑ - Or - ↓↓ Care & Share ↓↓

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.