23.04 : No route found for "GET /api/latest/auto-discovery/scheduling/jobs" after upgrade

Same for us on our test server, upgraded from 22.10.7, also have HTTPS customisations, and the above two URLs and also https://<centreon>/centreon/administration/extensions/manager does not work and just shows a blank page

Accept-Type: application/json; charset=utf-8
2023-05-02 09:21:03 - DEBUG - == Info: TLSv1.3 (IN), TLS handshake, [no content] (0):
2023-05-02 09:21:03 - DEBUG - == Info: TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
2023-05-02 09:21:03 - DEBUG - == Info: TLSv1.3 (IN), TLS handshake, [no content] (0):
2023-05-02 09:21:03 - DEBUG - == Info: TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
2023-05-02 09:21:03 - DEBUG - == Info: TLSv1.3 (IN), TLS app data, [no content] (0):
2023-05-02 09:21:03 - DEBUG - => Recv header: HTTP/1.1 404 Not Found
2023-05-02 09:21:03 - DEBUG - => Recv header: Date: Tue, 02 May 2023 07:21:03 GMT
2023-05-02 09:21:03 - DEBUG - => Recv header: Server: Apache
2023-05-02 09:21:03 - DEBUG - => Recv header: Cache-Control: no-cache, private
2023-05-02 09:21:03 - DEBUG - => Recv header: Api-Version: 23.04
2023-05-02 09:21:03 - DEBUG - => Recv header: Upgrade: h2,h2c
2023-05-02 09:21:03 - DEBUG - => Recv header: Connection: Upgrade
2023-05-02 09:21:03 - DEBUG - => Recv header: Transfer-Encoding: chunked
2023-05-02 09:21:03 - DEBUG - => Recv header: Content-Type: application/json
2023-05-02 09:21:03 - DEBUG - => Recv header: 
2023-05-02 09:21:03 - DEBUG - => Recv data: 95
{"code":404,"message":"No route found for \"GET https:\/\/<centreon>\/centreon\/api\/latest\/auto-discovery\/scheduling\/jobs\""}
0

I just spotted this in the Apache logs, will look into it to see if it helps to find he problem:

[Tue May 02 09:28:36.449519 2023] [mpm_event:notice] [pid 1033:tid 140081380907328] AH00492: caught SIGWINCH, shutting down gracefully
[Tue May 02 09:28:39.602406 2023] [suexec:notice] [pid 7966:tid 139820604209472] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Tue May 02 09:28:39.656151 2023] [ssl:warn] [pid 7966:tid 139820604209472] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache]
[Tue May 02 09:28:39.658228 2023] [lbmethod_heartbeat:notice] [pid 7966:tid 139820604209472] AH02282: No slotmem from mod_heartmonitor
[Tue May 02 09:28:39.665550 2023] [mpm_event:notice] [pid 7966:tid 139820604209472] AH00489: Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k configured -- resuming normal operations
[Tue May 02 09:28:39.665628 2023] [core:notice] [pid 7966:tid 139820604209472] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

Ok, so I fixed the blank page issue for extensions manager by clearing the browser cache, but the others still throw errors.

Yes

Hi,

In my case, the package is up to date.

The only things I changed is the group membership of the user www-data which are not available in Alma8.

 

I changed with :

usermod -a -G apache centreon-broker
usermod -a -G centreon-broker apache

I clean symphony cache and reload php-fpm and httpd and the auto-discovery api seams not working:

2023-05-03 09:08:52 - ERROR - [autodiscovery] -class- host discovery - cannot get host discovery jobs - request error [code: '404'] [message: 'No route found for "GET https://XXXXX/centreon/api/latest/auto-discovery/scheduling/jobs"']

 

Same here as it’s the same “apache” for RHEL8, but somehow it does not surprise me that the Centreon documentation never fits reality - worst one I came across was a plugin which was just a copy/paste of another plugin but none of the text was changed.

I don't use it on my test platform.
However, the installation of this version a few days after its availability makes it possible to anticipate the problems that we could encounter during the production’s migration.
So if the problem is proven, deleting the feature will only hide it :)

Am I to understand that automatic host discovery is no longer available for the IT-100 platform?

If so, it is strange to report that the API is not available.

Service auto-discovery seams work.

Will deleting the /etc/centreon-gorgone/config.d/41-autodiscovery.yaml file result in no longer processing host discovery, service discovery or both?

Hi @Laurent thanks for this confirmation :)

But, in my case, IT-100 is valid and the extension is deployed :

In fact I tried to remove the extension and reinstall it.

Now, api /auto-discovery/scheduling/jobs is now available and works.

But, I lose all my active discovery rules.

I hope not to have to do this operation during the migration of my production. It will be problematic to lose all my discovery rules.

Hello could you try to launch this command 

sudo -u apache php /usr/share/centreon/bin/console debug:router | grep scheduling

If your cache is correctly refreshed you should see the following result

# sudo -u apache php /usr/share/centreon/bin/console debug:router | grep scheduling
  autodiscovery.scheduling.findDiscoveryJobs                               GET      ANY      ANY    /{base_uri}api/{version}/auto-discovery/scheduling/jobs 

No update on getting this resolved ??