from:"Yao Lei \(JIRA\)"

[jira] [Updated] (AMBARI-25761) Add Ranger support for Bigtop 3.2.0 Stack

2022-10-18 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25761:
-
Description: 
Add Ranger support for Bigtop 3.2.0 Stack

Related JIRA
https://issues.apache.org/jira/browse/BIGTOP-3689
https://issues.apache.org/jira/browse/BIGTOP-1933

> Add Ranger support for Bigtop 3.2.0 Stack
> -
>
> Key: AMBARI-25761
> URL: https://issues.apache.org/jira/browse/AMBARI-25761
> Project: Ambari
>  Issue Type: Task
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
>
> Add Ranger support for Bigtop 3.2.0 Stack
> Related JIRA
> https://issues.apache.org/jira/browse/BIGTOP-3689
> https://issues.apache.org/jira/browse/BIGTOP-1933



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-25761) Add Ranger support for Bigtop 3.2.0 Stack

2022-10-18 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25761:


Assignee: Yao Lei

> Add Ranger support for Bigtop 3.2.0 Stack
> -
>
> Key: AMBARI-25761
> URL: https://issues.apache.org/jira/browse/AMBARI-25761
> Project: Ambari
>  Issue Type: Task
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25761) Add Ranger support for Bigtop 3.2.0 Stack

2022-10-18 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25761:


 Summary: Add Ranger support for Bigtop 3.2.0 Stack
 Key: AMBARI-25761
 URL: https://issues.apache.org/jira/browse/AMBARI-25761
 Project: Ambari
  Issue Type: Task
Reporter: Yao Lei






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Description: 
If hosts number is less than 4,  namenode federation wizard shoud not be 
allowed.

 !screenshot-3.png! 
 !screenshot-2.png! 

  was:
 !screenshot-3.png! 

 !screenshot-2.png! 


> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
> If hosts number is less than 4,  namenode federation wizard shoud not be 
> allowed.
>  !screenshot-3.png! 
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Attachment: screenshot-2.png

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Description:  !screenshot-2.png! 

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Description: 
 !screenshot-3.png! 

 !screenshot-2.png! 

  was: !screenshot-2.png! 


> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
>  !screenshot-3.png! 
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Attachment: screenshot-3.png

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Attachment: (was: screenshot-1.png)

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
>  !screenshot-3.png! 
>  !screenshot-2.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Attachment: screenshot-1.png

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25753:


 Summary: Web Should Not Support Enabling NameNode Federation If 
Hosts Number Is Less than 4 
 Key: AMBARI-25753
 URL: https://issues.apache.org/jira/browse/AMBARI-25753
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei
Assignee: Yao Lei






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25753) Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less than 4

2022-10-09 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25753:
-
Fix Version/s: 2.8.0

> Web Should Not Support Enabling NameNode Federation If Hosts Number Is Less 
> than 4 
> ---
>
> Key: AMBARI-25753
> URL: https://issues.apache.org/jira/browse/AMBARI-25753
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 2.8.0
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Resolved] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-10-05 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei resolved AMBARI-25747.
--
Resolution: Fixed

> 500 Server Error Occurrs When Access to /api/stomp/v1/xxx//xhr_send
> ---
>
> Key: AMBARI-25747
> URL: https://issues.apache.org/jira/browse/AMBARI-25747
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> In web browser console,  we can find fllowing error:
> {code:java}
> HTTP ERROR 500
> Problem accessing /api/stomp/v1/871/xjujmeoq/xhr_send. Reason:
> Server Error
> Caused by:
> org.springframework.web.util.NestedServletException: Request processing 
> failed; nested exception is java.lang.IllegalArgumentException: When 
> allowCredentials is true, allowedOrigins cannot contain the special value "*" 
> since that cannot be set on the "Access-Control-Allow-Origin" response 
> header. To allow credentials to a set of origins, list them explicitly or 
> consider using "allowedOriginPatterns" instead.
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter

[jira] [Updated] (AMBARI-25748) [BIGTOP]HDFS Service Check Fails in NameNode HA cluster

2022-10-02 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Summary: [BIGTOP]HDFS Service Check Fails in NameNode HA cluster  (was: 
[BIGTOP]HDFS Service Check Fails in NameNode HA)

> [BIGTOP]HDFS Service Check Fails in NameNode HA cluster
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}
> The reason is that http response code is 302 when access to 
> http://bigtop3:8480.
> And the code in checkWebUI.py at line 81  will see the reponse code 302 as a 
> failure.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25748) [BIGTOP]HDFS Service Check Fails in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Description: 
{code:java}
2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
{'content': StaticFile('checkWebUI.py'), 'mode': 0775}
2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
/var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
'ambari-qa', 'try_sleep': 3}
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
{code}


The reason is that http response code is 302 when access to http://bigtop3:8480.
And the code in checkWebUI.py at line 81  will see the reponse code 302 as a 
failure.
 


  was:

{code:java}
2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
{'content': StaticFile('checkWebUI.py'), 'mode': 0775}
2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
/var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
'ambari-qa', 'try_sleep': 3}
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
{code}



> [BIGTOP]HDFS Service Check Fails in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o

[jira] [Assigned] (AMBARI-25748) [BIGTOP]HDFS Service Check Faild in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25748:


Assignee: Yao Lei

> [BIGTOP]HDFS Service Check Faild in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25748) [BIGTOP]HDFS Service Check Fails in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Summary: [BIGTOP]HDFS Service Check Fails in NameNode HA  (was: 
[BIGTOP]HDFS Service Check Faild in NameNode HA)

