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

Client config tags may not be saved by agent

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
    • 2.5.0
    • 3.0.0, 2.5.0
    • ambari-agent
    • None

    Description

      Ambari agent does not save the config tags (eg. "V1") during component installation if it cannot determine that the component is a client. For this decision it requests the list of services/components right after it receives the first status command, which might happen after some client components are already installed. If the initial tags are missing, no subsequent config changes trigger updates on the affected host (except forced update via "Service Actions > Refresh configs").

      Attachments

        Activity

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

          People

            adoroszlai Attila Doroszlai Assign to me
            adoroszlai Attila Doroszlai
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment