Skip to main content

Hi,

I did the data migration again (I have to, because our 20.04 platform continues to live and our 22.10 isn’t released yet as our new production platform).

Once again, although the upgrade scripts showed no error. I get a new problem I didn’t had when migrating on previous 22.10 minor versions (!). I can’t upgrade the plugin pack because of this :

 

Luckily I have another 22.10.5 platform (for which I don’t have to refresh the data regularly) so I think I’ll be able to fix this issue, but I wonder if it would not be possible for Centreon QA team to test all upgrade’s and migration’s procedures before releasing a new version? Or if developers could avoid modifying the data structure for minor/bugfix versions?

Also, although the configuration of our five pollers has been migrated the same way (automated by a script), only four are able to generate and push the configuration. One can’t, it doesn’t generate the files in /var/cache/centreon/config/<poller ID> but get stuck after creating a /var/cache/centreon/config/tmpdir_REuz9B.d directory. And it also doesn’t create the broker configuration files. Another issue that I didn’t had on previous data migrations and that I’ll have to fix now (!).

We will try to follow the next releases for upgrades, although the two years support period is extremely short for our structure, so we don’t have to do another migration in the future, because it’s a nightmare. “Minor versions” (I should tell “revision”, because usually, when using a X.Y.Z version number, it means major.minor.revision…) break things nearly every times. Centreon’s quality is dropping every year. There weren’t those kind of issues in the 2.8 era and before. Now there even are some obvious display bugs that get released (like the one fixed in 22.10.5 due to a change in PHP), it’s like there were absolutely no testing before a release (this bug was visible with a standard Centreon plugin (Linux SNMP), not an exotic or third-party one).

I’m starting to understand why Centreon stopped anonymously available bug reports in Github and forced users and customers to use “TheWatch”… I’m not surprised the commercial support gets flooded, I don’t think this is due to the success represented by switching to Zendesk, as I read in a mail… 

We should switch our production to 22.10.5 soon so this bad experience with the migration will be no more, but I’m scared about Centreon’s future if so poor quality standards continue to be are practiced.

Hi @Stéphane, sorry to hear that. Your feedback is being reviewed to see what went wrong and if necessary, a member of our Product Team will get back you. I also expect that now that you're on 22.10, you'll be able to upgrade more often so you don't have to worry about big update skips.

For the next plugin updates I think I’ll do them one by one. So I’ll be able to fix the problems I’ll certainly have.

Yesterday I observed yet another thing I don’t understand: In the plugin to check broker health, in centreon_centreon_poller.pl the option --ssh-options has been replaced with a --ssh-username and such, why not. But in centreon_centreon_central.pl this is still --ssh-options which is used… It definitevly makes non sens.

Hi @Stéphane, sorry to hear that. Your feedback is being reviewed to see what went wrong and if necessary, a member of our Product Team will get back you. I also expect that now that you're on 22.10, you'll be able to upgrade more often so you don't have to worry about big update skips.

It’s not only about updates. We needed to do a migration in order to have a rollback solution (and going from CentOS7 to RHEL 8 would not have been possible with a simple update).
That’s this upgrade which has be a real pain in the ass because of the tons of compatibility breaks that have been introduced.

Still found another problem just today with the Netapp plugin. It has been replaced by a “Netapp Ontap” plugin which change all the options and so, made our current templates exploded in fly… The only solution was to get the 20.04 centreon_netapp.pl script from our 20.04 plateform.

Please be more cautious with backward compatibilty. Introducing new trending functionalities for new users/customers may not be done at the expense of existing users/customers. 


 

Reply


Terms & ConditionsCookie settings