I have just upgraded Checkmk from 2.3.0p34 to 2.4.0p10.
While running discovery on several hosts, I noticed that in the Changed services section the discovery parameters that had changed were listed. I selected some of them and executed Host → Update discovery parameters from the GUI (WATO → Host).
To my surprise, Checkmk not only updated the parameters for the services I had selected, but it also applied the changes to all changed services and, more importantly, it automatically inventoried all the Undecided services that had already been present before.
My question is:
is this a bug introduced in 2.4, or is this the intended logic of the new functionality?
There were no vanished services reported by the Check_MK Discovery service before executing the bulk discovery.
I tried reverting these changes, but the discovery still removed all services from a large number of hosts:
Hosts: 274 total (226 succeeded, 44 skipped, 4 failed)
Host labels: 640 total (6 added)
Services: 1125 total (0 added, 7535 removed, 1125 kept)
Bulk discovery successful
As Thomas just posted, we have a somewhat more critical bug here. Could you possibly place the issue internally so that someone can look into it promptly? We will also escalate the issue via our Checkmk partner. Many thanks
I can confirm also this problem. It also happened on one or two of my updates.
I had only no time to investigate further. The only “fix” was to do a complete discovery over all hosts after the initial only update the service parameters.
The speeling inside the werk got a little bit wrong
When both options "Update service parameters" and "Update service parameters" were selected for a bulk discovery, all services were removed from all selected hosts.
