[jira] [Commented] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348083#comment-16348083
]
Hudson commented on AMBARI-22864:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8665 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8665/])
AMBARI-22864. Agent commands hang even after freeing up disk space on
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=bee9c2b115345f174a50d8f72033539a1a3ca12d])
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch,
> AMBARI-22864.patch, AMBARI-22864.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348077#comment-16348077
]
Hudson commented on AMBARI-22864:
-
SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #589 (See
[https://builds.apache.org/job/Ambari-branch-2.6/589/])
AMBARI-22864. Agent commands hang even after freeing up disk space on
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=582e35088a2560312b50a305af32f89e38ca0944])
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch,
> AMBARI-22864.patch, AMBARI-22864.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account
[ https://issues.apache.org/jira/browse/AMBARI-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14163: Description: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. was: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. > zookeeper session timeout for hbase should take zookeeper tickTime into > account > --- > > Key: AMBARI-14163 > URL: https://issues.apache.org/jira/browse/AMBARI-14163 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Major > > With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value > of 1 min 40 seconds. > The change was accepted. > However, such timeout is not reachable (it is > 20 times tickTime). > Ambari should detect such scenario and warn user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22621) Ensure value for hbase.coprocessor.abortonerror is true
[ https://issues.apache.org/jira/browse/AMBARI-22621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-22621: Description: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. was: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. > Ensure value for hbase.coprocessor.abortonerror is true > --- > > Key: AMBARI-22621 > URL: https://issues.apache.org/jira/browse/AMBARI-22621 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > In the coprocessor refactor for hbase-2, Server#abort has been taken out of > reach. > We should ensure that value for hbase.coprocessor.abortonerror is true so > that coprocessor can abort the server by throwing exception. > See HBASE-19341 for related details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22822) Zeppelin's notebook-authorization.json doesn't get copied to HDFS on upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22822: Labels: pull-request-available (was: ) > Zeppelin's notebook-authorization.json doesn't get copied to HDFS on upgrade > > > Key: AMBARI-22822 > URL: https://issues.apache.org/jira/browse/AMBARI-22822 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.6.2 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh >Priority: Major > Labels: pull-request-available > > Zeppelin's notebook-authorization.json doesn't get copied to HDFS on upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22823) On upgrade all Zeppelin's interpreters are listed twice, with the exact same configuration.
[ https://issues.apache.org/jira/browse/AMBARI-22823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22823: Labels: pull-request-available (was: ) > On upgrade all Zeppelin's interpreters are listed twice, with the exact same > configuration. > --- > > Key: AMBARI-22823 > URL: https://issues.apache.org/jira/browse/AMBARI-22823 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh >Priority: Major > Labels: pull-request-available > > On upgrade all Zeppelin's interpreters are listed twice, with the exact same > configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Description:
cluster with only the service of zookeeper.
when start zk, error is like this:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 40, in
BeforeStartHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 314, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 28, in hook
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
line 320, in
if namenode_rpc:
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
was not found in configurations dictionary!
Error: Error: Unable to run the custom hook script ['/usr/bin/python',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
'START', '/var/lib/ambari-agent/data/command-31.json',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
'/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
'/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
was:
cluster with only the service of zookeeper.
when start zk, error is like this
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[
https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangxiaolu updated AMBARI-22894:
-
Status: Patch Available (was: Open)
> Install zk error when cluster just only installed zk.
> -
>
> Key: AMBARI-22894
> URL: https://issues.apache.org/jira/browse/AMBARI-22894
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
> Environment: cluster with only the service of zookeeper
>Reporter: zhangxiaolu
>Assignee: zhangxiaolu
>Priority: Major
> Fix For: trunk
>
> Attachments: AMBARI-22894.patch, screenshot-1.png
>
>
> cluster with only the service of zookeeper.
>
> when start zk, error is like this:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 40, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 314, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 28, in hook
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py",
> line 320, in
> if namenode_rpc:
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter 'core-site'
> was not found in configurations dictionary!
> Error: Error: Unable to run the custom hook script ['/usr/bin/python',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-31.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-31.json', 'INFO',
> '/var/lib/ambari-agent/tmp', 'PROTOCOL_TLSv1']
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Attachment: screenshot-1.png > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-22894.patch, screenshot-1.png > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22893) Update rat check rules for stack files
[ https://issues.apache.org/jira/browse/AMBARI-22893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22893: Labels: pull-request-available (was: ) > Update rat check rules for stack files > -- > > Key: AMBARI-22893 > URL: https://issues.apache.org/jira/browse/AMBARI-22893 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Attachment: AMBARI-22894.patch > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > Attachments: AMBARI-22894.patch > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22894) Install zk error when cluster just only installed zk.
[ https://issues.apache.org/jira/browse/AMBARI-22894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhangxiaolu updated AMBARI-22894: - Description: cluster with only the service of zookeeper. when start zk, error is like this > Install zk error when cluster just only installed zk. > - > > Key: AMBARI-22894 > URL: https://issues.apache.org/jira/browse/AMBARI-22894 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk > Environment: cluster with only the service of zookeeper >Reporter: zhangxiaolu >Assignee: zhangxiaolu >Priority: Major > Fix For: trunk > > > cluster with only the service of zookeeper. > > when start zk, error is like this -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22894) Install zk error when cluster just only installed zk.
zhangxiaolu created AMBARI-22894: Summary: Install zk error when cluster just only installed zk. Key: AMBARI-22894 URL: https://issues.apache.org/jira/browse/AMBARI-22894 Project: Ambari Issue Type: Bug Affects Versions: trunk Environment: cluster with only the service of zookeeper Reporter: zhangxiaolu Assignee: zhangxiaolu Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22893) Update rat check rules for stack files
Jayush Luniya created AMBARI-22893: -- Summary: Update rat check rules for stack files Key: AMBARI-22893 URL: https://issues.apache.org/jira/browse/AMBARI-22893 Project: Ambari Issue Type: Bug Components: stacks Affects Versions: trunk Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: trunk -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22873) Remove HDP 3.0 stack from Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-22873. Resolution: Fixed > Remove HDP 3.0 stack from Ambari > > > Key: AMBARI-22873 > URL: https://issues.apache.org/jira/browse/AMBARI-22873 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: trunk >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: trunk > > Time Spent: 0.5h > Remaining Estimate: 0h > > Remove HDP-3.0 stack definition from Ambari. Management Packs will replace > stacks in Ambari 3.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22892) Ambari 2.99.99 lists services that are not present in Atlantic-Beta1
[ https://issues.apache.org/jira/browse/AMBARI-22892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22892: --- Status: Patch Available (was: Open) > Ambari 2.99.99 lists services that are not present in Atlantic-Beta1 > > > Key: AMBARI-22892 > URL: https://issues.apache.org/jira/browse/AMBARI-22892 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.7.0 > > Attachments: AMBARI-22892.patch > > > Remove these services from list > - Sqoop > - Oozie > - Storm > - Slider -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22892) Ambari 2.99.99 lists services that are not present in Atlantic-Beta1
[ https://issues.apache.org/jira/browse/AMBARI-22892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22892: --- Attachment: AMBARI-22892.patch > Ambari 2.99.99 lists services that are not present in Atlantic-Beta1 > > > Key: AMBARI-22892 > URL: https://issues.apache.org/jira/browse/AMBARI-22892 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Blocker > Fix For: 2.7.0 > > Attachments: AMBARI-22892.patch > > > Remove these services from list > - Sqoop > - Oozie > - Storm > - Slider -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22892) Ambari 2.99.99 lists services that are not present in Atlantic-Beta1
Vitaly Brodetskyi created AMBARI-22892: -- Summary: Ambari 2.99.99 lists services that are not present in Atlantic-Beta1 Key: AMBARI-22892 URL: https://issues.apache.org/jira/browse/AMBARI-22892 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.7.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Fix For: 2.7.0 Remove these services from list - Sqoop - Oozie - Storm - Slider -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-22891:
--
Fix Version/s: 2.6.2
Status: Patch Available (was: In Progress)
> Logging improvement during the Upgrade when there is invalid Alert definition
> -
>
> Key: AMBARI-22891
> URL: https://issues.apache.org/jira/browse/AMBARI-22891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: amarnath reddy pappu
>Priority: Major
> Fix For: 2.6.2
>
> Attachments: AMBARI-22891.txt
>
>
> If there is invalid definition/json in alert definition then Upgrade would
> fail with below exception. there is no way to determine which alert is
> causing the issue here.
> its not clear how this alert definition gets corrupted but we have seen this
> with 3 to 4 customers already - printing the alert definition name would he
> helpful in support point of view to determine the root cause.. other wise it
> is very difficult to find it out - had a give a dev patch to customers to
> find it out.
> {noformat}
> 29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
> deserialize the alert definition source during coercion
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected STRING but was BEGIN_OBJECT
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:859)
> at com.google.gson.Gson$2.deserialize(Gson.java:131)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
> at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:761)
> at com.google.gson.Gson.fromJson(Gson.java:710)
> at com.google.gson.Gson.fromJson(Gson.java:682)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.IllegalStateException: Expected STRING but was
> BEGIN_OBJECT
> at
> com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
> ... 16 more
> 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> 29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.NullPointerException
> at
>
[jira] [Updated] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-22891:
--
Attachment: AMBARI-22891.txt
> Logging improvement during the Upgrade when there is invalid Alert definition
> -
>
> Key: AMBARI-22891
> URL: https://issues.apache.org/jira/browse/AMBARI-22891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: amarnath reddy pappu
>Priority: Major
> Attachments: AMBARI-22891.txt
>
>
> If there is invalid definition/json in alert definition then Upgrade would
> fail with below exception. there is no way to determine which alert is
> causing the issue here.
> its not clear how this alert definition gets corrupted but we have seen this
> with 3 to 4 customers already - printing the alert definition name would he
> helpful in support point of view to determine the root cause.. other wise it
> is very difficult to find it out - had a give a dev patch to customers to
> find it out.
> {noformat}
> 29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
> deserialize the alert definition source during coercion
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected STRING but was BEGIN_OBJECT
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:859)
> at com.google.gson.Gson$2.deserialize(Gson.java:131)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
> at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:761)
> at com.google.gson.Gson.fromJson(Gson.java:710)
> at com.google.gson.Gson.fromJson(Gson.java:682)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.IllegalStateException: Expected STRING but was
> BEGIN_OBJECT
> at
> com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
> ... 16 more
> 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> 29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
[jira] [Updated] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-22891:
--
Description:
If there is invalid definition/json in alert definition then Upgrade would fail
with below exception. there is no way to determine which alert is causing the
issue here.
its not clear how this alert definition gets corrupted but we have seen this
with 3 to 4 customers already - printing the alert definition name would he
helpful in support point of view to determine the root cause.. other wise it is
very difficult to find it out - had a give a dev patch to customers to find it
out.
{noformat}
29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
deserialize the alert definition source during coercion
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected
STRING but was BEGIN_OBJECT
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
at com.google.gson.Gson.fromJson(Gson.java:795)
at com.google.gson.Gson.fromJson(Gson.java:859)
at com.google.gson.Gson$2.deserialize(Gson.java:131)
at
org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
at
org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
at com.google.gson.Gson.fromJson(Gson.java:795)
at com.google.gson.Gson.fromJson(Gson.java:761)
at com.google.gson.Gson.fromJson(Gson.java:710)
at com.google.gson.Gson.fromJson(Gson.java:682)
at
org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
Caused by: java.lang.IllegalStateException: Expected STRING but was BEGIN_OBJECT
at
com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
at
com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
at
com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
... 16 more
29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 - Upgrade failed.
java.lang.NullPointerException
at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
occurred during upgrade, failed
org.apache.ambari.server.AmbariException
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
Caused by: java.lang.NullPointerException
at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
... 1 more
{noformat}
was:
If there is invalid definition/json in alert definition then Upgrade would fail
with below exception. there is no way to determine which alert is causing the
issue here.
its not clear how this alert definition gets corrupted but we have seen this
with 3 to 4 customers
[jira] [Created] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
amarnath reddy pappu created AMBARI-22891:
-
Summary: Logging improvement during the Upgrade when there is
invalid Alert definition
Key: AMBARI-22891
URL: https://issues.apache.org/jira/browse/AMBARI-22891
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.1
Reporter: amarnath reddy pappu
If there is invalid definition/json in alert definition then Upgrade would fail
with below exception. there is no way to determine which alert is causing the
issue here.
its not clear how this alert definition gets corrupted but we have seen this
with 3 to 4 customers already - printing the alert definition name would he
helpful in support point of view to determine the root cause.. other wise it is
very difficult to find it out - had a give a dev patch to customers to find it
out.
{noformat}
*no* further _formatting_ is done here{noformat}
29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
deserialize the alert definition source during coercion
com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected
STRING but was BEGIN_OBJECT at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
at com.google.gson.Gson.fromJson(Gson.java:795) at
com.google.gson.Gson.fromJson(Gson.java:859) at
com.google.gson.Gson$2.deserialize(Gson.java:131) at
org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
at
org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58) at
com.google.gson.Gson.fromJson(Gson.java:795) at
com.google.gson.Gson.fromJson(Gson.java:761) at
com.google.gson.Gson.fromJson(Gson.java:710) at
com.google.gson.Gson.fromJson(Gson.java:682) at
org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
Caused by: java.lang.IllegalStateException: Expected STRING but was
BEGIN_OBJECT at
com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
at com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
at com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337) at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
at
com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
... 16 more 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 -
Upgrade failed. java.lang.NullPointerException at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
occurred during upgrade, failed org.apache.ambari.server.AmbariException at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
Caused by: java.lang.NullPointerException at
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
at
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
... 1 more
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu reassigned AMBARI-22891:
-
Assignee: amarnath reddy pappu
> Logging improvement during the Upgrade when there is invalid Alert definition
> -
>
> Key: AMBARI-22891
> URL: https://issues.apache.org/jira/browse/AMBARI-22891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: amarnath reddy pappu
>Priority: Major
>
> If there is invalid definition/json in alert definition then Upgrade would
> fail with below exception. there is no way to determine which alert is
> causing the issue here.
> its not clear how this alert definition gets corrupted but we have seen this
> with 3 to 4 customers already - printing the alert definition name would he
> helpful in support point of view to determine the root cause.. other wise it
> is very difficult to find it out - had a give a dev patch to customers to
> find it out.
> {noformat}
> *no* further _formatting_ is done here{noformat}
> 29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
> deserialize the alert definition source during coercion
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected STRING but was BEGIN_OBJECT at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
> at com.google.gson.Gson.fromJson(Gson.java:795) at
> com.google.gson.Gson.fromJson(Gson.java:859) at
> com.google.gson.Gson$2.deserialize(Gson.java:131) at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
> at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58) at
> com.google.gson.Gson.fromJson(Gson.java:795) at
> com.google.gson.Gson.fromJson(Gson.java:761) at
> com.google.gson.Gson.fromJson(Gson.java:710) at
> com.google.gson.Gson.fromJson(Gson.java:682) at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.IllegalStateException: Expected STRING but was
> BEGIN_OBJECT at
> com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
> at com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
> at com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
> ... 16 more 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 -
> Upgrade failed. java.lang.NullPointerException at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> 29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
> occurred during upgrade, failed org.apache.ambari.server.AmbariException at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.NullPointerException at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
>
[jira] [Updated] (AMBARI-22890) LogSearch Integration support for external Shared LogSearch Server connections
[ https://issues.apache.org/jira/browse/AMBARI-22890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22890: Labels: pull-request-available (was: ) > LogSearch Integration support for external Shared LogSearch Server connections > -- > > Key: AMBARI-22890 > URL: https://issues.apache.org/jira/browse/AMBARI-22890 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22864:
-
Attachment: AMBARI-22864.patch
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch,
> AMBARI-22864.patch, AMBARI-22864.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22864:
Labels: pull-request-available system_test (was: system_test)
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch,
> AMBARI-22864.patch
>
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22830) Ambari-agent puts Python scripts in 2.6 directory on OSes that use python 2.7.x by default
[ https://issues.apache.org/jira/browse/AMBARI-22830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347589#comment-16347589 ] Hudson commented on AMBARI-22830: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8664 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8664/]) AMBARI-22830. Ambari-agent puts Python scripts in 2.6 directory on OSes (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=0bc48df2015432a0232db3bfdbcc2f139b187ae2]) * (edit) ambari-server/src/main/python/bootstrap.py * (edit) ambari-agent/conf/unix/ambari-agent * (edit) ambari-server/conf/ambari-env.sh * (edit) ambari-server/conf/unix/install-helper.sh * (edit) ambari-server/src/main/resources/scripts/Ambaripreupload.py * (edit) ambari-agent/src/main/python/ambari_agent/AmbariAgent.py * (edit) ambari-server/pom.xml * (edit) ambari-server/src/main/resources/scripts/check_ambari_permissions.py * (edit) ambari-server/src/main/package/rpm/posttrans_server.sh * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java * (edit) ambari-server/src/main/assemblies/server.xml * (edit) ambari-agent/pom.xml * (edit) ambari-agent/src/main/python/ambari_agent/HostCleanup.py * (edit) ambari-agent/conf/unix/install-helper.sh * (edit) ambari-server/conf/unix/ambari-env.sh * (edit) ambari-agent/conf/unix/ambari-env.sh * (edit) ambari-server/conf/unix/ambari.properties * (edit) ambari-agent/src/main/package/rpm/posttrans_agent.sh * (edit) ambari-server/src/main/resources/scripts/kerberos-setup.sh > Ambari-agent puts Python scripts in 2.6 directory on OSes that use python > 2.7.x by default > -- > > Key: AMBARI-22830 > URL: https://issues.apache.org/jira/browse/AMBARI-22830 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22830.patch, AMBARI-22830.patch, > AMBARI-22830.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > User needs to upgrade all OSes for security purposes, and will need to remove > all directories related to Python2.6 due to > TLS violations, they need this ASAP to test, as they have a hard deadline. > OS: Red Hat Enterprise Linux Server release 7.4 > JDK version: 1.8.0_144 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22864:
-
Attachment: AMBARI-22864.patch
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch,
> AMBARI-22864.patch
>
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22864:
-
Status: Patch Available (was: Open)
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch
>
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22864:
-
Attachment: AMBARI-22864.patch
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch
>
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22864) Agent commands hang even after freeing up disk space on the host
[
https://issues.apache.org/jira/browse/AMBARI-22864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22864:
-
Attachment: AMBARI-22864.patch
> Agent commands hang even after freeing up disk space on the host
>
>
> Key: AMBARI-22864
> URL: https://issues.apache.org/jira/browse/AMBARI-22864
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: system_test
> Fix For: 2.6.2
>
> Attachments: AMBARI-22864.patch, AMBARI-22864.patch
>
>
> *STR*
> # Install a cluster with Ambari-2.6.2 and HDP-2.6.4.0
> # Go the host (say host1) running Nimbus component and restart Nimbus
> # Fill up the disk space on host1 (in my test, the disk space was filled up
> on the host running Nimbus component)
> # Try to restart Nimbus. Nimbus restart expectedly fails with error:
> {code}
> Caught an exception while executing custom service command: 'exceptions.IOError'>: [Errno 28] No space left on device; [Errno 28] No
> space left on device
> {code}
> # Now free up the disk space on host1 and try to restart Nimbus
>
> *Result*
> Nimbus restart command hangs and eventually times out
> Looks like the issue is because the action queue is unable to create new
> command for Nimbus restart.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22830) Ambari-agent puts Python scripts in 2.6 directory on OSes that use python 2.7.x by default
[ https://issues.apache.org/jira/browse/AMBARI-22830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22830: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Ambari-agent puts Python scripts in 2.6 directory on OSes that use python > 2.7.x by default > -- > > Key: AMBARI-22830 > URL: https://issues.apache.org/jira/browse/AMBARI-22830 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22830.patch, AMBARI-22830.patch, > AMBARI-22830.patch > > Time Spent: 2h 20m > Remaining Estimate: 0h > > User needs to upgrade all OSes for security purposes, and will need to remove > all directories related to Python2.6 due to > TLS violations, they need this ASAP to test, as they have a hard deadline. > OS: Red Hat Enterprise Linux Server release 7.4 > JDK version: 1.8.0_144 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22881) Missing user_authentication_id_seq in ambari_sequences table upon upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347539#comment-16347539
]
Hudson commented on AMBARI-22881:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8663 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8663/])
[AMBARI-22881] Added user_authentication_id_seq into ambari_sequences (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cf58132f747828071fd7d418b607f8d85a3dd747])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java
> Missing user_authentication_id_seq in ambari_sequences table upon upgrade
> -
>
> Key: AMBARI-22881
> URL: https://issues.apache.org/jira/browse/AMBARI-22881
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Missing user_authentication_id_seq in ambari_sequences table upon upgrade.
> The missing sequence should be added using a value greater than the largest
> {{user_authentication.user_authentication_id}}. For example:
> {code:sql}
> insert into ambari_sequences (sequence_name, sequence_value)
> select 'user_authentication_id_seq', max(user_authentication_id) + 1 from
> user_authentication;{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22890) LogSearch Integration support for external Shared LogSearch Server connections
Olivér Szabó created AMBARI-22890: - Summary: LogSearch Integration support for external Shared LogSearch Server connections Key: AMBARI-22890 URL: https://issues.apache.org/jira/browse/AMBARI-22890 Project: Ambari Issue Type: Bug Components: ambari-logsearch, ambari-server Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22841) Fix upgrade-catalog after accordingly to kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-22841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347350#comment-16347350 ] Hudson commented on AMBARI-22841: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8662 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8662/]) AMBARI-22841. Fix upgrade-catalog after accordingly to kerberos (echekanskiy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a69872e24d08000da1bd53b7b7316a33f8118b03]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog300.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/AbstractPrepareKerberosServerAction.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog300Test.java > Fix upgrade-catalog after accordingly to kerberos changes > - > > Key: AMBARI-22841 > URL: https://issues.apache.org/jira/browse/AMBARI-22841 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22889) LDAP configuration is not reloaded in Guice
Sandor Molnar created AMBARI-22889: -- Summary: LDAP configuration is not reloaded in Guice Key: AMBARI-22889 URL: https://issues.apache.org/jira/browse/AMBARI-22889 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Sandor Molnar Assignee: Sandor Molnar Fix For: 2.7.0 +*Steps to reproduce:*+ run _ambari-server setup-ldap_ and set primary host:port to "myHost:1" run _ambari-server sync-ldap --all_ +*Actual results:*+ the synch process will fail due to a CommunicationException saying that *localhost:33389* is not reachable. +*Expected results:*+ the synch process will fail due to a CommunicationException saying that *myHost:1* is not reachable. +*Additional information:*+ in ambari-server.log I saw that AmbariConfigurationChangedEvent has been triggered and processed when setup-ldap updated the DB (see org.apache.ambari.server.ldap.service.AmbariLdapConfigurationProvider; however the get() method does not seem to be called when needed; it's maybe a Guice injection scope issue) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22885) LDAP sync fails with 'LDAP is not configured' error after configuring LDAP
[
https://issues.apache.org/jira/browse/AMBARI-22885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22885:
Labels: pull-request-available (was: )
> LDAP sync fails with 'LDAP is not configured' error after configuring LDAP
> --
>
> Key: AMBARI-22885
> URL: https://issues.apache.org/jira/browse/AMBARI-22885
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> LDAP sync fails with 'LDAP is not configured' error after configuring LDAP.
> *Steps to Reproduce*
> # ambari-server setup-ldap
> # ambari-server sync-ldap --all
> {noformat:title=Example}
> [root@c6404 ~]# ambari-server sync-ldap --all
> Using python /usr/bin/python
> Syncing with LDAP...
> ERROR: Exiting with exit code 1.
> REASON: LDAP is not configured. Run 'ambari-server setup-ldap' first.
> {noformat}
> *Cause*
> The ambari-server script is looking for the value of
> {{ambari.ldap.authentication.enabled}} (from the the {{ambari.properties}}
> file. The value is expected to be "true". Since
> {{ambari.ldap.authentication.enabled}} is not being set in the
> ambari.properties file, the check is failing and thus, the unexpected error.
> See {{ambari-server/src/main/python/ambari_server/setupSecurity.py:298}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22841) Fix upgrade-catalog after accordingly to kerberos changes
[ https://issues.apache.org/jira/browse/AMBARI-22841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy resolved AMBARI-22841. Resolution: Fixed > Fix upgrade-catalog after accordingly to kerberos changes > - > > Key: AMBARI-22841 > URL: https://issues.apache.org/jira/browse/AMBARI-22841 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22759) [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist in same Name
[ https://issues.apache.org/jira/browse/AMBARI-22759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346899#comment-16346899 ] Hudson commented on AMBARI-22759: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8661 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8661/]) AMBARI-22759 [Hive Views 2.0] Deleting a Saved query is Buggy when (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=858fbd239369274def05a0846e8fa63ee53a8ad9]) * (edit) contrib/views/hive20/src/main/resources/ui/app/routes/savedqueries.js > [Hive Views 2.0] Deleting a Saved query is Buggy when Mutliple Queries exist > in same Name > - > > Key: AMBARI-22759 > URL: https://issues.apache.org/jira/browse/AMBARI-22759 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 > Environment: ambari 2.5.2 >Reporter: Akhil S Naik >Priority: Major > Labels: newbie, patch, pull-request-available, usability > Fix For: 3.0.0 > > Attachments: AMBARI-22759-trunk.patch, > hive_duplicate_saved_query_issue.png > > Time Spent: 40m > Remaining Estimate: 0h > > Reproduction scenario : > Save some queries under same name . > !https://issues.apache.org/jira/secure/attachment/12905639/hive_duplicate_saved_query_issue.png! > delete one of the saved query > *hive views is deleting some other query randomly and the query i deleted > still exists in saved query even after refresh of page.* > Root Cause : > After the Fix of AMBARI-19958, Hive views is querying the saved Queries with > FilterBy queryId and server is responding mutiple queries as all the queries > has same name, > then Web client is deleting the first record from these savedQueries due to > which this issue is happening. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22888) Cancel operation during package deployment causing repository manager to be broken
Dmytro Grinenko created AMBARI-22888: Summary: Cancel operation during package deployment causing repository manager to be broken Key: AMBARI-22888 URL: https://issues.apache.org/jira/browse/AMBARI-22888 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.2 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2 During any failure on cluster deployment, server posting cancel operation to all pending and in progress operations. This causing package manager to be killed and enter in a bad state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22792) Refactor agent-side kerberos code
[ https://issues.apache.org/jira/browse/AMBARI-22792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy resolved AMBARI-22792. Resolution: Fixed > Refactor agent-side kerberos code > - > > Key: AMBARI-22792 > URL: https://issues.apache.org/jira/browse/AMBARI-22792 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22882) Long cannot be cast to String error when changing a user's password
[
https://issues.apache.org/jira/browse/AMBARI-22882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346602#comment-16346602
]
Hudson commented on AMBARI-22882:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8660 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8660/])
[AMBARI-22882] Long cannot be cast to String error when changing a (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e40e7e5bfcfffac78351278d74e1310a8aa35cc5])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/UserResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UserResourceProvider.java
> Long cannot be cast to String error when changing a user's password
> ---
>
> Key: AMBARI-22882
> URL: https://issues.apache.org/jira/browse/AMBARI-22882
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Long cannot be cast to String error when changing a user's password:
> {noformat}
> 30 Jan 2018 18:21:11,308 ERROR [ambari-client-thread-38]
> AbstractResourceProvider:353 - Caught AmbariException when modifying a
> resource
> org.apache.ambari.server.AmbariException: java.lang.Long cannot be cast to
> java.lang.String
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider.addOrUpdateLocalAuthenticationSource(UserResourceProvider.java:559)
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider.updateUsers(UserResourceProvider.java:486)
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider.access$200(UserResourceProvider.java:69)
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider$3.invoke(UserResourceProvider.java:264)
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider$3.invoke(UserResourceProvider.java:261)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.UserResourceProvider.updateResources(UserResourceProvider.java:261)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
> ...
> {noformat}
> *Steps to reproduce*
> # Create a {{LOCAL}} user account (using either the Ambari UI or REST API)
> {noformat}
> POST /api/v1/users
> {noformat}
> {code:title=Payload}
> {
> "Users" : {
> "user_name" : "myuser",
> "password" : "hadoop"
> }
> }
> {code}
> # Change the user's password (using either the Ambari UI or REST API via the
> users entry point)
> {noformat}
> PUT /api/v1/users/myuser
> {noformat}
> {code:title=Payload}
> {
> "Users" : {
> "old_password" : "hadoop"
> "password" : "hadoop1234"
> }
> }
> {code}
> {code:title=Response}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException: An
> internal system exception occurred: java.lang.Long cannot be cast to
> java.lang.String"
> }
> {code}
> *Cause*
> When building the internal request to set the user's password via the
> UserAuthenticationSource resource provider, the authentication source key is
> set as a {{Long}}. The UserAuthenticationSource resource provider expects
> this value to be a {{String}}.
> *Solution*
> The User resource provider should set the
> {{AuthenticationSourceInfo/source_id}} as a {{String}} value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22887) Configuration changes of acid switch button is not shown in compare / advanced
[
https://issues.apache.org/jira/browse/AMBARI-22887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated AMBARI-22887:
--
Attachment: advanced_tab_in_compare.png
> Configuration changes of acid switch button is not shown in compare / advanced
> --
>
> Key: AMBARI-22887
> URL: https://issues.apache.org/jira/browse/AMBARI-22887
> Project: Ambari
> Issue Type: Bug
>Reporter: Zoltan Haindrich
>Priority: Major
> Attachments: advanced_tab_in_compare.png
>
>
> I would expect to see the settings like:
> {code}
> hive.create.as.insert.only
> metastore.create.as.acid
> {code}
> they are shown when the warning is issued during changing the acid setting
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22830) Ambari-agent puts Python scripts in 2.6 directory on OSes that use python 2.7.x by default
[ https://issues.apache.org/jira/browse/AMBARI-22830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22830: - Attachment: AMBARI-22830.patch > Ambari-agent puts Python scripts in 2.6 directory on OSes that use python > 2.7.x by default > -- > > Key: AMBARI-22830 > URL: https://issues.apache.org/jira/browse/AMBARI-22830 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22830.patch, AMBARI-22830.patch, > AMBARI-22830.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > User needs to upgrade all OSes for security purposes, and will need to remove > all directories related to Python2.6 due to > TLS violations, they need this ASAP to test, as they have a hard deadline. > OS: Red Hat Enterprise Linux Server release 7.4 > JDK version: 1.8.0_144 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22887) Configuration changes of acid switch button is not shown in compare / advanced
[
https://issues.apache.org/jira/browse/AMBARI-22887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated AMBARI-22887:
--
Attachment: (was: compare_settings.png)
> Configuration changes of acid switch button is not shown in compare / advanced
> --
>
> Key: AMBARI-22887
> URL: https://issues.apache.org/jira/browse/AMBARI-22887
> Project: Ambari
> Issue Type: Bug
>Reporter: Zoltan Haindrich
>Priority: Major
>
> I would expect to see the settings like:
> {code}
> hive.create.as.insert.only
> metastore.create.as.acid
> {code}
> they are shown when the warning is issued during changing the acid setting
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22887) Configuration changes of acid switch button is not shown in compare / advanced
[
https://issues.apache.org/jira/browse/AMBARI-22887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated AMBARI-22887:
--
Attachment: compare_settings.png
> Configuration changes of acid switch button is not shown in compare / advanced
> --
>
> Key: AMBARI-22887
> URL: https://issues.apache.org/jira/browse/AMBARI-22887
> Project: Ambari
> Issue Type: Bug
>Reporter: Zoltan Haindrich
>Priority: Major
> Attachments: compare_settings.png
>
>
> I would expect to see the settings like:
> {code}
> hive.create.as.insert.only
> metastore.create.as.acid
> {code}
> they are shown when the warning is issued during changing the acid setting
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22830) Ambari-agent puts Python scripts in 2.6 directory on OSes that use python 2.7.x by default
[ https://issues.apache.org/jira/browse/AMBARI-22830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22830: - Attachment: AMBARI-22830.patch > Ambari-agent puts Python scripts in 2.6 directory on OSes that use python > 2.7.x by default > -- > > Key: AMBARI-22830 > URL: https://issues.apache.org/jira/browse/AMBARI-22830 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22830.patch, AMBARI-22830.patch, > AMBARI-22830.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > User needs to upgrade all OSes for security purposes, and will need to remove > all directories related to Python2.6 due to > TLS violations, they need this ASAP to test, as they have a hard deadline. > OS: Red Hat Enterprise Linux Server release 7.4 > JDK version: 1.8.0_144 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22887) Configuration changes of acid switch button is not shown in compare / advanced
Zoltan Haindrich created AMBARI-22887:
-
Summary: Configuration changes of acid switch button is not shown
in compare / advanced
Key: AMBARI-22887
URL: https://issues.apache.org/jira/browse/AMBARI-22887
Project: Ambari
Issue Type: Bug
Reporter: Zoltan Haindrich
I would expect to see the settings like:
{code}
hive.create.as.insert.only
metastore.create.as.acid
{code}
they are shown when the warning is issued during changing the acid setting
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22876) Disable consecutive authentication failure account lockout feature by default
[
https://issues.apache.org/jira/browse/AMBARI-22876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22876:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Disable consecutive authentication failure account lockout feature by default
> -
>
> Key: AMBARI-22876
> URL: https://issues.apache.org/jira/browse/AMBARI-22876
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: authentication, pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Disable consecutive authentication failure account lockout feature by
> default. This feature locks an account after a configured number of failed
> authentication attempts. By defaulting {{authentication.local.max.failures}}
> to {{0}}, this feature will be disabled by default.
> If enabled, a user account may be locked out due to number of authentication
> failures. There is a REST API call to unlock the user; however a user
> interface change will not be available until Ambari 3.x.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22886) Infra Manager: store s3 credentials in Hadoop credential store
Krisztian Kasa created AMBARI-22886: --- Summary: Infra Manager: store s3 credentials in Hadoop credential store Key: AMBARI-22886 URL: https://issues.apache.org/jira/browse/AMBARI-22886 Project: Ambari Issue Type: Improvement Components: ambari-infra Affects Versions: 3.0.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22885) LDAP sync fails with 'LDAP is not configured' error after configuring LDAP
Sandor Molnar created AMBARI-22885:
--
Summary: LDAP sync fails with 'LDAP is not configured' error after
configuring LDAP
Key: AMBARI-22885
URL: https://issues.apache.org/jira/browse/AMBARI-22885
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
LDAP sync fails with 'LDAP is not configured' error after configuring LDAP.
*Steps to Reproduce*
# ambari-server setup-ldap
# ambari-server sync-ldap --all
{noformat:title=Example}
[root@c6404 ~]# ambari-server sync-ldap --all
Using python /usr/bin/python
Syncing with LDAP...
ERROR: Exiting with exit code 1.
REASON: LDAP is not configured. Run 'ambari-server setup-ldap' first.
{noformat}
*Cause*
The ambari-server script is looking for the value of
{{ambari.ldap.authentication.enabled}} (from the the {{ambari.properties}}
file. The value is expected to be "true". Since
{{ambari.ldap.authentication.enabled}} is not being set in the
ambari.properties file, the check is failing and thus, the unexpected error.
See {{ambari-server/src/main/python/ambari_server/setupSecurity.py:298}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
