After deploying some custom packages, CM_NIMBUS_PACKAGE is not updated
Article ID: 375194
Updated On:
Products
Issue/Introduction
When I deploy some of my custom packages to destination robots, the cm_nimbus_package table that is usually updated automatically and immediately, does not update, until I restar the discovery_sever. Why does this happen?
Environment
DX UIM 20.4.* /23.4.*
Cause
The custom package that is created and deployed and that is creating this issue, is most likely not associated with any probe. Because of this, no event is being sent to the discovery server when the package is installed. As per the current design, an event is only triggered when a package containing a valid probe is deployed. Only then does the discovery server retrieve the necessary information from the corresponding robot and update the package and probe details in the database.
When a non-probe package is deployed on a robot, no event is generated specifically for it. Instead, the package details are simply recorded in the installed.pkg file. Even though an event is created in that particular case, it is an internal event, but only in response to changes related to probes on the robot.
when a valid probe package is subsequently installed, an event is generated. At this point, the discovery server retrieves all relevant information from the robot, including details about previously installed non-probe packages, and updates the database accordingly.
This means that while no immediate event is triggered for non-probe packages, their information is still captured and reflected in the discovery server during the next probe-related update.
Resolution
This is working as designed, it is expected that custom packages non associated to any probe do not trigger an event that updates the cm_nimbus_package table.
Having the controller to send events to the discovery server for custom packages without a valid probe an enhancement Request can be filled in in form of a Community IDEA.
Additional Information
Feedback
