[jira] [Commented] (AMBARI-24317) Lowercase g characters in the left-hand nav are getting slightly clipped bottom-up making them look like lowercase q's
[ https://issues.apache.org/jira/browse/AMBARI-24317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553613#comment-16553613 ] Hudson commented on AMBARI-24317: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #61 (See [https://builds.apache.org/job/Ambari-branch-2.7/61/]) AMBARI-24317. Lowercase g characters in the left-hand nav are getting (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9cd2457aa33a02dc4ae1463f8920a6edb1d78978]) * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css > Lowercase g characters in the left-hand nav are getting slightly clipped > bottom-up making them look like lowercase q's > -- > > Key: AMBARI-24317 > URL: https://issues.apache.org/jira/browse/AMBARI-24317 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > We need to make sure the service names have enough vertical padding or ensure > that they don't get clipped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24317) Lowercase g characters in the left-hand nav are getting slightly clipped bottom-up making them look like lowercase q's
[ https://issues.apache.org/jira/browse/AMBARI-24317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553588#comment-16553588 ] Hudson commented on AMBARI-24317: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9669 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9669/]) AMBARI-24317. Clicking on password warnings doesn't update the service (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1b32b2972a8422e7b0f69ee04843e7e15d8dfbb0]) * (edit) ambari-web/app/styles/theme/bootstrap-ambari.css > Lowercase g characters in the left-hand nav are getting slightly clipped > bottom-up making them look like lowercase q's > -- > > Key: AMBARI-24317 > URL: https://issues.apache.org/jira/browse/AMBARI-24317 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > We need to make sure the service names have enough vertical padding or ensure > that they don't get clipped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24342) PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for service.
[
https://issues.apache.org/jira/browse/AMBARI-24342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24342:
Labels: pull-request-available (was: )
> PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for
> service.
> -
>
> Key: AMBARI-24342
> URL: https://issues.apache.org/jira/browse/AMBARI-24342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> *ISSUE:*
> Post Trunk merge, deploy fails at Step 7.
> *Console O/P:*
> {code:java}
> app.js:67915 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.updateAttributesFromTheme
> (http://172.22.107.63:8080/javascripts/app.js:67915:90)
> at http://172.22.107.63:8080/javascripts/app.js:44914:21
> at Array.forEach (native)
> at Class.updateConfigAttributesFromThemes
> (http://172.22.107.63:8080/javascripts/app.js:44913:41)
> at Class.applyServicesConfigs
> (http://172.22.107.63:8080/javascripts/app.js:43405:10)
> at Class.loadStep (http://172.22.107.63:8080/javascripts/app.js:43345:12)
> at Class.willInsertElement
> (http://172.22.107.63:8080/javascripts/app.js:249561:30)
> at Class.newFunc [as willInsertElement]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> at Class.trigger
> (http://172.22.107.63:8080/javascripts/vendor.js:25526:21)
> at Class.newFunc [as trigger]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> {code}
> Code line:
> {code:java}
> updateAttributesFromTheme: function updateAttributesFromTheme(serviceName) {
> this.prepareSectionsConfigProperties(serviceName);
> var serviceConfigs = this.get('stepConfigs').findProperty('serviceName',
> serviceName).get('configs'), <-- Issue LINE
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24342) PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for service.
Ishan Bhatt created AMBARI-24342:
Summary: PostTrunkMerge : UI issue at Step 7 of deploy, while
getting configs for service.
Key: AMBARI-24342
URL: https://issues.apache.org/jira/browse/AMBARI-24342
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 3.0.0
*ISSUE:*
Post Trunk merge, deploy fails at Step 7.
*Console O/P:*
{code:java}
app.js:67915 Uncaught TypeError: Cannot read property 'get' of undefined
at Class.updateAttributesFromTheme
(http://172.22.107.63:8080/javascripts/app.js:67915:90)
at http://172.22.107.63:8080/javascripts/app.js:44914:21
at Array.forEach (native)
at Class.updateConfigAttributesFromThemes
(http://172.22.107.63:8080/javascripts/app.js:44913:41)
at Class.applyServicesConfigs
(http://172.22.107.63:8080/javascripts/app.js:43405:10)
at Class.loadStep (http://172.22.107.63:8080/javascripts/app.js:43345:12)
at Class.willInsertElement
(http://172.22.107.63:8080/javascripts/app.js:249561:30)
at Class.newFunc [as willInsertElement]
(http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
at Class.trigger (http://172.22.107.63:8080/javascripts/vendor.js:25526:21)
at Class.newFunc [as trigger]
(http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
{code}
Code line:
{code:java}
updateAttributesFromTheme: function updateAttributesFromTheme(serviceName) {
this.prepareSectionsConfigProperties(serviceName);
var serviceConfigs = this.get('stepConfigs').findProperty('serviceName',
serviceName).get('configs'), <-- Issue LINE
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar reassigned AMBARI-24341:
Assignee: Ishan Bhatt (was: Swapan Shridhar)
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Ishan Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> UI Service Config page hangs when clicked post deploy.
> Below is the calls made:
> -
> http://172.27.56.18:8080/api/v1/clusters/cl1?fields=Clusters/desired_configs&_=1532384868506
>
> which succeeds.
> !Screen Shot 2018-07-23 at 3.29.26 PM.png! !Screen Shot 2018-07-23 at
> 3.29.42 PM.png!
> And then the UI code fails :
> {code}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
> at *line 6* while processing the response:
> {code}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24341:
-
Description:
*ISSUE:*
UI Service Config page hangs when clicked post deploy.
Below is the calls made:
-
http://172.27.56.18:8080/api/v1/clusters/cl1?fields=Clusters/desired_configs&_=1532384868506
which succeeds.
!Screen Shot 2018-07-23 at 3.29.26 PM.png! !Screen Shot 2018-07-23 at 3.29.42
PM.png!
And then the UI code fails :
{code}
app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
at Class. (app.js:1898)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{code}
at *line 6* while processing the response:
{code}
1 loadConfigProperties: function loadConfigProperties() {
2var self = this;
3
App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
() {
4 App.config.loadClusterConfigsFromStack().always(function () {
5
App.router.get('configurationController').updateConfigTags().always(function ()
{
6
App.router.get('updateController').updateClusterEnv().always(function () {
7self.set('isConfigsPropertiesLoaded', true);
8 });
});
});
});
},
{code}
.
was:
*ISSUE:*
Post Trunk merge, Host API call breaks.
API call:
http://172.27.25.196:8080/api/v1/clusters/cl1/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/host_state,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/display_name,host_components/HostRoles/desired_admin_state,host_components/metrics/dfs/namenode/ClusterId,host_components/metrics/dfs/FSNamesystem/HAState,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name&minimal_response=true,host_components/logging&page_size=10&from=0&sortBy=Hosts/host_name.asc&_=1532118655459
Response:
{code}
{
"status" : 400,
"message" : "The properties
[stack_versions/repository_versions/RepositoryVersions/repository_version,
stack_versions/HostStackVersions,
stack_versions/repository_versions/RepositoryVersions/display_name,
stack_versions/repository_versions/RepositoryVersions/id] specified in the
request or predicate are not supported for the resource type Host."
}
{code}
!Screen Shot 2018-07-20 at 1.32.48 PM.png!
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> UI Service Config page hangs when clicked post deploy.
> Below is the calls made:
> -
> http://172.27.56.18:8080/api/v1/clusters/cl1?fields=Clusters/desired_configs&_=1532384868506
>
> which succeeds.
> !Screen Shot 2018-07-23 at 3.29.26 PM.png! !Screen Shot 2018-07-23 at
> 3.29.42 PM.png!
> And then the UI code fails :
> {code}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
> at *line 6* while processing the response:
> {code}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24341:
-
Attachment: Screen Shot 2018-07-23 at 3.29.42 PM.png
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> Post Trunk merge, Host API call breaks.
> API call:
> http://172.27.25.196:8080/api/v1/clusters/cl1/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/host_state,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/display_name,host_components/HostRoles/desired_admin_state,host_components/metrics/dfs/namenode/ClusterId,host_components/metrics/dfs/FSNamesystem/HAState,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name&minimal_response=true,host_components/logging&page_size=10&from=0&sortBy=Hosts/host_name.asc&_=1532118655459
> Response:
> {code}
> {
> "status" : 400,
> "message" : "The properties
> [stack_versions/repository_versions/RepositoryVersions/repository_version,
> stack_versions/HostStackVersions,
> stack_versions/repository_versions/RepositoryVersions/display_name,
> stack_versions/repository_versions/RepositoryVersions/id] specified in the
> request or predicate are not supported for the resource type Host."
> }
> {code}
> !Screen Shot 2018-07-20 at 1.32.48 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24341:
-
Attachment: Screen Shot 2018-07-23 at 3.29.26 PM.png
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> Post Trunk merge, Host API call breaks.
> API call:
> http://172.27.25.196:8080/api/v1/clusters/cl1/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/host_state,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/display_name,host_components/HostRoles/desired_admin_state,host_components/metrics/dfs/namenode/ClusterId,host_components/metrics/dfs/FSNamesystem/HAState,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name&minimal_response=true,host_components/logging&page_size=10&from=0&sortBy=Hosts/host_name.asc&_=1532118655459
> Response:
> {code}
> {
> "status" : 400,
> "message" : "The properties
> [stack_versions/repository_versions/RepositoryVersions/repository_version,
> stack_versions/HostStackVersions,
> stack_versions/repository_versions/RepositoryVersions/display_name,
> stack_versions/repository_versions/RepositoryVersions/id] specified in the
> request or predicate are not supported for the resource type Host."
> }
> {code}
> !Screen Shot 2018-07-20 at 1.32.48 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24341:
-
Labels: (was: pull-request-available)
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
>
> *ISSUE:*
> Post Trunk merge, Host API call breaks.
> API call:
> http://172.27.25.196:8080/api/v1/clusters/cl1/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/host_state,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/display_name,host_components/HostRoles/desired_admin_state,host_components/metrics/dfs/namenode/ClusterId,host_components/metrics/dfs/FSNamesystem/HAState,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name&minimal_response=true,host_components/logging&page_size=10&from=0&sortBy=Hosts/host_name.asc&_=1532118655459
> Response:
> {code}
> {
> "status" : 400,
> "message" : "The properties
> [stack_versions/repository_versions/RepositoryVersions/repository_version,
> stack_versions/HostStackVersions,
> stack_versions/repository_versions/RepositoryVersions/display_name,
> stack_versions/repository_versions/RepositoryVersions/id] specified in the
> request or predicate are not supported for the resource type Host."
> }
> {code}
> !Screen Shot 2018-07-20 at 1.32.48 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24341) UI service configs page hangs.
Swapan Shridhar created AMBARI-24341:
Summary: UI service configs page hangs.
Key: AMBARI-24341
URL: https://issues.apache.org/jira/browse/AMBARI-24341
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Swapan Shridhar
Assignee: Swapan Shridhar
Fix For: 3.0.0
*ISSUE:*
Post Trunk merge, Host API call breaks.
API call:
http://172.27.25.196:8080/api/v1/clusters/cl1/hosts?fields=Hosts/rack_info,Hosts/host_name,Hosts/maintenance_state,Hosts/public_host_name,Hosts/cpu_count,Hosts/ph_cpu_count,alerts_summary,Hosts/host_status,Hosts/host_state,Hosts/last_heartbeat_time,Hosts/ip,host_components/HostRoles/state,host_components/HostRoles/maintenance_state,host_components/HostRoles/stale_configs,host_components/HostRoles/service_name,host_components/HostRoles/display_name,host_components/HostRoles/desired_admin_state,host_components/metrics/dfs/namenode/ClusterId,host_components/metrics/dfs/FSNamesystem/HAState,Hosts/total_mem,stack_versions/HostStackVersions,stack_versions/repository_versions/RepositoryVersions/repository_version,stack_versions/repository_versions/RepositoryVersions/id,stack_versions/repository_versions/RepositoryVersions/display_name&minimal_response=true,host_components/logging&page_size=10&from=0&sortBy=Hosts/host_name.asc&_=1532118655459
Response:
{code}
{
"status" : 400,
"message" : "The properties
[stack_versions/repository_versions/RepositoryVersions/repository_version,
stack_versions/HostStackVersions,
stack_versions/repository_versions/RepositoryVersions/display_name,
stack_versions/repository_versions/RepositoryVersions/id] specified in the
request or predicate are not supported for the resource type Host."
}
{code}
!Screen Shot 2018-07-20 at 1.32.48 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24333) User is able to set the same short URLs for different view instances
[
https://issues.apache.org/jira/browse/AMBARI-24333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553258#comment-16553258
]
Hudson commented on AMBARI-24333:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9668 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9668/])
[AMBARI-24333] Raising an error when user is trying to create a view URL
(github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e374842ba7a9dda0a44c274dba77fbb9bd59efa1])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewURLResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ViewURLDAO.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewURLResourceProvider.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewURLEntity.java
> User is able to set the same short URLs for different view instances
>
>
> Key: AMBARI-24333
> URL: https://issues.apache.org/jira/browse/AMBARI-24333
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> *STR*
> # Let's say the user has CAPACITY-SCHEDULER view instance with
> {{/main/view/CAPACITY-SCHEDULER/auto_cs_instance}} short URL set
> # Clone this instance or create another CAPACITY-SCHEDULER instance manually
> # Set the same short URL as for the first instance
> *Result*
> - If 'Name' property is the same, request for adding new URL fails
> request:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response:
> {noformat}
> {
> "status" : 500,
> "message" : "An internal system exception occurred: This view URL name
> exists, URL names should be unique"
> }
> {noformat}
> - If name is different, the REST call succeeds even if URL itself is
> duplicate:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance1
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance1",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response is 201 in this case; URL is created
> - As result there are two view instances with the same URL, and the first
> one is no longer accessible by this URL
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24340) AMS Migration tools should auto-detect whitelist file
[
https://issues.apache.org/jira/browse/AMBARI-24340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24340:
Labels: pull-request-available (was: )
> AMS Migration tools should auto-detect whitelist file
> -
>
> Key: AMBARI-24340
> URL: https://issues.apache.org/jira/browse/AMBARI-24340
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
> upgrade, running the following command with no arguments fails:
> {noformat}
> # /usr/sbin/ambari-metrics-collector upgrade_start
> {noformat}
> This is the error in the logs:
> {noformat}
> 2018-07-12 13:47:05,373 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 9504, metadata objects from store.
> 2018-07-12 13:47:05,517 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 5 host objects from store.
> 2018-07-12 13:47:05,528 INFO
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Looking for whitelisted metric names...
> 2018-07-12 13:47:05,529 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> No whitelisted metrics specified. Exiting...
> 2018-07-12 13:47:05,530 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Exception during system setup, exiting...
> java.lang.Exception: List of whitelisted metrics must be provided
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24340) AMS Migration tools should auto-detect whitelist file
[
https://issues.apache.org/jira/browse/AMBARI-24340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-24340:
---
Summary: AMS Migration tools should auto-detect whitelist file (was: AMS
Migration tools should auto-detect whitelisting)
> AMS Migration tools should auto-detect whitelist file
> -
>
> Key: AMBARI-24340
> URL: https://issues.apache.org/jira/browse/AMBARI-24340
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.7.1
>
>
> In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
> upgrade, running the following command with no arguments fails:
> {noformat}
> # /usr/sbin/ambari-metrics-collector upgrade_start
> {noformat}
> This is the error in the logs:
> {noformat}
> 2018-07-12 13:47:05,373 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 9504, metadata objects from store.
> 2018-07-12 13:47:05,517 INFO
> org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
> Retrieved 5 host objects from store.
> 2018-07-12 13:47:05,528 INFO
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Looking for whitelisted metric names...
> 2018-07-12 13:47:05,529 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> No whitelisted metrics specified. Exiting...
> 2018-07-12 13:47:05,530 ERROR
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
> Exception during system setup, exiting...
> java.lang.Exception: List of whitelisted metrics must be provided
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
> at
> org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24340) AMS Migration tools should auto-detect whitelisting
Aravindan Vijayan created AMBARI-24340:
--
Summary: AMS Migration tools should auto-detect whitelisting
Key: AMBARI-24340
URL: https://issues.apache.org/jira/browse/AMBARI-24340
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.1
In a default Ambari 2.7 cluster that has just completed HDP 2.6 to HDP 3.0
upgrade, running the following command with no arguments fails:
{noformat}
# /usr/sbin/ambari-metrics-collector upgrade_start
{noformat}
This is the error in the logs:
{noformat}
2018-07-12 13:47:05,373 INFO
org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
Retrieved 9504, metadata objects from store.
2018-07-12 13:47:05,517 INFO
org.apache.ambari.metrics.core.timeline.discovery.TimelineMetricMetadataManager:
Retrieved 5 host objects from store.
2018-07-12 13:47:05,528 INFO
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
Looking for whitelisted metric names...
2018-07-12 13:47:05,529 ERROR
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
No whitelisted metrics specified. Exiting...
2018-07-12 13:47:05,530 ERROR
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher:
Exception during system setup, exiting...
java.lang.Exception: List of whitelisted metrics must be provided
at
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.(MetricsDataMigrationLauncher.java:113)
at
org.apache.ambari.metrics.core.timeline.upgrade.core.MetricsDataMigrationLauncher.main(MetricsDataMigrationLauncher.java:303)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24319) Multiple alerts after HDFS service only regenerate keytabs, as keytabs are out of sync
[ https://issues.apache.org/jira/browse/AMBARI-24319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553076#comment-16553076 ] Hudson commented on AMBARI-24319: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9667 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9667/]) AMBARI-24319. Regenerating keytabs for the given service(s) only (#1833) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=57b7d5adc6bcf7683363f3431c446a092876ea07]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/KerberosServerAction.java > Multiple alerts after HDFS service only regenerate keytabs, as keytabs are > out of sync > -- > > Key: AMBARI-24319 > URL: https://issues.apache.org/jira/browse/AMBARI-24319 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > *STR* > # Install Ambari 2.7.0 > # Deploy a cluster with some services > # Execute to HDFS / Actions / Regenerate Keytabs > # Restart all required components > *Result* > Multiple alerts have been shown saying they receive 403 when trying to > connect to different web UIs > *Expected result* > No alerts; everything should work as expected -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24270) Agent Status Command Are Randomly Failing With Empty stderr
[ https://issues.apache.org/jira/browse/AMBARI-24270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553075#comment-16553075 ] Hudson commented on AMBARI-24270: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9667 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9667/]) AMBARI-24270. Agent Status Command Are Randomly Failing With Empty (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5ecf5e8c4ecbd1cbd21699e53e27786729df8dbb]) * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py > Agent Status Command Are Randomly Failing With Empty stderr > --- > > Key: AMBARI-24270 > URL: https://issues.apache.org/jira/browse/AMBARI-24270 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch > > Time Spent: 4h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24291) Start All Services on 100-nodes cluster timed out after 1 hour
[ https://issues.apache.org/jira/browse/AMBARI-24291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24291: Labels: pull-request-available (was: ) > Start All Services on 100-nodes cluster timed out after 1 hour > -- > > Key: AMBARI-24291 > URL: https://issues.apache.org/jira/browse/AMBARI-24291 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > > ambari-server with 16 core CPU, 32GB RAM, fake agents on 2 hosts (16GB RAM, 2 > core CPU) - 50 agents on each host, Mysql db on last host > # Deploy a PERF cluster with 100 fake agents > # Initiate Stop All components > # Initiate Start All components > Observations: > # As part of initial deploy and start services, the Start All Services call > took about 6 minutes. > # The first call to Stop All Services took about 23 minutes. > # The subsequent call to Start All services timed out after 1 hour 1 minute. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24325) [Log Search UI] Unaccessible query filter type ahead element in small window
[ https://issues.apache.org/jira/browse/AMBARI-24325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553011#comment-16553011 ] Hudson commented on AMBARI-24325: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #60 (See [https://builds.apache.org/job/Ambari-branch-2.7/60/]) [AMBARI-24325] [Log Search UI] Unaccessible query filter type ahead (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=28836ac86204be6694200f12a3a050eab1c17598]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.less > [Log Search UI] Unaccessible query filter type ahead element in small window > > > Key: AMBARI-24325 > URL: https://issues.apache.org/jira/browse/AMBARI-24325 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 12h > Time Spent: 1h 20m > Remaining Estimate: 10h 40m > > * Click into the query filter bar input field > * A type ahead dropdown will appear > * When the user's screen is small the bottom of the dropdown is not visible > Expected behaviour: All the dropdown element should be available for > selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
[ https://issues.apache.org/jira/browse/AMBARI-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24338: --- Status: Patch Available (was: In Progress) > [Log Search UI] Add application routing information to README.md > > > Key: AMBARI-24338 > URL: https://issues.apache.org/jira/browse/AMBARI-24338 > Project: Ambari > Issue Type: Documentation > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Time Spent: 20m > Remaining Estimate: 23h 40m > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24269) All input fields are disabled after validation - cancel - filter for something on advanced tab
[ https://issues.apache.org/jira/browse/AMBARI-24269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24269: Labels: pull-request-available (was: ) > All input fields are disabled after validation - cancel - filter for > something on advanced tab > -- > > Key: AMBARI-24269 > URL: https://issues.apache.org/jira/browse/AMBARI-24269 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: Validation_cancel_search_issue.mov > > > STR: (see attached video) > 1. try to do some property modifications, and save it > 2. when some warnings appear, click cancel > 3. filter for a variable that is not on the Advanced tab > 4. everything is disabled on all tabs, even after discarding the modifications -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24339) Background Operations: minor UX changes
[ https://issues.apache.org/jira/browse/AMBARI-24339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24339: Labels: pull-request-available (was: ) > Background Operations: minor UX changes > --- > > Key: AMBARI-24339 > URL: https://issues.apache.org/jira/browse/AMBARI-24339 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: cancel-task.png, kill-milliseconds.png > > > See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24339) Background Operations: minor UX changes
[ https://issues.apache.org/jira/browse/AMBARI-24339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24339: -- Attachment: kill-milliseconds.png cancel-task.png > Background Operations: minor UX changes > --- > > Key: AMBARI-24339 > URL: https://issues.apache.org/jira/browse/AMBARI-24339 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.1 > > Attachments: cancel-task.png, kill-milliseconds.png > > > See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24339) Background Operations: minor UX changes
Andrii Tkach created AMBARI-24339: - Summary: Background Operations: minor UX changes Key: AMBARI-24339 URL: https://issues.apache.org/jira/browse/AMBARI-24339 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.1 See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24323: Labels: pull-request-available (was: ) > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch, > AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24327) Zeppelin server is shown as started even if it fails during start up
[ https://issues.apache.org/jira/browse/AMBARI-24327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552910#comment-16552910 ] Hudson commented on AMBARI-24327: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9666 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9666/]) [AMBARI-24327] Zeppelin server is shown as started even if it fails (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=5fa81ce899319710e99d4f33309201641f20f6b2]) * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/package/scripts/alert_check_zeppelin.py * (add) src/main/resources/stacks/HDP/3.0/services/ZEPPELIN/package/scripts/alerts/alert_check_zeppelin.py * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/package/scripts/alerts/alert_check_zeppelin.py * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/alerts/alert_check_zeppelin.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/alerts.json * (delete) ambari-server/src/main/resources/common-services/ZEPPELIN/0.7.0/package/scripts/alert_check_zeppelin.py * (edit) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0/alerts.json > Zeppelin server is shown as started even if it fails during start up > > > Key: AMBARI-24327 > URL: https://issues.apache.org/jira/browse/AMBARI-24327 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24327.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to reproduce: > 1) Set incorrect values in shiro.ini. For example set the value of > ldapRealm.hadoopSecurityCredentialPath to incorrect path > 2) Restart zeppelin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24332) PERF 1.0 package not installed in the cluster at deploy time
[ https://issues.apache.org/jira/browse/AMBARI-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24332: Labels: pull-request-available (was: ) > PERF 1.0 package not installed in the cluster at deploy time > > > Key: AMBARI-24332 > URL: https://issues.apache.org/jira/browse/AMBARI-24332 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0, 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
[ https://issues.apache.org/jira/browse/AMBARI-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24338: Labels: pull-request-available (was: ) > [Log Search UI] Add application routing information to README.md > > > Key: AMBARI-24338 > URL: https://issues.apache.org/jira/browse/AMBARI-24338 > Project: Ambari > Issue Type: Documentation > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.1 > > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
[ https://issues.apache.org/jira/browse/AMBARI-24338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24338: --- Issue Type: Documentation (was: Bug) > [Log Search UI] Add application routing information to README.md > > > Key: AMBARI-24338 > URL: https://issues.apache.org/jira/browse/AMBARI-24338 > Project: Ambari > Issue Type: Documentation > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Fix For: 2.7.1 > > Original Estimate: 24h > Remaining Estimate: 24h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24338) [Log Search UI] Add application routing information to README.md
Istvan Tobias created AMBARI-24338: -- Summary: [Log Search UI] Add application routing information to README.md Key: AMBARI-24338 URL: https://issues.apache.org/jira/browse/AMBARI-24338 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 2.7.0 Reporter: Istvan Tobias Assignee: Istvan Tobias Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24270) Agent Status Command Are Randomly Failing With Empty stderr
[ https://issues.apache.org/jira/browse/AMBARI-24270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24270: - Attachment: AMBARI-24270.patch > Agent Status Command Are Randomly Failing With Empty stderr > --- > > Key: AMBARI-24270 > URL: https://issues.apache.org/jira/browse/AMBARI-24270 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch > > Time Spent: 3h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24270) Agent Status Command Are Randomly Failing With Empty stderr
[ https://issues.apache.org/jira/browse/AMBARI-24270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24270: - Attachment: AMBARI-24270.patch > Agent Status Command Are Randomly Failing With Empty stderr > --- > > Key: AMBARI-24270 > URL: https://issues.apache.org/jira/browse/AMBARI-24270 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch, > AMBARI-24270.patch, AMBARI-24270.patch, AMBARI-24270.patch > > Time Spent: 3h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24323) Adding a component when the agent scripts are moved out and file download disabled takes > 1 hour and timeout
[ https://issues.apache.org/jira/browse/AMBARI-24323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24323: - Attachment: AMBARI-24323.patch > Adding a component when the agent scripts are moved out and file download > disabled takes > 1 hour and timeout > - > > Key: AMBARI-24323 > URL: https://issues.apache.org/jira/browse/AMBARI-24323 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24323.patch, AMBARI-24323.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)
[ https://issues.apache.org/jira/browse/AMBARI-23079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552849#comment-16552849 ] Hudson commented on AMBARI-23079: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #59 (See [https://builds.apache.org/job/Ambari-branch-2.7/59/]) AMBARI-23079. Log Feeder: support to use load balancer for Solr API (not (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=8dd0150cd364f293c555e09fa47ad9e022b59d1f]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/ApplicationConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederSolrClientFactory.java * (edit) ambari-logsearch/ambari-logsearch-config-solr/src/main/java/org/apache/ambari/logsearch/config/solr/LogLevelFilterManagerSolr.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/common/ConfigItem.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java > Log Feeder: support to use load balancer for Solr API (not only cloud client) > -- > > Key: AMBARI-23079 > URL: https://issues.apache.org/jira/browse/AMBARI-23079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24329) Log Feeder define default log levels per component
[
https://issues.apache.org/jira/browse/AMBARI-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552850#comment-16552850
]
Hudson commented on AMBARI-24329:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #59 (See
[https://builds.apache.org/job/Ambari-branch-2.7/59/])
AMBARI-24329. Log Feeder define default log levels per component. (oleewere:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c04daafbcbbaac4a5a2fe5796e3aa35cfdfe7585])
* (edit)
ambari-logsearch/ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputDescriptorImpl.java
* (edit)
ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-logsearch-docker.json
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManagerImpl.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputManagerTest.java
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerInput.java
* (edit)
ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputDescriptor.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/loglevelfilter/LogLevelFilterHandler.java
> Log Feeder define default log levels per component
> --
>
> Key: AMBARI-24329
> URL: https://issues.apache.org/jira/browse/AMBARI-24329
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now we can define a global default log level, make this work per
> component by defining default log levels in input configs.
> example:
> {code:json}
> {"inputs" [
> {
> "type": "logsearch_server",
> "default_log_levels" : [
> "WARN", "DEBUG"
>],
>
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24332) PERF 1.0 package not installed in the cluster at deploy time
[ https://issues.apache.org/jira/browse/AMBARI-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24332: Summary: PERF 1.0 package not installed in the cluster at deploy time (was: PERF 1.0 package not installed in the cluster) > PERF 1.0 package not installed in the cluster at deploy time > > > Key: AMBARI-24332 > URL: https://issues.apache.org/jira/browse/AMBARI-24332 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0, 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24332) PERF 1.0 package not installed in the cluster
[ https://issues.apache.org/jira/browse/AMBARI-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24332: Summary: PERF 1.0 package not installed in the cluster (was: ADDENDUM - PERF 1.0 package not installed in the cluster) > PERF 1.0 package not installed in the cluster > - > > Key: AMBARI-24332 > URL: https://issues.apache.org/jira/browse/AMBARI-24332 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0, 2.7.1 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24337) Ambari API - expose Ambari Config Revision Control
[ https://issues.apache.org/jira/browse/AMBARI-24337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24337: - Description: Feature Request to expose Ambari Config Revision Control via Ambari API . I had a look here but I don't think this is exactly what I want. [https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md] I was thinking about writing a tool to fetch all Ambari Config Revisions as the online Ambari Revision Control is much too basic compared to Git and doesn't allow us to see changes made across the team over time in useful ways, see linked tickets. was: Feature Request to expose Ambari Config Revision Control via Ambari API . I had a look here but I don't think this is exactly what I want. [https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md] I was thinking about writing a tool to fetch all Ambari Config Revisions as the online Ambari Revision Control is much too basic to be able to see config history across a team's changes over the course of say, a year. > Ambari API - expose Ambari Config Revision Control > -- > > Key: AMBARI-24337 > URL: https://issues.apache.org/jira/browse/AMBARI-24337 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2, 2.6.0 >Reporter: Hari Sekhon >Priority: Major > > Feature Request to expose Ambari Config Revision Control via Ambari API . > I had a look here but I don't think this is exactly what I want. > [https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md] > I was thinking about writing a tool to fetch all Ambari Config Revisions as > the online Ambari Revision Control is much too basic compared to Git and > doesn't allow us to see changes made across the team over time in useful > ways, see linked tickets. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24337) Ambari API - expose Ambari Config Revision Control
Hari Sekhon created AMBARI-24337: Summary: Ambari API - expose Ambari Config Revision Control Key: AMBARI-24337 URL: https://issues.apache.org/jira/browse/AMBARI-24337 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2, 2.6.0 Reporter: Hari Sekhon Feature Request to expose Ambari Config Revision Control via Ambari API . I had a look here but I don't think this is exactly what I want. [https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md] I was thinking about writing a tool to fetch all Ambari Config Revisions as the online Ambari Revision Control is much too basic to be able to see config history across a team's changes over the course of say, a year. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24329) Log Feeder define default log levels per component
[
https://issues.apache.org/jira/browse/AMBARI-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24329:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Log Feeder define default log levels per component
> --
>
> Key: AMBARI-24329
> URL: https://issues.apache.org/jira/browse/AMBARI-24329
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now we can define a global default log level, make this work per
> component by defining default log levels in input configs.
> example:
> {code:json}
> {"inputs" [
> {
> "type": "logsearch_server",
> "default_log_levels" : [
> "WARN", "DEBUG"
>],
>
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24336) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-24336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-24336: -- Attachment: photo_2018-07-03_18-52-37.jpg Screen Shot 2018-07-03 at 11.21.08 AM.png > Badge with count of empty or invalid properties are missed ar the services > panel during cluster installation > > > Key: AMBARI-24336 > URL: https://issues.apache.org/jira/browse/AMBARI-24336 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-07-03 at 11.21.08 AM.png, > photo_2018-07-03_18-52-37.jpg > > > STR: > 1)Initiate cluster installation > 2)Navigate to customize all services page > 3)Navigate to service tab > 4)Clear some service required property > Expected > Count of errors near service name > Actual > Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24336) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
Andrii Tkach created AMBARI-24336: - Summary: Badge with count of empty or invalid properties are missed ar the services panel during cluster installation Key: AMBARI-24336 URL: https://issues.apache.org/jira/browse/AMBARI-24336 Project: Ambari Issue Type: Bug Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Aleksandr Kovalenko Fix For: 2.7.1 STR: 1)Initiate cluster installation 2)Navigate to customize all services page 3)Navigate to service tab 4)Clear some service required property Expected Count of errors near service name Actual Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24327) Zeppelin server is shown as started even if it fails during start up
[ https://issues.apache.org/jira/browse/AMBARI-24327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-24327: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Zeppelin server is shown as started even if it fails during start up > > > Key: AMBARI-24327 > URL: https://issues.apache.org/jira/browse/AMBARI-24327 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24327.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Steps to reproduce: > 1) Set incorrect values in shiro.ini. For example set the value of > ldapRealm.hadoopSecurityCredentialPath to incorrect path > 2) Restart zeppelin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24335) Update service metainfo to declare Kerberos is required for SSO integration support
Sandor Molnar created AMBARI-24335:
--
Summary: Update service metainfo to declare Kerberos is required
for SSO integration support
Key: AMBARI-24335
URL: https://issues.apache.org/jira/browse/AMBARI-24335
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.1
Update service metainfo to declare Kerberos is required for SSO integration
support.
The metainfo file allow for a service to indicate that is supports SSO
integration.
{code:java|title=Example}
true
service-site/knox.sso.enabled
{code}
However, some services required that Kerberos is enabled to support SSO. This
needs to be indicated in the metainfo so that Ambari knows how to behave
properly.
{code:java|title=Example}
true
service-site/knox.sso.enabled
true
{code}
Along with this change, the following API request needs to be updated to supply
the relevant data:
{noformat:title=Get stack service details}
GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
{
"href" : ":URL",
"StackServices" : {
...
"sso_integration_supported": "true",
"sso_integration_requires_kerberos": "true",
...
},
...
{noformat}
{noformat:title=Get installed service information}
GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
{
"href" : ":URL",
"ServiceInfo" : {
"cluster_name" : ":CLUSTER_NAME",
...
"sso_integration_supported": "true",
"sso_integration_requires_kerberos": "true",
"sso_integration_enabled": "false",
"sso_integration_desired": "false",
...
},
...
{noformat}
{noformat:title=List installed services that support SSO integration only when
Kerberos to be enabled}
GET
/api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true&ServiceInfo/sso_integration_requires_kerberos=true
{
"href" : ":URL",
"items" : [
...
]
}
{noformat}
{noformat:title=List stack services that support SSO integration only when
Kerberos is enabed}
GET
/api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/sso_integration_supported=true&StackServices/sso_integration_requires_kerberos=true
{
"href" : ":URL",
"items" : [
...
]
}{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24333) User is able to set the same short URLs for different view instances
[
https://issues.apache.org/jira/browse/AMBARI-24333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24333:
Labels: pull-request-available (was: )
> User is able to set the same short URLs for different view instances
>
>
> Key: AMBARI-24333
> URL: https://issues.apache.org/jira/browse/AMBARI-24333
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> *STR*
> # Let's say the user has CAPACITY-SCHEDULER view instance with
> {{/main/view/CAPACITY-SCHEDULER/auto_cs_instance}} short URL set
> # Clone this instance or create another CAPACITY-SCHEDULER instance manually
> # Set the same short URL as for the first instance
> *Result*
> - If 'Name' property is the same, request for adding new URL fails
> request:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response:
> {noformat}
> {
> "status" : 500,
> "message" : "An internal system exception occurred: This view URL name
> exists, URL names should be unique"
> }
> {noformat}
> - If name is different, the REST call succeeds even if URL itself is
> duplicate:
> {noformat}
> POST api/v1/view/urls/auto_cs_instance1
> {
> "ViewUrlInfo": {
> "url_name": "auto_cs_instance1",
> "url_suffix": "auto_cs_instance",
> "view_instance_version": "1.0.0",
> "view_instance_name": "AUTO_CS_INSTANCE_Copy",
> "view_instance_common_name": "CAPACITY-SCHEDULER"
> }
> }
> {noformat}
> response is 201 in this case; URL is created
> - As result there are two view instances with the same URL, and the first
> one is no longer accessible by this URL
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24334) HBase Balancer - temporarily disable balancer for HBase rolling restart
Hari Sekhon created AMBARI-24334: Summary: HBase Balancer - temporarily disable balancer for HBase rolling restart Key: AMBARI-24334 URL: https://issues.apache.org/jira/browse/AMBARI-24334 Project: Ambari Issue Type: Improvement Components: ambari-server, rolling-upgrade Affects Versions: 2.5.2 Reporter: Hari Sekhon Temporarily disable HBase Balancer when doing HBase rolling restarts. I've noticed a drop in data locality after doing an HBase rolling restart looking at the Ambari Grafana graph found on the HBase Regionservers dashboard -> Locality (row at bottom) -> Percent Files Local graph. I believe the HBase balancer should be temporarily disabled (if enabled) and then re-enabled after all RegionServers have successfully completed. One must be careful to only re-enable the balancer if it was enabled before the rolling restart was initiated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24333) User is able to set the same short URLs for different view instances
Sandor Molnar created AMBARI-24333:
--
Summary: User is able to set the same short URLs for different
view instances
Key: AMBARI-24333
URL: https://issues.apache.org/jira/browse/AMBARI-24333
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.1
*STR*
# Let's say the user has CAPACITY-SCHEDULER view instance with
{{/main/view/CAPACITY-SCHEDULER/auto_cs_instance}} short URL set
# Clone this instance or create another CAPACITY-SCHEDULER instance manually
# Set the same short URL as for the first instance
*Result*
- If 'Name' property is the same, request for adding new URL fails
request:
{noformat}
POST api/v1/view/urls/auto_cs_instance
{
"ViewUrlInfo": {
"url_name": "auto_cs_instance",
"url_suffix": "auto_cs_instance",
"view_instance_version": "1.0.0",
"view_instance_name": "AUTO_CS_INSTANCE_Copy",
"view_instance_common_name": "CAPACITY-SCHEDULER"
}
}
{noformat}
response:
{noformat}
{
"status" : 500,
"message" : "An internal system exception occurred: This view URL name
exists, URL names should be unique"
}
{noformat}
- If name is different, the REST call succeeds even if URL itself is duplicate:
{noformat}
POST api/v1/view/urls/auto_cs_instance1
{
"ViewUrlInfo": {
"url_name": "auto_cs_instance1",
"url_suffix": "auto_cs_instance",
"view_instance_version": "1.0.0",
"view_instance_name": "AUTO_CS_INSTANCE_Copy",
"view_instance_common_name": "CAPACITY-SCHEDULER"
}
}
{noformat}
response is 201 in this case; URL is created
- As result there are two view instances with the same URL, and the first one
is no longer accessible by this URL
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24297) Show full JDBC URL's for Hive
[ https://issues.apache.org/jira/browse/AMBARI-24297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552653#comment-16552653 ] Hudson commented on AMBARI-24297: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9662 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9662/]) AMBARI-24297. Show full JDBC URL's for Hive (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=2c269346da779b4dbd04bdb0091d60de6828fbed]) * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/main/service/services/hive.hbs * (edit) ambari-web/app/views/main/service/services/hive.js > Show full JDBC URL's for Hive > - > > Key: AMBARI-24297 > URL: https://issues.apache.org/jira/browse/AMBARI-24297 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > > Instead of ellipsis, we should use forced breaks. Also, we should align > elements better. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24246) Ambari does not pick the existing hive database from the jdbc url set
[ https://issues.apache.org/jira/browse/AMBARI-24246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552652#comment-16552652 ] Hudson commented on AMBARI-24246: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9662 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9662/]) AMBARI-24246. Ambari does not pick the existing hive database from the (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=47260ab3935b8db0231964fda3e3b662189fa7c1]) * (edit) ambari-web/app/mixins/common/configs/config_recommendation_parser.js > Ambari does not pick the existing hive database from the jdbc url set > - > > Key: AMBARI-24246 > URL: https://issues.apache.org/jira/browse/AMBARI-24246 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23903) Ambari: Add-jdeb-support
[ https://issues.apache.org/jira/browse/AMBARI-23903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552618#comment-16552618 ] Naresh Bhat commented on AMBARI-23903: -- The pull request created for the following branches v2.6 - [https://github.com/apache/ambari/pull/1640] v2.7 - [https://github.com/apache/ambari/pull/1840] trunk - [https://github.com/apache/ambari/pull/1642] > Ambari: Add-jdeb-support > > > Key: AMBARI-23903 > URL: https://issues.apache.org/jira/browse/AMBARI-23903 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: trunk, 2.5.2, 2.6.0, 2.7.0 >Reporter: Naresh Bhat >Priority: Major > Fix For: trunk, 2.5.2, 2.6.0, 2.7.0 > > > utility needs tobe added jdeb support. The patch will help to generate > debian package for utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23903) Ambari: Add-jdeb-support
[ https://issues.apache.org/jira/browse/AMBARI-23903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naresh Bhat updated AMBARI-23903: - Fix Version/s: 2.7.0 > Ambari: Add-jdeb-support > > > Key: AMBARI-23903 > URL: https://issues.apache.org/jira/browse/AMBARI-23903 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: trunk, 2.5.2, 2.6.0, 2.7.0 >Reporter: Naresh Bhat >Priority: Major > Fix For: trunk, 2.5.2, 2.6.0, 2.7.0 > > > utility needs tobe added jdeb support. The patch will help to generate > debian package for utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23903) Ambari: Add-jdeb-support
[ https://issues.apache.org/jira/browse/AMBARI-23903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naresh Bhat updated AMBARI-23903: - Affects Version/s: 2.7.0 > Ambari: Add-jdeb-support > > > Key: AMBARI-23903 > URL: https://issues.apache.org/jira/browse/AMBARI-23903 > Project: Ambari > Issue Type: Improvement > Components: test >Affects Versions: trunk, 2.5.2, 2.6.0, 2.7.0 >Reporter: Naresh Bhat >Priority: Major > Fix For: trunk, 2.5.2, 2.6.0, 2.7.0 > > > utility needs tobe added jdeb support. The patch will help to generate > debian package for utility. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24329) Log Feeder define default log levels per component
[
https://issues.apache.org/jira/browse/AMBARI-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552579#comment-16552579
]
Hudson commented on AMBARI-24329:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9661 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9661/])
AMBARI-24329. Log Feeder define default log levels per component. (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=1070b65c2c2479a5687a5a70a9443e154d627ec2])
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputManagerTest.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputManagerImpl.java
* (edit)
ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputDescriptor.java
* (edit)
ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/loglevelfilter/LogLevelFilterHandler.java
* (edit)
ambari-logsearch/docker/test-config/logfeeder/shipper-conf/input.config-logsearch-docker.json
* (edit)
ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerInput.java
* (edit)
ambari-logsearch/ambari-logsearch-config-json/src/main/java/org/apache/ambari/logsearch/config/json/model/inputconfig/impl/InputDescriptorImpl.java
> Log Feeder define default log levels per component
> --
>
> Key: AMBARI-24329
> URL: https://issues.apache.org/jira/browse/AMBARI-24329
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now we can define a global default log level, make this work per
> component by defining default log levels in input configs.
> example:
> {code:json}
> {"inputs" [
> {
> "type": "logsearch_server",
> "default_log_levels" : [
> "WARN", "DEBUG"
>],
>
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24297) Show full JDBC URL's for Hive
[ https://issues.apache.org/jira/browse/AMBARI-24297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24297. -- Resolution: Fixed Committed to trunk > Show full JDBC URL's for Hive > - > > Key: AMBARI-24297 > URL: https://issues.apache.org/jira/browse/AMBARI-24297 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > > Instead of ellipsis, we should use forced breaks. Also, we should align > elements better. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24332) ADDENDUM - PERF 1.0 package not installed in the cluster
Krisztian Kasa created AMBARI-24332: --- Summary: ADDENDUM - PERF 1.0 package not installed in the cluster Key: AMBARI-24332 URL: https://issues.apache.org/jira/browse/AMBARI-24332 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0, 2.7.1 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.7.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24331) Hide not restartable components from Service Auto Start
Antonenko Alexander created AMBARI-24331: Summary: Hide not restartable components from Service Auto Start Key: AMBARI-24331 URL: https://issues.apache.org/jira/browse/AMBARI-24331 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24331) Hide not restartable components from Service Auto Start
[ https://issues.apache.org/jira/browse/AMBARI-24331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-24331: Assignee: Antonenko Alexander > Hide not restartable components from Service Auto Start > > > Key: AMBARI-24331 > URL: https://issues.apache.org/jira/browse/AMBARI-24331 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)
[ https://issues.apache.org/jira/browse/AMBARI-23079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552481#comment-16552481 ] Hudson commented on AMBARI-23079: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9660 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9660/]) AMBARI-23079. Log Feeder: support to use load balancer for Solr API (not (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=69a64a068911504db944d284b2ccf9f5db4462a3]) * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder-plugin-api/src/main/java/org/apache/ambari/logfeeder/plugin/common/ConfigItem.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/OutputSolr.java * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (add) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederSolrClientFactory.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/ApplicationConfig.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/common/LogFeederConstants.java * (edit) ambari-logsearch/ambari-logsearch-config-solr/src/main/java/org/apache/ambari/logsearch/config/solr/LogLevelFilterManagerSolr.java > Log Feeder: support to use load balancer for Solr API (not only cloud client) > -- > > Key: AMBARI-23079 > URL: https://issues.apache.org/jira/browse/AMBARI-23079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24329) Log Feeder define default log levels per component
[
https://issues.apache.org/jira/browse/AMBARI-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-24329:
--
Status: Patch Available (was: In Progress)
> Log Feeder define default log levels per component
> --
>
> Key: AMBARI-24329
> URL: https://issues.apache.org/jira/browse/AMBARI-24329
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now we can define a global default log level, make this work per
> component by defining default log levels in input configs.
> example:
> {code:json}
> {"inputs" [
> {
> "type": "logsearch_server",
> "default_log_levels" : [
> "WARN", "DEBUG"
>],
>
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)
[ https://issues.apache.org/jira/browse/AMBARI-23079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23079: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Log Feeder: support to use load balancer for Solr API (not only cloud client) > -- > > Key: AMBARI-23079 > URL: https://issues.apache.org/jira/browse/AMBARI-23079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24329) Log Feeder define default log levels per component
[
https://issues.apache.org/jira/browse/AMBARI-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24329:
Labels: pull-request-available (was: )
> Log Feeder define default log levels per component
> --
>
> Key: AMBARI-24329
> URL: https://issues.apache.org/jira/browse/AMBARI-24329
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
>
> Right now we can define a global default log level, make this work per
> component by defining default log levels in input configs.
> example:
> {code:json}
> {"inputs" [
> {
> "type": "logsearch_server",
> "default_log_levels" : [
> "WARN", "DEBUG"
>],
>
> }
> ]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
