[jira] [Updated] (AMBARI-22760) Infra Manager: install packages
[ https://issues.apache.org/jira/browse/AMBARI-22760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-22760: Resolution: Fixed Status: Resolved (was: Patch Available) > Infra Manager: install packages > --- > > Key: AMBARI-22760 > URL: https://issues.apache.org/jira/browse/AMBARI-22760 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22762: -- Attachment: AMBARI-22762.patch > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323406#comment-16323406 ] mathildaMa09 commented on AMBARI-22762: --- edit test files > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22762: -- Attachment: (was: AMBARI-22762.patch) > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22770) Bring jenkins job build script under version control
Vivek Ratnavel Subramanian created AMBARI-22770: --- Summary: Bring jenkins job build script under version control Key: AMBARI-22770 URL: https://issues.apache.org/jira/browse/AMBARI-22770 Project: Ambari Issue Type: Task Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16323316#comment-16323316 ] Hudson commented on AMBARI-20797: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #570 (See [https://builds.apache.org/job/Ambari-branch-2.6/570/]) AMBARI-20797 : Ambari Metrics Storm Sink compilation error due to (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=af5ce3f20989a9188855010773357284a6f923e5]) * (edit) ambari-metrics/ambari-metrics-storm-sink/pom.xml > 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.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16323278#comment-16323278 ] ASF GitHub Bot commented on AMBARI-20797: - Jetly-Jaimin closed pull request #97: AMBARI-20797 : Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT. (Masahiro Tanaka via avijayan) URL: https://github.com/apache/ambari/pull/97 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/ambari-metrics/ambari-metrics-storm-sink/pom.xml b/ambari-metrics/ambari-metrics-storm-sink/pom.xml index 07e2f769428..9f6bc617463 100644 --- a/ambari-metrics/ambari-metrics-storm-sink/pom.xml +++ b/ambari-metrics/ambari-metrics-storm-sink/pom.xml @@ -31,7 +31,7 @@ limitations under the License. jar -1.1.0-SNAPSHOT +1.1.0 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 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.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16323277#comment-16323277 ] ASF GitHub Bot commented on AMBARI-20797: - Jetly-Jaimin commented on issue #97: AMBARI-20797 : Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT. (Masahiro Tanaka via avijayan) URL: https://github.com/apache/ambari/pull/97#issuecomment-357105008 Earlier Jenkins job used to fail for **Ambari Web** and **Ambari Metrics Storm Sink** project on ambari branch-2.6 After the patch Jenkins Job fails only on **Ambari Web** project This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 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.4.14#64029)
[jira] [Commented] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323262#comment-16323262 ] Hudson commented on AMBARI-22768: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8592 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8592/]) AMBARI-22768. Update Welcome page style (akovalenko) (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8e59a86edfbd0ac0b56934f34755e43cc61546e8]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/styles/cluster-information.css * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/clusterInformation.html * (add) ambari-web/app/assets/img/install-box.svg > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22768: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22768) Update Welcome page style
[
https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16323206#comment-16323206
]
ASF GitHub Bot commented on AMBARI-22768:
-
aleksandrkovalenko closed pull request #94: AMBARI-22768. Update Welcome page
style
URL: https://github.com/apache/ambari/pull/94
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-admin/src/main/resources/ui/admin-web/app/styles/cluster-information.css
b/ambari-admin/src/main/resources/ui/admin-web/app/styles/cluster-information.css
index 64e9ecb29ba..519eeaea508 100644
---
a/ambari-admin/src/main/resources/ui/admin-web/app/styles/cluster-information.css
+++
b/ambari-admin/src/main/resources/ui/admin-web/app/styles/cluster-information.css
@@ -52,7 +52,30 @@
padding: 30px;
}
-#cluster-information .fa-cloud {
- font-size: 150px;
- color: #f0f0f0;
+#cluster-information .install-button {
+ height: 40px;
+}
+
+#cluster-information .install-button a {
+ height: 100%;
+ padding: 0;
+ width: 225px;
+ font-size: 16px;
+ line-height: 40px;
+}
+
+@keyframes INSTALL-BOX-ROTATE {
+ 0% {transform: rotate(0deg)}
+ 12.5% {transform: rotate(-30deg)}
+ 37.5% {transform: rotate(30deg)}
+ 62.5% {transform: rotate(-30deg)}
+ 87.5% {transform: rotate(30deg)}
+ 100% {transform: rotate(0deg)}
+}
+
+#cluster-information #install-box {
+ animation: INSTALL-BOX-ROTATE 2s;
+ width: 116px;
+ margin-bottom: 20px;
+ margin-top: 40px;
}
diff --git
a/ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/clusterInformation.html
b/ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/clusterInformation.html
index ead73c309f2..9747addcf8e 100644
---
a/ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/clusterInformation.html
+++
b/ambari-admin/src/main/resources/ui/admin-web/app/views/clusters/clusterInformation.html
@@ -20,17 +20,17 @@
{{'main.title' | translate}}
- {{'main.noClusterDescription' | translate}}
+ {{'main.noClusterDescription' |
translate}}
{{'main.createCluster.title' | translate}}
-
+
{{'main.createCluster.description' | translate}}
-
-
+
+
{{'main.createCluster.launchInstallWizard' | translate}}
diff --git a/ambari-web/app/assets/img/install-box.svg
b/ambari-web/app/assets/img/install-box.svg
new file mode 100644
index 000..e914885d43a
--- /dev/null
+++ b/ambari-web/app/assets/img/install-box.svg
@@ -0,0 +1,28 @@
+
+
+http://www.w3.org/2000/svg;
xmlns:xlink="http://www.w3.org/1999/xlink; x="0px" y="0px"
+viewBox="0 0 92 71.6" style="enable-background:new 0 0 92 71.6;"
xml:space="preserve">
+
+ .st0{fill:#66;}
+ .st1{fill:#DD;}
+ .st2{fill:#CC;}
+
+
+
+
+
+
+
+
+
+
+
+
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Update Welcome page style
> -
>
> Key: AMBARI-22768
> URL: https://issues.apache.org/jira/browse/AMBARI-22768
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-22768.patch
>
>
> Update layout Welcome page on Admin View.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (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:comment-tabpanel=16323138#comment-16323138 ] ASF GitHub Bot commented on AMBARI-20797: - Jetly-Jaimin opened a new pull request #97: AMBARI-20797 : Ambari Metrics Storm Sink compilation error due to storm-1.1.0-SNAPSHOT. (Masahiro Tanaka via avijayan) URL: https://github.com/apache/ambari/pull/97 ## What changes were proposed in this pull request? Cherry-pick a commit from trunk that changes storm version from 1.1.0-snapshot to 1.1.0 ## How was this patch tested? Tested manually This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 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.4.14#64029)
[jira] [Updated] (AMBARI-22504) Replace test-patch.sh with Yetus
[
https://issues.apache.org/jira/browse/AMBARI-22504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22504:
---
Resolution: Won't Do
Status: Resolved (was: Patch Available)
No longer needed, as the [new Jenkins
job|https://builds.apache.org/view/A/view/Ambari/job/Ambari-Github-PullRequest-Builder/]
can test changes on any branch.
CC [~vivekratnavel], [~oleewere]
> Replace test-patch.sh with Yetus
>
>
> Key: AMBARI-22504
> URL: https://issues.apache.org/jira/browse/AMBARI-22504
> Project: Ambari
> Issue Type: Improvement
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-22504.000.patch, AMBARI-22504.branch-2.6.patch,
> AMBARI-22504.branch-feature-AMBARI-14714-blueprintv2.002.patch,
> AMBARI-22504.branch-feature-AMBARI-22504.000.patch
>
>
> Most of Ambari 3.0 development is taking place in various feature branches,
> but {{test-patch.sh}} only tries patches on trunk. This makes "Hadoop QA"
> largely useless for Ambari, since in most cases the only feedback we get is
> that it could not apply the patch.
> {{test-patch.sh}} was originally copied from Hadoop. The Hadoop version has
> evolved and was extracted to [Apache Yetus|http://yetus.apache.org/].
> Instead of adding configurable branch support to the current script, we
> should replace it with one that utilizes Yetus. See for example
> [Hadoop|https://github.com/apache/hadoop/blob/trunk/dev-support/bin/test-patch],
> [Hive|https://github.com/apache/hive/blob/master/dev-support/test-patch.sh]
> and
> [Ratis|https://github.com/apache/incubator-ratis/blob/master/dev-support/test-patch].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322918#comment-16322918 ] ASF GitHub Bot commented on AMBARI-22763: - adoroszlai commented on issue #91: [AMBARI-22763] Fix unit test error in ambari-utility on branch-3.0-perf URL: https://github.com/apache/ambari/pull/91#issuecomment-357056004 @swagle @mpapirkovskyy Now that build goes beyond `ambari-utility`, the size of the [build log](https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/10/console) produced is ~220MB. It seems `ActiveWidgetLayoutResourceProviderTest` is responsible for 182MB of that due to `StackOverflowError` in `createInjector()`. I have added another commit to disable that test until the error can be investigated. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix checkstyle failure after merging trunk to branch-3.0-perf > - > > Key: AMBARI-22763 > URL: https://issues.apache.org/jira/browse/AMBARI-22763 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
[ https://issues.apache.org/jira/browse/AMBARI-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322904#comment-16322904 ] ASF GitHub Bot commented on AMBARI-22769: - avijayanhwx opened a new pull request #96: [AMBARI-22769] [ambari-metrics] Implement EMA Spark Streaming Driver (Initial work) (avijayan) URL: https://github.com/apache/ambari/pull/96 ## What changes were proposed in this pull request? Implement EMA Spark streaming application which takes in a list of Metric Keys as input and updates the EMA model whenever they are received through Kafka stream. ## How was this patch tested? Manually Tested. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) > > > Key: AMBARI-22769 > URL: https://issues.apache.org/jira/browse/AMBARI-22769 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
[
https://issues.apache.org/jira/browse/AMBARI-22766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322879#comment-16322879
]
Hudson commented on AMBARI-22766:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8591 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8591/])
AMBARI-22766 ambari-server setup with internal database may not work on
(3234762+hapylestat:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=40825494c10f6ecfa5d9516659c303b3864e9c16])
* (edit) ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
* (edit) ambari-common/src/main/python/ambari_commons/os_check.py
> ambari-server setup with internal database may not work on centos 7
> ---
>
> Key: AMBARI-22766
> URL: https://issues.apache.org/jira/browse/AMBARI-22766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
>
> it may happened so, that centos7 image will not have "service" command at all.
> {code}
> Default properties detected. Using built-in database.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Adjusting filesystem permissions
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Configuring ambari database...
> Checking PostgreSQL...
> INFO: about to run command: /usr/bin/env service postgresql status
> Running initdb: This may take up to a minute.
> INFO: about to run command: /usr/bin/postgresql-setup initdb
> About to start PostgreSQL
> INFO: about to run command: /usr/bin/env service postgresql status
> ERROR: Exiting with exit code 127.
> REASON: Unable to start PostgreSQL server. Exiting
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> {code}
> *Background:*
> This caused due to centos 7 using systemd by default and switched to use of
> {{systemctl}} command instead of {{service}}. Since that, service command
> exist only in backward compatibility context and r optional. Currently
> optional package, which provides this package called {{initscripts}}
> Currently, everything ok r with standalone centos 7 image and it includes
> this package installed by default. However docker image centos/centos:7
> doesn't provide this package by default, and systemd enabled image
> centos/systemd:latest use {{systemctl}} without installed {{initscripts}}:
> https://github.com/CentOS/sig-cloud-instance-images/issues/28
> *Summary:*
> Due to {{service}} command going to be deprecated, we need consider to switch
> fully to {{systemctl}} replacement for systemd enabled images
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322844#comment-16322844 ] Hudson commented on AMBARI-22635: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #569 (See [https://builds.apache.org/job/Ambari-branch-2.6/569/]) AMBARI-22635: Ambari should create a dummy core-site.xml for Ranger (swagle: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=21fb855c6be7adb473c13cb677474a74da3c5003]) * (edit) ambari-server/src/main/resources/common-services/STORM/0.9.1/package/scripts/setup_ranger_storm.py * (edit) ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py * (edit) ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22696) Whitelist execute latency from Storm Ambari metrics
[ https://issues.apache.org/jira/browse/AMBARI-22696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322830#comment-16322830 ] Jungtaek Lim commented on AMBARI-22696: --- [~avijayan] I know Ambari community made a decision to go with gitbox recently. Does it mean I need to submit pull request again? Two patches already got +1 in review board so just would like to check which further actions are needed to make patches committed. cc. [~arunmahadevan] [~ggolani] > Whitelist execute latency from Storm Ambari metrics > --- > > Key: AMBARI-22696 > URL: https://issues.apache.org/jira/browse/AMBARI-22696 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.6.2 >Reporter: Arun Mahadevan >Assignee: Jungtaek Lim > Attachments: AMBARI-22696-branch-2.6.patch, AMBARI-22696.patch > > > Whitelist execute latency from Storm Ambari metrics -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
[
https://issues.apache.org/jira/browse/AMBARI-22766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22766:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ambari-server setup with internal database may not work on centos 7
> ---
>
> Key: AMBARI-22766
> URL: https://issues.apache.org/jira/browse/AMBARI-22766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
>
> it may happened so, that centos7 image will not have "service" command at all.
> {code}
> Default properties detected. Using built-in database.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Adjusting filesystem permissions
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Configuring ambari database...
> Checking PostgreSQL...
> INFO: about to run command: /usr/bin/env service postgresql status
> Running initdb: This may take up to a minute.
> INFO: about to run command: /usr/bin/postgresql-setup initdb
> About to start PostgreSQL
> INFO: about to run command: /usr/bin/env service postgresql status
> ERROR: Exiting with exit code 127.
> REASON: Unable to start PostgreSQL server. Exiting
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> {code}
> *Background:*
> This caused due to centos 7 using systemd by default and switched to use of
> {{systemctl}} command instead of {{service}}. Since that, service command
> exist only in backward compatibility context and r optional. Currently
> optional package, which provides this package called {{initscripts}}
> Currently, everything ok r with standalone centos 7 image and it includes
> this package installed by default. However docker image centos/centos:7
> doesn't provide this package by default, and systemd enabled image
> centos/systemd:latest use {{systemctl}} without installed {{initscripts}}:
> https://github.com/CentOS/sig-cloud-instance-images/issues/28
> *Summary:*
> Due to {{service}} command going to be deprecated, we need consider to switch
> fully to {{systemctl}} replacement for systemd enabled images
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
[
https://issues.apache.org/jira/browse/AMBARI-22766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22766:
-
Status: Patch Available (was: In Progress)
> ambari-server setup with internal database may not work on centos 7
> ---
>
> Key: AMBARI-22766
> URL: https://issues.apache.org/jira/browse/AMBARI-22766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
>
> it may happened so, that centos7 image will not have "service" command at all.
> {code}
> Default properties detected. Using built-in database.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Adjusting filesystem permissions
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Configuring ambari database...
> Checking PostgreSQL...
> INFO: about to run command: /usr/bin/env service postgresql status
> Running initdb: This may take up to a minute.
> INFO: about to run command: /usr/bin/postgresql-setup initdb
> About to start PostgreSQL
> INFO: about to run command: /usr/bin/env service postgresql status
> ERROR: Exiting with exit code 127.
> REASON: Unable to start PostgreSQL server. Exiting
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> {code}
> *Background:*
> This caused due to centos 7 using systemd by default and switched to use of
> {{systemctl}} command instead of {{service}}. Since that, service command
> exist only in backward compatibility context and r optional. Currently
> optional package, which provides this package called {{initscripts}}
> Currently, everything ok r with standalone centos 7 image and it includes
> this package installed by default. However docker image centos/centos:7
> doesn't provide this package by default, and systemd enabled image
> centos/systemd:latest use {{systemctl}} without installed {{initscripts}}:
> https://github.com/CentOS/sig-cloud-instance-images/issues/28
> *Summary:*
> Due to {{service}} command going to be deprecated, we need consider to switch
> fully to {{systemctl}} replacement for systemd enabled images
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
[
https://issues.apache.org/jira/browse/AMBARI-22766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322815#comment-16322815
]
ASF GitHub Bot commented on AMBARI-22766:
-
hapylestat closed pull request #95: [AMBARI-22766] ambari-server setup with
internal database may not work on centos 7 (dgrinenko)
URL: https://github.com/apache/ambari/pull/95
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-common/src/main/python/ambari_commons/os_check.py
b/ambari-common/src/main/python/ambari_commons/os_check.py
index 04165848508..b2b227408ac 100644
--- a/ambari-common/src/main/python/ambari_commons/os_check.py
+++ b/ambari-common/src/main/python/ambari_commons/os_check.py
@@ -164,6 +164,8 @@ def __getattr__(cls, name):
class OSConst:
__metaclass__ = OS_CONST_TYPE
+ systemd_redhat_os_major_versions = ["7"]
+
class OSCheck:
diff --git
a/ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
b/ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
index 2ac5325b7e0..036a542d87b 100644
--- a/ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
+++ b/ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py
@@ -355,19 +355,27 @@ class PGConfig(LinuxDBMSConfig):
PG_ERROR_BLOCKED = "is being accessed by other users"
PG_STATUS_RUNNING = None
PG_STATUS_STOPPED = "stopped"
- SERVICE_CMD = "/usr/bin/env service"
PG_SERVICE_NAME = "postgresql"
PG_HBA_DIR = None
- PG_ST_CMD = "%s %s status" % (SERVICE_CMD, PG_SERVICE_NAME)
- if os.path.isfile("/usr/bin/postgresql-setup"):
- PG_INITDB_CMD = "/usr/bin/postgresql-setup initdb"
+ if OSCheck.is_redhat_family() and OSCheck.get_os_major_version() in
OSConst.systemd_redhat_os_major_versions:
+SERVICE_CMD = "/usr/bin/env systemctl"
+PG_ST_CMD = "%s status %s" % (SERVICE_CMD, PG_SERVICE_NAME)
+PG_INITDB_CMD = "/usr/bin/postgresql-setup initdb"
+PG_START_CMD = AMBARI_SUDO_BINARY + " %s start %s" % (SERVICE_CMD,
PG_SERVICE_NAME)
+PG_RESTART_CMD = AMBARI_SUDO_BINARY + " %s restart %s" % (SERVICE_CMD,
PG_SERVICE_NAME)
+PG_HBA_RELOAD_CMD = AMBARI_SUDO_BINARY + " %s reload %s" % (SERVICE_CMD,
PG_SERVICE_NAME)
else:
- PG_INITDB_CMD = "%s %s initdb" % (SERVICE_CMD, PG_SERVICE_NAME)
+SERVICE_CMD = "/usr/bin/env service"
+PG_ST_CMD = "%s %s status" % (SERVICE_CMD, PG_SERVICE_NAME)
+if os.path.isfile("/usr/bin/postgresql-setup"):
+PG_INITDB_CMD = "/usr/bin/postgresql-setup initdb"
+else:
+PG_INITDB_CMD = "%s %s initdb" % (SERVICE_CMD, PG_SERVICE_NAME)
- PG_START_CMD = AMBARI_SUDO_BINARY + " %s %s start" % (SERVICE_CMD,
PG_SERVICE_NAME)
- PG_RESTART_CMD = AMBARI_SUDO_BINARY + " %s %s restart" % (SERVICE_CMD,
PG_SERVICE_NAME)
- PG_HBA_RELOAD_CMD = AMBARI_SUDO_BINARY + " %s %s reload" % (SERVICE_CMD,
PG_SERVICE_NAME)
+PG_START_CMD = AMBARI_SUDO_BINARY + " %s %s start" % (SERVICE_CMD,
PG_SERVICE_NAME)
+PG_RESTART_CMD = AMBARI_SUDO_BINARY + " %s %s restart" % (SERVICE_CMD,
PG_SERVICE_NAME)
+PG_HBA_RELOAD_CMD = AMBARI_SUDO_BINARY + " %s %s reload" % (SERVICE_CMD,
PG_SERVICE_NAME)
PG_HBA_CONF_FILE = None
PG_HBA_CONF_FILE_BACKUP = None
@@ -611,7 +619,7 @@ def _get_postgre_status():
retcode, out, err = run_os_command(PGConfig.PG_ST_CMD)
# on RHEL and SUSE PG_ST_COMD returns RC 0 for running and 3 for stoppped
if retcode == 0:
- if out.strip() == "Running clusters:":
+ if out.strip() == "Running clusters:" or "active: inactive" in
out.lower():
pg_status = PGConfig.PG_STATUS_STOPPED
else:
pg_status = PGConfig.PG_STATUS_RUNNING
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> ambari-server setup with internal database may not work on centos 7
> ---
>
> Key: AMBARI-22766
> URL: https://issues.apache.org/jira/browse/AMBARI-22766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
>
> it may happened so, that centos7 image will not have "service" command at all.
> {code}
> Default properties detected. Using built-in database.
> INFO: Loading properties from
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322811#comment-16322811
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161052583
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322812#comment-16322812
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161052613
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
+ return m_isPreInstalled;
+}
+
+public boolean isScoped() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322810#comment-16322810
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161052030
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
+ return m_isPreInstalled;
+}
+
+public boolean isScoped() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322807#comment-16322807
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161051986
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322802#comment-16322802
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161051986
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322801#comment-16322801
]
ASF GitHub Bot commented on AMBARI-22763:
-
hapylestat commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r161052030
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getPreInstalled() {
+ return m_isPreInstalled;
+}
+
+public boolean isScoped() {
Review comment:
why this getter is needed? it is not used anywhere and the only one role he
have - be serialized to json
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[
https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322787#comment-16322787
]
ASF GitHub Bot commented on AMBARI-22635:
-
swagle closed pull request #90: AMBARI-22635: Ambari should create a dummy
core-site.xml for Ranger p…
URL: https://github.com/apache/ambari/pull/90
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
b/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
index 485c1a67436..78692cba45b 100644
---
a/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
+++
b/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
@@ -240,14 +240,14 @@ def setup_ranger_plugin_keystore(service_name,
audit_db_is_enabled, stack_versio
mode = 0640
)
-def setup_core_site_for_required_plugins(component_user, component_group,
create_core_site_path, config):
+def setup_core_site_for_required_plugins(component_user, component_group,
create_core_site_path, configurations = {}, configuration_attributes = {}):
XmlConfig('core-site.xml',
-conf_dir=create_core_site_path,
-configurations=config['configurations']['core-site'],
-configuration_attributes=config['configuration_attributes']['core-site'],
-owner=component_user,
-group=component_group,
-mode=0644
+conf_dir = create_core_site_path,
+configurations = configurations,
+configuration_attributes = configuration_attributes,
+owner = component_user,
+group = component_group,
+mode = 0644
)
def get_audit_configs(config):
diff --git
a/ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py
b/ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py
index 9aa09df18d4..16eff94eca1 100644
---
a/ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py
+++
b/ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/setup_ranger_kafka.py
@@ -81,9 +81,18 @@ def setup_ranger_kafka():
group = params.user_group,
mode = 0755
)
-if params.stack_supports_core_site_for_ranger_plugin and
params.enable_ranger_kafka and params.has_namenode and
params.kerberos_security_enabled:
- Logger.info("Stack supports core-site.xml creation for Ranger plugin,
creating create core-site.xml from namenode configuraitions")
-
setup_core_site_for_required_plugins(component_user=params.kafka_user,component_group=params.user_group,create_core_site_path
= params.conf_dir, config = params.config)
+if params.stack_supports_core_site_for_ranger_plugin and
params.enable_ranger_kafka and params.kerberos_security_enabled:
+ if params.has_namenode:
+Logger.info("Stack supports core-site.xml creation for Ranger plugin
and Namenode is installed, creating create core-site.xml from namenode
configurations")
+setup_core_site_for_required_plugins(component_user =
params.kafka_user, component_group = params.user_group,
+ create_core_site_path =
params.conf_dir, configurations = params.config['configurations']['core-site'],
+ configuration_attributes =
params.config['configuration_attributes']['core-site'])
+ else:
+Logger.info("Stack supports core-site.xml creation for Ranger plugin
and Namenode is not installed, creating create core-site.xml from default
configurations")
+setup_core_site_for_required_plugins(component_user =
params.kafka_user, component_group = params.user_group,
+ create_core_site_path =
params.conf_dir, configurations = { 'hadoop.security.authentication' :
'kerberos' if params.kerberos_security_enabled else 'simple' },
+ configuration_attributes = {})
+
else:
Logger.info("Stack does not support core-site.xml creation for Ranger
plugin, skipping core-site.xml configurations")
else:
diff --git
a/ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py
b/ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py
index c486ef7c8c7..67fec40e7da 100644
---
a/ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/setup_ranger_knox.py
+++
[jira] [Updated] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
[ https://issues.apache.org/jira/browse/AMBARI-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22769: --- Status: In Progress (was: Patch Available) > Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) > > > Key: AMBARI-22769 > URL: https://issues.apache.org/jira/browse/AMBARI-22769 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
[ https://issues.apache.org/jira/browse/AMBARI-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22769: --- Status: Patch Available (was: Open) > Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) > > > Key: AMBARI-22769 > URL: https://issues.apache.org/jira/browse/AMBARI-22769 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
Aravindan Vijayan created AMBARI-22769: -- Summary: Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) Key: AMBARI-22769 URL: https://issues.apache.org/jira/browse/AMBARI-22769 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 3.0.0 Reporter: Aravindan Vijayan -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
[ https://issues.apache.org/jira/browse/AMBARI-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22769: -- Assignee: Aravindan Vijayan > Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) > > > Key: AMBARI-22769 > URL: https://issues.apache.org/jira/browse/AMBARI-22769 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22769) Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work)
[ https://issues.apache.org/jira/browse/AMBARI-22769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22769: --- Issue Type: Task (was: Bug) > Point in Time Subsystem: Implement EMA Spark Streaming Driver (Initial work) > > > Key: AMBARI-22769 > URL: https://issues.apache.org/jira/browse/AMBARI-22769 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322711#comment-16322711
]
Hudson commented on AMBARI-22718:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #568 (See
[https://builds.apache.org/job/Ambari-branch-2.6/568/])
AMBARI-22718. ADDENDUM Cannot set security.inter.broker.protocol: (adoroszlai:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2e059c17f03f176e6210519545fe109e5c5944e9])
* (edit)
ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
[
https://issues.apache.org/jira/browse/AMBARI-22766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322701#comment-16322701
]
ASF GitHub Bot commented on AMBARI-22766:
-
hapylestat opened a new pull request #95: AMBARI-22766 ambari-server setup with
internal database may not work on centos 7 (dgrinenko)
URL: https://github.com/apache/ambari/pull/95
## What changes were proposed in this pull request?
Adding systemd handling support for internal database installation on
`service` package-less systems like CentOS7, RHEL7
cent 7 and rhel 7 installations and docker images could be shipped without
`service` package as it is not important after moving to `systemd` hypervisor.
Since that, `ambari-server setup` should support installation of internal
database on such systems
## How was this patch tested?
Manual ambari server installation with internal databse using `docker`
container `centos/systemd:latest` with executin base python UT:
```
[18:12:05]W: [Step 2/2] Total run:1211
[18:12:05]W: [Step 2/2] Total errors:0
[18:12:05]W: [Step 2/2] Total failures:0
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> ambari-server setup with internal database may not work on centos 7
> ---
>
> Key: AMBARI-22766
> URL: https://issues.apache.org/jira/browse/AMBARI-22766
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
>
> it may happened so, that centos7 image will not have "service" command at all.
> {code}
> Default properties detected. Using built-in database.
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Adjusting filesystem permissions
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Configuring ambari database...
> Checking PostgreSQL...
> INFO: about to run command: /usr/bin/env service postgresql status
> Running initdb: This may take up to a minute.
> INFO: about to run command: /usr/bin/postgresql-setup initdb
> About to start PostgreSQL
> INFO: about to run command: /usr/bin/env service postgresql status
> ERROR: Exiting with exit code 127.
> REASON: Unable to start PostgreSQL server. Exiting
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> [root@node-test0 /]# service postgresql status
> bash: service: command not found
> {code}
> *Background:*
> This caused due to centos 7 using systemd by default and switched to use of
> {{systemctl}} command instead of {{service}}. Since that, service command
> exist only in backward compatibility context and r optional. Currently
> optional package, which provides this package called {{initscripts}}
> Currently, everything ok r with standalone centos 7 image and it includes
> this package installed by default. However docker image centos/centos:7
> doesn't provide this package by default, and systemd enabled image
> centos/systemd:latest use {{systemctl}} without installed {{initscripts}}:
> https://github.com/CentOS/sig-cloud-instance-images/issues/28
> *Summary:*
> Due to {{service}} command going to be deprecated, we need consider to switch
> fully to {{systemctl}} replacement for systemd enabled images
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322573#comment-16322573 ] Aleksandr Kovalenko commented on AMBARI-22768: -- changing styles, no changes on js code, so no update for unit tests > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22768) Update Welcome page style
[
https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322567#comment-16322567
]
Hadoop QA commented on AMBARI-22768:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905708/AMBARI-22768.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12950//console
This message is automatically generated.
> Update Welcome page style
> -
>
> Key: AMBARI-22768
> URL: https://issues.apache.org/jira/browse/AMBARI-22768
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-22768.patch
>
>
> Update layout Welcome page on Admin View.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322563#comment-16322563 ] ASF GitHub Bot commented on AMBARI-22706: - aonishuk commented on issue #93: [AMBARI-22706] Ranger installation fails URL: https://github.com/apache/ambari/pull/93#issuecomment-356994269 Actually it gave me jenkins link for previous pull request. But anyway currently we have tests broken on feature branch. So failing jenkins is expected. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[
https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322556#comment-16322556
]
ASF GitHub Bot commented on AMBARI-22706:
-
aonishuk closed pull request #93: [AMBARI-22706] Ranger installation fails
URL: https://github.com/apache/ambari/pull/93
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
b/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
index 78692cba45b..e7289a2bb6d 100644
---
a/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
+++
b/ambari-common/src/main/python/resource_management/libraries/functions/setup_ranger_plugin_xml.py
@@ -256,13 +256,13 @@ def get_audit_configs(config):
xa_audit_db_name = default('/configurations/admin-properties/audit_db_name',
'ranger_audits')
if xa_audit_db_flavor == 'mysql':
-jdbc_jar_name = default("/hostLevelParams/custom_mysql_jdbc_name", None)
-previous_jdbc_jar_name =
default("/hostLevelParams/previous_custom_mysql_jdbc_name", None)
+jdbc_jar_name = default("/ambariLevelParams/custom_mysql_jdbc_name", None)
+previous_jdbc_jar_name =
default("/ambariLevelParams/previous_custom_mysql_jdbc_name", None)
audit_jdbc_url = format('jdbc:mysql://{xa_db_host}/{xa_audit_db_name}')
jdbc_driver = "com.mysql.jdbc.Driver"
elif xa_audit_db_flavor == 'oracle':
-jdbc_jar_name = default("/hostLevelParams/custom_oracle_jdbc_name", None)
-previous_jdbc_jar_name =
default("/hostLevelParams/previous_custom_oracle_jdbc_name", None)
+jdbc_jar_name = default("/ambariLevelParams/custom_oracle_jdbc_name", None)
+previous_jdbc_jar_name =
default("/ambariLevelParams/previous_custom_oracle_jdbc_name", None)
colon_count = xa_db_host.count(':')
if colon_count == 2 or colon_count == 0:
audit_jdbc_url = format('jdbc:oracle:thin:@{xa_db_host}')
@@ -270,18 +270,18 @@ def get_audit_configs(config):
audit_jdbc_url = format('jdbc:oracle:thin:@//{xa_db_host}')
jdbc_driver = "oracle.jdbc.OracleDriver"
elif xa_audit_db_flavor == 'postgres':
-jdbc_jar_name = default("/hostLevelParams/custom_postgres_jdbc_name", None)
-previous_jdbc_jar_name =
default("/hostLevelParams/previous_custom_postgres_jdbc_name", None)
+jdbc_jar_name = default("/ambariLevelParams/custom_postgres_jdbc_name",
None)
+previous_jdbc_jar_name =
default("/ambariLevelParams/previous_custom_postgres_jdbc_name", None)
audit_jdbc_url =
format('jdbc:postgresql://{xa_db_host}/{xa_audit_db_name}')
jdbc_driver = "org.postgresql.Driver"
elif xa_audit_db_flavor == 'mssql':
-jdbc_jar_name = default("/hostLevelParams/custom_mssql_jdbc_name", None)
-previous_jdbc_jar_name =
default("/hostLevelParams/previous_custom_mssql_jdbc_name", None)
+jdbc_jar_name = default("/ambariLevelParams/custom_mssql_jdbc_name", None)
+previous_jdbc_jar_name =
default("/ambariLevelParams/previous_custom_mssql_jdbc_name", None)
audit_jdbc_url =
format('jdbc:sqlserver://{xa_db_host};databaseName={xa_audit_db_name}')
jdbc_driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver"
elif xa_audit_db_flavor == 'sqla':
-jdbc_jar_name = default("/hostLevelParams/custom_sqlanywhere_jdbc_name",
None)
-previous_jdbc_jar_name =
default("/hostLevelParams/previous_custom_sqlanywhere_jdbc_name", None)
+jdbc_jar_name = default("/ambariLevelParams/custom_sqlanywhere_jdbc_name",
None)
+previous_jdbc_jar_name =
default("/ambariLevelParams/previous_custom_sqlanywhere_jdbc_name", None)
audit_jdbc_url =
format('jdbc:sqlanywhere:database={xa_audit_db_name};host={xa_db_host}')
jdbc_driver = "sap.jdbc4.sqlanywhere.IDriver"
else: raise Fail(format("'{xa_audit_db_flavor}' db flavor not supported."))
diff --git
a/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/params.py
b/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/params.py
index 49f73d78e45..5fe262a0101 100644
---
a/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/params.py
+++
b/ambari-server/src/main/resources/common-services/DRUID/0.10.1/package/scripts/params.py
@@ -111,7 +111,7 @@
metadata_storage_url =
config['configurations']['druid-common']['druid.metadata.storage.connector.connectURI']
jdk_location = config['ambariLevelParams']['jdk_location']
if 'mysql' == metadata_storage_type:
- jdbc_driver_jar = default("/hostLevelParams/custom_mysql_jdbc_name", None)
+ jdbc_driver_jar =
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322548#comment-16322548 ] ASF GitHub Bot commented on AMBARI-22706: - aonishuk commented on issue #93: [AMBARI-22706] Ranger installation fails URL: https://github.com/apache/ambari/pull/93#issuecomment-356991200 Jenkins here runs tests on trunk for some reason not branch-3.0-perf. Which doesn't even have the changes, ignoring it. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322549#comment-16322549 ] ASF GitHub Bot commented on AMBARI-22768: - aleksandrkovalenko opened a new pull request #94: AMBARI-22768. Update Welcome page style URL: https://github.com/apache/ambari/pull/94 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322537#comment-16322537 ] ASF GitHub Bot commented on AMBARI-22706: - aonishuk opened a new pull request #93: [AMBARI-22706] Ranger installation fails URL: https://github.com/apache/ambari/pull/93 ## What changes were proposed in this pull request? (Please fill in changes proposed in this fix) ## How was this patch tested? (Please explain how this patch was tested. Ex: unit tests, manual tests) (If this patch involves UI changes, please attach a screen-shot; otherwise, remove this) Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22768: - Status: Patch Available (was: Open) > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22768) Update Welcome page style
[ https://issues.apache.org/jira/browse/AMBARI-22768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22768: - Attachment: AMBARI-22768.patch > Update Welcome page style > - > > Key: AMBARI-22768 > URL: https://issues.apache.org/jira/browse/AMBARI-22768 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 3.0.0 > > Attachments: AMBARI-22768.patch > > > Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22706) Ranger installation fails
[
https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322518#comment-16322518
]
Hadoop QA commented on AMBARI-22706:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12903900/AMBARI-22706.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12949//console
This message is automatically generated.
> Ranger installation fails
> -
>
> Key: AMBARI-22706
> URL: https://issues.apache.org/jira/browse/AMBARI-22706
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22706.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22706: - Attachment: (was: AMBARI-22706.patch) > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22706) Ranger installation fails
[ https://issues.apache.org/jira/browse/AMBARI-22706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22706: - Attachment: AMBARI-22706.patch > Ranger installation fails > - > > Key: AMBARI-22706 > URL: https://issues.apache.org/jira/browse/AMBARI-22706 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22706.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22768) Update Welcome page style
Aleksandr Kovalenko created AMBARI-22768: Summary: Update Welcome page style Key: AMBARI-22768 URL: https://issues.apache.org/jira/browse/AMBARI-22768 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Update layout Welcome page on Admin View. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[ https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322447#comment-16322447 ] ASF GitHub Bot commented on AMBARI-22767: - hiveww opened a new pull request #92: AMBARI-22767. Kerberos wizard. Advanced kerberos-env password propert… URL: https://github.com/apache/ambari/pull/92 …ies should be visible only if the KDC type is 'Active Directory' (alexantonenko) ## What changes were proposed in this pull request? Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory" ## How was this patch tested? Unit tests for changing js files, manually Please review [Ambari Contributing Guide](https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute) before opening a pull request. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Kerberos wizard. Advanced kerberos-env password properties should be visible > only if the KDC type is "Active Directory" > > > Key: AMBARI-22767 > URL: https://issues.apache.org/jira/browse/AMBARI-22767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-22767.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322444#comment-16322444 ] ASF GitHub Bot commented on AMBARI-22763: - adoroszlai opened a new pull request #91: [AMBARI-22763] Fix unit test error in ambari-utility on branch-3.0-perf URL: https://github.com/apache/ambari/pull/91 ## What changes were proposed in this pull request? Unit test in `ambari-utility` runs into error due to `ClassNotFoundException: com.fasterxml.jackson.annotation.JsonInclude$Value`. This change fixes the errors. ## How was this patch tested? Ran unit tests. Before: ``` $ mvn -am -pl ambari-utility -Drat.skip -Dcheckstyle.skip clean test ... [ERROR] Tests run: 4, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.593 s <<< FAILURE! - in org.apache.ambari.swagger.AmbariSwaggerReaderTest [ERROR] swaggerBasicCase(org.apache.ambari.swagger.AmbariSwaggerReaderTest) Time elapsed: 0.221 s <<< ERROR! java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonInclude$Value at org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:68) Caused by: java.lang.ClassNotFoundException: com.fasterxml.jackson.annotation.JsonInclude$Value at org.apache.ambari.swagger.AmbariSwaggerReaderTest.swaggerBasicCase(AmbariSwaggerReaderTest.java:68) ... [ERROR] Tests run: 6, Failures: 0, Errors: 3, Skipped: 0 ``` After: ``` $ mvn -am -pl ambari-utility -Drat.skip -Dcheckstyle.skip clean test ... [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0 ``` This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix checkstyle failure after merging trunk to branch-3.0-perf > - > > Key: AMBARI-22763 > URL: https://issues.apache.org/jira/browse/AMBARI-22763 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22635) Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed
[ https://issues.apache.org/jira/browse/AMBARI-22635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322364#comment-16322364 ] ASF GitHub Bot commented on AMBARI-22635: - vishalsuvagia opened a new pull request #90: AMBARI-22635: Ambari should create a dummy core-site.xml for Ranger p… URL: https://github.com/apache/ambari/pull/90 AMBARI-22635: Ambari should create a dummy core-site.xml for Ranger plugins when namenode is not installed ## What changes were proposed in this pull request? For Ranger plugins to work properly in kerberised environments where HDFS is not installed. We need to create a core-site.xml for Storm and Kafka plugins so that the plugins can work to fetch latest policies from with kerberised calls from Ranger. The patch is committed on trunk branch, this pull request is for branch-2.6. ## How was this patch tested? Verified with installation on Cent-OS 6. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Ambari should create a dummy core-site.xml for Ranger plugins when namenode > is not installed > > > Key: AMBARI-22635 > URL: https://issues.apache.org/jira/browse/AMBARI-22635 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0, 2.6.1 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-22635-branch-2.6.1.patch, > AMBARI-22635-branch-2.6.2.patch, AMBARI-22635-branch-2.6.patch, > AMBARI-22635-trunk.1-addendum.patch, AMBARI-22635-trunk.1.patch, > AMBARI-22635-trunk.patch > > > For Ranger plugins to work properly in kerberised environments where HDFS is > not installed. We need to create a core-site.xml for Storm and Kafka plugins > so that the plugins can work to fetch latest policies from with kerberised > calls from Ranger. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[
https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322361#comment-16322361
]
Hadoop QA commented on AMBARI-22767:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905684/AMBARI-22767.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12948//console
This message is automatically generated.
> Kerberos wizard. Advanced kerberos-env password properties should be visible
> only if the KDC type is "Active Directory"
>
>
> Key: AMBARI-22767
> URL: https://issues.apache.org/jira/browse/AMBARI-22767
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22767.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[ https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22767: - Status: Patch Available (was: In Progress) > Kerberos wizard. Advanced kerberos-env password properties should be visible > only if the KDC type is "Active Directory" > > > Key: AMBARI-22767 > URL: https://issues.apache.org/jira/browse/AMBARI-22767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-22767.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[ https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22767: - Attachment: AMBARI-22767.patch > Kerberos wizard. Advanced kerberos-env password properties should be visible > only if the KDC type is "Active Directory" > > > Key: AMBARI-22767 > URL: https://issues.apache.org/jira/browse/AMBARI-22767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > Attachments: AMBARI-22767.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322265#comment-16322265
]
ASF GitHub Bot commented on AMBARI-22763:
-
adoroszlai commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r160968333
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getM_isPreInstalled() {
Review comment:
* does not fit naming convention
* method is unused
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[
https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322266#comment-16322266
]
ASF GitHub Bot commented on AMBARI-22763:
-
adoroszlai commented on a change in pull request #86: [AMBARI-22763] Fix
checkstyle failure after merging trunk to branch-3.0-perf
URL: https://github.com/apache/ambari/pull/86#discussion_r160968394
##
File path:
ambari-server/src/main/java/org/apache/ambari/server/agent/CommandRepository.java
##
@@ -234,6 +234,13 @@ public void setPreInstalled(String isPreInstalled) {
this.m_isPreInstalled = isPreInstalled.equalsIgnoreCase("true");
}
+public Boolean getM_isPreInstalled() {
+ return m_isPreInstalled;
+}
+
+public boolean isM_isScoped() {
Review comment:
* does not fit naming convention
* method is unused
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Fix checkstyle failure after merging trunk to branch-3.0-perf
> -
>
> Key: AMBARI-22763
> URL: https://issues.apache.org/jira/browse/AMBARI-22763
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
[ https://issues.apache.org/jira/browse/AMBARI-22767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-22767: Assignee: Antonenko Alexander > Kerberos wizard. Advanced kerberos-env password properties should be visible > only if the KDC type is "Active Directory" > > > Key: AMBARI-22767 > URL: https://issues.apache.org/jira/browse/AMBARI-22767 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22767) Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory"
Antonenko Alexander created AMBARI-22767: Summary: Kerberos wizard. Advanced kerberos-env password properties should be visible only if the KDC type is "Active Directory" Key: AMBARI-22767 URL: https://issues.apache.org/jira/browse/AMBARI-22767 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Antonenko Alexander Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[
https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322238#comment-16322238
]
Hadoop QA commented on AMBARI-22759:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905640/AMBARI-22759-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[contrib/views/hive20|https://builds.apache.org/job/Ambari-trunk-test-patch/12947//artifact/patch-work/testrun_hive20.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12947//console
This message is automatically generated.
> [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist
> in same Name
> -
>
> Key: AMBARI-22759
> URL: https://issues.apache.org/jira/browse/AMBARI-22759
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.5.2
> Environment: ambari 2.5.2
>Reporter: Akhil S Naik
> Labels: newbie, patch, usability
> Fix For: 3.0.0
>
> Attachments: AMBARI-22759-trunk.patch,
> hive_duplicate_saved_query_issue.png
>
>
> Reproduction scenario :
> Save some queries under same name .
> !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png!
> delete one of the saved query
> *hive views is deleting some other query randomly and the query i deleted
> still exists in saved query even after refresh of page.*
> Root Cause :
> After the Fix of AMBARI-19958, Hive views is querying the saved Queries with
> FilterBy queryId and server is responding mutiple queries as all the queries
> has same name,
> then Web client is deleting the first record from these savedQueries due to
> which this issue is happening.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322236#comment-16322236 ] Hudson commented on AMBARI-22764: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8590 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8590/]) [AMBARI-22764] NN HA wizard is broken due to recent commit for config (atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=417547afc6b455164c0fb72379992528501e993b]) * (edit) ambari-web/app/views/common/configs/service_configs_by_category_view.js * (edit) ambari-web/app/templates/common/configs/service_config.hbs > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[
https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322198#comment-16322198
]
Hadoop QA commented on AMBARI-22762:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905657/AMBARI-22762.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12946//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12946//console
This message is automatically generated.
> Can not stop one single flume agent when deployed on the same host
> --
>
> Key: AMBARI-22762
> URL: https://issues.apache.org/jira/browse/AMBARI-22762
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
> Environment: ambari 2.5.2,
> flume 1.8
>Reporter: mathildaMa09
> Attachments: AMBARI-22762.patch
>
>
> I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same
> host, once try stop agent, other agents stop also.
> notice: one agent named 'a', the other name 'b'
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22677) Don't call pprint.pformat unnecessarily in Ambari agent
[ https://issues.apache.org/jira/browse/AMBARI-22677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-22677. Resolution: Fixed > Don't call pprint.pformat unnecessarily in Ambari agent > --- > > Key: AMBARI-22677 > URL: https://issues.apache.org/jira/browse/AMBARI-22677 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > Attachments: AMBARI-22677-trunk.patch > > > The pprint.pformat is relatively slow and ambari agent calls it frequently > just to generate debug log. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22760) Infra Manager: install packages
[ https://issues.apache.org/jira/browse/AMBARI-22760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322183#comment-16322183 ] Hudson commented on AMBARI-22760: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8589 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8589/]) AMBARI-22760 Infra Manager: install packages (kasakrisz2: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=724637cb146696d9e7d4358b8779ea616fb73de4]) * (edit) ambari-infra/ambari-infra-manager/src/main/java/org/apache/ambari/infra/InfraManager.java * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infra-manager.properties * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infra-manager-env.sh * (edit) ambari-infra/ambari-infra-assembly/pom.xml * (add) ambari-infra/ambari-infra-assembly/src/main/package/rpm/manager/postremove.sh * (edit) ambari-infra/ambari-infra-manager/build.xml * (edit) ambari-infra/ambari-infra-assembly/src/main/package/rpm/manager/postinstall.sh * (edit) ambari-infra/ambari-infra-manager/src/main/resources/infraManager.sh * (edit) ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postinst * (edit) ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postrm * (edit) ambari-infra/ambari-infra-manager/pom.xml > Infra Manager: install packages > --- > > Key: AMBARI-22760 > URL: https://issues.apache.org/jira/browse/AMBARI-22760 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322177#comment-16322177
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12945//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322159#comment-16322159
]
ASF GitHub Bot commented on AMBARI-22764:
-
atkach closed pull request #87: [AMBARI-22764] NN HA wizard is broken due to
recent commit for config…
URL: https://github.com/apache/ambari/pull/87
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-web/app/templates/common/configs/service_config.hbs
b/ambari-web/app/templates/common/configs/service_config.hbs
index 34ac6029576..fe9706279ae 100644
--- a/ambari-web/app/templates/common/configs/service_config.hbs
+++ b/ambari-web/app/templates/common/configs/service_config.hbs
@@ -188,7 +188,7 @@
{{view App.SpinnerView}}
{{/if}}
-
+
diff --git
a/ambari-web/app/views/common/configs/service_configs_by_category_view.js
b/ambari-web/app/views/common/configs/service_configs_by_category_view.js
index 4726c612e1b..ffa4bfea738 100644
--- a/ambari-web/app/views/common/configs/service_configs_by_category_view.js
+++ b/ambari-web/app/views/common/configs/service_configs_by_category_view.js
@@ -189,7 +189,7 @@ App.ServiceConfigsByCategoryView =
Em.View.extend(App.Persist, App.ConfigOverrid
*/
isShowBlock: function () {
const isFilterEmpty = this.get('controller.filter') === '';
-const isFilterActive =
this.get('mainView.columns').someProperty('selected');
+const isFilterActive = this.get('mainView.columns') &&
this.get('mainView.columns').someProperty('selected');
const isCustomPropertiesCategory =
this.get('category.customCanAddProperty');
const isCompareMode = this.get('controller.isCompareMode');
const hasFilteredAdvancedConfigs =
this.get('categoryConfigs').filter(function (config) {
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22764: -- Resolution: Fixed Status: Resolved (was: Patch Available) > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22760) Infra Manager: install packages
[
https://issues.apache.org/jira/browse/AMBARI-22760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322147#comment-16322147
]
ASF GitHub Bot commented on AMBARI-22760:
-
oleewere closed pull request #85: AMBARI-22760 Infra Manager: install packages
URL: https://github.com/apache/ambari/pull/85
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/ambari-infra/ambari-infra-assembly/pom.xml
b/ambari-infra/ambari-infra-assembly/pom.xml
index bf0e6791d49..41fa5739c92 100644
--- a/ambari-infra/ambari-infra-assembly/pom.xml
+++ b/ambari-infra/ambari-infra-assembly/pom.xml
@@ -25,7 +25,7 @@
4.0.0
ambari-infra-assembly
- Ambari Infra Solr Assembly
+ Ambari Infra Assembly
http://maven.apache.org
@@ -41,7 +41,7 @@
ambari-infra-manager
${project.basedir}/../ambari-infra-manager
${mapping.base.path}/${infra-manager.package.name}
-
/etc/${infra-manager.package.name}/conf
+
${infra-manager.mapping.path}/conf
@@ -142,30 +142,16 @@
${project.basedir}/src/main/package/rpm/manager/postinstall.sh
utf-8
+
+
${project.basedir}/src/main/package/rpm/manager/postremove.sh
+utf-8
+
${infra-manager.mapping.path}
${infra-manager.dir}/target/package
-
-log4j.xml
-infra-manager.properties
-infra-manager-env.sh
-
-
-
-
-
- ${infra-manager.conf.mapping.path}
-
-
-
${infra-manager.dir}/target/package
-
-log4j.xml
-infra-manager.properties
-infra-manager-env.sh
-
@@ -354,23 +340,6 @@
root
${infra-manager.mapping.path}
-
-log4j.xml,infra-manager.properties,infra-manager-env.sh
-
-
-
- ${infra-manager.dir}/target/package
- directory
-
-${infra-manager.conf.mapping.path}
-perm
-root
-root
-644
-
-
-log4j.xml,infra-manager.properties,infra-manager-env.sh
-
diff --git
a/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postinst
b/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postinst
index c8d6ecd2042..acce62dd2cb 100644
--- a/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postinst
+++ b/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postinst
@@ -15,6 +15,13 @@
# limitations under the License
INFRA_MANAGER_LINK_NAME="/usr/bin/infra-manager"
-INFRA_MANAGER_SOURCE="/usr/lib/ambari-infra-manager/infraManager.sh"
+INFRA_MANAGER_SOURCE="/usr/lib/ambari-infra-manager/bin/infraManager.sh"
+INFRA_MANAGER_CONF_LINK_DIR="/etc/ambari-infra-manager"
+INFRA_MANAGER_CONF_LINK_NAME="$INFRA_MANAGER_CONF_LINK_DIR/conf"
+INFRA_MANAGER_CONF_SOURCE="/usr/lib/ambari-infra-manager/conf"
rm -f $INFRA_MANAGER_LINK_NAME ; ln -s $INFRA_MANAGER_SOURCE
$INFRA_MANAGER_LINK_NAME
+rm -f $INFRA_MANAGER_CONF_LINK_NAME
+rm -rf $INFRA_MANAGER_CONF_LINK_DIR
+mkdir -p $INFRA_MANAGER_CONF_LINK_DIR
+ln -s $INFRA_MANAGER_CONF_SOURCE $INFRA_MANAGER_CONF_LINK_NAME
diff --git
a/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postrm
b/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postrm
index 21a01faa534..e62abc6f2bc 100644
--- a/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postrm
+++ b/ambari-infra/ambari-infra-assembly/src/main/package/deb/manager/postrm
@@ -13,3 +13,11 @@
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License
+
[jira] [Commented] (AMBARI-22718) Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with Kerberos
[
https://issues.apache.org/jira/browse/AMBARI-22718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322148#comment-16322148
]
ASF GitHub Bot commented on AMBARI-22718:
-
adoroszlai opened a new pull request #88: [AMBARI-22718] Allow
security.inter.broker.protocol: SASL_SSL for all stack versions
URL: https://github.com/apache/ambari/pull/88
## What changes were proposed in this pull request?
This change removes the minimum stack version requirement for `SASL_SSL` in
Kafka.
8fce2a1741 added support for `security.inter.broker.protocol: SASL_SSL` in
Ambari, but only for stacks with the `KAFKA_EXTENDED_SASL_SUPPORT` flag. It
turned out that the flag is for other SASL features (eg. SASL/SCRAM, etc.), and
Kafka supports `SASL_SSL` in earlier versions, too.
This eliminates the need to manually tweak `stack_features.json`.
## How was this patch tested?
Installed kerberized HDP 2.4, 2.5 and 2.6 clusters via blueprints. Verified
that Kafka Brokers in all of these versions work fine with
`security.inter.broker.protocol: SASL_SSL`.
Existing unit tests pass:
```
Total run:1201
Total errors:0
Total failures:0
OK
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Cannot set security.inter.broker.protocol: SASL_SSL via Blueprint with
> Kerberos
> ---
>
> Key: AMBARI-22718
> URL: https://issues.apache.org/jira/browse/AMBARI-22718
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.1
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0, 2.6.2
>
> Attachments: AMBARI-22718.branch-2.6.patch, AMBARI-22718.trunk.patch
>
>
> STR:
> # Install Ambari 2.6.1
> # Tweak {{stack_features.json}} to lower {{min_version}} for
> {{kafka_extended_sasl_support}}
> # Create secure cluster via blueprint (ZooKeeper + Kafka) with
> {{security.inter.broker.protocol: SASL_SSL}}
> Result: Kafka Brokers stopped due to missing {{kafka_jaas.conf}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322146#comment-16322146
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12944//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22766) ambari-server setup with internal database may not work on centos 7
Dmytro Grinenko created AMBARI-22766:
Summary: ambari-server setup with internal database may not work
on centos 7
Key: AMBARI-22766
URL: https://issues.apache.org/jira/browse/AMBARI-22766
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: trunk
it may happened so, that centos7 image will not have "service" command at all.
{code}
Default properties detected. Using built-in database.
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Adjusting filesystem permissions
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
Configuring ambari database...
Checking PostgreSQL...
INFO: about to run command: /usr/bin/env service postgresql status
Running initdb: This may take up to a minute.
INFO: about to run command: /usr/bin/postgresql-setup initdb
About to start PostgreSQL
INFO: about to run command: /usr/bin/env service postgresql status
ERROR: Exiting with exit code 127.
REASON: Unable to start PostgreSQL server. Exiting
[root@node-test0 /]# service postgresql status
bash: service: command not found
[root@node-test0 /]# service postgresql status
bash: service: command not found
[root@node-test0 /]# service postgresql status
bash: service: command not found
[root@node-test0 /]# service postgresql status
bash: service: command not found
[root@node-test0 /]# service postgresql status
bash: service: command not found
{code}
*Background:*
This caused due to centos 7 using systemd by default and switched to use of
{{systemctl}} command instead of {{service}}. Since that, service command exist
only in backward compatibility context and r optional. Currently optional
package, which provides this package called {{initscripts}}
Currently, everything ok r with standalone centos 7 image and it includes this
package installed by default. However docker image centos/centos:7 doesn't
provide this package by default, and systemd enabled image
centos/systemd:latest use {{systemctl}} without installed {{initscripts}}:
https://github.com/CentOS/sig-cloud-instance-images/issues/28
*Summary:*
Due to {{service}} command going to be deprecated, we need consider to switch
fully to {{systemctl}} replacement for systemd enabled images
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[
https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322106#comment-16322106
]
Hadoop QA commented on AMBARI-22764:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12905665/AMBARI-22764.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12943//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12943//console
This message is automatically generated.
> NN HA wizard is broken due to recent commit for config compare
> --
>
> Key: AMBARI-22764
> URL: https://issues.apache.org/jira/browse/AMBARI-22764
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 3.0.0
>
> Attachments: AMBARI-22764.patch, log1.png, log2.png
>
>
> Save button on NN HA wizard step3 is disabled.
> Screenshots attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22765) Possible JSP problem solution?
Tulyakov Aleksander created AMBARI-22765:
Summary: Possible JSP problem solution?
Key: AMBARI-22765
URL: https://issues.apache.org/jira/browse/AMBARI-22765
Project: Ambari
Issue Type: Bug
Components: ambari-server, ambari-views
Affects Versions: 2.5.2, 2.6.1
Environment: 1) ubuntu 14.04, Ambari-2.5.2.0, HDP 2.6.2, jdk1.8.0_77
2) ubuntu 14.04, Ambari-2.6.1.0, HDP 2.6.4, jdk1.8.0_112
Reporter: Tulyakov Aleksander
When i opened "hello-spring-view" i have got exception similar to this:
https://issues.apache.org/jira/browse/AMBARI-18918
After many time googling, i found commit with change version of jsp library:
https://github.com/apache/ambari/commit/c03b6d4b01fbc336c296c9a1a92ca1308cba6ffc
I tried to fix it with change ambari-server/pom.xml
from
{code:xml}
org.mortbay.jetty
jsp-api-2.1-glassfish
org.mortbay.jetty
jsp-2.1-glassfish
{code}
to
{code:xml}
org.eclipse.jetty
jetty-jsp
${jetty.version}
{code}
After build branch-2.6 with changes all tests passed successfully.
Then i redeployed Ambari with fixes in second environment and example works
fine.
P.S. in first environment i just replace jars:
jsp-2.1-glassfish-2.1.v20100127.jar
jsp-api-2.1-glassfish-2.1.v20100127.jar
with:
com.sun.el-2.2.0.v20110806.jar
javax.el-2.2.0.v20110806.jar
javax.servlet.jsp-2.2.0.v201112011158.jar
javax.servlet.jsp.jstl-1.2.0.v201105211821.jar
jetty-jsp-8.1.19.v20160209.jar
org.apache.jasper.glassfish-2.2.2.v201112011158.jar
org.apache.taglibs.standard.glassfish-1.2.0.v201112081803.jar
org.eclipse.jdt.core-3.7.1.jar
and it fixed this problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22654) Kerberos: Kerberos-related tasks occur after INSTALL stage of services being added
[ https://issues.apache.org/jira/browse/AMBARI-22654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322097#comment-16322097 ] Maciej Sitarz commented on AMBARI-22654: Any progress or workaround for this issue? > Kerberos: Kerberos-related tasks occur after INSTALL stage of services being > added > -- > > Key: AMBARI-22654 > URL: https://issues.apache.org/jira/browse/AMBARI-22654 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.3, 2.5.2, 2.6.0 >Reporter: Maciej Sitarz >Assignee: Robert Levas >Priority: Critical > Attachments: SAMPLESRV2_v1.tgz, all_hosts.png, host1_master.png, > host2_master.png, host3_slave.png, host4_client.png, host5_slave_client.png > > > Kerberos-related configs (keytab,principal creation) are not applied before > INSTALL command is built on add service. > This occurs when new services and components are added to an existing cluster > where Kerberos is enabled. Due to the order Kerberos-related configurations > (keytabs, principals) will not be available for new services INSTALL step > functions. > This seems to be identical problem to the one mentioned in #AMBARI-17772 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322096#comment-16322096 ] ASF GitHub Bot commented on AMBARI-22764: - aBabiichuk commented on issue #87: [AMBARI-22764] NN HA wizard is broken due to recent commit for config… URL: https://github.com/apache/ambari/pull/87#issuecomment-356911862 LGTM This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22637) Fix misuses of os.path.dirname(path) in yarn.py
[ https://issues.apache.org/jira/browse/AMBARI-22637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322086#comment-16322086 ] Andrew Onischuk commented on AMBARI-22637: -- Hello [~ajisakaa] we have recently changed the process of contibuting to Ambari. Reviewboard and committing directly is no longer the way to do it. You have to create a pull request from you fork of ambari on github and let someone from committers (like me) to review and commit More details here: https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute > Fix misuses of os.path.dirname(path) in yarn.py > --- > > Key: AMBARI-22637 > URL: https://issues.apache.org/jira/browse/AMBARI-22637 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka > Fix For: 3.0.0 > > Attachments: AMBARI-22637.001.patch > > > As I written in AMBARI-22632, yarn.py wrongly sets 755 permission to > '/ats/done' and '/ats/active' by default. This is because the default value > of yarn.timeline-service.entity-group-fs-store.done-dir is '/ats/done/' and > the default value of yarn.timeline-service.entity-group-fs-store.active-dir > is '/ats/active/', and both of the default value have trailing '/'. > Next yarn.py sets 700 permission to the directories, so finally the > permissions become correct. > This issue causes redundant WebHDFS calls every time when launching ATS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22637) Fix misuses of os.path.dirname(path) in yarn.py
[ https://issues.apache.org/jira/browse/AMBARI-22637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322086#comment-16322086 ] Andrew Onischuk edited comment on AMBARI-22637 at 1/11/18 11:41 AM: Hello [~ajisakaa] we have recently changed the process of contibuting to Ambari. Reviewboard and committing directly is no longer the way to do it. You have to create a pull request from you fork of ambari on github and let someone from committers (like me) to review and merge the pull request in. More details here: https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute was (Author: aonishuk): Hello [~ajisakaa] we have recently changed the process of contibuting to Ambari. Reviewboard and committing directly is no longer the way to do it. You have to create a pull request from you fork of ambari on github and let someone from committers (like me) to review and commit More details here: https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute > Fix misuses of os.path.dirname(path) in yarn.py > --- > > Key: AMBARI-22637 > URL: https://issues.apache.org/jira/browse/AMBARI-22637 > Project: Ambari > Issue Type: Sub-task > Components: ambari-server >Reporter: Akira Ajisaka >Assignee: Akira Ajisaka > Fix For: 3.0.0 > > Attachments: AMBARI-22637.001.patch > > > As I written in AMBARI-22632, yarn.py wrongly sets 755 permission to > '/ats/done' and '/ats/active' by default. This is because the default value > of yarn.timeline-service.entity-group-fs-store.done-dir is '/ats/done/' and > the default value of yarn.timeline-service.entity-group-fs-store.active-dir > is '/ats/active/', and both of the default value have trailing '/'. > Next yarn.py sets 700 permission to the directories, so finally the > permissions become correct. > This issue causes redundant WebHDFS calls every time when launching ATS. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322084#comment-16322084 ] ASF GitHub Bot commented on AMBARI-22764: - atkach opened a new pull request #87: [AMBARI-22764] NN HA wizard is broken due to recent commit for config… URL: https://github.com/apache/ambari/pull/87 ## How was this patch tested? 21417 passing (27s) 50 pending This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22764: -- Attachment: AMBARI-22764.patch > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22764: -- Status: Patch Available (was: In Progress) > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: AMBARI-22764.patch, log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
[ https://issues.apache.org/jira/browse/AMBARI-22764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-22764: -- Attachment: log2.png log1.png > NN HA wizard is broken due to recent commit for config compare > -- > > Key: AMBARI-22764 > URL: https://issues.apache.org/jira/browse/AMBARI-22764 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 3.0.0 > > Attachments: log1.png, log2.png > > > Save button on NN HA wizard step3 is disabled. > Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22764) NN HA wizard is broken due to recent commit for config compare
Andrii Tkach created AMBARI-22764: - Summary: NN HA wizard is broken due to recent commit for config compare Key: AMBARI-22764 URL: https://issues.apache.org/jira/browse/AMBARI-22764 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 3.0.0 Save button on NN HA wizard step3 is disabled. Screenshots attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22625) Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different
[ https://issues.apache.org/jira/browse/AMBARI-22625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22625: -- Fix Version/s: (was: 2.6.0) 3.0.0 > Non DFS Used from HDFS Namenode UI and HDFS summary in Ambari is different > --- > > Key: AMBARI-22625 > URL: https://issues.apache.org/jira/browse/AMBARI-22625 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-22625-trunk.patch, ambari-2.png, namenode.png > > > 'NON DFS Used' value in Services -> HDFS -> Summary if different from the > Value shown in NameNode UI (see Picture). > in NAMENODE UI --> > !https://issues.apache.org/jira/secure/attachment/12901501/namenode.png! > In Services -> HDFS -> Summary > !https://issues.apache.org/jira/secure/attachment/12901499/ambari-2.png! > In NameNode UI the Non DFS Used is taken from 'NonDfsUsedSpace' variable from > REST API call : > http://host1:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeInfo > Where host1 is the Name Node Server FQDN > but in Ambari we are calculating the same value from (Total Allocated - DFS > USed - DFS Remaining) . > due to which this issue is happening. > as a Fix we need to use the 'capacityNonDfsUsed' which comes from Server in > NameNode metrics > 'FSNamesystem > CapacityNonDFSUsed' > attached the patch in the JIRA. > Please fix this bug -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
[ https://issues.apache.org/jira/browse/AMBARI-22763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322028#comment-16322028 ] ASF GitHub Bot commented on AMBARI-22763: - mpapirkovskyy opened a new pull request #86: [AMBARI-22763] Fix checkstyle failure after merging trunk to branch-3.0-perf URL: https://github.com/apache/ambari/pull/86 ## What changes were proposed in this pull request? Fix for various merge mistakes, especially checkstyle failure ## How was this patch tested? manual check This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Fix checkstyle failure after merging trunk to branch-3.0-perf > - > > Key: AMBARI-22763 > URL: https://issues.apache.org/jira/browse/AMBARI-22763 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22763) Fix checkstyle failure after merging trunk to branch-3.0-perf
Myroslav Papirkovskyi created AMBARI-22763: -- Summary: Fix checkstyle failure after merging trunk to branch-3.0-perf Key: AMBARI-22763 URL: https://issues.apache.org/jira/browse/AMBARI-22763 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22762: -- Status: Patch Available (was: Open) > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322006#comment-16322006 ] mathildaMa09 commented on AMBARI-22762: --- For flume agent a, Ambari send cmd ‘pgrep -o -u flume -f '^/user/lib/jvm/java.*a.* ’ to get pid, for agent b , send ‘pgrep -o -u flume -f '^/user/lib/jvm/java.*b.* ’. but these two cmd returns same pid, thus when stop one of them, the other stops as well. Sometime, 'pgrep -f ' cannot get real full command because flume command is too long to retrieve, so send 'ps' command instead. > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22762: -- Attachment: (was: 823663828502415422.jpg) > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
[ https://issues.apache.org/jira/browse/AMBARI-22762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mathildaMa09 updated AMBARI-22762: -- Attachment: AMBARI-22762.patch > Can not stop one single flume agent when deployed on the same host > -- > > Key: AMBARI-22762 > URL: https://issues.apache.org/jira/browse/AMBARI-22762 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 > Environment: ambari 2.5.2, > flume 1.8 >Reporter: mathildaMa09 > Attachments: AMBARI-22762.patch > > > I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same > host, once try stop agent, other agents stop also. > notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22762) Can not stop one single flume agent when deployed on the same host
mathildaMa09 created AMBARI-22762: - Summary: Can not stop one single flume agent when deployed on the same host Key: AMBARI-22762 URL: https://issues.apache.org/jira/browse/AMBARI-22762 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.2 Environment: ambari 2.5.2, flume 1.8 Reporter: mathildaMa09 Attachments: 823663828502415422.jpg I'm using ambari 2.5.2, flume 1.8, when i install one more agents on same host, once try stop agent, other agents stop also. notice: one agent named 'a', the other name 'b' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22761) Unexpected behavior on 'Right Click + Open link in new tab' on slave node under Ambari UI's Hosts tab
[ https://issues.apache.org/jira/browse/AMBARI-22761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valencia Edna Serrao updated AMBARI-22761: -- Description: Under Host tab, we see a listing of the cluster nodes, along with the master and slave nodes. However, I have observed that if we 'Right click + Open link in new tab' on the slave nodes, the master dashboard is displayed instead of the slave node details. This behavior is unexpected and misleading. It would be good if we can show the relevant slave node details once user does a 'Right Click + Open link in new tab' on the slave node also. was: Under Host tab, we see a listing of the cluster nodes, along with the master and slave nodes. However, I have observed that if we 'Right click + Open link in new tab' on the slave nodes, the master dashboard is displayed instead of the slave node details. This behavior is unexpected and misleading. It would be good if we can show the relevant slave node details once user does a 'Right Click + Open link in new tab' on the slave node. > Unexpected behavior on 'Right Click + Open link in new tab' on slave node > under Ambari UI's Hosts tab > -- > > Key: AMBARI-22761 > URL: https://issues.apache.org/jira/browse/AMBARI-22761 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 > Environment: Chrome Browser >Reporter: Valencia Edna Serrao >Priority: Minor > Labels: features, usability > > Under Host tab, we see a listing of the cluster nodes, along with the master > and slave nodes. However, I have observed that if we 'Right click + Open link > in new tab' on the slave nodes, the master dashboard is displayed instead of > the slave node details. This behavior is unexpected and misleading. > It would be good if we can show the relevant slave node details once user > does a 'Right Click + Open link in new tab' on the slave node also. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22760) Infra Manager: install packages
[ https://issues.apache.org/jira/browse/AMBARI-22760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-22760: Status: Patch Available (was: Open) > Infra Manager: install packages > --- > > Key: AMBARI-22760 > URL: https://issues.apache.org/jira/browse/AMBARI-22760 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22760) Infra Manager: install packages
[ https://issues.apache.org/jira/browse/AMBARI-22760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321970#comment-16321970 ] ASF GitHub Bot commented on AMBARI-22760: - kasakrisz opened a new pull request #85: AMBARI-22760 Infra Manager: install packages URL: https://github.com/apache/ambari/pull/85 ## What changes were proposed in this pull request? - package content split to three folders: bin, conf, lib - creating links during install: /usr/bin/infra-manager and /etc/ambari-infra-manager-conf - shell script for starting stopping and getting the status of infra manager ## How was this patch tested? manual testing using vagrant and yum checking the content of ambari-infra-manager.deb @oleewere @swagle @zeroflag This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Infra Manager: install packages > --- > > Key: AMBARI-22760 > URL: https://issues.apache.org/jira/browse/AMBARI-22760 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22761) Unexpected behavior on 'Right Click + Open link in new tab' on slave node under Ambari UI's Hosts tab
Valencia Edna Serrao created AMBARI-22761: - Summary: Unexpected behavior on 'Right Click + Open link in new tab' on slave node under Ambari UI's Hosts tab Key: AMBARI-22761 URL: https://issues.apache.org/jira/browse/AMBARI-22761 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.0 Environment: Chrome Browser Reporter: Valencia Edna Serrao Priority: Minor Under Host tab, we see a listing of the cluster nodes, along with the master and slave nodes. However, I have observed that if we 'Right click + Open link in new tab' on the slave nodes, the master dashboard is displayed instead of the slave node details. This behavior is unexpected and misleading. It would be good if we can show the relevant slave node details once user does a 'Right Click + Open link in new tab' on the slave node. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22759: -- Summary: [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name (was: [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name) > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Labels: newbie, patch, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22760) Infra Manager: install packages
Krisztian Kasa created AMBARI-22760: --- Summary: Infra Manager: install packages Key: AMBARI-22760 URL: https://issues.apache.org/jira/browse/AMBARI-22760 Project: Ambari Issue Type: Improvement Components: ambari-infra Affects Versions: 3.0.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22759: -- Labels: newbie patch usability (was: ) Fix Version/s: 3.0.0 Status: Patch Available (was: Open) > [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Labels: patch, newbie, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22759: -- Attachment: AMBARI-22759-trunk.patch > [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Labels: newbie, patch, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16321891#comment-16321891 ] Akhil S Naik commented on AMBARI-22759: --- Attached the Fix of the issue. web client will seek for the record from the saved-query's using the id and will delete the record and reload the table. Tested and working fine in latest ambari . > [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Attachments: hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22759: -- Description: Reproduction scenario : Save some queries under same name . !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! delete one of the saved query *hive views is deleting some other query randomly and the query i deleted still exists in saved query even after refresh of page.* Root Cause : After the Fix of AMBARI-19958, Hive views is querying the saved Queries with FilterBy queryId and server is responding mutiple queries as all the queries has same name, then Web client is deleting the first record from these savedQueries due to which this issue is happening. was: Reproduction scenario : Save some queries under same name . !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! delete one of the saved query *hive views is deleting some other query randomly and the query i deleted still exists in saved query even after refresh of page.* Root Cause : After the Fix of AMBARI-19958, Hive views is querying the saved Queries with FilterBy queryId and server is responding mutiple queries as all the queries has same name, then Web client is deleting the first record of the savedQueries due to which this issue is happening. > [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Attachments: hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22759: -- Description: Reproduction scenario : Save some queries under same name . !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! delete one of the saved query *hive views is deleting some other query randomly and the query i deleted still exists in saved query even after refresh of page.* Root Cause : After the Fix of AMBARI-19958, Hive views is querying the saved Queries with FilterBy queryId and server is responding mutiple queries as all the queries has same name, then Web client is deleting the first record of the savedQueries due to which this issue is happening. was: Reproduction scenario : Save some queries under same name . !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! delete one of the saved query *hive views is deleting some other query randomly and the query i deleted still exists in saved query even after refresh of page.* Root Cause : After the Fix of AMBARI-19958[https://issues.apache.org/jira/browse/AMBARI-19958] , Hive views is querying the saved Queries with FilterBy queryId and server is responding mutiple queries as all the queries has same name, then Web client is deleting the first record of the savedQueries due to which this issue is happening. > [Hive Views 2.0] Deleting a Saved query is Buddy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik > Attachments: hive_duplicate_saved_query_issue.png > > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record of the savedQueries due to which > this issue is happening. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