> [BIGTOP]HDFS Service Check Fails in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25748) [BIGTOP]HDFS Service Check Faild in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Fix Version/s: 2.8.0

> [BIGTOP]HDFS Service Check Faild in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25748) [BIGTOP]HDFS Service Check Faild in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Summary: [BIGTOP]HDFS Service Check Faild in NameNode HA  (was: HDFS 
Service Check Faild in NameNode HA)

> [BIGTOP]HDFS Service Check Faild in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25748) HDFS Service Check Faild in NameNode HA

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25748:
-
Description: 

{code:java}
2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
{'content': StaticFile('checkWebUI.py'), 'mode': 0775}
2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
/var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
'ambari-qa', 'try_sleep': 3}
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
Cannot access WEB UI on: http://bigtop3:8480
Cannot access WEB UI on: http://bigtop3:8480
{code}


> HDFS Service Check Faild in NameNode HA
> ---
>
> Key: AMBARI-25748
> URL: https://issues.apache.org/jira/browse/AMBARI-25748
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
>
> {code:java}
> 2022-10-02 13:25:04,065 - File['/var/lib/ambari-agent/tmp/checkWebUI.py'] 
> {'content': StaticFile('checkWebUI.py'), 'mode': 0775}
> 2022-10-02 13:25:04,067 - Execute['ambari-python-wrap 
> /var/lib/ambari-agent/tmp/checkWebUI.py -m bigtop3,bigtop4,bigtop1 -p 8480 -s 
> False -o PROTOCOL_TLSv1_2'] {'logoutput': True, 'tries': 5, 'user': 
> 'ambari-qa', 'try_sleep': 3}
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:04,279 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:07,462 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:10,706 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> 2022-10-02 13:25:13,890 - Retrying after 3 seconds. Reason: Execution of 
> 'ambari-python-wrap /var/lib/ambari-agent/tmp/checkWebUI.py -m 
> bigtop3,bigtop4,bigtop1 -p 8480 -s False -o PROTOCOL_TLSv1_2' returned 1. 
> Cannot access WEB UI on: http://bigtop3:8480
> Cannot access WEB UI on: http://bigtop3:8480
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25748) HDFS Service Check Faild in NameNode HA

2022-10-01 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25748:


 Summary: HDFS Service Check Faild in NameNode HA
 Key: AMBARI-25748
 URL: https://issues.apache.org/jira/browse/AMBARI-25748
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Resolved] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-10-01 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei resolved AMBARI-25744.
--
Resolution: Fixed

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25747:
-
Description: 
In web browser console,  we can find fllowing error:

{code:java}
HTTP ERROR 500
Problem accessing /api/stomp/v1/871/xjujmeoq/xhr_send. Reason:

Server Error
Caused by:
org.springframework.web.util.NestedServletException: Request processing failed; 
nested exception is java.lang.IllegalArgumentException: When allowCredentials 
is true, allowedOrigins cannot contain the special value "*" since that cannot 
be set on the "Access-Control-Allow-Origin" response header. To allow 
credentials to a set of origins, list them explicitly or consider using 
"allowedOriginPatterns" instead.
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90)
at 
org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springfr

[jira] [Updated] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25747:
-
Attachment: screenshot-1.png

> 500 Server Error Occurrs When Access to /api/stomp/v1/xxx//xhr_send
> ---
>
> Key: AMBARI-25747
> URL: https://issues.apache.org/jira/browse/AMBARI-25747
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
>
> In web browser console,  we can find fllowing error:
> {code:java}
> HTTP ERROR 500
> Problem accessing /api/stomp/v1/871/xjujmeoq/xhr_send. Reason:
> Server Error
> Caused by:
> org.springframework.web.util.NestedServletException: Request processing 
> failed; nested exception is java.lang.IllegalArgumentException: When 
> allowCredentials is true, allowedOrigins cannot contain the special value "*" 
> since that cannot be set on the "Access-Control-Allow-Origin" response 
> header. To allow credentials to a set of origins, list them explicitly or 
> consider using "allowedOriginPatterns" instead.
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
>   at 
>

[jira] [Updated] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25747:
-
Description: 
In web browser console,  we can find fllowing error:

{code:java}
HTTP ERROR 500
Problem accessing /api/stomp/v1/871/xjujmeoq/xhr_send. Reason:

Server Error
Caused by:
org.springframework.web.util.NestedServletException: Request processing failed; 
nested exception is java.lang.IllegalArgumentException: When allowCredentials 
is true, allowedOrigins cannot contain the special value "*" since that cannot 
be set on the "Access-Control-Allow-Origin" response header. To allow 
credentials to a set of origins, list them explicitly or consider using 
"allowedOriginPatterns" instead.
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90)
at 
org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springfr

[jira] [Updated] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25747:
-
Description: 
In web browser console,  we can find fllowing error:

{code:java}
HTTP ERROR 500
Problem accessing /api/stomp/v1/607/feclayx4/xhr_send. Reason:

Server Error
Caused by:
org.springframework.web.util.NestedServletException: Request processing failed; 
nested exception is java.lang.IllegalArgumentException: When allowCredentials 
is true, allowedOrigins cannot contain the special value "*" since that cannot 
be set on the "Access-Control-Allow-Origin" response header. To allow 
credentials to a set of origins, list them explicitly or consider using 
"allowedOriginPatterns" instead.
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90)
at 
org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springfr

[jira] [Assigned] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25747:


Assignee: Yao Lei

