Known Issues

N/A

Manually restart the metrics collectors on affected nodes.

N/A

BUG-108926

After using patch upgrade on storm, exceptions are found in the logs when running service checks.

No known workaround. Service checks exceptions for this service immediately after patch upgrade can be safely ignored.

AMBARI-24848

BUG-113526

When using redhat satelite for repository management, if a repo URL is not specified for each operating system, the installation can fail.

1. Do a fresh sign into Ambari Server.

2. Click on Register Version screen.

3. Click on option "Use local repository"

4. Select the appropriate OS version and remove the unwanted OS version.

5. Put some dummy url (that starts with http://) in the repo fields

6. Now select the option "Use Redhat Satellite repo"

7. Make the package changes if needed and proceed.

AMBARI-24506

BUG-109436

Upgrade History page is blank after a cluster is upgraded multiple times.

No known workaround.

N/A

BUG-109760

YARN Timeline Service V 2.0 Reader component stops after a patch upgrade of the service HBase from HDP 3.0.0 to HDP 3.0.1.

Manually start the YARN Timeline Service V 2.0 Reader component.

N/A

BUG-115503

Unable to create tables after upgrade if running hive as custom user.

Change permissions on the Hive directory.

N/A

BUG-115309

Ambari Metrics System Collector HBase cannot be started after Express Upgrade on secured clusters.

msg=org.apache.hadoop.hbase.NotServingRegionException: 
hbase:meta,,1 is not online 

Clear out the data on the znode specified in ams-hbase-site:zookeeper.znode.parent.

• If Ambari Metrics System is in embedded mode, this can be done by deleting the directory as specified in the ams-hbase-site property 'HBase ZooKeeper Property DataDir'.
• If Ambari Metrics System is in distributed mode, this can be done by deleting the znode in cluster zookeeper using zkCli. Instead of deleting the znode, you canchange the value of the znode from /ams-hbase-unsecure to something like /ams-hbase-unsecure-new.

N/A

Zeppelin Server status alerts are not triggered even when Zeppelin server is stopped.

In the alert_check_zeppelin.py script located in the /var/lib/ambari-agent/cache/common-services/ZEPPELIN/<version>/package/scripts/ folder, change the 'return' statement to the following:

return (RESULT_CODE_CRITICAL, ["Zeppelin is not running"])

N/A

Spectrum Scale installation Fails in Ambari for scripts not found reason.

Exception is seen when the Mpack is integrated with the following error:

stdout: /var/lib/ambari-agent/data/output-402.txt
Caught an exception while executing custom service command: 
<class 'ambari_agent.AgentException.AgentException'>: 
'Script /var/lib/ambari-agent/cache/extensions/SpectrumScaleExtension
/2.7.0.1/services/GPFS/package/scripts/slave.py does not exist'; 
'Script /var/lib/ambari-agent/cache/extensions/SpectrumScaleExtension
/2.7.0.1/services/GPFS/package/scripts/slave.py does not exist'

AMBARI-25069

HDP 3.1.0 with local repository fails to deploy. Empty baseurl values written to the repo files when using a local repository causes an HDP stack installation failure.

1. Go to the folder /usr/lib/ambari-server/web/javascipts using

   cd /usr/lib/ambari-server/web/javascripts 

2. Take a backup of app.js using

   cp app.js app.js_backup 

3. Edit the app.js file. Find the line(39892)

   onNetworkIssuesExist: function () { 

   Change the line from :

    /**
      * Use Local Repo if some network issues exist
      */
     onNetworkIssuesExist: function () {
       if (this.get('networkIssuesExist')) {
         this.get('content.stacks').forEach(function (stack) {
             stack.setProperties({
               usePublicRepo: false,
               useLocalRepo: true
             });
             stack.cleanReposBaseUrls();
         });
       }
     }.observes('networkIssuesExist'),

   to

    /**
      * Use Local Repo if some network issues exist
      */
     onNetworkIssuesExist: function () {
       if (this.get('networkIssuesExist')) {
         this.get('content.stacks').forEach(function (stack) {
           if(stack.get('useLocalRepo') != true){
             stack.setProperties({
               usePublicRepo: false,
               useLocalRepo: true
             });
             stack.cleanReposBaseUrls();
           } 
         });
       }
     }.observes('networkIssuesExist'), 

4. Reload the page, and then start the create cluster wizard again.