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

Blueprints do not handle some failures properly

    XMLWordPrintableJSON

    Details

      Description

      Failures in the cluster configuration task and topology host tasks during blueprint cluster deployment or upscaling are not visible via request status. The logical request stays PENDING even after Ambari Server gave up retrying. Both the fact that it no longer makes progress and any reason of the failure can be seen only in ambari-server.log.

      Some ways to reproduce (all via blueprints):

      • Create cluster with ZooKeeper and HDFS, but omit the NAMENODE component
      • Create a secure cluster with wrong Kerberos credentials
      • Create a secure cluster without storing Kerberos credentials, restart Ambari Server, add a new node

        Attachments

          Activity

            People

            • Assignee:
              adoroszlai Attila Doroszlai
              Reporter:
              adoroszlai Attila Doroszlai
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 2h
                2h