> 500 Server Error Occurrs When Access to /api/stomp/v1/xxx//xhr_send
> ---
>
> Key: AMBARI-25747
> URL: https://issues.apache.org/jira/browse/AMBARI-25747
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> In web browser console,  we can find fllowing error:
> {code:java}
> HTTP ERROR 500
> Problem accessing /api/stomp/v1/607/feclayx4/xhr_send. Reason:
> Server Error
> Caused by:
> org.springframework.web.util.NestedServletException: Request processing 
> failed; nested exception is java.lang.IllegalArgumentException: When 
> allowCredentials is true, allowedOrigins cannot contain the special value "*" 
> since that cannot be set on the "Access-Control-Allow-Origin" response 
> header. To allow credentials to a set of origins, list them explicitly or 
> consider using "allowedOriginPatterns" instead.
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
>   at 
> org.springframework.security.web.FilterChainP

[jira] [Updated] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25747:
-
Fix Version/s: 2.8.0

> 500 Server Error Occurrs When Access to /api/stomp/v1/xxx//xhr_send
> ---
>
> Key: AMBARI-25747
> URL: https://issues.apache.org/jira/browse/AMBARI-25747
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
>
> {code:java}
> HTTP ERROR 500
> Problem accessing /api/stomp/v1/607/feclayx4/xhr_send. Reason:
> Server Error
> Caused by:
> org.springframework.web.util.NestedServletException: Request processing 
> failed; nested exception is java.lang.IllegalArgumentException: When 
> allowCredentials is true, allowedOrigins cannot contain the special value "*" 
> since that cannot be set on the "Access-Control-Allow-Origin" response 
> header. To allow credentials to a set of origins, list them explicitly or 
> consider using "allowedOriginPatterns" instead.
>   at 
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
>   at 
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
>   at 
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
>   at 
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
>   at 
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
>   at 
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
>   at 
> org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
>   at 
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
>   at 
> org.springframew

[jira] [Created] (AMBARI-25747) 500 Server Error Occurrs When Access to /api/stomp/v1/xxx/xxxx/xhr_send

2022-09-30 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25747:


 Summary: 500 Server Error Occurrs When Access to 
/api/stomp/v1/xxx//xhr_send
 Key: AMBARI-25747
 URL: https://issues.apache.org/jira/browse/AMBARI-25747
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei



{code:java}
HTTP ERROR 500
Problem accessing /api/stomp/v1/607/feclayx4/xhr_send. Reason:

Server Error
Caused by:
org.springframework.web.util.NestedServletException: Request processing failed; 
nested exception is java.lang.IllegalArgumentException: When allowCredentials 
is true, allowedOrigins cannot contain the special value "*" since that cannot 
be set on the "Access-Control-Allow-Origin" response header. To allow 
credentials to a set of origins, list them explicitly or consider using 
"allowedOriginPatterns" instead.
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1014)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:327)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:294)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:135)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103)
at 
org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:336)
at 
org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90)
at 
org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117)
at 
org.springframework.security.web.Filt

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Fix Version/s: (was: trunk)

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) [BIGTOP]Fails to enable NameNode HA

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Fix Version/s: (was: trunk)

> [BIGTOP]Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) [BIGTOP]Fails to enable NameNode HA

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Fix Version/s: 2.8.0

> [BIGTOP]Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk, 2.8.0
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Fix Version/s: 2.8.0

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk, 2.8.0
>
> Attachments: screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



[ https://issues.apache.org/jira/browse/AMBARI-25744 ]


Yao Lei deleted comment on AMBARI-25744:
--

was (Author: yaolei):
This issue seems caused by AMBARI-24921

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25744:


Assignee: Yao Lei

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients')// result is null {code} ,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  serviceCheckSupported is false that lead to the 
Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients')// result is null {code} ,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  'serviceCheckSupported' is false that make the 
Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  serviceCheckSupported is false that lead to the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients')// result is null {code} ,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  'serviceCheckSupported' is false that make the 
Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  'serviceCheckSupported' is false that make the 
Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients')// result is null {code} ,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  'serviceCheckSupported' is false that make the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  'serviceCheckSupported' is false that make the 
Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  *serviceCheckSupported  *is false that make the 
Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients'){code} is null,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  'serviceCheckSupported' is false that make the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable  *serviceCheckSupported  *is false that make the 
Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable *serviceCheckSupported *is false that make the 
Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients'){code} is null,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable  *serviceCheckSupported  *is false that make the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so the code {code:java}
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;
var serviceCheckSupported = 
App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
{code}will make the variable *serviceCheckSupported *is false that make the 
Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients'){code} is null,
>  so the code {code:java}
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;
> var serviceCheckSupported = 
> App.get('services.supportsServiceCheck').contains(serviceName) && hasClient;
> {code}will make the variable *serviceCheckSupported *is false that make the 
> Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in the file app/views/main/service/item.js  at 
line 162
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in app/views/main/service/item.js line 162
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in the file app/views/main/service/item.js  
> at line 162
> {code:java}service.get('installedClients'){code} is null,
>  so {code:java}var hasClient = 
> App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;{code}will return false that make 
> the Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in app/views/main/service/item.js line 162
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in app/views/main/service/item.js 
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in app/views/main/service/item.js line 162
> {code:java}service.get('installedClients'){code} is null,
>  so {code:java}var hasClient = 
> App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;{code}will return false that make 
> the Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921.
When access to  MapReduce page,  in app/views/main/service/item.js 
{code:java}service.get('installedClients'){code} is null,
 so {code:java}var hasClient = 
App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921. In MapReduce Page , 
{code:java}service.get('installedClients'){code} is null, so 
{code:java}var hasClient = App.StackService.find(serviceName).get('hasClient') 
? service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921.
> When access to  MapReduce page,  in app/views/main/service/item.js 
> {code:java}service.get('installedClients'){code} is null,
>  so {code:java}var hasClient = 
> App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;{code}will return false that make 
> the Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921. In MapReduce Page , 
{code:java}service.get('installedClients'){code} is null, so 
{code:java}var hasClient = App.StackService.find(serviceName).get('hasClient') 
? service.get('installedClients') > 0 : true;{code}will return false that make 
the Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921. In MapReduce Page , 
service.get('installedClients') is null, so 
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true; will return false that make 
the Service Check buttion invisible


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921. In MapReduce Page , 
> {code:java}service.get('installedClients'){code} is null, so 
> {code:java}var hasClient = 
> App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true;{code}will return false that make 
> the Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems  caused by AMBARI-24921. In MapReduce Page , 
service.get('installedClients') is null, so 
var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
service.get('installedClients') > 0 : true; will return false that make 
the Service Check buttion invisible

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems caused by 


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems  caused by AMBARI-24921. In MapReduce Page , 
> service.get('installedClients') is null, so 
> var hasClient = App.StackService.find(serviceName).get('hasClient') ? 
> service.get('installedClients') > 0 : true; will return false that 
> make the Service Check buttion invisible



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-29 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 


The reason seems caused by 

  was:
As shown in  the flowing picture

 !screenshot-1.png! 


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 
> The reason seems caused by 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Commented] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-28 Thread Yao Lei (Jira)



[ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610548#comment-17610548
 ] 

Yao Lei commented on AMBARI-25744:
--

This issue seems caused by AMBARI-24921

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Resolved] (AMBARI-25740) [BIGTOP]Fails to enable NameNode HA

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei resolved AMBARI-25740.
--
Resolution: Fixed

> [BIGTOP]Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description: 
As shown in  the flowing picture

 !screenshot-1.png! 

  was: !screenshot-1.png! 


> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> As shown in  the flowing picture
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Description:  !screenshot-1.png! 

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25744:
-
Attachment: screenshot-1.png

> [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
> -
>
> Key: AMBARI-25744
> URL: https://issues.apache.org/jira/browse/AMBARI-25744
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25744) [BIGTOP]MapReduce Actions Menu Lacks Service Check Button

2022-09-28 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25744:


 Summary: [BIGTOP]MapReduce Actions Menu Lacks Service Check Button
 Key: AMBARI-25744
 URL: https://issues.apache.org/jira/browse/AMBARI-25744
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei
 Fix For: trunk






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) [BIGTOP]Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed Correctly

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Summary: [BIGTOP]Hosts in Step 2 of ResourceManager HA Wizard Cannot Be 
Displayed Correctly   (was: Hosts in Step 2 of ResourceManager HA Wizard Cannot 
Be Displayed Correctly )

> [BIGTOP]Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed 
> Correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Bigtop 3.2 cluster is deployed and current ResourceManager is on bigtop3.
> In step 2 of ResourceManager HA wizard,  if you select any other host as 
> additional ResourceManager node  in dropdown box,  you will find that 
> selected hosts in dropdown box cannot be displayed correctly in right text 
> area 
> As shown in below picture:
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) [BIGTOP]Fails to enable NameNode HA

2022-09-28 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Summary: [BIGTOP]Fails to enable NameNode HA   (was: Fails to enable 
NameNode HA )

> [BIGTOP]Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed Correctly

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Bigtop 3.2 cluster is deployed and current ResourceManager is on bigtop3.
In step 2 of ResourceManager HA wizard,  if you select any other host as 
additional ResourceManager node  in dropdown box,  you will find that selected 
hosts in dropdown box cannot be displayed correctly in right text area 

As shown in below picture:
 !screenshot-1.png! 

  was:
Bigtop 3.2 cluster is deployed in local vm.
Current ResourceManager is on bigtop3.
If you select any other host as additional ResourceManager node  in dropdown 
box,  you will find that selected hosts in dropdown box cannot be displayed 
correctly in right text area 



 !screenshot-1.png! 


> Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed Correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Bigtop 3.2 cluster is deployed and current ResourceManager is on bigtop3.
> In step 2 of ResourceManager HA wizard,  if you select any other host as 
> additional ResourceManager node  in dropdown box,  you will find that 
> selected hosts in dropdown box cannot be displayed correctly in right text 
> area 
> As shown in below picture:
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Bigtop 3.2 cluster is deployed in local vm.
Current ResourceManager is on bigtop3.
If you select any other host as additional ResourceManager node  in dropdown 
box,  you will find that selected hosts in dropdown box cannot be displayed 
correctly in right text area 



 !screenshot-1.png! 

  was:
Current ResourceManager is on bigtop3.
If you select any other host as additional ResourceManager node  in dropdown 
box,  you will find that selected hosts in dropdown box cannot be displayed 
correctly in right text area 



 !screenshot-1.png! 


> Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Bigtop 3.2 cluster is deployed in local vm.
> Current ResourceManager is on bigtop3.
> If you select any other host as additional ResourceManager node  in dropdown 
> box,  you will find that selected hosts in dropdown box cannot be displayed 
> correctly in right text area 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed Correctly

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Summary: Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed 
Correctly   (was: Hosts in Step 2 of ResourceManager HA Wizard cannot be 
displayed correctly )

> Hosts in Step 2 of ResourceManager HA Wizard Cannot Be Displayed Correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Bigtop 3.2 cluster is deployed in local vm.
> Current ResourceManager is on bigtop3.
> If you select any other host as additional ResourceManager node  in dropdown 
> box,  you will find that selected hosts in dropdown box cannot be displayed 
> correctly in right text area 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Summary: Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed 
correctly   (was: Step 2 of ResourceManager HA Wizard Occurs Exception)

> Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3.
> If you select any other host as additional ResourceManager node  in dropdown 
> box,  you will find that selected hosts in dropdown box cannot be displayed 
> correctly in right text area 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Fix Version/s: trunk

> Hosts in Step 2 of ResourceManager HA Wizard cannot be displayed correctly 
> ---
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3.
> If you select any other host as additional ResourceManager node  in dropdown 
> box,  you will find that selected hosts in dropdown box cannot be displayed 
> correctly in right text area 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Current ResourceManager is on bigtop3.
If you select any other host as additional ResourceManager node  in dropdown 
box,  you will find that selected hosts in dropdown box cannot be displayed 
correctly in right text area 



 !screenshot-1.png! 

  was:
Current ResourceManager is on bigtop3.
If you select any other additional ResourceManager host in dropdown box,  you 
will see the exception. 



 !screenshot-1.png! 


> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3.
> If you select any other host as additional ResourceManager node  in dropdown 
> box,  you will find that selected hosts in dropdown box cannot be displayed 
> correctly in right text area 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Current ResourceManager is on bigtop3.
If you select any other additional ResourceManager host in dropdown box,  you 
will see the exception. 

 !screenshot-1.png! 

  was:
Current ResourceManager is on bigtop3,  if you select any other additional 
ResourceManager host in dropdown box, you will see the excpetion. 

 !screenshot-1.png! 


> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3.
> If you select any other additional ResourceManager host in dropdown box,  you 
> will see the exception. 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Current ResourceManager is on bigtop3.
If you select any other additional ResourceManager host in dropdown box,  you 
will see the exception. 



 !screenshot-1.png! 

  was:
Current ResourceManager is on bigtop3.
If you select any other additional ResourceManager host in dropdown box,  you 
will see the exception. 

 !screenshot-1.png! 


> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3.
> If you select any other additional ResourceManager host in dropdown box,  you 
> will see the exception. 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Current ResourceManager is on bigtop3,  if you select any other additional 
ResourceManager host in dropdown box, you will see the excpetion. 

 !screenshot-1.png! 

  was:
Current ResourceManager is on bigtop3,  if you select any other additional RM 
host in dropdown box

 !screenshot-1.png! 


> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3,  if you select any other additional 
> ResourceManager host in dropdown box, you will see the excpetion. 
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Attachment: screenshot-1.png

> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3,  if you select any other additional RM 
> host in dropdown box
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Attachment: (was: screenshot-1.png)

> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3,  if you select any other additional RM 
> host in dropdown box
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Description: 
Current ResourceManager is on bigtop3,  if you select any other additional RM 
host in dropdown box

 !screenshot-1.png! 

> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>
> Current ResourceManager is on bigtop3,  if you select any other additional RM 
> host in dropdown box
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25742:
-
Attachment: screenshot-1.png

> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Attachments: screenshot-1.png
>
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25742:


 Summary: Step 2 of ResourceManager HA Wizard Occurs Exception
 Key: AMBARI-25742
 URL: https://issues.apache.org/jira/browse/AMBARI-25742
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-25742) Step 2 of ResourceManager HA Wizard Occurs Exception

2022-09-27 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25742:


Assignee: Yao Lei

> Step 2 of ResourceManager HA Wizard Occurs Exception
> 
>
> Key: AMBARI-25742
> URL: https://issues.apache.org/jira/browse/AMBARI-25742
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
>




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Description: 
NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 











this patch aims to fix this issue

 !screenshot-1.png! 



  was:
NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 











this patch aims to fix this issue

 !screenshot-1.png! 




> Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error in BIGTOP 3.2.0 cluster
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Summary: Fails to enable NameNode HA   (was: Fails to enable NameNode HA in 
BIGTOP 3.2.0 cluster)

> Fails to enable NameNode HA 
> 
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Description: 
NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 











this patch aims to fix this issue

 !screenshot-1.png! 



  was:
NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 











this patch aims to fix this issue




> Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
> ---
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue
>  !screenshot-1.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Attachment: screenshot-1.png

> Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
> ---
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png, screenshot-1.png
>
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Description: 
NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 











this patch aims to fix this issue



  was:
NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 



> Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
> ---
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png
>
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 
> this patch aims to fix this issue



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Assigned] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25740:


Assignee: Yao Lei

> Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
> ---
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png
>
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Created] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)

Yao Lei created AMBARI-25740:


 Summary: Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
 Key: AMBARI-25740
 URL: https://issues.apache.org/jira/browse/AMBARI-25740
 Project: Ambari
  Issue Type: Bug
Reporter: Yao Lei
 Attachments: image-2022-09-26-18-17-33-337.png

NameNode HA wizard runs into an error.
The reason is that BIGTOP lacks relevant components.

 !image-2022-09-26-18-17-33-337.png! 




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25740) Fails to enable NameNode HA in BIGTOP 3.2.0 cluster

2022-09-26 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25740:
-
Fix Version/s: trunk

> Fails to enable NameNode HA in BIGTOP 3.2.0 cluster
> ---
>
> Key: AMBARI-25740
> URL: https://issues.apache.org/jira/browse/AMBARI-25740
> Project: Ambari
>  Issue Type: Bug
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: image-2022-09-26-18-17-33-337.png
>
>
> NameNode HA wizard runs into an error.
> The reason is that BIGTOP lacks relevant components.
>  !image-2022-09-26-18-17-33-337.png! 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Updated] (AMBARI-25735) Fix build failure on Ambari Agent due to maven-shade-plugin version

2022-09-24 Thread Yao Lei (Jira)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25735:
-
Fix Version/s: trunk
   2.8.0

