Actions
Bug #25368
closedApply policy returns a json error when clicking on trigger agent
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
It bothers me each time
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Very Small
Priority:
134
Name check:
To do
Fix check:
To do
Regression:
No
Description
The Trigger agent
button now returns an error from the API every time :
Exception in thread "zio-fiber-3992" com.normation.errors$Chained: Chained(An error occurred when applying policy on Node 'c872b43f-77c7-4f12-9e4b-bd5b07f2b464',Unexpected(Unexpected end of input))|?at com.normation.errors.PureToIoResult.toIO(ZioCommons.scala:214)|?at com.normation.rudder.rest.lift.NodeApi.ApplyPolicy.process(NodeApi.scala:524)|?at com.normation.errors.IOChainError.chainError(ZioCommons.scala:202)|?at com.normation.zio.ZioRuntime.unsafeRun(ZioCommons.scala:445) at com.normation.errors.PureToIoResult.toIO(ZioCommons.scala:214) at com.normation.rudder.rest.lift.NodeApi.ApplyPolicy.process(NodeApi.scala:524) at com.normation.errors.IOChainError.chainError(ZioCommons.scala:202) at com.normation.zio.ZioRuntime.unsafeRun(ZioCommons.scala:445)
It seems that the v20 API now expects a JSON object since #24851 but receives an empty string.
The API should support an empty string for the /applyPolicy
endpoint.
Updated by Clark ANDRIANASOLO about 2 months ago
- Related to Architecture #24851: Migrate NodeApi to zio-json added
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5840
Updated by Clark ANDRIANASOLO about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|fafecf586385c809f5cf75dba0aa9e1e03523852.
Updated by Vincent MEMBRÉ about 1 month ago
- Status changed from Pending release to Released
- Priority changed from 67 to 134
This bug has been fixed in Rudder 8.2.0~beta1 which was released today.
Actions