Uninstalling vRops Management Pack

I recently had the pleasure of needing to uninstalling vRops Management Pack. Simply because the management pack wouldn’t start collecting after I upgraded the management pack.


All you need is to ssh into a vRops node and execute three lines of commands.

  1. Cat the manifest.txt file of the management pack you need to uninstall and get the name
  2. Change directory to where the opscli tools are located
  3. Execute the opscli.sh script with a few paramenters

Management Packs are located under /storage/db/pakRepoLocal/ as can be seen below by using “tab completion” (hit tab twice in a row). Now its just a matter of choosing the right management pack you want to uninstall and complete the path by adding manifest.txt to the end of the command line. The command cat will output the content of the manifest.txt file. From this we need the “name” in this case its “ep-ops-ad”.

Cat manifest.txt

Now change directory to /usr/lib/vmware-vcops/tools/opscli/ and then type ./ops-cli.sh solution uninstall and then the name of the management pack. By the way quotations marks are needed as part of the command, so you might as well copy that from the output.

Uninstall Management Pack

Hit enter.

Dead easy, now sit back relax and enjoy the show. (it only lasts a short while)

Uninstall Management Pack finished

The second to last line will tell you the status of the uninstall command. In this case it successfully finished. Hooray!


The commands

By the way if you think less people using cd – Here is the command for running the python command without the ops-cli.sh script wrapper, which is just what ops-cli.sh is.

$VMWARE_PYTHON_BIN /usr/lib/vmware-vcops/tools/opscli/ops-cli.py solution uninstall “ep-ops-ad”


Final note before I finish this blog post – Note the three lines which are highlighted below – These lines always shows an doesn’t change the out come of the uninstall process.

Uninstall Management Pack finished failure

SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.


Thanks for reading – Take care

Leave a Reply

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