Loading...
Loading...
An upgrade precheck may display an error message as illustrated here:
The state change of VMDir into read-only mode is a known issue, with one potential trigger being the prevention of data corruption amongst ELM partners.
As highlighted previously, the read-only mode is implemented as a protective measure against data corruption incidents, hence a definitive resolution is not available. However, this guide presents a workaround for scenarios where one or more ELM partners are detected in read-only mode.
The steps to be followed are:Preparation: Identify a healthy PSC Node (either external or embedded) that you will use as a reference to retrieve VMDIR data. Remember the FQDN of this healthy PSC Node and its root password. Note: If you're fixing an embedded node, choose another embedded node as the reference. If fixing an external node, choose an external node as your reference. Keep a note of the `administrator@your_domain` password. Steps to Repair:Step 1: Snapshot Creation Make offline snapshots of the entire ELM setup, including all VCs. Step 2: Tool Download & Transfer Download the `fix-psc-master.zip` tool from the provided [link] Copy this tool to the problematic PSC Node and then extract it. Step 3: Preliminary Check Execute the pre-check command: ./fixpsc data --mode pre-check --healthy-psc-fqdn <healthy-node-fqdn> Successful results can be compared to the sample found here [link] Step 4: Export Local Data Use the command: ./fixpsc data --mode export --healthy-psc-fqdn <healthy-node-fqdn> Compare your output to the sample here [link] Step 5: VMDIR Rebuild Execute the command: ./fixpsc rebuild --healthy-psc-fqdn <healthy-node-fqdn> For reference, see the sample output here [link] Step 6: Import Data Use the command: ./fixpsc data --mode import --healthy-psc-fqdn <healthy-node-fqdn> A successful operation can be checked against the example here [link ] Step 7: Service Registration Rectification (If required) After running fix-psc, you can verify service registrations with the lsdoctor tool. Find detailed information [here]. Once you've finished these steps and if the problem persists, please gather the support bundle logs and note the exact time when the issue occurred. Note: Please be advised that we strongly recommend creating offline snapshots of the ELM setup(including VCs) prior to implementing the workaround. This measure will ensure that comprehensive rollback options are available if necessary.
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.