Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-18415

Stack definition: service component 'cardinality' inheritance not working properly

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.5.0
    • None
    • None

    Description

      In the stack definition if a property of service component is not defined in
      one specific version than it will be inherited from the parent version.

      The `ComponentInfo.cardinality` always has a default value of "0+" from the
      moment the object is instantiated thus the inheritance logic is never applied.
      This leads to if a specific version of a service component doesn't have a
      property set in stack definition it won't inherit it from its parent but
      rather will take the "0+" default value.

      This is not the correct behaviour. First the inheritance should be applied and
      only set `cardinality` to "0+" only if it can't be inherited from the parents
      (as it's not defined in any of the parents up in the inheritance chain)

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            aonishuk Andrew Onischuk Assign to me
            aonishuk Andrew Onischuk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment