[jira] [Updated] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25461: - Status: Patch Available (was: Open) > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25461: Labels: pull-request-available (was: ) > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25461: Assignee: Antonenko Alexander > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
Antonenko Alexander created AMBARI-25461: Summary: Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir Key: AMBARI-25461 URL: https://issues.apache.org/jira/browse/AMBARI-25461 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.6.2 Reporter: Antonenko Alexander Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25459) Ambari doesn't show versions page after invalid repo was added
[
https://issues.apache.org/jira/browse/AMBARI-25459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Papirkovskyy Myroslav resolved AMBARI-25459.
Resolution: Fixed
Merged to branch-2.7.
> Ambari doesn't show versions page after invalid repo was added
> --
>
> Key: AMBARI-25459
> URL: https://issues.apache.org/jira/browse/AMBARI-25459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: Papirkovskyy Myroslav
>Assignee: Papirkovskyy Myroslav
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.6
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> # Deploy cluster.
> # Add repository version with ":" as credentials (set skip
> validation before saving).
> # Try to open versions page.
> ambari-server log:
> {code:java}
> 2020-01-18 00:45:14,915 ERROR [ambari-client-thread-388] ReadHandler:99 - Bad
> request:
> java.util.regex.PatternSyntaxException: Dangling meta character '*' near
> index 0
> *:*
> ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.sequence(Pattern.java:2123)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at java.lang.String.replaceFirst(String.java:2178)
> at
> org.apache.ambari.server.utils.URLCredentialsHider.hideCredentials(URLCredentialsHider.java:48)
> at
> org.apache.ambari.server.controller.internal.RepositoryResourceProvider.getResources(RepositoryResourceProvider.java:182)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:
> 965)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:139)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:482)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:454)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:164)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:128)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.getClusterStackVersions(ClusterStackVersionService.java:68)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (AMBARI-25459) Ambari doesn't show versions page after invalid repo was added
[
https://issues.apache.org/jira/browse/AMBARI-25459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020304#comment-17020304
]
Hudson commented on AMBARI-25459:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #647 (See
[https://builds.apache.org/job/Ambari-branch-2.7/647/])
AMBARI-25459. Ambari doesn't show versions page after invalid repo was (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d18e06b27c90dcd3fabf2dff70c39f4c95a3b5bc])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/utils/URLCredentialsHider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/utils/URLCredentialsHiderTest.java
> Ambari doesn't show versions page after invalid repo was added
> --
>
> Key: AMBARI-25459
> URL: https://issues.apache.org/jira/browse/AMBARI-25459
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.5
>Reporter: Papirkovskyy Myroslav
>Assignee: Papirkovskyy Myroslav
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.6
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> # Deploy cluster.
> # Add repository version with ":" as credentials (set skip
> validation before saving).
> # Try to open versions page.
> ambari-server log:
> {code:java}
> 2020-01-18 00:45:14,915 ERROR [ambari-client-thread-388] ReadHandler:99 - Bad
> request:
> java.util.regex.PatternSyntaxException: Dangling meta character '*' near
> index 0
> *:*
> ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.sequence(Pattern.java:2123)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at java.lang.String.replaceFirst(String.java:2178)
> at
> org.apache.ambari.server.utils.URLCredentialsHider.hideCredentials(URLCredentialsHider.java:48)
> at
> org.apache.ambari.server.controller.internal.RepositoryResourceProvider.getResources(RepositoryResourceProvider.java:182)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:
> 965)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:139)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:482)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForSubResources(QueryImpl.java:503)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:454)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:164)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:128)
> at
> org.apache.ambari.server.api.services.ClusterStackVersionService.getClusterStackVersions(ClusterStackVersionService.java:68)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (AMBARI-24028) can't do ldap sync with ambari on https
[ https://issues.apache.org/jira/browse/AMBARI-24028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko resolved AMBARI-24028. - Resolution: Duplicate > can't do ldap sync with ambari on https > --- > > Key: AMBARI-24028 > URL: https://issues.apache.org/jira/browse/AMBARI-24028 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Charles Hedrick >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.0 > > > I converted ambari to https. Then I tried to do ldap sync. Got an error that > 127.0.0.1 didn't match my hostname. ldap sync starts by making a connection > to the ambari server. That needs to done using https, which require the > certificate the match the hostname. But by hardcoding 127.0.0.1 as the > hostname, you generate a mismatch. > in /usr/lib/python2.6/site-packages/ambari_server/serverUtils.py, > SERVER_API_HOST needs to be computed, not hardwire. By hardwiring it to my > hostname I got things to proceed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-24028) can't do ldap sync with ambari on https
[ https://issues.apache.org/jira/browse/AMBARI-24028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-24028: Fix Version/s: 2.7.0 > can't do ldap sync with ambari on https > --- > > Key: AMBARI-24028 > URL: https://issues.apache.org/jira/browse/AMBARI-24028 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Charles Hedrick >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.0 > > > I converted ambari to https. Then I tried to do ldap sync. Got an error that > 127.0.0.1 didn't match my hostname. ldap sync starts by making a connection > to the ambari server. That needs to done using https, which require the > certificate the match the hostname. But by hardcoding 127.0.0.1 as the > hostname, you generate a mismatch. > in /usr/lib/python2.6/site-packages/ambari_server/serverUtils.py, > SERVER_API_HOST needs to be computed, not hardwire. By hardwiring it to my > hostname I got things to proceed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-24028) can't do ldap sync with ambari on https
[ https://issues.apache.org/jira/browse/AMBARI-24028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17020271#comment-17020271 ] Dmitry Lysnichenko commented on AMBARI-24028: - [~agrams], thank you for reporting that. Actually, that is already fixed at AMBARI-23382 > can't do ldap sync with ambari on https > --- > > Key: AMBARI-24028 > URL: https://issues.apache.org/jira/browse/AMBARI-24028 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Charles Hedrick >Assignee: Dmitry Lysnichenko >Priority: Major > > I converted ambari to https. Then I tried to do ldap sync. Got an error that > 127.0.0.1 didn't match my hostname. ldap sync starts by making a connection > to the ambari server. That needs to done using https, which require the > certificate the match the hostname. But by hardcoding 127.0.0.1 as the > hostname, you generate a mismatch. > in /usr/lib/python2.6/site-packages/ambari_server/serverUtils.py, > SERVER_API_HOST needs to be computed, not hardwire. By hardwiring it to my > hostname I got things to proceed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-24028) can't do ldap sync with ambari on https
[ https://issues.apache.org/jira/browse/AMBARI-24028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko reassigned AMBARI-24028: --- Assignee: Dmitry Lysnichenko > can't do ldap sync with ambari on https > --- > > Key: AMBARI-24028 > URL: https://issues.apache.org/jira/browse/AMBARI-24028 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Charles Hedrick >Assignee: Dmitry Lysnichenko >Priority: Major > > I converted ambari to https. Then I tried to do ldap sync. Got an error that > 127.0.0.1 didn't match my hostname. ldap sync starts by making a connection > to the ambari server. That needs to done using https, which require the > certificate the match the hostname. But by hardcoding 127.0.0.1 as the > hostname, you generate a mismatch. > in /usr/lib/python2.6/site-packages/ambari_server/serverUtils.py, > SERVER_API_HOST needs to be computed, not hardwire. By hardwiring it to my > hostname I got things to proceed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