> Fix build failure on Ambari Agent due to maven-shade-plugin version
> ---
>
> Key: AMBARI-25735
> URL: https://issues.apache.org/jira/browse/AMBARI-25735
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
> Environment: Ambari: trunk
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: trunk, 2.8.0
>
> Attachments: image-2022-09-21-16-12-10-861.png
>
>  Time Spent: 50m
>  Remaining Estimate: 0h
>
> !image-2022-09-21-16-12-10-861.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org

[jira] [Commented] (AMBARI-25669) The usage rate of Ambari Old memory is almost 100%, and cannot return to normal levels

2021-09-21 Thread Yao Lei (Jira)



[ 
https://issues.apache.org/jira/browse/AMBARI-25669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418391#comment-17418391
 ] 

Yao Lei commented on AMBARI-25669:
--

You can add cookie information to header of  http request

> The usage rate of Ambari Old memory is almost 100%, and cannot return to 
> normal levels
> --
>
> Key: AMBARI-25669
> URL: https://issues.apache.org/jira/browse/AMBARI-25669
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-sever
>Affects Versions: 2.7.3
> Environment: os type： linux
> Node env： 32cores 64GB
> three-nodes cluster
> ambari version:2.7.3
> Ambari memory： -Xmx8192m -Xms8192m
>Reporter: guluo
>Priority: Major
>
> A large number of HTTP requests to access Ambari over a period of time，the 
> usage rate of Ambari Old memory is almost 100%. When stopping HTTP requests， 
> the useage memory cannot return  to normal levels.
>  
> I executed command： jmap -histo:live | grep Session, and found the number of 
> Session instances is close to 2，and maintain this level for a long 
> time（sometim more than one day）.  Under normal circumstances, the number of 
> this object will not exceed 2000
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Status: Patch Available  (was: In Progress)

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-25206.patch, screenshot-1.png, screenshot-2.png, 
> screenshot-3.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei reassigned AMBARI-25206:


Assignee: Yao Lei

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-25206.patch, screenshot-1.png, screenshot-2.png, 
> screenshot-3.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Attachment: screenshot-3.png

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Attachment: AMBARI-25206.patch

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-25206.patch, screenshot-1.png, screenshot-2.png, 
> screenshot-3.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Attachment: screenshot-2.png

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Attachment: screenshot-1.png

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
> Attachments: screenshot-1.png
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Description: 
Assume that HDFS NameNode federation is enabled.
STR:
1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
2. Edit any widget, change threshhold value and click apply buttton.
3. Open the widget again and find threshhold value is not updated 
Details see the attached pictures

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated 
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Description: 
Assume that HDFS NameNode federation is enabled.
STR:
1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
2. Edit any widget, change threshhold value and click apply buttton.
3. Open the widget again and find threshhold value is not updated.
Details see the attached pictures

  was:
Assume that HDFS NameNode federation is enabled.
STR:
1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
2. Edit any widget, change threshhold value and click apply buttton.
3. Open the widget again and find threshhold value is not updated 
Details see the attached pictures


> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
>
> Assume that HDFS NameNode federation is enabled.
> STR:
> 1. Open Dashboard ->METRICS and scroll to the NAMESPACE.
> 2. Edit any widget, change threshhold value and click apply buttton.
> 3. Open the widget again and find threshhold value is not updated.
> Details see the attached pictures



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (AMBARI-25206) HDFS NameSpace Widgets Threshold Value Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)

Yao Lei created AMBARI-25206:


 Summary: HDFS NameSpace Widgets Threshold Value  Are Not Updated 
after Change
 Key: AMBARI-25206
 URL: https://issues.apache.org/jira/browse/AMBARI-25206
 Project: Ambari
  Issue Type: Improvement
Reporter: Yao Lei






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widget Threshold Values Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Summary: HDFS NameSpace Widget Threshold Values  Are Not Updated after 
Change  (was: HDFS NameSpace Widgets Threshold Value  Are Not Updated after 
Change)

> HDFS NameSpace Widget Threshold Values  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widgets Threshold Value Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Affects Version/s: trunk

> HDFS NameSpace Widgets Threshold Value  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (AMBARI-25206) HDFS NameSpace Widgets Threshold Value Are Not Updated after Change

2019-03-20 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-25206:
-
Fix Version/s: trunk

> HDFS NameSpace Widgets Threshold Value  Are Not Updated after Change
> 
>
> Key: AMBARI-25206
> URL: https://issues.apache.org/jira/browse/AMBARI-25206
> Project: Ambari
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Yao Lei
>Priority: Major
> Fix For: trunk
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-21216) Add support for consecutive login failure accounting

2018-08-05 Thread Yao Lei (JIRA)



[ 
https://issues.apache.org/jira/browse/AMBARI-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569704#comment-16569704
 ] 

Yao Lei commented on AMBARI-21216:
--

[~rlevas] 
Got it.Thanks for your explaination

> Add support for consecutive login failure accounting
> 
>
> Key: AMBARI-21216
> URL: https://issues.apache.org/jira/browse/AMBARI-21216
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-21216_branch-feature-AMBARI-20859_01.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_02.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_03.patch
>
>
> Add support for consecutive login failure accounting where as log-in failures 
> should increment the {{users.consecutive_failures}} and successful 
> authentication attempts should reset the value to 0.
> Concurrency should be kept in mind to handle simultaneous authentication 
> attempts for the same user.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (AMBARI-21216) Add support for consecutive login failure accounting

2018-08-04 Thread Yao Lei (JIRA)



[ 
https://issues.apache.org/jira/browse/AMBARI-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569386#comment-16569386
 ] 

