VxRail: Incorrect file permissions for some libraries During Upgrade to 7.0.400 with STIG

Summary: During the upgrade of a hardened VxRail environment to version 7.0.400, some newly deployed packages may get incorrect file permissions. This fails the LCM process.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Instructions

SCENARIO 1:
For the scenario where no upgrade has been attempted yet, perform the following steps before initiating the LCM process:

  1. Take a Snapshot of VxRail Manager VM
  2. SSH into VxRail Manager VM
  3. Su to root
  4. Modify the /etc/login.defs, change umask to 022. (It should be 077)
  5. Perform the LCM process using the VxRail plugin to update to version 7.0.400.
  6. Once LCM has completed, SSH back to VxRail Manager and Resets the umask in /etc/login.defs back to the hardening value of 077.

SCENARIO 2:
For this scenario, an upgrade has already been attempted and failed.

To identify scenario 2:

  • Upgrade to 7.0.400 fails with: "Failed to retrieve the existing value of the vSAN disk object repair timeout."
  • In the lcm-web.log, it shows the errors below:
    2022-10-12 10:25:04,072 WARN [LCM] [lcm-node-0] c.v.c.c.ScriptServiceImpl [ScriptServiceImpl.java:494] [/etc/vmware-marvin/scripts/lcm/scripts/update-vsan-clom-repair-timeout.py@localhost]: <stderr> Traceback (most recent call last):
      File "/usr/lib/vmware-marvin/marvind/temp/16190242744258415283.tmp", line 14, in <module>
        from pyVim.connect import Connect, Disconnect
      File "/usr/lib/python3.6/site-packages/pyVim/connect.py", line 35, in <module>
        from requests.auth import HTTPBasicAuth
    ModuleNotFoundError: No module named 'requests.auth'
  • Check to see the file permissions:
    Run the following command on the VxRail Manager:
    ls -ltr /usr/lib/python3.6/site-packages/requests/
    --They look like the below image if the issue has occurred
    ls -ltr command output example

For this scenario where an upgrade has already been attempted and failed due to this issue, perform the following steps before retrying the LCM process:

  1. Take a Snapshot of VxRail Manager VM
  2. SSH into VxRail Manager VM
  3. Su to root
  4. Check the umask level by running the command: "umask" (Should be 077)
  5. Change umask to 022 by running the command: "umask 022"
  6. Check that the umask level of your session is now 022 by running the command: "umask"
  7. Reinstall the element package to restore correct file permissions:
    1. pip3 install --force-reinstall /agent/requirements/requirements/* >/tmp/update-element-package.reinstall.log 2>&1
    2. /usr/bin/pip install --force-reinstall /agent/requirements/requirements/* >/tmp/update-element-package.reinstall.log 2>&1
  8. Check the file permission to see if they are set correctly.
    ls -ltr /usr/lib/python3.6/site-packages/requests/
    -- They should look like below after running the commands from the previous step:
    ls ltr command output example
  9. Retry the LCM process using the VxRail plugin to update to version 7.0.400.

 

Article Properties
Article Number: 000204473
Article Type: How To
Last Modified: 04 Jun 2025
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.