A reminder some week ago would have been welcome. I can’t find any mail sent around 6 or 8 months ago but that’s should comes from our side, probable communication issue. Are you able to tell us who was the recipient of the mail you probably sent to warn us?

If you made the change the 1st of May, Six months from May the 1st leads to November the 1st, if I’m correct.

I can’t find find where the packs are. I guess they’re not publicly available, and so, in another repository/place. We do pay a licence for this part of Centreon (even two licences to be exact).

I will investigate from my side to find who may have receive the warning. Maybe there were instruction for packs in it?

@Centreon  : Can you you still sent them to me by mail?
 

Hello,

I am facing exactly the same issue.
@Stéphane : what OS platform are you running your Centreon app on? Mine is Alma Linux and the same issue can be reproduced on AlmaLinux release 8.8 (Sapphire Caracal) and AlmaLinux release 8.7 (Stone Smilodon).

At the same time the same repos work fine when used from our old CentOS 7.9 platfrom (where yum is still the package manager).

For me it looks like something is wrong with dnf package manager on Alma.

this is what dnf.log file is showing:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 573, in load
    ret = self._repo.load()
  File "/usr/lib64/python3.6/site-packages/libdnf/repo.py", line 397, in load
    return _repo.Repo_load(self)
libdnf._error.Error: Failed to download metadata for repo 'centreon-plugin-packs-stable-noarch': repomd.xml parser error: Element <repomd> was not found - Bad repomd file

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 67, in main
    return _main(base, args, cli_class, option_parser_class)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 106, in _main
    return cli_run(cli, base)
  File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 122, in cli_run
    cli.run()
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1038, in run
    self._process_demands()
  File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 741, in _process_demands
    load_available_repos=self.demands.available_repos)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 405, in fill_sack
    self._add_repo_to_sack(r)
  File "/usr/lib/python3.6/site-packages/dnf/base.py", line 140, in _add_repo_to_sack
    repo.load()
  File "/usr/lib/python3.6/site-packages/dnf/repo.py", line 580, in load
    raise dnf.exceptions.RepoError(str(e))
dnf.exceptions.RepoError: Failed to download metadata for repo 'centreon-plugin-packs-stable-noarch': repomd.xml parser error: Element <repomd> was not found - Bad repomd file
2023-10-02T12:03:31+0200 CRITICAL Error: Failed to download metadata for repo 'centreon-plugin-packs-stable-noarch': repomd.xml parser error: Element <repomd> was not found - Bad repomd file

Hi,

If it works on CentOS, I guess this is because it’s an older version and there isn’t a redirection for it.

We use RHEL 8.8 here, Centreon 22.10.11

I also can’t find any Plugin Packs in the new repository, even when trying  with the “secret” part of the URL we had for the old repository.

A nice thing would be that the packs (ie: the templating sorry : “connectors” that goes with de plugins) to be now opensource too and distributed alongside the connectors.
 

Hi,

I guess you’re correct. I’ve just opened a ticket to Centreon support asking to provide me with the valid urls for connectors respositories as they described in the article ( Reorganization of Centreon repositories | Community ):
“Commercial software editions

Contact our support team for updates to Monitoring Connectors repositories (formerly Plugin Packs) and commercial extensions.”

Becasue we are using a commercial edition of Centreon.

Hi,

@Stéphane : I received correct repos from Centreon support for my version. Now it works fine.

I suggest you could do the same as it looks like you are using commercial version of Centreon as well (at least it looks so from the url from your first post).

I just saw it. I’m doing it right now. Thx.

Have you been warned by email six month ago or did you happen to read the blog this post, or elsewhere?

 

Frankly I don’t remember if I received such a warning. And in the meantime we migrated and upgraded Centreon from 21.10 on CentOS to 22.10 on AlmaLinux. So it might be we missed this warning somehow.

I came across this blog post about reorganization of Centreon repositories today when I started creating a ticket in support portal reporting the issue we had both. While creating a description of my ticket some hints with links was presented.
One of them was:
https://support.centreon.com/hc/en-us/articles/10344005610385?input_string=cannot+install+a

From this article I went to the blog post where I found further info:
https://thewatch.centreon.com/product-updates/reorganization-of-centreon-repositories-1771

Following this advice I was supplied with valid repos for the commercial Centreon edition.

“Commercial software editions

Contact our support team for updates to Monitoring Connectors repositories (formerly Plugin Packs) and commercial extensions.”

Didn’t receive an answer yet but it seems they put back the redirection in place.