Yao Lei edited comment on AMBARI-21216 at 8/5/18 6:34 AM:
--

Hi [~rlevas],
 If user is locked due to consecutive failures reach the allowed value, how can 
we unlock this user? Whether can we support the feature that user can be 
unlocked automaticlly beyond the setted period?


was (Author: yaolei):
Hi [~rlevas],
If user is locked due to consecutive failures reach the allowed value, how can 
we unlock this user?

> Add support for consecutive login failure accounting
> 
>
> Key: AMBARI-21216
> URL: https://issues.apache.org/jira/browse/AMBARI-21216
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-21216_branch-feature-AMBARI-20859_01.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_02.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_03.patch
>
>
> Add support for consecutive login failure accounting where as log-in failures 
> should increment the {{users.consecutive_failures}} and successful 
> authentication attempts should reset the value to 0.
> Concurrency should be kept in mind to handle simultaneous authentication 
> attempts for the same user.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-21216) Add support for consecutive login failure accounting

2018-08-04 Thread Yao Lei (JIRA)



[ 
https://issues.apache.org/jira/browse/AMBARI-21216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569386#comment-16569386
 ] 

Yao Lei commented on AMBARI-21216:
--

Hi [~rlevas],
If user is locked due to consecutive failures reach the allowed value, how can 
we unlock this user?

> Add support for consecutive login failure accounting
> 
>
> Key: AMBARI-21216
> URL: https://issues.apache.org/jira/browse/AMBARI-21216
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.0
>
> Attachments: AMBARI-21216_branch-feature-AMBARI-20859_01.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_02.patch, 
> AMBARI-21216_branch-feature-AMBARI-20859_03.patch
>
>
> Add support for consecutive login failure accounting where as log-in failures 
> should increment the {{users.consecutive_failures}} and successful 
> authentication attempts should reset the value to 0.
> Concurrency should be kept in mind to handle simultaneous authentication 
> attempts for the same user.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (AMBARI-13769) Ambari Automated Install with IPv6 hosts

2018-07-31 Thread Yao Lei (JIRA)



 [ 
https://issues.apache.org/jira/browse/AMBARI-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-13769:
-
Comment: was deleted

(was: Hi [~qzzeng]
Could you please tell me whether ambari support IPv6 hosts in your deployed 
cluster?
)

> Ambari Automated Install with IPv6 hosts
> 
>
> Key: AMBARI-13769
> URL: https://issues.apache.org/jira/browse/AMBARI-13769
> Project: Ambari
>  Issue Type: Test
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.2
> Environment: CentOS 7, IPv6 
>Reporter: zeng qijia
>Priority: Trivial
>
> All of the hosts are using IPv6 address with Cent OS 7, Cluster Install 
> Wizard ->Confirm Host section failed, log shows ambari agent can't access the 
> ambari host, but I just confirmed that log in from agent to server via 
> browser, and ssh without password are successful. Everything is okay if I 
> assign IPv4 address to hosts instead. I assume that it is cause by some hard 
> codes only works for IPv4 addresses in configure scripts.
> Here is the error in log:
> ==
> Running setup agent script...
> ==
> Command start time 2015-11-06 08:50:12
> Host registration aborted. Ambari Agent host cannot reach Ambari Server 
> 'm1.hdp2:8080'. Please check the network connectivity between the Ambari 
> Agent host and the Ambari Server
> Connection to m2.hdp2 closed.
> SSH command execution finished
> host=m2.hdp2, exitcode=1
> Command end time 2015-11-06 08:50:12
> ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with 
> non-zero exit code (1)
> ERROR MESSAGE: Connection to m2.hdp2 closed.
> STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari 
> Server 'm1.hdp2:8080'. Please check the network connectivity between the 
> Ambari Agent host and the Ambari Server
> Connection to m2.hdp2 closed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (AMBARI-13769) Ambari Automated Install with IPv6 hosts

2017-12-19 Thread Yao Lei (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-13769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296636#comment-16296636
 ] 

Yao Lei commented on AMBARI-13769:
--

Hi [~qzzeng]
Could you please tell me whether ambari support IPv6 hosts in your deployed 
cluster?


> Ambari Automated Install with IPv6 hosts
> 
>
> Key: AMBARI-13769
> URL: https://issues.apache.org/jira/browse/AMBARI-13769
> Project: Ambari
>  Issue Type: Test
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.1.2
> Environment: CentOS 7, IPv6 
>Reporter: zeng qijia
>Priority: Trivial
>
> All of the hosts are using IPv6 address with Cent OS 7, Cluster Install 
> Wizard ->Confirm Host section failed, log shows ambari agent can't access the 
> ambari host, but I just confirmed that log in from agent to server via 
> browser, and ssh without password are successful. Everything is okay if I 
> assign IPv4 address to hosts instead. I assume that it is cause by some hard 
> codes only works for IPv4 addresses in configure scripts.
> Here is the error in log:
> ==
> Running setup agent script...
> ==
> Command start time 2015-11-06 08:50:12
> Host registration aborted. Ambari Agent host cannot reach Ambari Server 
> 'm1.hdp2:8080'. Please check the network connectivity between the Ambari 
> Agent host and the Ambari Server
> Connection to m2.hdp2 closed.
> SSH command execution finished
> host=m2.hdp2, exitcode=1
> Command end time 2015-11-06 08:50:12
> ERROR: Bootstrap of host m2.hdp2 fails because previous action finished with 
> non-zero exit code (1)
> ERROR MESSAGE: Connection to m2.hdp2 closed.
> STDOUT: Host registration aborted. Ambari Agent host cannot reach Ambari 
> Server 'm1.hdp2:8080'. Please check the network connectivity between the 
> Ambari Agent host and the Ambari Server
> Connection to m2.hdp2 closed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (AMBARI-13852) Can't access the stack admin interface [Error 500]

2017-11-02 Thread Yao Lei (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-13852:
-
Comment: was deleted

(was: I find one solution, it works for me but i think it is not recommended.
Comment one line code in 
AmbariHandlerList#getHandler(org.apache.ambari.server.orm.entities.ViewInstanceEntity)
 like following:
{code:java}
//webAppContext.addFilter(new FilterHolder(springSecurityFilter), "/*", 
AmbariServer.DISPATCHER_TYPES);
{code}
)

> Can't access the stack admin interface [Error 500]
> --
>
> Key: AMBARI-13852
> URL: https://issues.apache.org/jira/browse/AMBARI-13852
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Loïc C. Chanel
>Priority: Blocker
>  Labels: ambari-server, stacktrace
>
> As I click on Stack & Version and then on the Manage Version button in the 
> Versions tab, I get an HTTP 500 Error, with the following stack : 
> HTTP ERROR 500
> Problem accessing /views/ADMIN_VIEW/2.1.2/INSTANCE/. Reason:
> Server Error
> Caused by:
> java.lang.IllegalStateException: No WebApplicationContext found: no 
> ContextLoaderListener registered?
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:159)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>   at 
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:209)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:197)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.handle(AmbariHandlerList.java:132)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>   at org.eclipse.jetty.server.Server.handle(Server.java:370)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
>   at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
>   at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>   at 
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers

