[MGNLACTIVATION-145] Publishing config:modules broke public instances Created: 24/Jan/17  Updated: 22/Sep/17  Resolved: 28/Jul/17

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.5.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jarkko Mantysaari Assignee: Viet Nguyen
Resolution: Obsolete Votes: 1
Labels: None
Remaining Estimate: 5d
Time Spent: 0.25d
Original Estimate: 5.25d
Environment:

Linux RHEL
H2 Database
Oracle Java 1.8
Apache Tomcat 8.0


Attachments: File userroles.foo.yaml    
Issue Links:
Relates
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:

 Description   

Please refer to bug description and comments in SUPPORT-7161 for more detail.
For short:

  • We have a user who has permission on Configuration app and his module (any module) only, note that he don't have permission on other modules, configuration or server.
  • He made a minor change on his /modules/xyz@abc='changed'
  • He published his /modules node include sub-nodes.
  • After restarting public instance, all configs gone and the instance started from scratch.

    Expected result: Either the publish gets rejected (node contains unpermitted subnodes) or only the allowed module is published.



 Comments   
Comment by Viet Nguyen [ 28/Jul/17 ]

Dear jarkko.mantysaari,
The issue does not happen on 5.5.5 anymore, and also because all other nodes get published once (the sequence is not guaranteed), so result of such publishing is unpredictable and might result in instance going down (but was still functional in my case).
--> So let's just close it as it has been fixed somewhere or it just happen occasionally and unpredictably when allowing a specific user to publish all configurations.
Have a good day!

Generated at Sun Feb 11 23:00:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.