Bug #12752
closedDatasources plugin scheduler problems after updating/deleting a datasource
Description
plugin version : rudder-plugin-datasources-4.3-1.3-SNAPSHOT.rpkg
When updating some parameters in a datasource (for exemple jsonpath, update trigger, ...), the execution of this datasource is twice or more. It's hard to reproduce, but if you change settings multiple times the problem occure.
I notice that it happen when both "update periodically" and "update when a policy update start" trigger are configured.
Restarting jetty doesn't solve the problem if the datasource is still present.
You can see logs in attachement for more details.
Notice : At this time the datasource was delete but still in execution.
[2018-06-06 16:38:02] DEBUG datasources - Stopping data source with id 'cmdb-debug'
[2018-06-06 16:38:02] TRACE datasources - The datasource with id 'cmdb-debug' is disabled. Not scheduling future runs for it.
[2018-06-06 16:38:02] DEBUG datasources - Data source 'cmdb-debug' (cmdb-debug) udpated
[2018-06-06 16:38:10] DEBUG datasources - Stopping data source with id 'cmdb-debug'
Restarting jetty after deleting the datasource stop this execution.
We already have similar problem when deleting a datasource here https://www.rudder-project.org/redmine//issues/10677
Thank you
Files
Updated by Benoît PECCATTE over 6 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 52
Updated by François ARMAND over 6 years ago
- Related to Bug #10677: Datasources plugin call continuously datasource url even after delete added
Updated by Vincent MEMBRÉ about 6 years ago
- Project changed from Rudder to 54
- Category deleted (
71) - Target version set to 433
- Priority changed from 52 to 50
Updated by Vincent MEMBRÉ about 6 years ago
- Project changed from 54 to Datasources
- Target version changed from 433 to 4.1-1.3
- Priority changed from 50 to 49
Updated by François ARMAND over 1 year ago
- Status changed from New to In progress
- Target version changed from 4.1-1.3 to 7.2
- Priority changed from 49 to 0
- Regression set to No
We are resurecting that old bug because we see it again.
Updated by François ARMAND over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-plugins/pull/550
Updated by Anonymous over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder-plugins|a6c14022e62f12637c2cfa6802309a1c9e87777f.
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder plugin datasources v7.3.0-2.3
Updated by Vincent MEMBRÉ over 1 year ago
This bug has been fixed in Rudder plugin datasources v7.3.0-2.3
Updated by Vincent MEMBRÉ over 1 year ago
This bug has been fixed in Rudder plugin datasources v7.2.6-2.2
Updated by François ARMAND over 1 year ago
- Related to Bug #22971: Spurious test error on the killing of old fiber on datasource save/delete added