Uploaded image for project: 'Activation'
  1. Activation
  2. MGNLACTIVATION-145

Publishing config:modules broke public instances

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 5.5.1
    • None
    • Linux RHEL
      H2 Database
      Oracle Java 1.8
      Apache Tomcat 8.0
    • Yes
    • Yes

    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.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              viet.nguyen Viet Nguyen
              jarkko.mantysaari Jarkko Mantysaari
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - 5.25d
                    5.25d
                    Remaining:
                    Time Spent - 0.25d Remaining Estimate - 5d
                    5d
                    Logged:
                    Time Spent - 0.25d Remaining Estimate - 5d
                    0.25d