[jira] [Created] (AMBARI-24524) nable to validate password complexity for properties rangertagsync_user_password, rangerusersync_user_password
Andrii Tkach created AMBARI-24524:
-
Summary: nable to validate password complexity for properties
rangertagsync_user_password, rangerusersync_user_password
Key: AMBARI-24524
URL: https://issues.apache.org/jira/browse/AMBARI-24524
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.2
STR
- perform UI deploy with selecting Ranger & Ranger KMS
Used password: {{78C%4KwS5J$&}} or any other, created by password generator
with defined complexity
Additionally, check on glitches picture 1 & 2. Additionally, I believe it is
best to put special characters to grayed/dashed box to make user attention to
them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24524) nable to validate password complexity for properties rangertagsync_user_password, rangerusersync_user_password
[
https://issues.apache.org/jira/browse/AMBARI-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-24524:
--
Attachment: ui_glitches.PNG
> nable to validate password complexity for properties
> rangertagsync_user_password, rangerusersync_user_password
> --
>
> Key: AMBARI-24524
> URL: https://issues.apache.org/jira/browse/AMBARI-24524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.7.2
>
> Attachments: ui_glitches.PNG
>
>
> STR
> - perform UI deploy with selecting Ranger & Ranger KMS
> Used password: {{78C%4KwS5J$&}} or any other, created by password generator
> with defined complexity
> Additionally, check on glitches picture 1 & 2. Additionally, I believe it is
> best to put special characters to grayed/dashed box to make user attention to
> them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24524) Unable to validate password complexity for properties rangertagsync_user_password, rangerusersync_user_password
[
https://issues.apache.org/jira/browse/AMBARI-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-24524:
--
Summary: Unable to validate password complexity for properties
rangertagsync_user_password, rangerusersync_user_password (was: nable to
validate password complexity for properties rangertagsync_user_password,
rangerusersync_user_password)
> Unable to validate password complexity for properties
> rangertagsync_user_password, rangerusersync_user_password
> ---
>
> Key: AMBARI-24524
> URL: https://issues.apache.org/jira/browse/AMBARI-24524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.7.2
>
> Attachments: ui_glitches.PNG
>
>
> STR
> - perform UI deploy with selecting Ranger & Ranger KMS
> Used password: {{78C%4KwS5J$&}} or any other, created by password generator
> with defined complexity
> Additionally, check on glitches picture 1 & 2. Additionally, I believe it is
> best to put special characters to grayed/dashed box to make user attention to
> them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24524) Unable to validate password complexity for properties rangertagsync_user_password, rangerusersync_user_password
[
https://issues.apache.org/jira/browse/AMBARI-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24524:
Labels: pull-request-available (was: )
> Unable to validate password complexity for properties
> rangertagsync_user_password, rangerusersync_user_password
> ---
>
> Key: AMBARI-24524
> URL: https://issues.apache.org/jira/browse/AMBARI-24524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Attachments: ui_glitches.PNG
>
>
> STR
> - perform UI deploy with selecting Ranger & Ranger KMS
> Used password: {{78C%4KwS5J$&}} or any other, created by password generator
> with defined complexity
> Additionally, check on glitches picture 1 & 2. Additionally, I believe it is
> best to put special characters to grayed/dashed box to make user attention to
> them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24521) CLONE - Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-24521. Resolution: Fixed Merged to trunk. > CLONE - Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24521 > URL: https://issues.apache.org/jira/browse/AMBARI-24521 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24521) CLONE - Requests STOMP topic sent updates for host check request
[ https://issues.apache.org/jira/browse/AMBARI-24521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588776#comment-16588776 ] Hudson commented on AMBARI-24521: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9881 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9881/]) AMBARI-24521. CLONE - Requests STOMP topic sent updates for host check (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=d497004d39639102d4092509ef8d955840bf3ecc]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/events/listeners/tasks/TaskStatusListener.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionDBAccessorImpl.java > CLONE - Requests STOMP topic sent updates for host check request > > > Key: AMBARI-24521 > URL: https://issues.apache.org/jira/browse/AMBARI-24521 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Server should post only cluster related request updates to "/events/requests" > STOMP topic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
[ https://issues.apache.org/jira/browse/AMBARI-24458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24458: Labels: pull-request-available (was: ) > Start operation is disabled for HDFS after stopping components for one > namespace > > > Key: AMBARI-24458 > URL: https://issues.apache.org/jira/browse/AMBARI-24458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 > Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 > ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot > 2018-08-10 at 10.17.01 AM.png > > > Start operation is disabled for HDFS after stopping components for one > namespace > > STR: > 1) On hdfs service page, stop components for one namespace (ns1) > 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24426) [Log Search UI] Show user friendly component names in Log Index Filter screen
[ https://issues.apache.org/jira/browse/AMBARI-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24426: Labels: pull-request-available (was: ) > [Log Search UI] Show user friendly component names in Log Index Filter screen > - > > Key: AMBARI-24426 > URL: https://issues.apache.org/jira/browse/AMBARI-24426 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Original Estimate: 6h > Remaining Estimate: 6h > > Show the user friendly component names on the screen of the Log Index Filter, > where the filter level can be set up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-24525:
--
Description:
In a manually setup federated cluster (not through deployNG) --
Accumulo was installed and when trying to start, below error thrown --
{noformat}
2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
'org.apache.accumulo.master.state.SetGoalState' died.
java.lang.IllegalArgumentException: Expected fully qualified URI for
instance.volumes got ns2/apps/accumulo/data
at
org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
{noformat}
Caused by incorrect config value:
*instance.volumes = hdfs://ns1,ns2/apps/accumulo/data*
where ns1 and ns2 are namespaces
*Expected is --*
*instance.volumes = hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data*
according to --
https://accumulo.apache.org/docs/2.0/administration/multivolume
was:
In a manually setup federated cluster (not through deployNG) --
Accumulo was installed and when trying to start, below error thrown --
2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
'org.apache.accumulo.master.state.SetGoalState' died.
java.lang.IllegalArgumentException: Expected fully qualified URI for
instance.volumes got ns2/apps/accumulo/data
at
org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
Caused by incorrect config value:
*instance.volumes = hdfs://ns1,ns2/apps/accumulo/data*
where ns1 and ns2 are namespaces
*Expected is --*
*instance.volumes = hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data*
according to --
https://accumulo.apache.org/docs/2.0/administration/multivolume
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.7.2
>
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> *instance.volumes = hdfs://ns1,ns2/apps/accumulo/data*
> where ns1 and ns2 are namespaces
> *Expected is --*
> *instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data*
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24525) Accumulo does not startup in Federated Cluster
Andrii Babiichuk created AMBARI-24525: - Summary: Accumulo does not startup in Federated Cluster Key: AMBARI-24525 URL: https://issues.apache.org/jira/browse/AMBARI-24525 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.2 In a manually setup federated cluster (not through deployNG) -- Accumulo was installed and when trying to start, below error thrown -- 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread 'org.apache.accumulo.master.state.SetGoalState' died. java.lang.IllegalArgumentException: Expected fully qualified URI for instance.volumes got ns2/apps/accumulo/data at org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107) at org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334) Caused by incorrect config value: *instance.volumes = hdfs://ns1,ns2/apps/accumulo/data* where ns1 and ns2 are namespaces *Expected is --* *instance.volumes = hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data* according to -- https://accumulo.apache.org/docs/2.0/administration/multivolume -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-24525:
--
Description:
In a manually setup federated cluster (not through deployNG) --
Accumulo was installed and when trying to start, below error thrown --
{noformat}
2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
'org.apache.accumulo.master.state.SetGoalState' died.
java.lang.IllegalArgumentException: Expected fully qualified URI for
instance.volumes got ns2/apps/accumulo/data
at
org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
{noformat}
Caused by incorrect config value:
{{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
where ns1 and ns2 are namespaces
Expected is --
{{instance.volumes =
hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
according to --
https://accumulo.apache.org/docs/2.0/administration/multivolume
was:
In a manually setup federated cluster (not through deployNG) --
Accumulo was installed and when trying to start, below error thrown --
{noformat}
2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
'org.apache.accumulo.master.state.SetGoalState' died.
java.lang.IllegalArgumentException: Expected fully qualified URI for
instance.volumes got ns2/apps/accumulo/data
at
org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
at
org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
{noformat}
Caused by incorrect config value:
*instance.volumes = hdfs://ns1,ns2/apps/accumulo/data*
where ns1 and ns2 are namespaces
*Expected is --*
*instance.volumes = hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data*
according to --
https://accumulo.apache.org/docs/2.0/administration/multivolume
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.7.2
>
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24525:
Labels: pull-request-available (was: )
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.2
>
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
Andrew Onischuk created AMBARI-24526: Summary: Status of components does not become RED if their deamon goes down immediately after successful start Key: AMBARI-24526 URL: https://issues.apache.org/jira/browse/AMBARI-24526 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.1 Attachments: AMBARI-24526.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24526: - Attachment: AMBARI-24526.patch > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24526.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24526: - Status: Patch Available (was: Open) > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24526.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24526: Labels: pull-request-available (was: ) > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24526.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24527: - Attachment: AMBARI-24527.patch > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24527: - Status: Patch Available (was: Open) > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24527: - Attachment: AMBARI-24527.patch > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
Andrew Onischuk created AMBARI-24527: Summary: Unable to Add ZooKeeper-Only Host To Cluster With Hadoop Key: AMBARI-24527 URL: https://issues.apache.org/jira/browse/AMBARI-24527 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.1 Attachments: AMBARI-24527.patch, AMBARI-24527.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-24527: - Attachment: AMBARI-24527.patch > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24527: Labels: pull-request-available (was: ) > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24526: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24526.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24527: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589714#comment-16589714 ] Hudson commented on AMBARI-24527: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #199 (See [https://builds.apache.org/job/Ambari-branch-2.7/199/]) AMBARI-24527. Unable to Add ZooKeeper-Only Host To Cluster With Hadoop (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=033079ebf6731df734dd8ecdfec56c4d861c0e1d]) * (edit) ambari-server/src/main/resources/stack-hooks/before-START/scripts/shared_initialization.py > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589789#comment-16589789 ] Hudson commented on AMBARI-24526: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9883 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9883/]) AMBARI-24526. Status of components does not become RED if their deamon (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=500a00b92c76f7444665865a42f26fe356cb28a9]) * (edit) ambari-agent/src/main/python/ambari_agent/CustomServiceOrchestrator.py > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: AMBARI-24526.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
