Actions
Bug #22830
closed
Message “Error getting directive compliance” when creating new directive
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I was bothered the first time
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
108
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Hello,
Seen on Rudder 7.3.2 :
When creating a new directive, clicking on the “compliance” tab for the first time displays message as attached below.
Files
Updated by Vincent MEMBRÉ about 1 year ago
- Target version changed from 7.3.3 to 7.3.4
Updated by Vincent MEMBRÉ 12 months ago
- Target version changed from 7.3.4 to 7.3.5
- Priority changed from 110 to 109
Updated by Raphael GAUTHIER 12 months ago
- Status changed from New to In progress
- Assignee set to Raphael GAUTHIER
Updated by Raphael GAUTHIER 12 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder/pull/4947
Updated by Raphael GAUTHIER 12 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|2e7b67be999e3b155e9d9046f0af5d7fcddd3ac5.
Updated by Nicolas CHARLES 12 months ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset 11 months ago
- Status changed from Pending release to Released
- Priority changed from 109 to 108
This bug has been fixed in Rudder 7.3.5 which was released today.
Actions