Actions
Bug #18052
closedError displayed when switching from full access to read only
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
54
Name check:
To do
Fix check:
Checked
Regression:
Description
Error is: Unknow diff attribute: ApiAccountKind
So most likely there is something wrong with the event log.
It was for a rudder upgraded from 4.1.7 to 5.0.17 on sles 12.
It does not seems to break anything (API token is read only and can be change back without error).
Files
Updated by François ARMAND over 4 years ago
- Project changed from API authorizations to Rudder
- Target version set to 5.0.19
It's actually without api authz plugin
Updated by François ARMAND over 4 years ago
- Related to Bug #12958: Transient error when disabling system api account added
Updated by François ARMAND over 4 years ago
- Related to Bug #13913: Logs full of WARN Attribute 'apiAuthorizationKind' or 'expirationTimestamp' is defined for API account but it will be ignored added
Updated by François ARMAND over 4 years ago
I can't reproduce it with a fresh 5.0 installation, so migration from 4.1 may be mandatory to find it.
Updated by Nicolas CHARLES over 4 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Elaad FURREEDAN
- Pull Request set to https://github.com/Normation/rudder/pull/3160
Updated by Nicolas CHARLES over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|505a290d394de7a689a5dc2f6c1558fe8419a7f9.
Updated by François ARMAND about 4 years ago
- Related to deleted (Bug #12958: Transient error when disabling system api account)
Updated by François ARMAND about 4 years ago
- Has duplicate Bug #12958: Transient error when disabling system api account added
Updated by François ARMAND about 4 years ago
- Priority changed from 65 to 64
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.19, 6.0.8 and 6.1.4 which were released today.
Actions