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

proxy user settings need to be set when provisioning via a blueprint

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

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.5.0
    • 1.6.0
    • None

    Description

      In core-site, there are a bunch of proxyuser settings.

      These are in the form of :
      hadoop.proxyuser.<username>.hosts
      hadoop.proxyuser.<username>.groups

      These are dynamically generated property names because they contain the user name in the property name.
      These are currently not present in the stack definitions and are generated by the UI.

      These are currently not being set when provisioning via a blueprint.

      Until this is completed, users that deploy clusters that require proxy user properties will have to add them to the blueprint manually.
      For example:

      {
          "configurations" : [
              { 
                  "core-site" : {
                     "hadoop.proxyuser.oozie.hosts" : "*",
                     "hadoop.proxyuser.oozie.groups" : "users" ,
                     ...
                  } 
              }
          ]
          ...
      }   
      

      For more on cluster scoped blueprint configuration see:
      https://issues.apache.org/jira/browse/AMBARI-5114

      Attachments

        Activity

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

          People

            jspeidel John Speidel Assign to me
            jspeidel John Speidel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment