Module-Manager is not in a clean state after aborted update process

Products

• VMware Smart Assurance

Issue/Introduction

• You have got two instances of module-manager after update process from 7.7 to 7.8 abortion. It aborts the removal either of the instances without further explanation. All it has to say every time it runs is:

 ! WARNING: The installed module Module-Manager 1.17.6u1 is not in a clean state, and thus should not be used. It is very likely that the previous operation (installation or update) did not complete successfully. It is recommended to solve the issue, if any, then remove it and re-install it or, if available, restore the previous version and launch the update again.

 ! WARNING: The installed module Module-Manager 1.17.6 is not in a clean state, and thus should not be used. It is very likely that the previous operation (installation or update) did not complete successfully. It is recommended to solve the issue, if any, then remove it and re-install it or, if available, restore the previous version and launch the update again.

 

• Also, module-manager is no longer listed within available modules, although the .pkg files are still located in /APG_HOME/Tools/Module-Repository/:

 

• There are two sub directories under the /APG_HOME/Tools/Module-Manager/
  • 1.17.6  (containing all the files and listed in .current)
  • 1.17.6u1 (this one is completely empty)

Environment

All supported releases of M&R

Cause

• Module-Manager not in a clean state.

• In /APG_HOME/Tools/Module-Manager/1.17.6/data/ folder module-manager-1.17.6u1 is present which is causing this issue.

• Below files under /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6u1 has reference of 1.17.6u1:

  • INSTALL

  • INSTANCE

  • VERSION

• Also, STATUS file under /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6u1 is set to DIRTY.

Resolution

• Delete folder /APG_HOME/Tools/Module-Manager/1.17.6u1

• Replace string 1.17.6.u1 with 1.17.6 in the below files under /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6u1:

  • INSTALL

  • INSTANCE

  • VERSION

• In the /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6u1/STATUS file replace string DIRTY with INSTALLED.

• Rename folder /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6u1 as /APG_HOME/Tools/Module-Manager/1.17.6/data/module-manager-1.17.6, this should resolve the issue.