[jira] [Comment Edited] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
[
https://issues.apache.org/jira/browse/AMBARI-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150767#comment-17150767
]
Masahiro Tanaka edited comment on AMBARI-25528 at 7/3/20, 6:39 AM:
---
When we compile ambari like {{mvn clean package -DskipTests -Drat.skip}}, it
kicks
[azuredb_create_generator.sh|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/pom.xml#L774].
Then it runs
[azuredb_create_generator.py|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/src/main/python/azuredb_create_generator.py#L1]
which has {{#!/usr/bin/env python}} shebang.
It might be replaced with {{#!/usr/bin/env python2}} as [Python community
encourages to have python2 command|https://www.python.org/dev/peps/pep-0394/].
As far as I confirmed, AmazonLinux2, Ubuntu18.04, CentOS7 have {{python2}}
command.
was (Author: masatana):
When we compile ambari like {{mvn clean package -DskipTests -Drat.skip}}, it
kicks
[azuredb_create_generator.sh|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/pom.xml#L774].
Then it runs
[azuredb_create_generator.py|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/src/main/python/azuredb_create_generator.py#L1]
which has {{#!/usr/bin/env python}} shebang.
It might be replaced with {{#!/usr/bin/env python2}} as [Python community
encourages to have python2 command|https://www.python.org/dev/peps/pep-0394/].
As far as I confirmed, AmazonLinux2, Ubuntu18.04, CentOS7 have {{pythno2}}
command.
> Unable to build Ambari Server on RHEL8 due to lack of python command
>
>
> Key: AMBARI-25528
> URL: https://issues.apache.org/jira/browse/AMBARI-25528
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.1, 2.7.6
> Environment: CentOS8/RHEL8
>Reporter: Masahiro Tanaka
>Priority: Major
>
> When building ambari-server on RHEL8/CentOS8, I got an error like below:
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
> /usr/bin/env: 'python': No such file or directory
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Web . SUCCESS [ 34.585
> s]
> [INFO] Ambari Views ... SUCCESS [ 1.296
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 54.170
> s]
> [INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.264
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 3.927
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [ 23.907
> s]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.315
> s]
> [INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:14
> min]
> [INFO] Ambari Server .. FAILURE [ 3.976
> s]
> [INFO] Ambari Functional Tests SKIPPED
> {code}
> I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
[
https://issues.apache.org/jira/browse/AMBARI-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150767#comment-17150767
]
Masahiro Tanaka commented on AMBARI-25528:
--
When we compile ambari like {{mvn clean package -DskipTests -Drat.skip}}, it
kicks
[azuredb_create_generator.sh|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/pom.xml#L774].
Then it runs
[azuredb_create_generator.py|https://github.com/apache/ambari/blob/branch-2.7/ambari-server/src/main/python/azuredb_create_generator.py#L1]
which has {{#!/usr/bin/env python}} shebang.
It might be replaced with {{#!/usr/bin/env python2}} as [Python community
encourages to have python2 command|https://www.python.org/dev/peps/pep-0394/].
As far as I confirmed, AmazonLinux2, Ubuntu18.04, CentOS7 have {{pythno2}}
command.
> Unable to build Ambari Server on RHEL8 due to lack of python command
>
>
> Key: AMBARI-25528
> URL: https://issues.apache.org/jira/browse/AMBARI-25528
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.1, 2.7.6
> Environment: CentOS8/RHEL8
>Reporter: Masahiro Tanaka
>Priority: Major
>
> When building ambari-server on RHEL8/CentOS8, I got an error like below:
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
> /usr/bin/env: 'python': No such file or directory
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Web . SUCCESS [ 34.585
> s]
> [INFO] Ambari Views ... SUCCESS [ 1.296
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 54.170
> s]
> [INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.264
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 3.927
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [ 23.907
> s]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.315
> s]
> [INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:14
> min]
> [INFO] Ambari Server .. FAILURE [ 3.976
> s]
> [INFO] Ambari Functional Tests SKIPPED
> {code}
> I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
[
https://issues.apache.org/jira/browse/AMBARI-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148524#comment-17148524
]
Masahiro Tanaka commented on AMBARI-25528:
--
I checked with branch-2.7 and it's reproducible.
> Unable to build Ambari Server on RHEL8 due to lack of python command
>
>
> Key: AMBARI-25528
> URL: https://issues.apache.org/jira/browse/AMBARI-25528
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.1, 2.7.6
> Environment: CentOS8/RHEL8
>Reporter: Masahiro Tanaka
>Priority: Major
>
> When building ambari-server on RHEL8/CentOS8, I got an error like below:
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
> /usr/bin/env: 'python': No such file or directory
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Web . SUCCESS [ 34.585
> s]
> [INFO] Ambari Views ... SUCCESS [ 1.296
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 54.170
> s]
> [INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.264
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 3.927
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [ 23.907
> s]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.315
> s]
> [INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:14
> min]
> [INFO] Ambari Server .. FAILURE [ 3.976
> s]
> [INFO] Ambari Functional Tests SKIPPED
> {code}
> I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
[
https://issues.apache.org/jira/browse/AMBARI-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-25528:
-
Affects Version/s: 2.7.6
2.6.1
> Unable to build Ambari Server on RHEL8 due to lack of python command
>
>
> Key: AMBARI-25528
> URL: https://issues.apache.org/jira/browse/AMBARI-25528
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.6.1, 2.7.6
> Environment: CentOS8/RHEL8
>Reporter: Masahiro Tanaka
>Priority: Major
>
> When building ambari-server on RHEL8/CentOS8, I got an error like below:
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
> /usr/bin/env: 'python': No such file or directory
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Web . SUCCESS [ 34.585
> s]
> [INFO] Ambari Views ... SUCCESS [ 1.296
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 54.170
> s]
> [INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.264
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 3.927
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [ 23.907
> s]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.315
> s]
> [INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:14
> min]
> [INFO] Ambari Server .. FAILURE [ 3.976
> s]
> [INFO] Ambari Functional Tests SKIPPED
> {code}
> I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
[
https://issues.apache.org/jira/browse/AMBARI-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148455#comment-17148455
]
Masahiro Tanaka commented on AMBARI-25528:
--
[~hapylestat] Thank you for the comment.
I noticed this problem with BIGTOP-3371 . So the ambari version is 2.6.1.
I'll check whether other versions affect this problem, and will update this
issue's information.
> Unable to build Ambari Server on RHEL8 due to lack of python command
>
>
> Key: AMBARI-25528
> URL: https://issues.apache.org/jira/browse/AMBARI-25528
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Environment: CentOS8/RHEL8
>Reporter: Masahiro Tanaka
>Priority: Major
>
> When building ambari-server on RHEL8/CentOS8, I got an error like below:
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
> /usr/bin/env: 'python': No such file or directory
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.008
> s]
> [INFO] Ambari Web . SUCCESS [ 34.585
> s]
> [INFO] Ambari Views ... SUCCESS [ 1.296
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 54.170
> s]
> [INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.264
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 3.927
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [ 23.907
> s]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.315
> s]
> [INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:14
> min]
> [INFO] Ambari Server .. FAILURE [ 3.976
> s]
> [INFO] Ambari Functional Tests SKIPPED
> {code}
> I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (AMBARI-25528) Unable to build Ambari Server on RHEL8 due to lack of python command
Masahiro Tanaka created AMBARI-25528:
Summary: Unable to build Ambari Server on RHEL8 due to lack of
python command
Key: AMBARI-25528
URL: https://issues.apache.org/jira/browse/AMBARI-25528
Project: Ambari
Issue Type: Improvement
Components: ambari-server
Environment: CentOS8/RHEL8
Reporter: Masahiro Tanaka
When building ambari-server on RHEL8/CentOS8, I got an error like below:
{code}
[INFO] --- exec-maven-plugin:1.2.1:exec (azuredb-gen) @ ambari-server ---
/usr/bin/env: 'python': No such file or directory
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main 2.6.1.0.0 .. SUCCESS [ 1.548 s]
[INFO] Apache Ambari Project POM .. SUCCESS [ 0.008 s]
[INFO] Ambari Web . SUCCESS [ 34.585 s]
[INFO] Ambari Views ... SUCCESS [ 1.296 s]
[INFO] Ambari Admin View .. SUCCESS [ 54.170 s]
[INFO] utility 1.0.0.0-SNAPSHOT ... SUCCESS [ 0.245 s]
[INFO] ambari-metrics . SUCCESS [ 0.264 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 3.927 s]
[INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.345 s]
[INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.508 s]
[INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.568 s]
[INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.129 s]
[INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 1.918 s]
[INFO] Ambari Metrics Collector ... SUCCESS [ 23.907 s]
[INFO] Ambari Metrics Monitor . SUCCESS [ 1.315 s]
[INFO] Ambari Metrics Grafana 2.1.0.0.0 ... SUCCESS [ 5.045 s]
[INFO] Ambari Metrics Assembly SUCCESS [01:14 min]
[INFO] Ambari Server .. FAILURE [ 3.976 s]
[INFO] Ambari Functional Tests SKIPPED
{code}
I guess the root cause is RHEL8/CentOS8 drops python command but python2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25499) Unable to build ambari 2.7.5
[
https://issues.apache.org/jira/browse/AMBARI-25499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114009#comment-17114009
]
Masahiro Tanaka commented on AMBARI-25499:
--
[~hapylestat], [~csaltos] Thanks for working on this!
> Unable to build ambari 2.7.5
>
>
> Key: AMBARI-25499
> URL: https://issues.apache.org/jira/browse/AMBARI-25499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.7.1, 2.7.3, 2.7.4, 2.7.5
>Reporter: Luigi Caramico
>Assignee: Dmytro Grinenko
>Priority: Major
> Fix For: 2.7.6
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> following the instruction on
> [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.5]
>
> I started to build Ambari but I get the error:
>
> {code}
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> {code}
>
> {code}
> [INFO] bower@1.3.8 node_modules/bower
> [INFO] ├── is-root@0.1.0
> [INFO] ├── stringify-object@0.2.1
> [INFO] ├── junk@0.3.0
> [INFO] ├── abbrev@1.0.9
> [INFO] ├── which@1.0.9
> [INFO] ├── opn@0.1.2
> [INFO] ├── bower-endpoint-parser@0.2.2
> [INFO] ├── chmodr@0.1.2
> [INFO] ├── bower-logger@0.2.2
> [INFO] ├── archy@0.0.2
> [INFO] ├── q@1.0.1
> [INFO] ├── lockfile@0.4.3
> [INFO] ├── nopt@3.0.6
> [INFO] ├── rimraf@2.2.8
> [INFO] ├── lru-cache@2.5.2
> [INFO] ├── retry@0.6.1
> [INFO] ├── tmp@0.0.23
> [INFO] ├── osenv@0.1.5 (os-tmpdir@1.0.2, os-homedir@1.0.2)
> [INFO] ├── chalk@0.4.0 (ansi-styles@1.0.0, has-color@0.1.7, strip-ansi@0.1.1)
> [INFO] ├── semver@2.3.2
> [INFO] ├── request-progress@0.3.1 (throttleit@0.0.2)
> [INFO] ├── p-throttler@0.0.1 (q@0.9.7)
> [INFO] ├── graceful-fs@3.0.12 (natives@1.1.6)
> [INFO] ├── shell-quote@1.4.3 (array-filter@0.0.1, jsonify@0.0.0,
> array-reduce@0.0.0, array-map@0.0.0)
> [INFO] ├── bower-json@0.4.0 (intersect@0.0.3, deep-extend@0.2.11,
> graceful-fs@2.0.3)
> [INFO] ├── mkdirp@0.5.5 (minimist@1.2.5)
> [INFO] ├── promptly@0.2.1 (read@1.0.7)
> [INFO] ├── fstream@0.1.31 (inherits@2.0.4)
> [INFO] ├── tar@0.1.20 (inherits@2.0.4, block-stream@0.0.9)
> [INFO] ├── fstream-ignore@0.0.10 (inherits@2.0.4, minimatch@0.3.0)
> [INFO] ├── glob@4.0.6 (inherits@2.0.4, once@1.4.0, minimatch@1.0.0)
> [INFO] ├── request@2.36.0 (tunnel-agent@0.4.3, aws-sign2@0.5.0,
> forever-agent@0.5.2, qs@0.6.6, oauth-sign@0.3.0, mime@1.2.11,
> json-stringify-safe@5.0.1, node-uuid@1.4.8, tough-cookie@4.0.0,
> http-signature@0.10.1, form-data@0.1.4, hawk@1.0.0)
> [INFO] ├── bower-config@0.5.3 (osenv@0.0.3, graceful-fs@2.0.3,
> optimist@0.6.1)
> [INFO] ├── cardinal@0.4.4 (ansicolors@0.2.1, redeyed@0.4.4)
> [INFO] ├── decompress-zip@0.0.8 (nopt@2.2.1, mkpath@0.1.0, touch@0.0.2,
> readable-stream@1.1.14, binary@0.3.0)
> [INFO] ├── bower-registry-client@0.2.4 (async@0.2.10, graceful-fs@2.0.3,
> request-replay@0.2.0, lru-cache@2.3.1, mkdirp@0.3.5, request@2.51.0)
> [INFO] ├── update-notifier@0.2.2 (is-npm@1.0.0, semver-diff@2.1.0,
> chalk@0.5.1, string-length@1.0.1, latest-version@1.0.1, configstore@0.3.2)
> [INFO] ├── handlebars@1.3.0 (optimist@0.3.7, uglify-js@2.3.6)
> [INFO] ├── insight@0.3.1 (object-assign@0.1.2, async@0.2.10,
> lodash.debounce@2.4.1, request@2.27.0, configstore@0.2.3, inquirer@0.4.1)
> [INFO] ├── mout@0.9.1
> [INFO] └── inquirer@0.5.1 (mute-stream@0.0.4, async@0.8.0, through@2.3.8,
> lodash@2.4.2, readline2@0.1.1, cli-color@0.3.3)
> [INFO]
> [INFO] phantomjs@2.1.7 node_modules/phantomjs
> [INFO] ├── progress@1.1.8
> [INFO] ├── kew@0.7.0
> [INFO] ├── which@1.2.14 (isexe@2.0.0)
> [INFO] ├── request-progress@2.0.1 (throttleit@1.0.0)
> [INFO] ├── hasha@2.2.0 (is-stream@1.1.0, pinkie-promise@2.0.1)
> [INFO] ├── extract-zip@1.5.0 (debug@0.7.4, yauzl@2.4.1, concat-stream@1.5.0,
> mkdirp@0.5.0)
> [INFO] ├── fs-extra@0.26.7 (path-is-absolute@1.0.1, klaw@1.3.1,
> graceful-fs@4.2.3, jsonfile@2.4.0, rimraf@2.7.1)
> [INFO] └── request@2.67.0 (aws-sign2@0.6.0, tunnel-agent@0.4.3,
> oauth-sign@0.8.2, forever-agent@0.6.1, caseless@0.11.0, is-typedarray@1.0.0,
> stringstream@0.0.6, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.2,
> tough-cookie@2.2.2, qs@5.2.1, node-uuid@1.4.8, combined-stream@1.0.8,
> mime-types@2.1.26, bl@1.0.3, hawk@3.1.3, har-validator@2.0.6,
> http-signature@1.1.1, form-data@1.0.1)
> [INFO]
> [INFO] karma-phantomjs-launcher@0.1.4 node_modules/karma-phantomjs-launcher
> [INFO] └── phantomjs@1.9.20 (progress@1.1.8, kew@0.7.0, which@1.2.14,
> request-progress@2.0.1, hasha@2.2.0, extract-zip@1.5.0, fs-extra@0.26.7,
> request@2.67.0)
> [INFO]
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> Stack trace:
> SyntaxError: Unexpected
[jira] [Commented] (AMBARI-25499) Unable to build ambari 2.7.5
[
https://issues.apache.org/jira/browse/AMBARI-25499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111667#comment-17111667
]
Masahiro Tanaka commented on AMBARI-25499:
--
[~hapylestat] ping
> Unable to build ambari 2.7.5
>
>
> Key: AMBARI-25499
> URL: https://issues.apache.org/jira/browse/AMBARI-25499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.7.1, 2.7.3, 2.7.4, 2.7.5
>Reporter: Luigi Caramico
>Assignee: Dmytro Grinenko
>Priority: Major
>
> following the instruction on
> [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.5]
>
> I started to build Ambari but I get the error:
>
> {code}
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> {code}
>
> {code}
> [INFO] bower@1.3.8 node_modules/bower
> [INFO] ├── is-root@0.1.0
> [INFO] ├── stringify-object@0.2.1
> [INFO] ├── junk@0.3.0
> [INFO] ├── abbrev@1.0.9
> [INFO] ├── which@1.0.9
> [INFO] ├── opn@0.1.2
> [INFO] ├── bower-endpoint-parser@0.2.2
> [INFO] ├── chmodr@0.1.2
> [INFO] ├── bower-logger@0.2.2
> [INFO] ├── archy@0.0.2
> [INFO] ├── q@1.0.1
> [INFO] ├── lockfile@0.4.3
> [INFO] ├── nopt@3.0.6
> [INFO] ├── rimraf@2.2.8
> [INFO] ├── lru-cache@2.5.2
> [INFO] ├── retry@0.6.1
> [INFO] ├── tmp@0.0.23
> [INFO] ├── osenv@0.1.5 (os-tmpdir@1.0.2, os-homedir@1.0.2)
> [INFO] ├── chalk@0.4.0 (ansi-styles@1.0.0, has-color@0.1.7, strip-ansi@0.1.1)
> [INFO] ├── semver@2.3.2
> [INFO] ├── request-progress@0.3.1 (throttleit@0.0.2)
> [INFO] ├── p-throttler@0.0.1 (q@0.9.7)
> [INFO] ├── graceful-fs@3.0.12 (natives@1.1.6)
> [INFO] ├── shell-quote@1.4.3 (array-filter@0.0.1, jsonify@0.0.0,
> array-reduce@0.0.0, array-map@0.0.0)
> [INFO] ├── bower-json@0.4.0 (intersect@0.0.3, deep-extend@0.2.11,
> graceful-fs@2.0.3)
> [INFO] ├── mkdirp@0.5.5 (minimist@1.2.5)
> [INFO] ├── promptly@0.2.1 (read@1.0.7)
> [INFO] ├── fstream@0.1.31 (inherits@2.0.4)
> [INFO] ├── tar@0.1.20 (inherits@2.0.4, block-stream@0.0.9)
> [INFO] ├── fstream-ignore@0.0.10 (inherits@2.0.4, minimatch@0.3.0)
> [INFO] ├── glob@4.0.6 (inherits@2.0.4, once@1.4.0, minimatch@1.0.0)
> [INFO] ├── request@2.36.0 (tunnel-agent@0.4.3, aws-sign2@0.5.0,
> forever-agent@0.5.2, qs@0.6.6, oauth-sign@0.3.0, mime@1.2.11,
> json-stringify-safe@5.0.1, node-uuid@1.4.8, tough-cookie@4.0.0,
> http-signature@0.10.1, form-data@0.1.4, hawk@1.0.0)
> [INFO] ├── bower-config@0.5.3 (osenv@0.0.3, graceful-fs@2.0.3,
> optimist@0.6.1)
> [INFO] ├── cardinal@0.4.4 (ansicolors@0.2.1, redeyed@0.4.4)
> [INFO] ├── decompress-zip@0.0.8 (nopt@2.2.1, mkpath@0.1.0, touch@0.0.2,
> readable-stream@1.1.14, binary@0.3.0)
> [INFO] ├── bower-registry-client@0.2.4 (async@0.2.10, graceful-fs@2.0.3,
> request-replay@0.2.0, lru-cache@2.3.1, mkdirp@0.3.5, request@2.51.0)
> [INFO] ├── update-notifier@0.2.2 (is-npm@1.0.0, semver-diff@2.1.0,
> chalk@0.5.1, string-length@1.0.1, latest-version@1.0.1, configstore@0.3.2)
> [INFO] ├── handlebars@1.3.0 (optimist@0.3.7, uglify-js@2.3.6)
> [INFO] ├── insight@0.3.1 (object-assign@0.1.2, async@0.2.10,
> lodash.debounce@2.4.1, request@2.27.0, configstore@0.2.3, inquirer@0.4.1)
> [INFO] ├── mout@0.9.1
> [INFO] └── inquirer@0.5.1 (mute-stream@0.0.4, async@0.8.0, through@2.3.8,
> lodash@2.4.2, readline2@0.1.1, cli-color@0.3.3)
> [INFO]
> [INFO] phantomjs@2.1.7 node_modules/phantomjs
> [INFO] ├── progress@1.1.8
> [INFO] ├── kew@0.7.0
> [INFO] ├── which@1.2.14 (isexe@2.0.0)
> [INFO] ├── request-progress@2.0.1 (throttleit@1.0.0)
> [INFO] ├── hasha@2.2.0 (is-stream@1.1.0, pinkie-promise@2.0.1)
> [INFO] ├── extract-zip@1.5.0 (debug@0.7.4, yauzl@2.4.1, concat-stream@1.5.0,
> mkdirp@0.5.0)
> [INFO] ├── fs-extra@0.26.7 (path-is-absolute@1.0.1, klaw@1.3.1,
> graceful-fs@4.2.3, jsonfile@2.4.0, rimraf@2.7.1)
> [INFO] └── request@2.67.0 (aws-sign2@0.6.0, tunnel-agent@0.4.3,
> oauth-sign@0.8.2, forever-agent@0.6.1, caseless@0.11.0, is-typedarray@1.0.0,
> stringstream@0.0.6, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.2,
> tough-cookie@2.2.2, qs@5.2.1, node-uuid@1.4.8, combined-stream@1.0.8,
> mime-types@2.1.26, bl@1.0.3, hawk@3.1.3, har-validator@2.0.6,
> http-signature@1.1.1, form-data@1.0.1)
> [INFO]
> [INFO] karma-phantomjs-launcher@0.1.4 node_modules/karma-phantomjs-launcher
> [INFO] └── phantomjs@1.9.20 (progress@1.1.8, kew@0.7.0, which@1.2.14,
> request-progress@2.0.1, hasha@2.2.0, extract-zip@1.5.0, fs-extra@0.26.7,
> request@2.67.0)
> [INFO]
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> Stack trace:
> SyntaxError: Unexpected token {
> at exports.runInThisContext (vm.js:53:16)
> at Module._compile (module.js:373:25)
> at
[jira] [Commented] (AMBARI-25499) Unable to build ambari 2.7.5
[
https://issues.apache.org/jira/browse/AMBARI-25499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084581#comment-17084581
]
Masahiro Tanaka commented on AMBARI-25499:
--
Hi [~hapylestat] , do you have a plan to write a patch to fix this? Thanks!
> Unable to build ambari 2.7.5
>
>
> Key: AMBARI-25499
> URL: https://issues.apache.org/jira/browse/AMBARI-25499
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.7.1, 2.7.3, 2.7.4, 2.7.5
>Reporter: Luigi Caramico
>Assignee: Dmytro Grinenko
>Priority: Major
>
> following the instruction on
> [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.5]
>
> I started to build Ambari but I get the error:
>
> {code}
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> {code}
>
> {code}
> [INFO] bower@1.3.8 node_modules/bower
> [INFO] ├── is-root@0.1.0
> [INFO] ├── stringify-object@0.2.1
> [INFO] ├── junk@0.3.0
> [INFO] ├── abbrev@1.0.9
> [INFO] ├── which@1.0.9
> [INFO] ├── opn@0.1.2
> [INFO] ├── bower-endpoint-parser@0.2.2
> [INFO] ├── chmodr@0.1.2
> [INFO] ├── bower-logger@0.2.2
> [INFO] ├── archy@0.0.2
> [INFO] ├── q@1.0.1
> [INFO] ├── lockfile@0.4.3
> [INFO] ├── nopt@3.0.6
> [INFO] ├── rimraf@2.2.8
> [INFO] ├── lru-cache@2.5.2
> [INFO] ├── retry@0.6.1
> [INFO] ├── tmp@0.0.23
> [INFO] ├── osenv@0.1.5 (os-tmpdir@1.0.2, os-homedir@1.0.2)
> [INFO] ├── chalk@0.4.0 (ansi-styles@1.0.0, has-color@0.1.7, strip-ansi@0.1.1)
> [INFO] ├── semver@2.3.2
> [INFO] ├── request-progress@0.3.1 (throttleit@0.0.2)
> [INFO] ├── p-throttler@0.0.1 (q@0.9.7)
> [INFO] ├── graceful-fs@3.0.12 (natives@1.1.6)
> [INFO] ├── shell-quote@1.4.3 (array-filter@0.0.1, jsonify@0.0.0,
> array-reduce@0.0.0, array-map@0.0.0)
> [INFO] ├── bower-json@0.4.0 (intersect@0.0.3, deep-extend@0.2.11,
> graceful-fs@2.0.3)
> [INFO] ├── mkdirp@0.5.5 (minimist@1.2.5)
> [INFO] ├── promptly@0.2.1 (read@1.0.7)
> [INFO] ├── fstream@0.1.31 (inherits@2.0.4)
> [INFO] ├── tar@0.1.20 (inherits@2.0.4, block-stream@0.0.9)
> [INFO] ├── fstream-ignore@0.0.10 (inherits@2.0.4, minimatch@0.3.0)
> [INFO] ├── glob@4.0.6 (inherits@2.0.4, once@1.4.0, minimatch@1.0.0)
> [INFO] ├── request@2.36.0 (tunnel-agent@0.4.3, aws-sign2@0.5.0,
> forever-agent@0.5.2, qs@0.6.6, oauth-sign@0.3.0, mime@1.2.11,
> json-stringify-safe@5.0.1, node-uuid@1.4.8, tough-cookie@4.0.0,
> http-signature@0.10.1, form-data@0.1.4, hawk@1.0.0)
> [INFO] ├── bower-config@0.5.3 (osenv@0.0.3, graceful-fs@2.0.3,
> optimist@0.6.1)
> [INFO] ├── cardinal@0.4.4 (ansicolors@0.2.1, redeyed@0.4.4)
> [INFO] ├── decompress-zip@0.0.8 (nopt@2.2.1, mkpath@0.1.0, touch@0.0.2,
> readable-stream@1.1.14, binary@0.3.0)
> [INFO] ├── bower-registry-client@0.2.4 (async@0.2.10, graceful-fs@2.0.3,
> request-replay@0.2.0, lru-cache@2.3.1, mkdirp@0.3.5, request@2.51.0)
> [INFO] ├── update-notifier@0.2.2 (is-npm@1.0.0, semver-diff@2.1.0,
> chalk@0.5.1, string-length@1.0.1, latest-version@1.0.1, configstore@0.3.2)
> [INFO] ├── handlebars@1.3.0 (optimist@0.3.7, uglify-js@2.3.6)
> [INFO] ├── insight@0.3.1 (object-assign@0.1.2, async@0.2.10,
> lodash.debounce@2.4.1, request@2.27.0, configstore@0.2.3, inquirer@0.4.1)
> [INFO] ├── mout@0.9.1
> [INFO] └── inquirer@0.5.1 (mute-stream@0.0.4, async@0.8.0, through@2.3.8,
> lodash@2.4.2, readline2@0.1.1, cli-color@0.3.3)
> [INFO]
> [INFO] phantomjs@2.1.7 node_modules/phantomjs
> [INFO] ├── progress@1.1.8
> [INFO] ├── kew@0.7.0
> [INFO] ├── which@1.2.14 (isexe@2.0.0)
> [INFO] ├── request-progress@2.0.1 (throttleit@1.0.0)
> [INFO] ├── hasha@2.2.0 (is-stream@1.1.0, pinkie-promise@2.0.1)
> [INFO] ├── extract-zip@1.5.0 (debug@0.7.4, yauzl@2.4.1, concat-stream@1.5.0,
> mkdirp@0.5.0)
> [INFO] ├── fs-extra@0.26.7 (path-is-absolute@1.0.1, klaw@1.3.1,
> graceful-fs@4.2.3, jsonfile@2.4.0, rimraf@2.7.1)
> [INFO] └── request@2.67.0 (aws-sign2@0.6.0, tunnel-agent@0.4.3,
> oauth-sign@0.8.2, forever-agent@0.6.1, caseless@0.11.0, is-typedarray@1.0.0,
> stringstream@0.0.6, isstream@0.1.2, json-stringify-safe@5.0.1, extend@3.0.2,
> tough-cookie@2.2.2, qs@5.2.1, node-uuid@1.4.8, combined-stream@1.0.8,
> mime-types@2.1.26, bl@1.0.3, hawk@3.1.3, har-validator@2.0.6,
> http-signature@1.1.1, form-data@1.0.1)
> [INFO]
> [INFO] karma-phantomjs-launcher@0.1.4 node_modules/karma-phantomjs-launcher
> [INFO] └── phantomjs@1.9.20 (progress@1.1.8, kew@0.7.0, which@1.2.14,
> request-progress@2.0.1, hasha@2.2.0, extract-zip@1.5.0, fs-extra@0.26.7,
> request@2.67.0)
> [INFO]
> [INFO] — exec-maven-plugin:1.2.1:exec (Bower install) @ ambari-admin —
> bower error Unexpected token {
> Stack trace:
> SyntaxError: Unexpected token {
> at exports.runInThisContext (vm.js:53:16)
> at
[jira] [Created] (AMBARI-25119) Ambari Files Views incorrectly shows the permission of directories with sticky bit
Masahiro Tanaka created AMBARI-25119: Summary: Ambari Files Views incorrectly shows the permission of directories with sticky bit Key: AMBARI-25119 URL: https://issues.apache.org/jira/browse/AMBARI-25119 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.7.3 Reporter: Masahiro Tanaka When listing directories on the HDFS with Ambari Files View, though the permission of the directory is set as "drwxrwxrwt", it is shown as "drwxrwxrwx". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-16302) "Hadoop Root Logger" does not take effect when changing the value
[ https://issues.apache.org/jira/browse/AMBARI-16302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka reassigned AMBARI-16302: Assignee: Masahiro Tanaka > "Hadoop Root Logger" does not take effect when changing the value > - > > Key: AMBARI-16302 > URL: https://issues.apache.org/jira/browse/AMBARI-16302 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.3.0 >Reporter: Yuanbo Liu >Assignee: Masahiro Tanaka >Priority: Critical > Attachments: screenshot-1.png > > > From ambari -> HDFS -> Configs -> Advanced hadoop-env > modify > Hadoop Root Logger > from INFO,RFA to DEBUG,RFA and restart HDFS, it does not take effect. > See the pic in the attachment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22407) MaxFileSize does not work with DailyRollingFileAppender
[
https://issues.apache.org/jira/browse/AMBARI-22407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka reassigned AMBARI-22407:
Assignee: Masahiro Tanaka
> MaxFileSize does not work with DailyRollingFileAppender
> ---
>
> Key: AMBARI-22407
> URL: https://issues.apache.org/jira/browse/AMBARI-22407
> Project: Ambari
> Issue Type: Bug
> Environment: Ambari 2.6.0
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
>
> Apache Ranger uses DailyRollingFileAppender which doesn't use maxfilesize
> property.
> AMBARI-21889 fixed a part of this issue, but if we contain maxFileSize
> property, it shows a warning message like below
> {code}
> log4j:WARN No such property [maxFileSize] in
> org.apache.log4j.DailyRollingFileAppender.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22758) Configs in "Custom krb5-conf" aren't reflected in /etc/krb5.conf
Masahiro Tanaka created AMBARI-22758: Summary: Configs in "Custom krb5-conf" aren't reflected in /etc/krb5.conf Key: AMBARI-22758 URL: https://issues.apache.org/jira/browse/AMBARI-22758 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.2 Reporter: Masahiro Tanaka Priority: Minor While I entered some settings in "Custom krb5-conf", these are not reflected in /etc/krb5.conf. I can change /etc/krb5.conf by entering options into "Advanced krb-conf". -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22434) Ranger KMS HA setup wizard automatically puts incorrect settings
[ https://issues.apache.org/jira/browse/AMBARI-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-22434: - Description: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which are added are not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should be 'sasl' when using Kerberized ZooKeeper was: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which are added are not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should be 'sasl' when using Kerberized Hadoop > Ranger KMS HA setup wizard automatically puts incorrect settings > > > Key: AMBARI-22434 > URL: https://issues.apache.org/jira/browse/AMBARI-22434 > Project: Ambari > Issue Type: Bug > Environment: CentOS7.3, Ambari 2.5.2 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > Ambari adds the Ranger KMS HA releated settings automatically by > AMBARI-20569, but the settings which are added are not correct. > * > hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string > should be ZooKeeper ensemble, not ranger hostnames > * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should > be 'sasl' when using Kerberized ZooKeeper -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22434) Ranger KMS HA setup wizard automatically puts incorrect settings
[ https://issues.apache.org/jira/browse/AMBARI-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-22434: - Description: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which are added are not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should be 'sasl' when using Kerberized Hadoop was: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which are added are not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop > Ranger KMS HA setup wizard automatically puts incorrect settings > > > Key: AMBARI-22434 > URL: https://issues.apache.org/jira/browse/AMBARI-22434 > Project: Ambari > Issue Type: Bug > Environment: CentOS7.3, Ambari 2.5.2 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > Ambari adds the Ranger KMS HA releated settings automatically by > AMBARI-20569, but the settings which are added are not correct. > * > hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string > should be ZooKeeper ensemble, not ranger hostnames > * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should > be 'sasl' when using Kerberized Hadoop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22434) Ranger KMS HA setup wizard automatically puts incorrect settings
[ https://issues.apache.org/jira/browse/AMBARI-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-22434: - Description: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which are added are not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop was: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which is added is not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop > Ranger KMS HA setup wizard automatically puts incorrect settings > > > Key: AMBARI-22434 > URL: https://issues.apache.org/jira/browse/AMBARI-22434 > Project: Ambari > Issue Type: Bug > Environment: CentOS7.3, Ambari 2.5.2 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > Ambari adds the Ranger KMS HA releated settings automatically by > AMBARI-20569, but the settings which are added are not correct. > * > hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string > should be ZooKeeper ensemble, not ranger hostnames > * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should > not be 'sasl' when using Kerberized Hadoop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22434) Ranger KMS HA setup wizard automatically puts incorrect settings
[ https://issues.apache.org/jira/browse/AMBARI-22434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-22434: - Description: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which is added is not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble, not ranger hostnames * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop was: Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which is added is not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble. * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop > Ranger KMS HA setup wizard automatically puts incorrect settings > > > Key: AMBARI-22434 > URL: https://issues.apache.org/jira/browse/AMBARI-22434 > Project: Ambari > Issue Type: Bug > Environment: CentOS7.3, Ambari 2.5.2 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > Ambari adds the Ranger KMS HA releated settings automatically by > AMBARI-20569, but the settings which is added is not correct. > * > hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string > should be ZooKeeper ensemble, not ranger hostnames > * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should > not be 'sasl' when using Kerberized Hadoop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22434) Ranger KMS HA setup wizard automatically puts incorrect settings
Masahiro Tanaka created AMBARI-22434: Summary: Ranger KMS HA setup wizard automatically puts incorrect settings Key: AMBARI-22434 URL: https://issues.apache.org/jira/browse/AMBARI-22434 Project: Ambari Issue Type: Bug Environment: CentOS7.3, Ambari 2.5.2 Reporter: Masahiro Tanaka Assignee: Masahiro Tanaka Ambari adds the Ranger KMS HA releated settings automatically by AMBARI-20569, but the settings which is added is not correct. * hadoop.kms.authentication.signer.secret.provider.zookeeper.connection.string should be ZooKeeper ensemble. * hadoop.kms.authentication.signer.secret.provider.zookeeper.auth.type should not be 'sasl' when using Kerberized Hadoop -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22407) MaxFileSize does not work with DailyRollingFileAppender
Masahiro Tanaka created AMBARI-22407:
Summary: MaxFileSize does not work with DailyRollingFileAppender
Key: AMBARI-22407
URL: https://issues.apache.org/jira/browse/AMBARI-22407
Project: Ambari
Issue Type: Bug
Environment: Ambari 2.6.0
Reporter: Masahiro Tanaka
Priority: Minor
Apache Ranger uses DailyRollingFileAppender which doesn't use maxfilesize
property.
AMBARI-21889 fixed a part of this issue, but if we contain maxFileSize
property, it shows a warning message like below
{code}
log4j:WARN No such property [maxFileSize] in
org.apache.log4j.DailyRollingFileAppender.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-21267) HDFS DataNode installation failed on Ubuntu 16.04 due to a change of libsnappy package
[ https://issues.apache.org/jira/browse/AMBARI-21267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka reassigned AMBARI-21267: Assignee: (was: Masahiro Tanaka) > HDFS DataNode installation failed on Ubuntu 16.04 due to a change of > libsnappy package > -- > > Key: AMBARI-21267 > URL: https://issues.apache.org/jira/browse/AMBARI-21267 > Project: Ambari > Issue Type: Bug > Environment: Ubuntu 16.04 > ODPi (not using HDP) >Reporter: Masahiro Tanaka > > Related Issue: https://issues.apache.org/jira/browse/AMBARI-18025 > HDP package repository hosts a libsnappy1 package by themselves, so DataNode > install doesn't fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22271) Need hdfs-site for additional hiveserver2 with NameNode HA
Masahiro Tanaka created AMBARI-22271:
Summary: Need hdfs-site for additional hiveserver2 with NameNode HA
Key: AMBARI-22271
URL: https://issues.apache.org/jira/browse/AMBARI-22271
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Environment: CentOS7.3
Ambari 2.5.2
HDP 2.6.2
Reporter: Masahiro Tanaka
When I added HiveServer2 to a server which is not installed other components
with NameNode HA env, I got an error below
{code}
java.lang.Error: Max start attempts 5 exhausted
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:506)
at
org.apache.hive.service.server.HiveServer2.access$700(HiveServer2.java:87)
at
org.apache.hive.service.server.HiveServer2$StartOptionExecutor.execute(HiveServer2.java:
720)
at org.apache.hive.service.server.HiveServer2.main(HiveServer2.java:593)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.hadoop.util.RunJar.run(RunJar.java:233)
at org.apache.hadoop.util.RunJar.main(RunJar.java:148)
Caused by: java.lang.RuntimeException: Error applying authorization policy on
hive configuration: j
ava.lang.IllegalArgumentException: java.net.UnknownHostException: mycluster
at org.apache.hive.service.cli.CLIService.init(CLIService.java:117)
at
org.apache.hive.service.CompositeService.init(CompositeService.java:59)
at org.apache.hive.service.server.HiveServer2.init(HiveServer2.java:122)
at
org.apache.hive.service.server.HiveServer2.startHiveServer2(HiveServer2.java:474)
... 9 more
Caused by: java.lang.RuntimeException: java.lang.IllegalArgumentException:
java.net.UnknownHostExce
ption: mycluster
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:547)
at
org.apache.hive.service.cli.CLIService.applyAuthorizationConfigPolicy(CLIService.java:13
0)
at org.apache.hive.service.cli.CLIService.init(CLIService.java:115)
... 12 more
Caused by: java.lang.IllegalArgumentException: java.net.UnknownHostException:
mycluster
at
org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:438)
at
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:321)
at
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:690)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:631)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:160)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2795)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:99)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2829)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2811)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:390)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:179)
at
org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:530)
... 14 more
Caused by: java.net.UnknownHostException: mycluster
... 27 more
2017-10-20 01:27:04,136 INFO [pool-1-thread-1]: server.HiveServer2
(HiveStringUtils.java:run(711))
- SHUTDOWN_MSG:
{code}
I looked into the environment, and noticed there is no hdfs-site.xml and thus
it could not load
org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider.
That's might be the cause.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
[
https://issues.apache.org/jira/browse/AMBARI-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21921:
-
Attachment: AMBARI-21921.1.patch
> A print_warning_msg() in serverConfiguration.py has too few arguments.
> --
>
> Key: AMBARI-21921
> URL: https://issues.apache.org/jira/browse/AMBARI-21921
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-21921.0.patch, AMBARI-21921.1.patch
>
>
> {{update_database_name_property}} function which is in
> {{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
> {{check_database_name_property}} throws {{FatalException}}.
> {code}
> except FatalException:
> properties = get_ambari_properties()
> if properties == -1:
> err = "Error getting ambari properties"
> raise FatalException(-1, err)
> print_warning_msg("{0} property isn't set in {1} . Setting it to default
> value - {3}".format(JD
> BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
> configDefaults.DEFAULT_DB_NAME))
> properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
> configDefaults.DEFAULT_DB_NAME)
> conf_file = find_properties_file()
> {code}
> The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
> {3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
[
https://issues.apache.org/jira/browse/AMBARI-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21921:
-
Attachment: AMBARI-21921.0.patch
> A print_warning_msg() in serverConfiguration.py has too few arguments.
> --
>
> Key: AMBARI-21921
> URL: https://issues.apache.org/jira/browse/AMBARI-21921
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-21921.0.patch
>
>
> {{update_database_name_property}} function which is in
> {{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
> {{check_database_name_property}} throws {{FatalException}}.
> {code}
> except FatalException:
> properties = get_ambari_properties()
> if properties == -1:
> err = "Error getting ambari properties"
> raise FatalException(-1, err)
> print_warning_msg("{0} property isn't set in {1} . Setting it to default
> value - {3}".format(JD
> BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
> configDefaults.DEFAULT_DB_NAME))
> properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
> configDefaults.DEFAULT_DB_NAME)
> conf_file = find_properties_file()
> {code}
> The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
> {3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
[
https://issues.apache.org/jira/browse/AMBARI-21921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21921:
-
Status: Patch Available (was: Open)
> A print_warning_msg() in serverConfiguration.py has too few arguments.
> --
>
> Key: AMBARI-21921
> URL: https://issues.apache.org/jira/browse/AMBARI-21921
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
> Attachments: AMBARI-21921.0.patch
>
>
> {{update_database_name_property}} function which is in
> {{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
> {{check_database_name_property}} throws {{FatalException}}.
> {code}
> except FatalException:
> properties = get_ambari_properties()
> if properties == -1:
> err = "Error getting ambari properties"
> raise FatalException(-1, err)
> print_warning_msg("{0} property isn't set in {1} . Setting it to default
> value - {3}".format(JD
> BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
> configDefaults.DEFAULT_DB_NAME))
> properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
> configDefaults.DEFAULT_DB_NAME)
> conf_file = find_properties_file()
> {code}
> The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
> {3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21921) A print_warning_msg() in serverConfiguration.py has too few arguments.
Masahiro Tanaka created AMBARI-21921:
Summary: A print_warning_msg() in serverConfiguration.py has too
few arguments.
Key: AMBARI-21921
URL: https://issues.apache.org/jira/browse/AMBARI-21921
Project: Ambari
Issue Type: Bug
Affects Versions: trunk
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Priority: Minor
{{update_database_name_property}} function which is in
{{serverConfiguration.py}} uses {{print_warning_msg}} to show a warning when
{{check_database_name_property}} throws {{FatalException}}.
{code}
except FatalException:
properties = get_ambari_properties()
if properties == -1:
err = "Error getting ambari properties"
raise FatalException(-1, err)
print_warning_msg("{0} property isn't set in {1} . Setting it to default
value - {3}".format(JD
BC_DATABASE_NAME_PROPERTY, AMBARI_PROPERTIES_FILE,
configDefaults.DEFAULT_DB_NAME))
properties.process_pair(JDBC_DATABASE_NAME_PROPERTY,
configDefaults.DEFAULT_DB_NAME)
conf_file = find_properties_file()
{code}
The argument should be use {code}{0}, {1}, {2}{code}, not {code}{0}, {1},
{3}{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21267) HDFS DataNode installation failed on Ubuntu 16.04 due to a change of libsnappy package
Masahiro Tanaka created AMBARI-21267: Summary: HDFS DataNode installation failed on Ubuntu 16.04 due to a change of libsnappy package Key: AMBARI-21267 URL: https://issues.apache.org/jira/browse/AMBARI-21267 Project: Ambari Issue Type: Bug Environment: Ubuntu 16.04 ODPi (not using HDP) Reporter: Masahiro Tanaka Assignee: Masahiro Tanaka Related Issue: https://issues.apache.org/jira/browse/AMBARI-18025 HDP package repository hosts a libsnappy1 package by themselves, so DataNode install doesn't fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16017361#comment-16017361 ] Masahiro Tanaka commented on AMBARI-21045: -- Hi [~sriharsha], I think this commit may break a test. You need to escape '&' in XML. > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-21045.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21038) Rebalance HDFS button on Hosts page doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-21038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21038:
-
Description:
When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
pulldown menu on each Hosts page.
I expected it worked same as I pushed "Rebalance HDFS" on Service Page, though
it doesn't work.
The error log on Ambari Web is as below:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 420, in
NameNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 282, in rebalancehdfs
name_node_parameters = json.loads( params.name_node_params )
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
{code}
was:
When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
pulldown menu on each Hosts page.
I expected it worked same as I pushed "Rebalance HDFS" on Service Page, though
it doesn't work.
The error log is as below:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 420, in
NameNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 282, in rebalancehdfs
name_node_parameters = json.loads( params.name_node_params )
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
{code}
> Rebalance HDFS button on Hosts page doesn't work
>
>
> Key: AMBARI-21038
> URL: https://issues.apache.org/jira/browse/AMBARI-21038
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4 on CentOS6.8
> Ambari 2.5 on CentOS7.2
>Reporter: Masahiro Tanaka
>
> When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
> pulldown menu on each Hosts page.
> I expected it worked same as I pushed "Rebalance HDFS" on Service Page,
> though it doesn't work.
> The error log on Ambari Web is as below:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 420, in
> NameNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 282, in rebalancehdfs
> name_node_parameters = json.loads( params.name_node_params )
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> TypeError: expected string or buffer
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21038) Rebalance HDFS button on Hosts page doesn't work
Masahiro Tanaka created AMBARI-21038:
Summary: Rebalance HDFS button on Hosts page doesn't work
Key: AMBARI-21038
URL: https://issues.apache.org/jira/browse/AMBARI-21038
Project: Ambari
Issue Type: Bug
Components: ambari-server, ambari-web
Affects Versions: 2.5.0, 2.4.2
Environment: Ambari 2.4 on CentOS6.8
Ambari 2.5 on CentOS7.2
Reporter: Masahiro Tanaka
When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
pulldown menu on each Hosts page.
I expected it worked same as I pushed "Rebalance HDFS" on Service Page, though
it doesn't work.
The error log is as below:
{{{
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 420, in
NameNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 282, in rebalancehdfs
name_node_parameters = json.loads( params.name_node_params )
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
}}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21038) Rebalance HDFS button on Hosts page doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-21038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-21038:
-
Description:
When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
pulldown menu on each Hosts page.
I expected it worked same as I pushed "Rebalance HDFS" on Service Page, though
it doesn't work.
The error log is as below:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 420, in
NameNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 282, in rebalancehdfs
name_node_parameters = json.loads( params.name_node_params )
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
{code}
was:
When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
pulldown menu on each Hosts page.
I expected it worked same as I pushed "Rebalance HDFS" on Service Page, though
it doesn't work.
The error log is as below:
{{{
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 420, in
NameNode().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
line 282, in rebalancehdfs
name_node_parameters = json.loads( params.name_node_params )
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
}}}
> Rebalance HDFS button on Hosts page doesn't work
>
>
> Key: AMBARI-21038
> URL: https://issues.apache.org/jira/browse/AMBARI-21038
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4 on CentOS6.8
> Ambari 2.5 on CentOS7.2
>Reporter: Masahiro Tanaka
>
> When I tried to rebalance HDFS with Ambari, I pushed "Rebalance HDFS" in the
> pulldown menu on each Hosts page.
> I expected it worked same as I pushed "Rebalance HDFS" on Service Page,
> though it doesn't work.
> The error log is as below:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 420, in
> NameNode().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py",
> line 282, in rebalancehdfs
> name_node_parameters = json.loads( params.name_node_params )
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line
> 307, in loads
> return _default_decoder.decode(s)
> File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line
> 335, in decode
> obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> TypeError: expected string or buffer
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk
[
https://issues.apache.org/jira/browse/AMBARI-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007641#comment-16007641
]
Masahiro Tanaka commented on AMBARI-20983:
--
Should we use JDK7? I thinks its support is already finished.
> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
> Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy) SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor SKIPPED
> [INFO] Ambari Metrics Grafana SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO]
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install
> node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn
> (install node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:170)
> at
>
[jira] [Comment Edited] (AMBARI-20983) ambari/dev-support/docker build is broken on trunk
[
https://issues.apache.org/jira/browse/AMBARI-20983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16007641#comment-16007641
]
Masahiro Tanaka edited comment on AMBARI-20983 at 5/12/17 5:02 AM:
---
Should we use JDK7? I think its support is already finished.
was (Author: masatana):
Should we use JDK7? I thinks its support is already finished.
> ambari/dev-support/docker build is broken on trunk
> --
>
> Key: AMBARI-20983
> URL: https://issues.apache.org/jira/browse/AMBARI-20983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Michael Harp
>Assignee: Michael Harp
>Priority: Minor
> Labels: docker
> Attachments: AMBARI_20983.patch
>
>
> Several issues need to be fixed to get the container working;
> 1. Version of maven needs to be updated
> 2. JDK should be version 7
> 3. Set bower flag to run as root in container
> {code}
> docker build -t ambari/build ./dev-support/docker/docker
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main ... SUCCESS [4:58.949s]
> [INFO] Apache Ambari Project POM . SUCCESS [6.050s]
> [INFO] Ambari Web FAILURE [15.348s]
> [INFO] Ambari Views .. SKIPPED
> [INFO] Ambari Admin View . SKIPPED
> [INFO] utility ... SKIPPED
> [INFO] ambari-metrics SKIPPED
> [INFO] Ambari Metrics Common . SKIPPED
> [INFO] Ambari Metrics Hadoop Sink SKIPPED
> [INFO] Ambari Metrics Flume Sink . SKIPPED
> [INFO] Ambari Metrics Kafka Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink . SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy) SKIPPED
> [INFO] Ambari Metrics Collector .. SKIPPED
> [INFO] Ambari Metrics Monitor SKIPPED
> [INFO] Ambari Metrics Grafana SKIPPED
> [INFO] Ambari Metrics Assembly ... SKIPPED
> [INFO] Ambari Server . SKIPPED
> [INFO] Ambari Functional Tests ... SKIPPED
> [INFO] Ambari Agent .. SKIPPED
> [INFO] Ambari Client . SKIPPED
> [INFO] Ambari Python Client .. SKIPPED
> [INFO] Ambari Groovy Client .. SKIPPED
> [INFO] Ambari Shell .. SKIPPED
> [INFO] Ambari Python Shell ... SKIPPED
> [INFO] Ambari Groovy Shell ... SKIPPED
> [INFO] ambari-logsearch .. SKIPPED
> [INFO] Ambari Logsearch Appender . SKIPPED
> [INFO] Ambari Logsearch Config Api ... SKIPPED
> [INFO] Ambari Logsearch Config Zookeeper . SKIPPED
> [INFO] Ambari Logsearch Web .. SKIPPED
> [INFO] Ambari Logsearch Server ... SKIPPED
> [INFO] Ambari Logsearch Log Feeder ... SKIPPED
> [INFO] Ambari Logsearch Assembly . SKIPPED
> [INFO] Ambari Logsearch Integration Test . SKIPPED
> [INFO] ambari-infra .. SKIPPED
> [INFO] Ambari Infra Solr Client .. SKIPPED
> [INFO] Ambari Infra Solr Plugin .. SKIPPED
> [INFO] Ambari Infra Solr Assembly SKIPPED
> [INFO] Ambari Infra Manager .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:01.681s
> [INFO] Finished at: Wed May 10 19:58:42 UTC 2017
> [INFO] Final Memory: 21M/225M
> [INFO]
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install
> node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0 ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn
> (install node and yarn) on project ambari-web: The plugin
> com.github.eirslett:frontend-maven-plugin:1.4 requires Maven version 3.1.0
> at
>
[jira] [Updated] (AMBARI-20797) Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/AMBARI-20797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-20797: - Status: Patch Available (was: Open) > Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT > --- > > Key: AMBARI-20797 > URL: https://issues.apache.org/jira/browse/AMBARI-20797 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Critical > Attachments: AMBARI-20797.0.patch > > > I had in trouble compiling same as in > https://community.hortonworks.com/questions/93448/compile-ambari-metrics-storm-sink-error.html > The solution is also mentioned in the URL above. We should use storm-1.1.0 , > not storm-1.1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20797) Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT
[ https://issues.apache.org/jira/browse/AMBARI-20797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-20797: - Attachment: AMBARI-20797.0.patch > Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT > --- > > Key: AMBARI-20797 > URL: https://issues.apache.org/jira/browse/AMBARI-20797 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Critical > Attachments: AMBARI-20797.0.patch > > > I had in trouble compiling same as in > https://community.hortonworks.com/questions/93448/compile-ambari-metrics-storm-sink-error.html > The solution is also mentioned in the URL above. We should use storm-1.1.0 , > not storm-1.1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20797) Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT
Masahiro Tanaka created AMBARI-20797: Summary: Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT Key: AMBARI-20797 URL: https://issues.apache.org/jira/browse/AMBARI-20797 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: Masahiro Tanaka Assignee: Masahiro Tanaka Priority: Critical I had in trouble compiling same as in https://community.hortonworks.com/questions/93448/compile-ambari-metrics-storm-sink-error.html The solution is also mentioned in the URL above. We should use storm-1.1.0 , not storm-1.1.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Attachment: AMBARI-20443.3.patch
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: AMBARI-20443.0.patch, AMBARI-20443.1.patch,
> AMBARI-20443.2.patch, AMBARI-20443.3.patch, screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Attachment: AMBARI-20443.1.patch
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: AMBARI-20443.0.patch, AMBARI-20443.1.patch,
> screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Affects Version/s: 2.5.0
Status: Patch Available (was: Open)
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: AMBARI-20443.0.patch, screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Attachment: AMBARI-20443.0.patch
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0, 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: AMBARI-20443.0.patch, screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Description:
In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
Though I change the parameter, it looks like nothing has changed. And I greped
the entire ambari source code, the parameter is not referenced.
was:
In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
Though I change the parameter, I looks like nothing has changed. And I greped
the entire ambari source code, the parameter is not referenced.
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. And I
> greped the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Description:
In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
Though I change the parameter, it looks like nothing has changed. I greped the
entire ambari source code, the parameter is not referenced.
was:
In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
Though I change the parameter, it looks like nothing has changed. And I greped
the entire ambari source code, the parameter is not referenced.
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, it looks like nothing has changed. I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20443) No need to show `hive_ambari_database`
Masahiro Tanaka created AMBARI-20443:
Summary: No need to show `hive_ambari_database`
Key: AMBARI-20443
URL: https://issues.apache.org/jira/browse/AMBARI-20443
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Environment: Ambari 2.4.2 with Hive
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Fix For: trunk
Attachments: screenshot-1.png
In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
Though I change the parameter, I looks like nothing has changed. And I greped
the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20443) No need to show `hive_ambari_database`
[
https://issues.apache.org/jira/browse/AMBARI-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-20443:
-
Attachment: screenshot-1.png
> No need to show `hive_ambari_database`
> --
>
> Key: AMBARI-20443
> URL: https://issues.apache.org/jira/browse/AMBARI-20443
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
> Environment: Ambari 2.4.2 with Hive
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> In Advanced hive-env, there is a parameter named {{hive_ambari_database}}.
> Though I change the parameter, I looks like nothing has changed. And I greped
> the entire ambari source code, the parameter is not referenced.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-19976) Cannot build ambari-server due to rat check
[
https://issues.apache.org/jira/browse/AMBARI-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863782#comment-15863782
]
Masahiro Tanaka edited comment on AMBARI-19976 at 2/17/17 3:11 PM:
---
I don't think reviewboard is needed for this patch.
[~aonishuk], [~smnaha], [~swagle], [~u39kun] could you review this patch?
was (Author: masatana):
I don't think reviewboard is needed for this patch.
[~aonishuk], [~smnaha], [~swagle] could you review this patch?
> Cannot build ambari-server due to rat check
> ---
>
> Key: AMBARI-19976
> URL: https://issues.apache.org/jira/browse/AMBARI-19976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS6
> branch-2.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19976.0.patch, AMBARI-19976.1.patch
>
>
> When I run {code}mvn -B clean install rpm:rpm -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl{code} from ambari source root, I
> got an error message like below
> {code}
> [INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
> approved: 5342 licence.
> [7/959]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.958
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.282
> s]
> [INFO] Ambari Web . SUCCESS [01:13
> min]
> [INFO] Ambari Views ... SUCCESS [ 1.620
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 9.132
> s]
> [INFO] utility SUCCESS [ 0.287
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.838
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 4.482
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [01:46
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.546
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 20.060
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:28
> min]
> [INFO] Ambari Server .. FAILURE [ 27.860
> s]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell SKIPPED
> [INFO] Ambari Groovy Shell SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Portal SKIPPED
> [INFO] Ambari Logsearch Log Feeder SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch Integration Test .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-02-11T12:26:55+00:00
> [INFO] Final Memory: 186M/991M
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari-server: Too many files with unapproved license: 1
> See RAT report in: /tmp/ambari/ambari-server/tar
> get/rat.txt -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven
[jira] [Commented] (AMBARI-19976) Cannot build ambari-server due to rat check
[
https://issues.apache.org/jira/browse/AMBARI-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15863782#comment-15863782
]
Masahiro Tanaka commented on AMBARI-19976:
--
I don't think reviewboard is needed for this patch.
[~aonishuk], [~smnaha], [~swagle] could you review this patch?
> Cannot build ambari-server due to rat check
> ---
>
> Key: AMBARI-19976
> URL: https://issues.apache.org/jira/browse/AMBARI-19976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS6
> branch-2.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19976.0.patch, AMBARI-19976.1.patch
>
>
> When I run {code}mvn -B clean install rpm:rpm -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl{code} from ambari source root, I
> got an error message like below
> {code}
> [INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
> approved: 5342 licence.
> [7/959]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.958
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.282
> s]
> [INFO] Ambari Web . SUCCESS [01:13
> min]
> [INFO] Ambari Views ... SUCCESS [ 1.620
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 9.132
> s]
> [INFO] utility SUCCESS [ 0.287
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.838
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 4.482
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [01:46
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.546
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 20.060
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:28
> min]
> [INFO] Ambari Server .. FAILURE [ 27.860
> s]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell SKIPPED
> [INFO] Ambari Groovy Shell SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Portal SKIPPED
> [INFO] Ambari Logsearch Log Feeder SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch Integration Test .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-02-11T12:26:55+00:00
> [INFO] Final Memory: 186M/991M
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari-server: Too many files with unapproved license: 1
> See RAT report in: /tmp/ambari/ambari-server/tar
> get/rat.txt -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> In {code}/tmp/ambari/ambari-server/target/rat.txt{code},
> {code}
> *
> Summary
> ---
[jira] [Updated] (AMBARI-19976) Cannot build ambari-server due to rat check
[
https://issues.apache.org/jira/browse/AMBARI-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19976:
-
Attachment: AMBARI-19976.1.patch
> Cannot build ambari-server due to rat check
> ---
>
> Key: AMBARI-19976
> URL: https://issues.apache.org/jira/browse/AMBARI-19976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS6
> branch-2.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19976.0.patch, AMBARI-19976.1.patch
>
>
> When I run {code}mvn -B clean install rpm:rpm -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl{code} from ambari source root, I
> got an error message like below
> {code}
> [INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
> approved: 5342 licence.
> [7/959]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.958
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.282
> s]
> [INFO] Ambari Web . SUCCESS [01:13
> min]
> [INFO] Ambari Views ... SUCCESS [ 1.620
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 9.132
> s]
> [INFO] utility SUCCESS [ 0.287
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.838
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 4.482
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [01:46
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.546
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 20.060
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:28
> min]
> [INFO] Ambari Server .. FAILURE [ 27.860
> s]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell SKIPPED
> [INFO] Ambari Groovy Shell SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Portal SKIPPED
> [INFO] Ambari Logsearch Log Feeder SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch Integration Test .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-02-11T12:26:55+00:00
> [INFO] Final Memory: 186M/991M
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari-server: Too many files with unapproved license: 1
> See RAT report in: /tmp/ambari/ambari-server/tar
> get/rat.txt -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> In {code}/tmp/ambari/ambari-server/target/rat.txt{code},
> {code}
> *
> Summary
> ---
> Generated at: 2017-02-11T12:26:52+00:00
> Notes: 5
> Binaries: 2
> Archives: 3
> Standards: 5343
> Apache Licensed:
[jira] [Updated] (AMBARI-19976) Cannot build ambari-server due to rat check
[
https://issues.apache.org/jira/browse/AMBARI-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19976:
-
Attachment: AMBARI-19976.0.patch
Attached a patch
> Cannot build ambari-server due to rat check
> ---
>
> Key: AMBARI-19976
> URL: https://issues.apache.org/jira/browse/AMBARI-19976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS6
> branch-2.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19976.0.patch
>
>
> When I run {code}mvn -B clean install rpm:rpm -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl{code} from ambari source root, I
> got an error message like below
> {code}
> [INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
> approved: 5342 licence.
> [7/959]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.958
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.282
> s]
> [INFO] Ambari Web . SUCCESS [01:13
> min]
> [INFO] Ambari Views ... SUCCESS [ 1.620
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 9.132
> s]
> [INFO] utility SUCCESS [ 0.287
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.838
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 4.482
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [01:46
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.546
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 20.060
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:28
> min]
> [INFO] Ambari Server .. FAILURE [ 27.860
> s]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell SKIPPED
> [INFO] Ambari Groovy Shell SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Portal SKIPPED
> [INFO] Ambari Logsearch Log Feeder SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch Integration Test .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-02-11T12:26:55+00:00
> [INFO] Final Memory: 186M/991M
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari-server: Too many files with unapproved license: 1
> See RAT report in: /tmp/ambari/ambari-server/tar
> get/rat.txt -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> In {code}/tmp/ambari/ambari-server/target/rat.txt{code},
> {code}
> *
> Summary
> ---
> Generated at: 2017-02-11T12:26:52+00:00
> Notes: 5
> Binaries: 2
> Archives: 3
> Standards: 5343
> Apache Licensed: 5342
[jira] [Updated] (AMBARI-19976) Cannot build ambari-server due to rat check
[
https://issues.apache.org/jira/browse/AMBARI-19976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19976:
-
Status: Patch Available (was: Open)
> Cannot build ambari-server due to rat check
> ---
>
> Key: AMBARI-19976
> URL: https://issues.apache.org/jira/browse/AMBARI-19976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
> Environment: CentOS6
> branch-2.5
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19976.0.patch
>
>
> When I run {code}mvn -B clean install rpm:rpm -DskipTests
> -Dpython.ver="python >= 2.6" -Preplaceurl{code} from ambari source root, I
> got an error message like below
> {code}
> [INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
> approved: 5342 licence.
> [7/959]
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main SUCCESS [ 7.958
> s]
> [INFO] Apache Ambari Project POM .. SUCCESS [ 0.282
> s]
> [INFO] Ambari Web . SUCCESS [01:13
> min]
> [INFO] Ambari Views ... SUCCESS [ 1.620
> s]
> [INFO] Ambari Admin View .. SUCCESS [ 9.132
> s]
> [INFO] utility SUCCESS [ 0.287
> s]
> [INFO] ambari-metrics . SUCCESS [ 0.838
> s]
> [INFO] Ambari Metrics Common .. SUCCESS [ 4.482
> s]
> [INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295
> s]
> [INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616
> s]
> [INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525
> s]
> [INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577
> s]
> [INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039
> s]
> [INFO] Ambari Metrics Collector ... SUCCESS [01:46
> min]
> [INFO] Ambari Metrics Monitor . SUCCESS [ 1.546
> s]
> [INFO] Ambari Metrics Grafana . SUCCESS [ 20.060
> s]
> [INFO] Ambari Metrics Assembly SUCCESS [01:28
> min]
> [INFO] Ambari Server .. FAILURE [ 27.860
> s]
> [INFO] Ambari Functional Tests SKIPPED
> [INFO] Ambari Agent ... SKIPPED
> [INFO] Ambari Client .. SKIPPED
> [INFO] Ambari Python Client ... SKIPPED
> [INFO] Ambari Groovy Client ... SKIPPED
> [INFO] Ambari Shell ... SKIPPED
> [INFO] Ambari Python Shell SKIPPED
> [INFO] Ambari Groovy Shell SKIPPED
> [INFO] ambari-logsearch ... SKIPPED
> [INFO] Ambari Logsearch Appender .. SKIPPED
> [INFO] Ambari Logsearch Portal SKIPPED
> [INFO] Ambari Logsearch Log Feeder SKIPPED
> [INFO] Ambari Logsearch Solr Client ... SKIPPED
> [INFO] Ambari Infra Solr Plugin ... SKIPPED
> [INFO] Ambari Logsearch Assembly .. SKIPPED
> [INFO] Ambari Logsearch Integration Test .. SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 05:53 min
> [INFO] Finished at: 2017-02-11T12:26:55+00:00
> [INFO] Final Memory: 186M/991M
> [INFO]
>
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
> (default) on project ambari-server: Too many files with unapproved license: 1
> See RAT report in: /tmp/ambari/ambari-server/tar
> get/rat.txt -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
> In {code}/tmp/ambari/ambari-server/target/rat.txt{code},
> {code}
> *
> Summary
> ---
> Generated at: 2017-02-11T12:26:52+00:00
> Notes: 5
> Binaries: 2
> Archives: 3
> Standards: 5343
> Apache Licensed: 5342
> Generated
[jira] [Created] (AMBARI-19976) Cannot build ambari-server due to rat check
Masahiro Tanaka created AMBARI-19976:
Summary: Cannot build ambari-server due to rat check
Key: AMBARI-19976
URL: https://issues.apache.org/jira/browse/AMBARI-19976
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Environment: CentOS6
branch-2.5
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
When I run {code}mvn -B clean install rpm:rpm -DskipTests -Dpython.ver="python
>= 2.6" -Preplaceurl{code} from ambari source root, I got an error message like
below
{code}
[INFO] Rat check: Summary of files. Unapproved: 1 unknown: 1 generated: 0
approved: 5342 licence.
[7/959]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Main SUCCESS [ 7.958 s]
[INFO] Apache Ambari Project POM .. SUCCESS [ 0.282 s]
[INFO] Ambari Web . SUCCESS [01:13 min]
[INFO] Ambari Views ... SUCCESS [ 1.620 s]
[INFO] Ambari Admin View .. SUCCESS [ 9.132 s]
[INFO] utility SUCCESS [ 0.287 s]
[INFO] ambari-metrics . SUCCESS [ 0.838 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 4.482 s]
[INFO] Ambari Metrics Hadoop Sink . SUCCESS [ 2.295 s]
[INFO] Ambari Metrics Flume Sink .. SUCCESS [ 1.616 s]
[INFO] Ambari Metrics Kafka Sink .. SUCCESS [ 1.525 s]
[INFO] Ambari Metrics Storm Sink .. SUCCESS [ 2.577 s]
[INFO] Ambari Metrics Storm Sink (Legacy) . SUCCESS [ 2.039 s]
[INFO] Ambari Metrics Collector ... SUCCESS [01:46 min]
[INFO] Ambari Metrics Monitor . SUCCESS [ 1.546 s]
[INFO] Ambari Metrics Grafana . SUCCESS [ 20.060 s]
[INFO] Ambari Metrics Assembly SUCCESS [01:28 min]
[INFO] Ambari Server .. FAILURE [ 27.860 s]
[INFO] Ambari Functional Tests SKIPPED
[INFO] Ambari Agent ... SKIPPED
[INFO] Ambari Client .. SKIPPED
[INFO] Ambari Python Client ... SKIPPED
[INFO] Ambari Groovy Client ... SKIPPED
[INFO] Ambari Shell ... SKIPPED
[INFO] Ambari Python Shell SKIPPED
[INFO] Ambari Groovy Shell SKIPPED
[INFO] ambari-logsearch ... SKIPPED
[INFO] Ambari Logsearch Appender .. SKIPPED
[INFO] Ambari Logsearch Portal SKIPPED
[INFO] Ambari Logsearch Log Feeder SKIPPED
[INFO] Ambari Logsearch Solr Client ... SKIPPED
[INFO] Ambari Infra Solr Plugin ... SKIPPED
[INFO] Ambari Logsearch Assembly .. SKIPPED
[INFO] Ambari Logsearch Integration Test .. SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 05:53 min
[INFO] Finished at: 2017-02-11T12:26:55+00:00
[INFO] Final Memory: 186M/991M
[INFO]
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check
(default) on project ambari-server: Too many files with unapproved license: 1
See RAT report in: /tmp/ambari/ambari-server/tar
get/rat.txt -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{code}
In {code}/tmp/ambari/ambari-server/target/rat.txt{code},
{code}
*
Summary
---
Generated at: 2017-02-11T12:26:52+00:00
Notes: 5
Binaries: 2
Archives: 3
Standards: 5343
Apache Licensed: 5342
Generated Documents: 0
JavaDocs are generated and so license header is optional
Generated files do not required license headers
1 Unknown Licenses
***
Unapproved licenses:
/tmp/ambari/ambari-server/derby.log
{code}
I think we don't have to check the licence of the derby.log
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] (AMBARI-18002) Parse Error in ambari-server.log with LogSearch
Title: Message Title Masahiro Tanaka commented on AMBARI-18002 Re: Parse Error in ambari-server.log with LogSearch Hi Olivér Szabó Thank you for letting me know! I'll try that new config. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Commented] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833518#comment-15833518
]
Masahiro Tanaka commented on AMBARI-19415:
--
Thanks [~u39kun]!
Thanks [~afernandez] for reviewing!
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: 2.5.0
>
> Attachments: AMBARI-19415.0.patch, AMBARI-19415.1.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832912#comment-15832912
]
Masahiro Tanaka commented on AMBARI-19415:
--
Hi [~afernandez], [~aonishuk], [~oleewere], [~stoader],[~u39kun], could you
review the patch on reviewboard?
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch, AMBARI-19415.1.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Attachment: AMBARI-19415.1.patch
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch, AMBARI-19415.1.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Status: Patch Available (was: Open)
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Attachment: AMBARI-19415.0.patch
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-19415.0.patch
>
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Affects Version/s: trunk
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: trunk, 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
[
https://issues.apache.org/jira/browse/AMBARI-19415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19415:
-
Description:
Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux, but
some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{ifconfig}} command, but {{ip}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{code}
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
{code}
It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
better coverage.
was:
Ambari Agent Hardware check assumes there is {{{ifconfig}}} command in Linux,
but some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{{ifconfig}} command, but {{{ip}}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{{{
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
}}}
It would be better to check the NIC with {{{ifconfig}}} and {{{ip}}} both for
better coverage.
> Network interface check returns no value if there is no `ifconfig` command
> --
>
> Key: AMBARI-19415
> URL: https://issues.apache.org/jira/browse/AMBARI-19415
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.5.0
> Environment: CentOS7.3 Minimal Install
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> Ambari Agent Hardware check assumes there is {{ifconfig}} command in Linux,
> but some environments (e.g. CentOS 7.3 with minimal install) doens't have
> {{ifconfig}} command, but {{ip}} command.
> A warning like below (which is in ambari-agent.log) is because of the
> assumption.
> {code}
> WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network
> interfaces list from
> {code}
> It would be better to check the NIC with {{ifconfig}} and {{ip}} both for
> better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19415) Network interface check returns no value if there is no `ifconfig` command
Masahiro Tanaka created AMBARI-19415:
Summary: Network interface check returns no value if there is no
`ifconfig` command
Key: AMBARI-19415
URL: https://issues.apache.org/jira/browse/AMBARI-19415
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.5.0
Environment: CentOS7.3 Minimal Install
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Ambari Agent Hardware check assumes there is {{{ifconfig}}} command in Linux,
but some environments (e.g. CentOS 7.3 with minimal install) doens't have
{{{ifconfig}} command, but {{{ip}}} command.
A warning like below (which is in ambari-agent.log) is because of the
assumption.
{{{
WARNING 2017-01-08 14:53:48,021 Facter.py:487 - Can't get a network interfaces
list from
}}}
It would be better to check the NIC with {{{ifconfig}}} and {{{ip}}} both for
better coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723810#comment-15723810
]
Masahiro Tanaka commented on AMBARI-19076:
--
Thanks [~adoroszlai]!
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Status: Patch Available (was: Open)
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Attachment: AMBARI-19076.patch
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
> Attachments: AMBARI-19076.patch
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Description:
This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
We can jump to there by using
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
was:This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
> We can jump to there by using
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md#postputdelete-resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
[
https://issues.apache.org/jira/browse/AMBARI-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-19076:
-
Description: This is very trivial thing. When I see API document on
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the link.
(was: This is very trivial thing. When I see API document on
[github](https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md),
I can't jump to {{{POST/PUT/DELETE resource]}}} by clicking the link.)
> Broken links in ambari-server/docs/api/v1/schemas.md
>
>
> Key: AMBARI-19076
> URL: https://issues.apache.org/jira/browse/AMBARI-19076
> Project: Ambari
> Issue Type: Documentation
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Trivial
> Fix For: trunk
>
>
> This is very trivial thing. When I see API document on
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md,
> I can't jump to {code} [POST/PUT/DELETE resource] {code} by clicking the
> link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19076) Broken links in ambari-server/docs/api/v1/schemas.md
Masahiro Tanaka created AMBARI-19076:
Summary: Broken links in ambari-server/docs/api/v1/schemas.md
Key: AMBARI-19076
URL: https://issues.apache.org/jira/browse/AMBARI-19076
Project: Ambari
Issue Type: Documentation
Affects Versions: trunk
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
Priority: Trivial
Fix For: trunk
This is very trivial thing. When I see API document on
[github](https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/schemas.md),
I can't jump to {{{POST/PUT/DELETE resource]}}} by clicking the link.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17847) ambari-agent register failed with HostNotFoundException: Host not found, hostname=
[
https://issues.apache.org/jira/browse/AMBARI-17847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-17847:
-
Description:
At the 'Confirm Hosts' step , ambari-agent install successed but register
failed.
20 Jul 2016 17:24:47,710 INFO [Thread-130] BSRunner:220 - Host=
gmjk-bdc-b21,gmjk-bdc-b22,gmjk-bdc-b12,gmjk-bdc-b13,gmjk-bdc-b14,gmjk-bdc-b15,gmjk-bdc-b16,gmjk-bdc-b17,gmjk-bdc-b30,gmjk-bdc-b31,gmjk-bdc-b32,gmjk-bdc-b33,gmjk-bdc-b34,gmjk-bdc-b35,gmjk-bdc-b36
bs=/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py
requestDir=/var/run/ambari-server/bootstrap/4 user=root
keyfile=/var/run/ambari-server/bootstrap/4/sshKey passwordFile null
server=gmjk-bdc-b22 version=2.2.1.0 serverPort=8080 userRunAs=root
20 Jul 2016 17:24:57,710 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:24:57,711 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:25:07,714 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:25:07,714 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:25:10,023 INFO [Thread-130] BSRunner:264 - Bootstrap output,
log=/var/run/ambari-server/bootstrap/4/bootstrap.err
/var/run/ambari-server/bootstrap/4/bootstrap.out at gmjk-bdc-b22
20 Jul 2016 17:25:10,026 INFO [Thread-130] BSRunner:275 - Script log Mesg
INFO:root:BootStrapping hosts ['gmjk-bdc-b21',
'gmjk-bdc-b22',
'gmjk-bdc-b12',
'gmjk-bdc-b13',
'gmjk-bdc-b14',
'gmjk-bdc-b15',
'gmjk-bdc-b16',
'gmjk-bdc-b17',
'gmjk-bdc-b30',
'gmjk-bdc-b31',
'gmjk-bdc-b32',
'gmjk-bdc-b33',
'gmjk-bdc-b34',
'gmjk-bdc-b35',
'gmjk-bdc-b36'] using /usr/lib/python2.6/site-packages/ambari_server cluster
primary OS: redhat6 with user 'root' sshKey File
/var/run/ambari-server/bootstrap/4/sshKey password File null using tmp dir
/var/run/ambari-server/bootstrap/4 ambari: gmjk-bdc-b22; server_port: 8080;
ambari version: 2.2.1.0; user_run_as: root
INFO:root:Executing parallel bootstrap
ERROR:root:ERROR: Bootstrap of host gmjk-bdc-b21 fails because previous action
finished with non-zero exit code (255)
ERROR MESSAGE: tcgetattr: Invalid argument
Connection to gmjk-bdc-b21 closed.
STDOUT: tput: unknown terminal "unknown"
tput: unknown terminal "unknown"
('WARNING 2016-07-20 16:05:46,843 NetUtil.py:89 - Failed to connect to
https://gmjk-bdc-b21:8440/ca due to [Errno 111] Connection refused \nWARNING
2016-07-20 16:05:46,843 NetUtil.py:112 - Server at https://gmjk-bdc-b21:8440 is
not reachable, sleeping for 10 seconds...\nINFO 2016-07-20 16:05:56,843
NetUtil.py:60 - Connecting to https://gmjk-bdc-b21:8440/ca\nWARNING 2016-07-20
16:05:56,844 NetUtil.py:89 - Failed to connect to https://gmjk-bdc-b21:8440/ca
due to [Errno 111] Connection refused \nWARNING 2016-07-20 16:05:56,844
NetUtil.py:112 - Server at https://gmjk-bdc-b21:8440 is not reachable, sleeping
for 10
tcgetattr: Invalid argument
Connection to gmjk-bdc-b21 closed.
INFO:root:Finished parallel bootstrap
20 Jul 2016 17:25:10,027 INFO [pool-11-thread-1] BSHostStatusCollector:55 -
Request directory /var/run/ambari-server/bootstrap/4
20 Jul 2016 17:25:10,027 INFO [pool-11-thread-1] BSHostStatusCollector:62 -
HostList for polling on [gmjk-bdc-b21, gmjk-bdc-b22, gmjk-bdc-b12,
gmjk-bdc-b13, gmjk-bdc-b14, gmjk-bdc-b15, gmjk-bdc-b16, gmjk-bdc-b17,
gmjk-bdc-b30, gmjk-bdc-b31, gmjk-bdc-b32, gmjk-bdc-b33, gmjk-bdc-b34,
gmjk-bdc-b35, gmjk-bdc-b36]
20 Jul 2016 17:27:18,328 ERROR [qtp-ambari-client-170]
AbstractResourceProvider:280 - Caught AmbariException when creating a resource
org.apache.ambari.server.HostNotFoundException: Host not found, hostname=
at
org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:370)
at
org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:107)
at
org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:1876)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
was:
At the 'Confirm Hosts' step , ambari-agent install successed but register
failed.
20 Jul 2016 17:24:47,710 INFO [Thread-130] BSRunner:220 - Host=
[jira] [Commented] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15646185#comment-15646185 ] Masahiro Tanaka commented on AMBARI-18761: -- Thanks [~swagle] and [~afernandez] for reviewing on RB! > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18761.1.patch, AMBARI-18761.2.patch, > AMBARI-18761.3.patch, AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15639348#comment-15639348 ] Masahiro Tanaka commented on AMBARI-18761: -- Attached a latest patch > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.1.patch, AMBARI-18761.2.patch, > AMBARI-18761.3.patch, AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Attachment: AMBARI-18761.3.patch > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.1.patch, AMBARI-18761.2.patch, > AMBARI-18761.3.patch, AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Attachment: AMBARI-18761.2.patch > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.1.patch, AMBARI-18761.2.patch, > AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Attachment: AMBARI-18761.1.patch > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.1.patch, AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Status: Patch Available (was: Open) > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Attachment: AMBARI-18761.patch Attached the first patch > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > Attachments: AMBARI-18761.patch > > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Affects Version/s: trunk Status: Patch Available (was: Open) > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
[ https://issues.apache.org/jira/browse/AMBARI-18761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18761: - Status: Open (was: Patch Available) > NTP check fails even if chrony is working on CentOS7 > > > Key: AMBARI-18761 > URL: https://issues.apache.org/jira/browse/AMBARI-18761 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.1 > Environment: CentOS7.2, Ambari 2.4.1 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka > > I use CentOS 7 as a host OS. When the host check runs, it shows warning. The > warning says "The following services should be up: Service ntpd." > I think "chrony" is a default NTP client and server on CentOS7. So We should > check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18761) NTP check fails even if chrony is working on CentOS7
Masahiro Tanaka created AMBARI-18761: Summary: NTP check fails even if chrony is working on CentOS7 Key: AMBARI-18761 URL: https://issues.apache.org/jira/browse/AMBARI-18761 Project: Ambari Issue Type: Bug Affects Versions: 2.4.1 Environment: CentOS7.2, Ambari 2.4.1 Reporter: Masahiro Tanaka Assignee: Masahiro Tanaka I use CentOS 7 as a host OS. When the host check runs, it shows warning. The warning says "The following services should be up: Service ntpd." I think "chrony" is a default NTP client and server on CentOS7. So We should check if there are ntpd or chronyd on a host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Status: Open (was: Patch Available)
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18303) Ambari Files View should show stickybit
[ https://issues.apache.org/jira/browse/AMBARI-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18303: - Status: Open (was: Patch Available) > Ambari Files View should show stickybit > --- > > Key: AMBARI-18303 > URL: https://issues.apache.org/jira/browse/AMBARI-18303 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk > Environment: CentOS6.7 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-18303.patch > > > I used files view to see directories on HDFS, and noticed that it doesn't > show stickybit even if stickybit is added to a directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18113) Installing ambari-metrics-grafana fails due to lack of conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496361#comment-15496361
]
Masahiro Tanaka commented on AMBARI-18113:
--
[~avijayan] I forgot to change the status of this JIRA, I couldn't reproduce
this error, maybe I missed some configuration.
Thanks for reminding me!
> Installing ambari-metrics-grafana fails due to lack of conf directory
> -
>
> Key: AMBARI-18113
> URL: https://issues.apache.org/jira/browse/AMBARI-18113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
> Environment: Ambari trunk, Centos 6.7
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: 2.5.0
>
> Attachments: AMBARI-18113.1.patch, AMBARI-18113.patch
>
>
> When installing Ambari Metrics, I got an error:
> Stderr
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 67, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 32, in install
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 37, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 413, in ams
> recursive_ownership = True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/etc/ambari-metrics-grafana/conf'] failed, parent directory
> /etc/ambari-metrics-grafana doesn't exist
> {code}
> Stdout
> {code}
> 2016-08-11 13:38:44,481 - Group['hadoop'] {}
> 2016-08-11 13:38:44,483 - Adding group Group['hadoop']
> 2016-08-11 13:38:44,499 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,499 - Adding user User['zookeeper']
> 2016-08-11 13:38:44,555 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,556 - Adding user User['ams']
> 2016-08-11 13:38:44,582 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['users']}
> 2016-08-11 13:38:44,582 - Adding user User['ambari-qa']
> 2016-08-11 13:38:44,616 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-08-11 13:38:44,622 - Writing
> File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
> 2016-08-11 13:38:44,622 - Changing permission for
> /var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
> 2016-08-11 13:38:44,622 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2016-08-11 13:38:44,666 - Initializing 2 repositories
> 2016-08-11 13:38:44,666 - Repository['HDP-2.5'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-1181',
> 'action': ['create'], 'components': ['HDP', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif
> %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'HDP', 'mirror_list':
> None}
> 2016-08-11 13:38:44,684 - File['/etc/yum.repos.d/HDP.repo'] {'content':
> InlineTemplate(...)}
> 2016-08-11 13:38:44,685 - Writing File['/etc/yum.repos.d/HDP.repo'] because
> it doesn't exist
> 2016-08-11 13:38:44,686 - Repository['HDP-UTILS-1.1.0.21'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6',
> 'action':
[jira] [Resolved] (AMBARI-18113) Installing ambari-metrics-grafana fails due to lack of conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka resolved AMBARI-18113.
--
Resolution: Cannot Reproduce
> Installing ambari-metrics-grafana fails due to lack of conf directory
> -
>
> Key: AMBARI-18113
> URL: https://issues.apache.org/jira/browse/AMBARI-18113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
> Environment: Ambari trunk, Centos 6.7
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: 2.5.0
>
> Attachments: AMBARI-18113.1.patch, AMBARI-18113.patch
>
>
> When installing Ambari Metrics, I got an error:
> Stderr
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 67, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 32, in install
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 37, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 413, in ams
> recursive_ownership = True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/etc/ambari-metrics-grafana/conf'] failed, parent directory
> /etc/ambari-metrics-grafana doesn't exist
> {code}
> Stdout
> {code}
> 2016-08-11 13:38:44,481 - Group['hadoop'] {}
> 2016-08-11 13:38:44,483 - Adding group Group['hadoop']
> 2016-08-11 13:38:44,499 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,499 - Adding user User['zookeeper']
> 2016-08-11 13:38:44,555 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,556 - Adding user User['ams']
> 2016-08-11 13:38:44,582 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['users']}
> 2016-08-11 13:38:44,582 - Adding user User['ambari-qa']
> 2016-08-11 13:38:44,616 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-08-11 13:38:44,622 - Writing
> File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
> 2016-08-11 13:38:44,622 - Changing permission for
> /var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
> 2016-08-11 13:38:44,622 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2016-08-11 13:38:44,666 - Initializing 2 repositories
> 2016-08-11 13:38:44,666 - Repository['HDP-2.5'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-1181',
> 'action': ['create'], 'components': ['HDP', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif
> %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'HDP', 'mirror_list':
> None}
> 2016-08-11 13:38:44,684 - File['/etc/yum.repos.d/HDP.repo'] {'content':
> InlineTemplate(...)}
> 2016-08-11 13:38:44,685 - Writing File['/etc/yum.repos.d/HDP.repo'] because
> it doesn't exist
> 2016-08-11 13:38:44,686 - Repository['HDP-UTILS-1.1.0.21'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6',
> 'action': ['create'], 'components': ['HDP-UTILS', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else
[jira] [Updated] (AMBARI-18113) Installing ambari-metrics-grafana fails due to lack of conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18113:
-
Status: Open (was: Patch Available)
> Installing ambari-metrics-grafana fails due to lack of conf directory
> -
>
> Key: AMBARI-18113
> URL: https://issues.apache.org/jira/browse/AMBARI-18113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
> Environment: Ambari trunk, Centos 6.7
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: 2.5.0
>
> Attachments: AMBARI-18113.1.patch, AMBARI-18113.patch
>
>
> When installing Ambari Metrics, I got an error:
> Stderr
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 67, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 32, in install
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 37, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 413, in ams
> recursive_ownership = True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/etc/ambari-metrics-grafana/conf'] failed, parent directory
> /etc/ambari-metrics-grafana doesn't exist
> {code}
> Stdout
> {code}
> 2016-08-11 13:38:44,481 - Group['hadoop'] {}
> 2016-08-11 13:38:44,483 - Adding group Group['hadoop']
> 2016-08-11 13:38:44,499 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,499 - Adding user User['zookeeper']
> 2016-08-11 13:38:44,555 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,556 - Adding user User['ams']
> 2016-08-11 13:38:44,582 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['users']}
> 2016-08-11 13:38:44,582 - Adding user User['ambari-qa']
> 2016-08-11 13:38:44,616 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-08-11 13:38:44,622 - Writing
> File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
> 2016-08-11 13:38:44,622 - Changing permission for
> /var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
> 2016-08-11 13:38:44,622 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2016-08-11 13:38:44,666 - Initializing 2 repositories
> 2016-08-11 13:38:44,666 - Repository['HDP-2.5'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-1181',
> 'action': ['create'], 'components': ['HDP', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif
> %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'HDP', 'mirror_list':
> None}
> 2016-08-11 13:38:44,684 - File['/etc/yum.repos.d/HDP.repo'] {'content':
> InlineTemplate(...)}
> 2016-08-11 13:38:44,685 - Writing File['/etc/yum.repos.d/HDP.repo'] because
> it doesn't exist
> 2016-08-11 13:38:44,686 - Repository['HDP-UTILS-1.1.0.21'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6',
> 'action': ['create'], 'components': ['HDP-UTILS', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{%
[jira] [Commented] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495500#comment-15495500
]
Masahiro Tanaka commented on AMBARI-18337:
--
Hi [~lavjain], thank you for reviewing on RB.
Hi [~adenisso], [~mithmatt], could you review this?
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18337:
-
Status: Patch Available (was: Open)
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18337:
-
Attachment: AMBARI-18337.patch
Attach a patch
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18337.patch
>
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18337:
-
Description:
With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
{code}
As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
comma-separated list of elements within braces, for example: {'jack',
'sjoerd'}, in addition to the set constructor.
{code}
Error
{code}
Traceback (most recent call last):
File "unitTests.py", line 129, in stack_test_executor
modules]
File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
module = __import__('.'.join(parts_copy))
File
"/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
li
ne 646
self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
^
SyntaxError: invalid syntax
{code}
was:
With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
{code}
As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
comma-separated list of elements within braces, for example: {'jack',
'sjoerd'}, in addition to the set constructor.
{code}
> Syntax Error in Ambari HAWQ Unit test with Python 2.6
> -
>
> Key: AMBARI-18337
> URL: https://issues.apache.org/jira/browse/AMBARI-18337
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
> Environment: CentOS6, Python 2.6
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
> Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
> {code}
> As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
> comma-separated list of elements within braces, for example: {'jack',
> 'sjoerd'}, in addition to the set constructor.
> {code}
> Error
> {code}
> Traceback (most recent call last):
> File "unitTests.py", line 129, in stack_test_executor
> modules]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "/tmp/ambari/ambari-server/src/test/python/common-services/HAWQ/test_service_advisor.py",
> li
> ne 646
> self.assertFalse({'HAWQMASTER', 'HAWQSTANDBY'}.issubset(hostComponents))
> ^
> SyntaxError: invalid syntax
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18337) Syntax Error in Ambari HAWQ Unit test with Python 2.6
Masahiro Tanaka created AMBARI-18337:
Summary: Syntax Error in Ambari HAWQ Unit test with Python 2.6
Key: AMBARI-18337
URL: https://issues.apache.org/jira/browse/AMBARI-18337
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Environment: CentOS6, Python 2.6
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
With Python 2.6, {code} {"A", "B"} {code} syntax isn't allowed.
Ref. https://docs.python.org/2/library/stdtypes.html#set-types-set-frozenset
{code}
As of Python 2.7, non-empty sets (not frozensets) can be created by placing a
comma-separated list of elements within braces, for example: {'jack',
'sjoerd'}, in addition to the set constructor.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18303) Ambari Files View should show stickybit
[ https://issues.apache.org/jira/browse/AMBARI-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18303: - Status: Patch Available (was: Open) > Ambari Files View should show stickybit > --- > > Key: AMBARI-18303 > URL: https://issues.apache.org/jira/browse/AMBARI-18303 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk > Environment: CentOS6.7 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-18303.patch > > > I used files view to see directories on HDFS, and noticed that it doesn't > show stickybit even if stickybit is added to a directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18303) Ambari Files View should show stickybit
[ https://issues.apache.org/jira/browse/AMBARI-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-18303: - Attachment: AMBARI-18303.patch > Ambari Files View should show stickybit > --- > > Key: AMBARI-18303 > URL: https://issues.apache.org/jira/browse/AMBARI-18303 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk > Environment: CentOS6.7 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-18303.patch > > > I used files view to see directories on HDFS, and noticed that it doesn't > show stickybit even if stickybit is added to a directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18303) Ambari Files View should show stickybit
[ https://issues.apache.org/jira/browse/AMBARI-18303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467417#comment-15467417 ] Masahiro Tanaka commented on AMBARI-18303: -- Attached a patch > Ambari Files View should show stickybit > --- > > Key: AMBARI-18303 > URL: https://issues.apache.org/jira/browse/AMBARI-18303 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk > Environment: CentOS6.7 >Reporter: Masahiro Tanaka >Assignee: Masahiro Tanaka >Priority: Minor > Attachments: AMBARI-18303.patch > > > I used files view to see directories on HDFS, and noticed that it doesn't > show stickybit even if stickybit is added to a directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18303) Ambari Files View should show stickybit
Masahiro Tanaka created AMBARI-18303: Summary: Ambari Files View should show stickybit Key: AMBARI-18303 URL: https://issues.apache.org/jira/browse/AMBARI-18303 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: trunk Environment: CentOS6.7 Reporter: Masahiro Tanaka Assignee: Masahiro Tanaka Priority: Minor I used files view to see directories on HDFS, and noticed that it doesn't show stickybit even if stickybit is added to a directory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426047#comment-15426047
]
Masahiro Tanaka commented on AMBARI-18192:
--
Attached a patch
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Status: Patch Available (was: Open)
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Attachment: AMBARI-18192.patch
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Attachments: AMBARI-18192.patch
>
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
[
https://issues.apache.org/jira/browse/AMBARI-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18192:
-
Description:
When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 6:14.285s
[INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
[INFO] Final Memory: 226M/1125M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
(make-assembly) on project ambari-server: Failed to create assembly: Error
adding file to archive:
/tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
{code}
was:When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an
error
> Can't build RPM package due to lack of upgradeHelper.py
> ---
>
> Key: AMBARI-18192
> URL: https://issues.apache.org/jira/browse/AMBARI-18192
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>
> When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
> {code}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 6:14.285s
> [INFO] Finished at: Thu Aug 18 03:53:29 UTC 2016
> [INFO] Final Memory: 226M/1125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:single
> (make-assembly) on project ambari-server: Failed to create assembly: Error
> adding file to archive:
> /tmp/ambari/ambari-server/src/main/python/upgradeHelper.py isn't a file. ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18192) Can't build RPM package due to lack of upgradeHelper.py
Masahiro Tanaka created AMBARI-18192:
Summary: Can't build RPM package due to lack of upgradeHelper.py
Key: AMBARI-18192
URL: https://issues.apache.org/jira/browse/AMBARI-18192
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Masahiro Tanaka
Assignee: Masahiro Tanaka
When I ran {{mvn clean install package rpm:rpm -DskipTests}}, I got an error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation
[
https://issues.apache.org/jira/browse/AMBARI-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15423642#comment-15423642
]
Masahiro Tanaka commented on AMBARI-18126:
--
Thanks!
> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from
> {{ambari.properties}} need a way to be organized and queried in order to
> generate documentation.
> This Jira proposes to change our disorganized String/String (key/default)
> structure found in {{Configuration}}, and instead, have a strongly-coupled
> relationship between key/default/type.
> Additionally, expose a way to provide extra information in the markdown
> (similar to JavaDoc, but geared more for users and not developers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-17999) Typo in property name "yarn.nodemanager.log.retain-second", should be "seconds"
[ https://issues.apache.org/jira/browse/AMBARI-17999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiro Tanaka updated AMBARI-17999: - Comment: was deleted (was: I would like to work on this issue. Will upload a patch) > Typo in property name "yarn.nodemanager.log.retain-second", should be > "seconds" > --- > > Key: AMBARI-17999 > URL: https://issues.apache.org/jira/browse/AMBARI-17999 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Ying Zhang >Priority: Minor > Attachments: AMBARI-17999.001.patch > > > In yarn-site.xml, property name "yarn.nodemanager.log.retain-second" is > wrong, should be "yarn.nodemanager.log.retain-seconds" instead. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation
[
https://issues.apache.org/jira/browse/AMBARI-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422164#comment-15422164
]
Masahiro Tanaka commented on AMBARI-18126:
--
Thnak you for checking. I used {{dev-support/docker/docker/Dockerfile}} with
Java 7.
(BTW, there is a bug in the Dockerfile which I made. If you want to try this,
please change line 28 to {{RUN wget --no-check-certificate --no-cookies
--header "Cookie:oraclelicense=accept-securebackup-cookie"
http://download.oracle.com/otn-pub/java/jdk/7u55-b13/jdk-7u55-linux-x64.rpm -O
jdk-7u55-linux-x64.rpm}}. Sorry for inconvenience.)
I ran {{mvn clean compile}}, and yes, it worked well as you wrote.
But when I ran {{mvn clean install package rpm:rpm -DskipTests}} from Ambari
root directory, I got the error above.
{code}
[root@e18b03aaa58f ambari]# mvn --version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
13:51:28+)
Maven home: /opt/maven/apache-maven-3.0.5
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_55/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-327.22.2.el7.x86_64", arch: "amd64", family:
"unix"
{code}
> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from
> {{ambari.properties}} need a way to be organized and queried in order to
> generate documentation.
> This Jira proposes to change our disorganized String/String (key/default)
> structure found in {{Configuration}}, and instead, have a strongly-coupled
> relationship between key/default/type.
> Additionally, expose a way to provide extra information in the markdown
> (similar to JavaDoc, but geared more for users and not developers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation
[
https://issues.apache.org/jira/browse/AMBARI-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422164#comment-15422164
]
Masahiro Tanaka edited comment on AMBARI-18126 at 8/16/16 4:51 AM:
---
Thank you for checking. I used {{dev-support/docker/docker/Dockerfile}} with
Java 7.
(BTW, there is a bug in the Dockerfile which I made. If you want to try this,
please change line 28 to {{RUN wget --no-check-certificate --no-cookies
--header "Cookie:oraclelicense=accept-securebackup-cookie"
http://download.oracle.com/otn-pub/java/jdk/7u55-b13/jdk-7u55-linux-x64.rpm -O
jdk-7u55-linux-x64.rpm}}. Sorry for inconvenience.)
I ran {{mvn clean compile}}, and yes, it worked well as you wrote.
But when I ran {{mvn clean install package rpm:rpm -DskipTests}} from Ambari
root directory, I got the error above.
{code}
[root@e18b03aaa58f ambari]# mvn --version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
13:51:28+)
Maven home: /opt/maven/apache-maven-3.0.5
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_55/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-327.22.2.el7.x86_64", arch: "amd64", family:
"unix"
{code}
was (Author: masatana):
Thnak you for checking. I used {{dev-support/docker/docker/Dockerfile}} with
Java 7.
(BTW, there is a bug in the Dockerfile which I made. If you want to try this,
please change line 28 to {{RUN wget --no-check-certificate --no-cookies
--header "Cookie:oraclelicense=accept-securebackup-cookie"
http://download.oracle.com/otn-pub/java/jdk/7u55-b13/jdk-7u55-linux-x64.rpm -O
jdk-7u55-linux-x64.rpm}}. Sorry for inconvenience.)
I ran {{mvn clean compile}}, and yes, it worked well as you wrote.
But when I ran {{mvn clean install package rpm:rpm -DskipTests}} from Ambari
root directory, I got the error above.
{code}
[root@e18b03aaa58f ambari]# mvn --version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
13:51:28+)
Maven home: /opt/maven/apache-maven-3.0.5
Java version: 1.7.0_55, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_55/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-327.22.2.el7.x86_64", arch: "amd64", family:
"unix"
{code}
> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from
> {{ambari.properties}} need a way to be organized and queried in order to
> generate documentation.
> This Jira proposes to change our disorganized String/String (key/default)
> structure found in {{Configuration}}, and instead, have a strongly-coupled
> relationship between key/default/type.
> Additionally, expose a way to provide extra information in the markdown
> (similar to JavaDoc, but geared more for users and not developers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18126) Refactor Configuration To Allow For Generation Of Documentation
[
https://issues.apache.org/jira/browse/AMBARI-18126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422077#comment-15422077
]
Masahiro Tanaka commented on AMBARI-18126:
--
Hi [~jonathan.hurley], I think this patch may break the UT.
After the commit {{b1a6340}}, I got a compilation error
{code}
[INFO]
[INFO] Building Ambari Functional Tests 2.0.0.0-SNAPSHOT
[INFO]
[INFO][info] --- maven-clean-plugin:2.5:clean (default-clean) @ ambari-funtest
---
[INFO] Deleting /tmp/ambari/ambari-funtest/target
[INFO] Deleting /tmp/ambari/ambari-funtest (includes = [*/.pyc], excludes = [])
[INFO][info] --- build-helper-maven-plugin:1.8:regex-property
(parse-package-version) @ ambari-funtest --
-
[INFO][info] --- build-helper-maven-plugin:1.8:regex-property
(parse-package-release) @ ambari-funtest --
-
[INFO][info] --- maven-resources-plugin:2.5:resources (default-resources) @
ambari-funtest ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/tmp/ambari/ambari-funtest/src/main/resources
[INFO] skip non existing resourceDirectory
/tmp/ambari/ambari-funtest/src/main/resources
[INFO][info] --- maven-compiler-plugin:3.0:compile (default-compile) @
ambari-funtest ---
[INFO] No sources to compile
[INFO][info] --- maven-resources-plugin:2.5:testResources
(default-testResources) @ ambari-funtest ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 353 resources
[INFO][info] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @
ambari-funtest ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 44 source files to
/tmp/ambari/ambari-funtest/target/test-classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/tmp/ambari/ambari-funtest/src/test/java/org/apache/ambari/funtest/server/tests/ServerTestB
ase.java:[102,49] cannot find symbol
symbol: variable SERVER_PERSISTENCE_TYPE_KEY
location: class org.apache.ambari.server.configuration.Configuration
[ERROR]
/tmp/ambari/ambari-funtest/src/test/java/org/apache/ambari/funtest/server/tests/ServerTestB
ase.java:[103,49] cannot find symbol
symbol: variable SERVER_JDBC_URL_KEY
location: class org.apache.ambari.server.configuration.Configuration
{code}
Could you update the patch? Thank you.
> Refactor Configuration To Allow For Generation Of Documentation
> ---
>
> Key: AMBARI-18126
> URL: https://issues.apache.org/jira/browse/AMBARI-18126
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-18126.patch
>
>
> As part of the work for AMBARI-18089, all of the potential properties from
> {{ambari.properties}} need a way to be organized and queried in order to
> generate documentation.
> This Jira proposes to change our disorganized String/String (key/default)
> structure found in {{Configuration}}, and instead, have a strongly-coupled
> relationship between key/default/type.
> Additionally, expose a way to provide extra information in the markdown
> (similar to JavaDoc, but geared more for users and not developers).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18113) Installing ambari-metrics-grafana fails due to lack of conf directory
[
https://issues.apache.org/jira/browse/AMBARI-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka updated AMBARI-18113:
-
Attachment: AMBARI-18113.1.patch
> Installing ambari-metrics-grafana fails due to lack of conf directory
> -
>
> Key: AMBARI-18113
> URL: https://issues.apache.org/jira/browse/AMBARI-18113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
> Environment: Ambari trunk, Centos 6.7
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
> Fix For: 2.5.0
>
> Attachments: AMBARI-18113.1.patch, AMBARI-18113.patch
>
>
> When installing Ambari Metrics, I got an error:
> Stderr
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 67, in
> AmsGrafana().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 280, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 32, in install
> self.configure(env) # for security
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
> line 37, in configure
> ams(name='grafana', action=action)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py",
> line 413, in ams
> recursive_ownership = True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 189, in action_create
> raise Fail("Applying %s failed, parent directory %s doesn't exist" %
> (self.resource, dirname))
> resource_management.core.exceptions.Fail: Applying
> Directory['/etc/ambari-metrics-grafana/conf'] failed, parent directory
> /etc/ambari-metrics-grafana doesn't exist
> {code}
> Stdout
> {code}
> 2016-08-11 13:38:44,481 - Group['hadoop'] {}
> 2016-08-11 13:38:44,483 - Adding group Group['hadoop']
> 2016-08-11 13:38:44,499 - User['zookeeper'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,499 - Adding user User['zookeeper']
> 2016-08-11 13:38:44,555 - User['ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop']}
> 2016-08-11 13:38:44,556 - Adding user User['ams']
> 2016-08-11 13:38:44,582 - User['ambari-qa'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['users']}
> 2016-08-11 13:38:44,582 - Adding user User['ambari-qa']
> 2016-08-11 13:38:44,616 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> {'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2016-08-11 13:38:44,622 - Writing
> File['/var/lib/ambari-agent/tmp/changeUid.sh'] because it doesn't exist
> 2016-08-11 13:38:44,622 - Changing permission for
> /var/lib/ambari-agent/tmp/changeUid.sh from 644 to 555
> 2016-08-11 13:38:44,622 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
> {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2016-08-11 13:38:44,666 - Initializing 2 repositories
> 2016-08-11 13:38:44,666 - Repository['HDP-2.5'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos6/2.x/BUILDS/2.5.0.0-1181',
> 'action': ['create'], 'components': ['HDP', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else %}baseurl={{base_url}}{% endif
> %}\n\npath=/\nenabled=1\ngpgcheck=0', 'repo_file_name': 'HDP', 'mirror_list':
> None}
> 2016-08-11 13:38:44,684 - File['/etc/yum.repos.d/HDP.repo'] {'content':
> InlineTemplate(...)}
> 2016-08-11 13:38:44,685 - Writing File['/etc/yum.repos.d/HDP.repo'] because
> it doesn't exist
> 2016-08-11 13:38:44,686 - Repository['HDP-UTILS-1.1.0.21'] {'base_url':
> 'http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6',
> 'action': ['create'], 'components': ['HDP-UTILS', 'main'], 'repo_template':
> '[{{repo_id}}]\nname={{repo_id}}\n{% if mirror_list
> %}mirrorlist={{mirror_list}}{% else
