PowerStore: VSI Plugin Not Updating or Reading Host Best Practices

After registering vCenter in the VSI Plugin, VSI fails to apply the Host Best Practices; however, there is no error reported in vCenter.

In this case, the vCenter password contained the "|" pipe character which was causing the API call to fail as seen in the VSI log output below:

 

2021-03-01 01:33:20 [pool] ERROR c.e.i.c.c.ExecuteResult:23 - /bin/sh: XXX_XXx: command not found
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='ANSI_X3.4-1968'>
BrokenPipeError: [Errno 32] Broken pipe

In the error above, XXX_XXx was actually a part of the vCenter password of XXX|XXX_XXx.  VSI API call was interpreting the password as a command due to the "|" pipe character.  This resulted in the failure to apply the Host Best Practice.

Replace the incorrect special character with a supported special character. In this case, the "|" pipe character was replaced with the "@" character.  It is advised to use special characters that cannot be interpreted as a command such as the "|" pipe character and the "!" bang character.

The following steps will need to be followed:

1) Reset vCenter password
2) Unregister vCenter in VSI
3) Re-register vCenter in VSI
4) Apply the Host Best Practice

An additional note to consider.  During the re-registering of vCenter within VSI, the incorrect IP address may be associated with the vCenter FQDN due to an HA adapter being configured for the vCenter host.  In this case, the HA adapter was added after the original VSI registration. When the re-register attempt was made, an "Incorrect Password" error was received.  Upon investigation, it was found that VSI was associating the HA adapter as the Primary network adapter for the vCenter host which caused the password error.  The HA adapter was removed from the host and the re-registration was successful.