2017-10-26 Thread Yao Lei (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-20739:
-
Comment: was deleted

(was: Sounds good.Thanks)

> Specify the script directly in alert target for script-based alert dispatchers
> --
>
> Key: AMBARI-20739
> URL: https://issues.apache.org/jira/browse/AMBARI-20739
> Project: Ambari
>  Issue Type: Task
>  Components: alerts, ambari-web
>Affects Versions: trunk
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
>
> Although we can create the alert target of type ALERT_SCRIPT by web ui 
> (AMBARI-18423), we still need access to ambari.properties to add the new 
> script and then  restart ambari server to make this function take effect.It 
> is better specify the script directly in alert target rather than in 
> ambari.properties.In this way,we also don't need to restart ambari server.
> So now on web ui we can offer two ways to configure the script location for 
> script-based alert dispatchers:
> 1.By script dispatch property (*ambari.dispatch-property.script*).This is 
> already supported in previous ambari release.
> Please see 
> https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0
> 2.By script filename(*ambari.dispatch-property.script.filename*).
> This new way will lookup the script by filename in script directory,default 
> in /var/lib/ambari-server/resources/scripts.
> We can change the directory in ambari.properties by 
> *notification.dispatch.alert.script.directory* property.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup

2017-10-26 Thread Yao Lei (JIRA)


 [ 
https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yao Lei updated AMBARI-21097:
-
Resolution: Won't Fix
Status: Resolved  (was: Patch Available)

> Edit notifications options are always grey but can click and open a popup
> -
>
> Key: AMBARI-21097
> URL: https://issues.apache.org/jira/browse/AMBARI-21097
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 2.5.3
>
> Attachments: AMBARI-21097.2.patch, AMBARI-21097.patch, 
> notification-2.png, notification.png
>
>
> Two Problems 
> Steps to reproduce problem one (see notifiction.png):
> 1.Open Alerts / Actions / Manage Alert Notifications
> 2.Create an alert notification named test
> 3.Select the created notification and click gear icon, you will find 
> Edit/Duplicate items are always grey but you can click and open a popup.
> Steps to reproduce problem two(see notification-2.png):
> 1.Open Alerts / Actions / Manage Alert Notifications and delete all 
> notifications if exit
> 2.Firstly click the gear icon and then click Edit(Duplicate) item,some errors 
> ouput in browser console.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-13852) Can't access the stack admin interface [Error 500]

2017-09-29 Thread Yao Lei (JIRA)


[ 
https://issues.apache.org/jira/browse/AMBARI-13852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16185653#comment-16185653
 ] 

Yao Lei commented on AMBARI-13852:
--

I find one solution, it works for me but i think it is not recommended.
Comment one line code in 
AmbariHandlerList#getHandler(org.apache.ambari.server.orm.entities.ViewInstanceEntity)
 like following:
{code:java}
//webAppContext.addFilter(new FilterHolder(springSecurityFilter), "/*", 
AmbariServer.DISPATCHER_TYPES);
{code}


> Can't access the stack admin interface [Error 500]
> --
>
> Key: AMBARI-13852
> URL: https://issues.apache.org/jira/browse/AMBARI-13852
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Loïc C. Chanel
>Priority: Blocker
>  Labels: ambari-server, stacktrace
>
> As I click on Stack & Version and then on the Manage Version button in the 
> Versions tab, I get an HTTP 500 Error, with the following stack : 
> HTTP ERROR 500
> Problem accessing /views/ADMIN_VIEW/2.1.2/INSTANCE/. Reason:
> Server Error
> Caused by:
> java.lang.IllegalStateException: No WebApplicationContext found: no 
> ContextLoaderListener registered?
>   at 
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:159)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>   at 
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:47)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1467)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:209)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:197)
>   at 
> org.apache.ambari.server.controller.AmbariHandlerList.handle(AmbariHandlerList.java:132)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>   at org.eclipse.jetty.server.Server.handle(Server.java:370)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)
>   at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
>   at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>   at 
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>   at java.lang.Thread.run(Thread.java:744)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

1 2 3 4 5 >

1 - 100 of 472 matches

Mail list logo