vmware plugin doesnt work since upgrade to Centreon 25.10

Are the other plugins working in comparason ? i have issues with credentials not correctly being decrypted globally. Just so i can see if it’s related or not

I don’t have other issues with other plugins but they are not designed in same way, I mean they use only the snmp things. 

Hello

I’m having the same issue after upgrading from 24.04 to 25.10.

I have multiple pollers and multiple vcenter, I upgradred the platform fully today, and I can see 2 things

for most of the pollers that have the vmware daemon, the json file doesn’t contain the encrypted password, the daemon connect correctly

only one poller has the json with the encrypted login/passwor, and I get the credential error in the log.

I don’t know the difference between the poller, I don’t understand why some poller have the encrypted file and not other, there were no issue during the upgrade process and I have used the command to import the key on every pollers…

here are the packages

rpm -qa | grep -i vmware
perl-VMware-vSphere-7.0.1-17698549.el8.x86_64
centreon-plugin-Applications-Vmware-Vcsa-Snmp-20251100-1.el8.noarch
centreon-plugin-Virtualization-VMWare-daemon-20250800-1.el8.noarch
centreon-plugin-Applications-Vmware-Vcsa-Restapi-20251100-1.el8.noarch
centreon-plugin-Virtualization-Vmware2-Esx-Wsman-20251100-1.el8.noarch
centreon-plugin-Cloud-Vmware-Velocloud-Restapi-20251100-1.el8.noarch
centreon-plugin-Virtualization-Vmware2-Connector-Plugin-20251100-1.el8.noarch

I ‘m seeing a version for the daemon which is older than the other centreon-vmware package, was there a support for the encrypted credential in version 2025-08 of the daemon?

​@christophe.niel-ACT  when you mention the encrypted file, are you talking about the credentials used to decrypt de password between pollers ? There was a step within the upgrade to extract that value, i suppose it is supposed to be done on all pollers for it to work Upgrade from Centreon 24.10 | Centreon Documentation 

​@Alexandre Belhomme, that step with the script at the end 

/usr/share/centreon/bin/writeEngineSecrets.sh xxx xxxx

that is done, that’s not the issue. this just get a small json file with a key/salt and store that on the poller

when I talk about the encrypted json file I’m talking about the “/etc/centreon/centreon_vmware.json” which now contains that :

I went from 24.04 which didn’t have the “additional configuration” so I was ediiting this file manually, I followed the notice from the documentation to create the configuration before pushing the config, i did that

now the files are either containing the vmware credential in clear, or encrypted, it varies.

if I edit the file and put the “unencrypted values” the daemon works

if I leave the encrypt:: strings, the daemon does not work. that’s the issue.

for now I’m making a copy of the file and when I push a config I swap the file and restart the daemon, I ‘m thinking of making a post generation command.

ah

I found out why some poller were generated with the encrypted credentials, now they are all encrypted

I upgraded the platform, and created the additionnal configurations, but I had not upgraded the connector itself before creating the vmware config, I modified one after the connector update and it was the one with the encrypted strings.

now if I update a vmware config from the ui, it is encrypted on the poller

and I tried a post generation command…but it cannot ovwrite the config file. the only solution for now is to change the owner of the file (chown centreon:centreon centreon_vmware.json) this prevent gorgoned to modify the file

not ideal

back to my initial message, is the plugin daemon at a correct version with 202508 ? (for a centreonian)

I’m opening a support ticket in parallel