[jira] [Commented] (AMBARI-19470) Error in ru_execute_tasks.py - Logger has no attribute 'warn'
[ https://issues.apache.org/jira/browse/AMBARI-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821228#comment-15821228 ] Hudson commented on AMBARI-19470: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #696 (See [https://builds.apache.org/job/Ambari-branch-2.5/696/]) AMBARI-19470 - Error in ru_execute_tasks.py - Logger has no attribute (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=50d391da0b2ae871136fff16f4c91245123d0bcd]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py * (edit) ambari-server/src/main/resources/custom_actions/scripts/ru_execute_tasks.py > Error in ru_execute_tasks.py - Logger has no attribute 'warn' > - > > Key: AMBARI-19470 > URL: https://issues.apache.org/jira/browse/AMBARI-19470 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19470.patch > > > Traceback (most recent call last): > File "/var/lib/ambari- > agent/cache/custom_actions/scripts/ru_execute_tasks.py", line 156, in > ExecuteUpgradeTasks().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 219, inexecute method(env) > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 94, in actionexecute resolve_ambari_config() > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 82, in resolve_ambari_config Logger.warn(err) > AttributeError: class Logger has no attribute 'warn' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19464) Stack Downgrading Potentially Corrupts Kerberos Descriptor
[ https://issues.apache.org/jira/browse/AMBARI-19464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821230#comment-15821230 ] Hudson commented on AMBARI-19464: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #696 (See [https://builds.apache.org/job/Ambari-branch-2.5/696/]) AMBARI-19464. Stack Downgrading Potentially Corrupts Kerberos Descriptor (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=98f03b5f89f9e4a3467bc7f7cd53f29c4fb5c378]) * (add) ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptorTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ArtifactEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/UpgradeUserKerberosDescriptor.java > Stack Downgrading Potentially Corrupts Kerberos Descriptor > -- > > Key: AMBARI-19464 > URL: https://issues.apache.org/jira/browse/AMBARI-19464 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19464.2.patch, AMBARI-19464.patch > > > AMBARI-18335 addresses an issue where configuration properties in the > Kerberos descriptor don't change during a stack upgrade. It accounts for both > upgrade/downgrade scenarios and situations where properties are added/removed. > However, it does not take into account the potential for a property to be > customized by the user (not a new property, but a property which the user > changes the value of). In this case, the downgrade would be destructive, > overriding the user's values with those from the downgrade stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19466) Sqlline-thin is unable to connect to phoenix
[ https://issues.apache.org/jira/browse/AMBARI-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821227#comment-15821227 ] Hudson commented on AMBARI-19466: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #696 (See [https://builds.apache.org/job/Ambari-branch-2.5/696/]) AMBARI-19466. Sqlline-thin is unable to connect to phoenix (echekankiy (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9388184ebf105d68f2597195a213619f7946fae9]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.1/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py > Sqlline-thin is unable to connect to phoenix > > > Key: AMBARI-19466 > URL: https://issues.apache.org/jira/browse/AMBARI-19466 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19466-2.5.path, AMBARI-19466-trunk.path > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19241) Ambari python scripts should support hdfs download
[ https://issues.apache.org/jira/browse/AMBARI-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821143#comment-15821143 ] Hudson commented on AMBARI-19241: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #695 (See [https://builds.apache.org/job/Ambari-branch-2.5/695/]) AMBARI-19241 - Ambari python scripts should support hdfs download (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ae75c871e497ee4a8de23579b3fbc175f8d073d5]) * (add) ambari-common/src/main/python/resource_management/libraries/functions/download_from_hdfs.py * (edit) ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py * (edit) contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Resource.java * (edit) ambari-common/src/main/python/resource_management/libraries/resources/hdfs_resource.py * (edit) contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Runner.java > Ambari python scripts should support hdfs download > -- > > Key: AMBARI-19241 > URL: https://issues.apache.org/jira/browse/AMBARI-19241 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, contrib >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19241.patch > > Original Estimate: 192h > Remaining Estimate: 192h > > Currently the hdfs_resources.py supports > 1) create files/directories in HDFS > 2) delete files/directories in HDFS > 3) upload files/directories to HDFS > We should also support download of files/directories from HDFS. This will > help particularly in cloud environments where the users of the cluster don't > necessarily have write access to the local file system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19466) Sqlline-thin is unable to connect to phoenix
[ https://issues.apache.org/jira/browse/AMBARI-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821108#comment-15821108 ] Dmitry Lysnichenko commented on AMBARI-19466: - remote: ambari git commit: AMBARI-19466. Sqlline-thin is unable to connect to phoenix (echekankiy via dlysnichenko) remote: ambari git commit: AMBARI-19464. Stack Downgrading Potentially Corrupts Kerberos Descriptor (echekanskiy via dlysnichenko) remote: ambari git commit: AMBARI-19466. Sqlline-thin is unable to connect to phoenix (echekankiy via dlysnichenko) remote: ambari git commit: AMBARI-19464. Stack Downgrading Potentially Corrupts Kerberos Descriptor (echekanskiy via dlysnichenko) To https://git-wip-us.apache.org/repos/asf/ambari.git 50d391da0b..9388184ebf branch-2.5 -> branch-2.5 384a7f0363..fdbe0939e9 trunk -> trunk > Sqlline-thin is unable to connect to phoenix > > > Key: AMBARI-19466 > URL: https://issues.apache.org/jira/browse/AMBARI-19466 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19466-2.5.path, AMBARI-19466-trunk.path > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19464) Stack Downgrading Potentially Corrupts Kerberos Descriptor
[ https://issues.apache.org/jira/browse/AMBARI-19464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821109#comment-15821109 ] Dmitry Lysnichenko commented on AMBARI-19464: - remote: ambari git commit: AMBARI-19466. Sqlline-thin is unable to connect to phoenix (echekankiy via dlysnichenko) remote: ambari git commit: AMBARI-19464. Stack Downgrading Potentially Corrupts Kerberos Descriptor (echekanskiy via dlysnichenko) remote: ambari git commit: AMBARI-19466. Sqlline-thin is unable to connect to phoenix (echekankiy via dlysnichenko) remote: ambari git commit: AMBARI-19464. Stack Downgrading Potentially Corrupts Kerberos Descriptor (echekanskiy via dlysnichenko) To https://git-wip-us.apache.org/repos/asf/ambari.git 50d391da0b..9388184ebf branch-2.5 -> branch-2.5 384a7f0363..fdbe0939e9 trunk -> trunk > Stack Downgrading Potentially Corrupts Kerberos Descriptor > -- > > Key: AMBARI-19464 > URL: https://issues.apache.org/jira/browse/AMBARI-19464 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19464.2.patch, AMBARI-19464.patch > > > AMBARI-18335 addresses an issue where configuration properties in the > Kerberos descriptor don't change during a stack upgrade. It accounts for both > upgrade/downgrade scenarios and situations where properties are added/removed. > However, it does not take into account the potential for a property to be > customized by the user (not a new property, but a property which the user > changes the value of). In this case, the downgrade would be destructive, > overriding the user's values with those from the downgrade stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19241) Ambari python scripts should support hdfs download
[ https://issues.apache.org/jira/browse/AMBARI-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821096#comment-15821096 ] Hudson commented on AMBARI-19241: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6417 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6417/]) AMBARI-19241 - Ambari python scripts should support hdfs download (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5228e1847bd7b92d7a3379d26002879dbfeafffe]) * (edit) ambari-common/src/main/python/resource_management/libraries/resources/hdfs_resource.py * (edit) contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Resource.java * (edit) ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py * (add) ambari-common/src/main/python/resource_management/libraries/functions/download_from_hdfs.py * (edit) contrib/fast-hdfs-resource/src/main/java/org/apache/ambari/fast_hdfs_resource/Runner.java > Ambari python scripts should support hdfs download > -- > > Key: AMBARI-19241 > URL: https://issues.apache.org/jira/browse/AMBARI-19241 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, contrib >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19241.patch > > Original Estimate: 192h > Remaining Estimate: 192h > > Currently the hdfs_resources.py supports > 1) create files/directories in HDFS > 2) delete files/directories in HDFS > 3) upload files/directories to HDFS > We should also support download of files/directories from HDFS. This will > help particularly in cloud environments where the users of the cluster don't > necessarily have write access to the local file system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19466) Sqlline-thin is unable to connect to phoenix
[ https://issues.apache.org/jira/browse/AMBARI-19466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-19466: --- Attachment: AMBARI-19466-2.5.path > Sqlline-thin is unable to connect to phoenix > > > Key: AMBARI-19466 > URL: https://issues.apache.org/jira/browse/AMBARI-19466 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19466-2.5.path, AMBARI-19466-trunk.path > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19464) Stack Downgrading Potentially Corrupts Kerberos Descriptor
[ https://issues.apache.org/jira/browse/AMBARI-19464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-19464: --- Attachment: AMBARI-19464.2.patch > Stack Downgrading Potentially Corrupts Kerberos Descriptor > -- > > Key: AMBARI-19464 > URL: https://issues.apache.org/jira/browse/AMBARI-19464 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 2.5.0 > > Attachments: AMBARI-19464.2.patch, AMBARI-19464.patch > > > AMBARI-18335 addresses an issue where configuration properties in the > Kerberos descriptor don't change during a stack upgrade. It accounts for both > upgrade/downgrade scenarios and situations where properties are added/removed. > However, it does not take into account the potential for a property to be > customized by the user (not a new property, but a property which the user > changes the value of). In this case, the downgrade would be destructive, > overriding the user's values with those from the downgrade stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19470) Error in ru_execute_tasks.py - Logger has no attribute 'warn'
[ https://issues.apache.org/jira/browse/AMBARI-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19470: Resolution: Fixed Status: Resolved (was: Patch Available) > Error in ru_execute_tasks.py - Logger has no attribute 'warn' > - > > Key: AMBARI-19470 > URL: https://issues.apache.org/jira/browse/AMBARI-19470 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19470.patch > > > Traceback (most recent call last): > File "/var/lib/ambari- > agent/cache/custom_actions/scripts/ru_execute_tasks.py", line 156, in > ExecuteUpgradeTasks().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 219, inexecute method(env) > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 94, in actionexecute resolve_ambari_config() > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 82, in resolve_ambari_config Logger.warn(err) > AttributeError: class Logger has no attribute 'warn' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Attachment: AMBARI-19029.2.patch
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.2.patch,
> AMBARI-19029.patch
>
>
> After enabling Namenode-HA, atlas had a critical alert that "This host-level
> alert is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Suvagia resolved AMBARI-19386. - Resolution: Fixed committed on [branch-2.5|https://github.com/apache/ambari/commit/20380d69270ab64933855dd1668305b14f39e91c] and [trunk|https://github.com/apache/ambari/commit/4975864796b9a301f4e0ee0b36673f41cb0f1b21] > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19241) Ambari python scripts should support hdfs download
[ https://issues.apache.org/jira/browse/AMBARI-19241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19241: Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari python scripts should support hdfs download > -- > > Key: AMBARI-19241 > URL: https://issues.apache.org/jira/browse/AMBARI-19241 > Project: Ambari > Issue Type: New Feature > Components: ambari-agent, contrib >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19241.patch > > Original Estimate: 192h > Remaining Estimate: 192h > > Currently the hdfs_resources.py supports > 1) create files/directories in HDFS > 2) delete files/directories in HDFS > 3) upload files/directories to HDFS > We should also support download of files/directories from HDFS. This will > help particularly in cloud environments where the users of the cluster don't > necessarily have write access to the local file system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821034#comment-15821034 ] Vishal Suvagia commented on AMBARI-19386: - committed on [branch-2.5|https://github.com/apache/ambari/commit/20380d69270ab64933855dd1668305b14f39e91c] and [trunk|https://github.com/apache/ambari/commit/4975864796b9a301f4e0ee0b36673f41cb0f1b21] > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19470) Error in ru_execute_tasks.py - Logger has no attribute 'warn'
[ https://issues.apache.org/jira/browse/AMBARI-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19470: > Error in ru_execute_tasks.py - Logger has no attribute 'warn' > - > > Key: AMBARI-19470 > URL: https://issues.apache.org/jira/browse/AMBARI-19470 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19470.patch > > > Traceback (most recent call last): > File "/var/lib/ambari- > agent/cache/custom_actions/scripts/ru_execute_tasks.py", line 156, in > ExecuteUpgradeTasks().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 219, inexecute method(env) > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 94, in actionexecute resolve_ambari_config() > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 82, in resolve_ambari_config Logger.warn(err) > AttributeError: class Logger has no attribute 'warn' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19470) Error in ru_execute_tasks.py - Logger has no attribute 'warn'
[ https://issues.apache.org/jira/browse/AMBARI-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19470: Attachment: (was: AMBARI-19470.patch) > Error in ru_execute_tasks.py - Logger has no attribute 'warn' > - > > Key: AMBARI-19470 > URL: https://issues.apache.org/jira/browse/AMBARI-19470 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19470.patch > > > Traceback (most recent call last): > File "/var/lib/ambari- > agent/cache/custom_actions/scripts/ru_execute_tasks.py", line 156, in > ExecuteUpgradeTasks().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 219, inexecute method(env) > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 94, in actionexecute resolve_ambari_config() > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 82, in resolve_ambari_config Logger.warn(err) > AttributeError: class Logger has no attribute 'warn' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19470) Error in ru_execute_tasks.py - Logger has no attribute 'warn'
[ https://issues.apache.org/jira/browse/AMBARI-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-19470: Attachment: AMBARI-19470.patch > Error in ru_execute_tasks.py - Logger has no attribute 'warn' > - > > Key: AMBARI-19470 > URL: https://issues.apache.org/jira/browse/AMBARI-19470 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-19470.patch > > > Traceback (most recent call last): > File "/var/lib/ambari- > agent/cache/custom_actions/scripts/ru_execute_tasks.py", line 156, in > ExecuteUpgradeTasks().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 219, inexecute method(env) > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 94, in actionexecute resolve_ambari_config() > File > "/var/lib/ambari-agent/cache/custom_actions/scripts/ru_execute_tasks.py", > line 82, in resolve_ambari_config Logger.warn(err) > AttributeError: class Logger has no attribute 'warn' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Description:
After enabling Namenode-HA, atlas had a critical alert that "This host-level
alert is triggered if the Metadata Server Web UI is unreachable."
>From atlas logs I can see :
{code}
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
at
org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
at
org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
at
com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
at com.google.inject.spi.Elements.getElements(Elements.java:110)
at
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
at com.google.inject.Guice.createInjector(Guice.java:99)
at com.google.inject.Guice.createInjector(Guice.java:84)
at
org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
at
com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
at
org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
at
org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
at org.eclipse.jetty.server.Server.start(Server.java:387)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
at
org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
at org.eclipse.jetty.server.Server.doStart(Server.java:354)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at
org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
at org.apache.atlas.Atlas.main(Atlas.java:118)
{code}
was:
After kerberization, atlas had a critical alert that "This host-level alert is
triggered if the Metadata Server Web UI is unreachable."
>From atlas logs I can see :
{code}
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at
org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
at
org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
at
org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
at
com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
at com.google.inject.spi.Elements.getElements(Elements.java:110)
at
com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
at
com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
at com.google.inject.Guice.createInjector(Guice.java:99)
at com.google.inject.Guice.createInjector(Guice.java:84)
at
org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
at
com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
at
org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
[jira] [Updated] (AMBARI-19029) Atlas web UI inaccessible alert after enabling Namenode-HA
[
https://issues.apache.org/jira/browse/AMBARI-19029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Suvagia updated AMBARI-19029:
Summary: Atlas web UI inaccessible alert after enabling Namenode-HA (was:
Atlas web UI inaccessible alert after enabling security)
> Atlas web UI inaccessible alert after enabling Namenode-HA
> --
>
> Key: AMBARI-19029
> URL: https://issues.apache.org/jira/browse/AMBARI-19029
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Shreya Bhat
>Assignee: Vishal Suvagia
>Priority: Critical
> Labels: system_test
> Fix For: 2.5.0
>
> Attachments: AMBARI-19029.1.patch, AMBARI-19029.patch
>
>
> After kerberization, atlas had a critical alert that "This host-level alert
> is triggered if the Metadata Server Web UI is unreachable."
> From atlas logs I can see :
> {code}
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at
> org.apache.atlas.ApplicationProperties.getClass(ApplicationProperties.java:115)
> at
> org.apache.atlas.util.AtlasRepositoryConfiguration.getDeleteHandlerImpl(AtlasRepositoryConfiguration.java:76)
> at
> org.apache.atlas.RepositoryMetadataModule.configure(RepositoryMetadataModule.java:104)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:99)
> at com.google.inject.Guice.createInjector(Guice.java:84)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.getInjector(GuiceServletConfig.java:77)
> at
> com.google.inject.servlet.GuiceServletContextListener.contextInitialized(GuiceServletContextListener.java:47)
> at
> org.apache.atlas.web.listeners.GuiceServletConfig.contextInitialized(GuiceServletConfig.java:141)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.apache.atlas.web.service.EmbeddedServer.start(EmbeddedServer.java:92)
> at org.apache.atlas.Atlas.main(Atlas.java:118)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19468) Logsearch should run zk/solr operations internally (instead of in ambari-agent code)
[ https://issues.apache.org/jira/browse/AMBARI-19468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-19468: -- Attachment: AMBARI-19468.patch > Logsearch should run zk/solr operations internally (instead of in > ambari-agent code) > > > Key: AMBARI-19468 > URL: https://issues.apache.org/jira/browse/AMBARI-19468 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 2.5.0 > > Attachments: AMBARI-19468.patch, AMBARI-19468.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18961) Ambari HiveView does not create or upload script in UTF-8 format
[
https://issues.apache.org/jira/browse/AMBARI-18961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gaurav Nagar reopened AMBARI-18961:
---
> Ambari HiveView does not create or upload script in UTF-8 format
>
>
> Key: AMBARI-18961
> URL: https://issues.apache.org/jira/browse/AMBARI-18961
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.1
> Environment: All
>Reporter: JaySenSharma
>Assignee: JaySenSharma
> Fix For: 2.5.0
>
> Attachments: AMBARI-18961.patch
>
>
> - When we run an insert query with some special character in the Hive
> (Hive-next) View then we see that the values are not being reflected
> properly. The special characters are being replaced with "?"
> Example:
> {code}
> CREATE table test (id int, name string);
> insert into test values (100, "€");
> insert into test values (200, "$");
> insert into test values (300, "£");
> insert into test values (400, "₡");
> SELECT * FROM test LIMIT 100;
> {code}
> - Once the above script is executed then we will see the output something
> like "HiveView_UTF-8_Issue.png" (attached)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19426) Modify quick link resource provider to consider filters and return visibility
[ https://issues.apache.org/jira/browse/AMBARI-19426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Toader updated AMBARI-19426: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Modify quick link resource provider to consider filters and return visibility > - > > Key: AMBARI-19426 > URL: https://issues.apache.org/jira/browse/AMBARI-19426 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári > Fix For: 2.5.0 > > Attachments: AMBARI-19426-Use-profile-trunk-v4.patch > > > Existing quicklinks API (e.g: > http://c6401:8080/api/v1/stacks/HDP/versions/2.5/services/ACCUMULO/quicklinks/quicklinks.json) > should return visible = true/false based on the quick links profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
