[jira] [Created] (AMBARI-25131) Alert notification properties are wiped after enabling/disabling the notification
Dmytro Sen created AMBARI-25131: --- Summary: Alert notification properties are wiped after enabling/disabling the notification Key: AMBARI-25131 URL: https://issues.apache.org/jira/browse/AMBARI-25131 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 STR: Create alert notification (tested on ALERT_SCRIPT notification_type) Populate Script Dispatch Property and/or Script Filename Disable the notification Enable the notification Script Dispatch Property and/or Script Filename properties are empty -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25106) Add Ozone JMX ports
[ https://issues.apache.org/jira/browse/AMBARI-25106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-25106. - Resolution: Fixed > Add Ozone JMX ports > --- > > Key: AMBARI-25106 > URL: https://issues.apache.org/jira/browse/AMBARI-25106 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25106) Add Ozone JMX ports
Dmytro Sen created AMBARI-25106: --- Summary: Add Ozone JMX ports Key: AMBARI-25106 URL: https://issues.apache.org/jira/browse/AMBARI-25106 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24976) List Ozone as file system user
Dmytro Sen created AMBARI-24976: --- Summary: List Ozone as file system user Key: AMBARI-24976 URL: https://issues.apache.org/jira/browse/AMBARI-24976 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24976) List Ozone as file system service
[ https://issues.apache.org/jira/browse/AMBARI-24976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-24976: Summary: List Ozone as file system service (was: List Ozone as file system user) > List Ozone as file system service > - > > Key: AMBARI-24976 > URL: https://issues.apache.org/jira/browse/AMBARI-24976 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Fix For: 2.8.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24971) HDFS datanode process fails with class not found exception when installed with OZONE
[
https://issues.apache.org/jira/browse/AMBARI-24971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-24971.
-
Resolution: Fixed
> HDFS datanode process fails with class not found exception when installed
> with OZONE
> -
>
> Key: AMBARI-24971
> URL: https://issues.apache.org/jira/browse/AMBARI-24971
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.8.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When HDFS DN is started with OZONE service installed DN process fails with
> "Class org.apache.hadoop.ozone.HddsDatanodeService not found".
> This is caused because OZONE_HOME env variable is set only in
> /usr/hdp/3.0.100.0-75/hadoop-ozone/bin/ozone/usr/hdp/3.0.100.0-75/hadoop-ozone/bin/ozone
> :
> {code:java}
> export
> HADOOP_OZONE_HOME=${HADOOP_OZONE_HOME:-/usr/hdp/3.0.100.0-75/hadoop-ozone}{code}
> Need to define the OZONE_HOME in the hadoop-env to add the jars into DN class
> path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24971) HDFS datanode process fails with class not found exception when installed with OZONE
Dmytro Sen created AMBARI-24971:
---
Summary: HDFS datanode process fails with class not found
exception when installed with OZONE
Key: AMBARI-24971
URL: https://issues.apache.org/jira/browse/AMBARI-24971
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.8.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.8.0
When HDFS DN is started with OZONE service installed DN process fails with
"Class org.apache.hadoop.ozone.HddsDatanodeService not found".
This is caused because OZONE_HOME env variable is set only in
/usr/hdp/3.0.100.0-75/hadoop-ozone/bin/ozone/usr/hdp/3.0.100.0-75/hadoop-ozone/bin/ozone
:
{code:java}
export
HADOOP_OZONE_HOME=${HADOOP_OZONE_HOME:-/usr/hdp/3.0.100.0-75/hadoop-ozone}{code}
Need to define the OZONE_HOME in the hadoop-env to add the jars into DN class
path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24914) Block Ozone datanode co-location with HDFS Datanode when added though the API
[ https://issues.apache.org/jira/browse/AMBARI-24914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-24914. - Resolution: Fixed > Block Ozone datanode co-location with HDFS Datanode when added though the API > - > > Key: AMBARI-24914 > URL: https://issues.apache.org/jira/browse/AMBARI-24914 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.8.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > * Do not allow user to call and API that add Ozone datanode to a host with > HDFS datanode > * Converse also holds > * Make sure this is a flag at stack level and blueprints also follow the > same validation rule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24914) Block Ozone datanode co-location with HDFS Datanode when added though the API
Dmytro Sen created AMBARI-24914: --- Summary: Block Ozone datanode co-location with HDFS Datanode when added though the API Key: AMBARI-24914 URL: https://issues.apache.org/jira/browse/AMBARI-24914 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 * Do not allow user to call and API that add Ozone datanode to a host with HDFS datanode * Converse also holds * Make sure this is a flag at stack level and blueprints also follow the same validation rule -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24841) Pause after first batch
Dmytro Sen created AMBARI-24841: --- Summary: Pause after first batch Key: AMBARI-24841 URL: https://issues.apache.org/jira/browse/AMBARI-24841 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 Option to automatically pause after the first batch is completed -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24814) Add a rolling_restart_supported flag at the stack service endpoint
Dmytro Sen created AMBARI-24814: --- Summary: Add a rolling_restart_supported flag at the stack service endpoint Key: AMBARI-24814 URL: https://issues.apache.org/jira/browse/AMBARI-24814 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 Similar to the one at stack service component level we need a flag for HDFS, YARN and Zookeeper at api/v1/stacks/HDP/versions//services/ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24733) Rolling Restarts: Option to pause, resume and abort restarts
Dmytro Sen created AMBARI-24733: --- Summary: Rolling Restarts: Option to pause, resume and abort restarts Key: AMBARI-24733 URL: https://issues.apache.org/jira/browse/AMBARI-24733 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24682) Rolling Restarts: Option to specify number of failures per batch
Dmytro Sen created AMBARI-24682: --- Summary: Rolling Restarts: Option to specify number of failures per batch Key: AMBARI-24682 URL: https://issues.apache.org/jira/browse/AMBARI-24682 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.8.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.8.0 User may choose maximum number of failures or specify the number of failures per batch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-24604. - Resolution: Fixed > Stack advisor error popup with "500 status code" thrown during customize > service page of install wizard > --- > > Key: AMBARI-24604 > URL: https://issues.apache.org/jira/browse/AMBARI-24604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > ams-hbase hbase.rootdir property being set to "file://" leads to 500 server > error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
Dmytro Sen created AMBARI-24604: --- Summary: Stack advisor error popup with "500 status code" thrown during customize service page of install wizard Key: AMBARI-24604 URL: https://issues.apache.org/jira/browse/AMBARI-24604 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.2 ams-hbase hbase.rootdir property being set to "file://" leads to 500 server error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24573) Clarify the warning message during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-24573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-24573. - Resolution: Fixed > Clarify the warning message during ambari server setup > -- > > Key: AMBARI-24573 > URL: https://issues.apache.org/jira/browse/AMBARI-24573 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 40m > Remaining Estimate: 0h > > Change > WARNING: Before starting Ambari Server, you must run the following DDL > against the database to create the schema: > /var/lib/ambari-server/resources/Ambari-DDL-MySQL-CREATE.sql > so that it's clear that the dll script should be run from the DB console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24594) ams keystore password logged in clear text
Dmytro Sen created AMBARI-24594: --- Summary: ams keystore password logged in clear text Key: AMBARI-24594 URL: https://issues.apache.org/jira/browse/AMBARI-24594 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.2 We execute a command to convert truststore from JKS to PKCS12 before starting up the AMS component. That command takes in the password as an argument. The command output contains the password, need to replace it with a placeholder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
[ https://issues.apache.org/jira/browse/AMBARI-24458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-24458. - Resolution: Fixed > Start operation is disabled for HDFS after stopping components for one > namespace > > > Key: AMBARI-24458 > URL: https://issues.apache.org/jira/browse/AMBARI-24458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 > Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 > ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot > 2018-08-10 at 10.17.01 AM.png > > Time Spent: 1h > Remaining Estimate: 0h > > Start operation is disabled for HDFS after stopping components for one > namespace > > STR: > 1) On hdfs service page, stop components for one namespace (ns1) > 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24573) Clarify the warning message during ambari server setup
Dmytro Sen created AMBARI-24573: --- Summary: Clarify the warning message during ambari server setup Key: AMBARI-24573 URL: https://issues.apache.org/jira/browse/AMBARI-24573 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.1 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.2 Change WARNING: Before starting Ambari Server, you must run the following DDL against the database to create the schema: /var/lib/ambari-server/resources/Ambari-DDL-MySQL-CREATE.sql so that it's clear that the dll script should be run from the DB console. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24552) Storm service-check fails due to missung StringUtils class definition
[
https://issues.apache.org/jira/browse/AMBARI-24552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-24552:
Summary: Storm service-check fails due to missung StringUtils class
definition (was: Storm service-check failure due to missung StringUtils class
definition)
> Storm service-check fails due to missung StringUtils class definition
> -
>
> Key: AMBARI-24552
> URL: https://issues.apache.org/jira/browse/AMBARI-24552
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.7.2
>
>
> {code:java}
> 2018-08-21 21:46:35.810 o.a.s.util
> Thread-24-__metricsorg.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink-executor[4
> 4] [ERROR] Async loop died!
> java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils
> at
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink.prepare(StormTimelineMetricsSink.java:133)
> ~[ambari-metrics-storm-sink-with-common-2.6.1.0.144.jar:?]
> at
> org.apache.storm.metric.MetricsConsumerBolt.prepare(MetricsConsumerBolt.java:75)
> ~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at
> org.apache.storm.daemon.executor$fn__10252$fn__10265.invoke(executor.clj:800)
> ~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at org.apache.storm.util$async_loop$fn__553.invoke(util.clj:482)
> [storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.lang.StringUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> ~[?:1.8.0_112]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ~[?:1.8.0_112]
> ... 6 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24552) Storm service-check failure due to missung StringUtils class definition
Dmytro Sen created AMBARI-24552:
---
Summary: Storm service-check failure due to missung StringUtils
class definition
Key: AMBARI-24552
URL: https://issues.apache.org/jira/browse/AMBARI-24552
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.6.2
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.7.2
{code:java}
2018-08-21 21:46:35.810 o.a.s.util
Thread-24-__metricsorg.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink-executor[4
4] [ERROR] Async loop died!
java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils
at
org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink.prepare(StormTimelineMetricsSink.java:133)
~[ambari-metrics-storm-sink-with-common-2.6.1.0.144.jar:?]
at
org.apache.storm.metric.MetricsConsumerBolt.prepare(MetricsConsumerBolt.java:75)
~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
at
org.apache.storm.daemon.executor$fn__10252$fn__10265.invoke(executor.clj:800)
~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
at org.apache.storm.util$async_loop$fn__553.invoke(util.clj:482)
[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
Caused by: java.lang.ClassNotFoundException: org.apache.commons.lang.StringUtils
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
~[?:1.8.0_112]
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_112]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
~[?:1.8.0_112]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_112]
... 6 more{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24260) Ambari shows success when Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-24260: Fix Version/s: (was: 2.7.0) 2.7.1 > Ambari shows success when Decommission/Recommission operations fail > --- > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Fix For: 2.7.1 > > > Ambari shows success when Decommission/Recommission operations fail > If Decommission/Recommission operation fails with non zero exit code, that > component still gets decommissioned/recommissioned. We need to handle this > failure and not transition the state to Decommissioned/Recommissioned when > the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24260) Ambari shows success when Decommission/Recommission operations fail
[ https://issues.apache.org/jira/browse/AMBARI-24260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen reassigned AMBARI-24260: --- Assignee: Dmytro Sen > Ambari shows success when Decommission/Recommission operations fail > --- > > Key: AMBARI-24260 > URL: https://issues.apache.org/jira/browse/AMBARI-24260 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Fix For: 2.7.1 > > > Ambari shows success when Decommission/Recommission operations fail > If Decommission/Recommission operation fails with non zero exit code, that > component still gets decommissioned/recommissioned. We need to handle this > failure and not transition the state to Decommissioned/Recommissioned when > the respective operation fails -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24146) Metrics migrated during AMS upgrade are not saved into metadata table
Dmytro Sen created AMBARI-24146: --- Summary: Metrics migrated during AMS upgrade are not saved into metadata table Key: AMBARI-24146 URL: https://issues.apache.org/jira/browse/AMBARI-24146 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 the data migration itself works, but the UUIDs calculated for those metrics are not inserted into METADATA_UUID table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24103) topology_script.py return incorrect data
Dmytro Sen created AMBARI-24103:
---
Summary: topology_script.py return incorrect data
Key: AMBARI-24103
URL: https://issues.apache.org/jira/browse/AMBARI-24103
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.7.0
STR:
1) Change the rack of master HOST on '/\{YOUR_NEW_RACK_NAME}'
2) Restart all required services
3) Check that execute of bash 'topology_script.py HOST' returned
\{YOUR_NEW_RACK_NAME}
Actual result: topology_script.py return incorrect data, when the rack of host
was changed on UI.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24050) Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs
Dmytro Sen created AMBARI-24050:
---
Summary: Oozie service check failed during EU on unsecure cluster
due to presence of "ELService" configs
Key: AMBARI-24050
URL: https://issues.apache.org/jira/browse/AMBARI-24050
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Dmytro Sen
*STR*
# Deployed an unsecure cluster with Ambari version: 2.6.2.0-155 and HDP
version: 2.6.5.0-292 (cluster has Oozie, Falcon installed)
# Upgrade Ambari to Target Version: 2.7.0.0-652
# Start an Express Upgrade to HDP-3.0.0.0-1440, Falcon got deleted at one of
the steps and later Oozie got restarted
*Result*
Afterwards observed Oozie service check failed during EU
Further checked that Oozie logs say the following:
{code}
ERROR StatusLogger No log4j2 configuration file found. Using default
configuration: logging only errors to the console. Set system property
'log4j2.debug' to show Log4j2 internal initialization logging.
log4j:WARN No appenders could be found for logger
(org.apache.oozie.service.Services).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
info.
ERROR: Oozie could not be started
REASON: org.apache.oozie.service.ServiceException: E0113: class not found
[org.apache.oozie.extensions.OozieELExtensions]
Stacktrace:
-
org.apache.oozie.service.ServiceException: E0113: class not found
[org.apache.oozie.extensions.OozieELExtensions]
at org.apache.oozie.service.ELService.findMethod(ELService.java:226)
at
org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
at org.apache.oozie.service.ELService.init(ELService.java:135)
at
org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
at org.apache.oozie.service.Services.setService(Services.java:372)
at org.apache.oozie.service.Services.loadServices(Services.java:305)
at org.apache.oozie.service.Services.init(Services.java:213)
at
org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
{code}
Need to remove ELService properties during upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24050) Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs
[
https://issues.apache.org/jira/browse/AMBARI-24050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-24050:
Affects Version/s: 2.7.0
> Oozie service check failed during EU on unsecure cluster due to presence of
> "ELService" configs
> ---
>
> Key: AMBARI-24050
> URL: https://issues.apache.org/jira/browse/AMBARI-24050
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed an unsecure cluster with Ambari version: 2.6.2.0-155 and HDP
> version: 2.6.5.0-292 (cluster has Oozie, Falcon installed)
> # Upgrade Ambari to Target Version: 2.7.0.0-652
> # Start an Express Upgrade to HDP-3.0.0.0-1440, Falcon got deleted at one of
> the steps and later Oozie got restarted
> *Result*
> Afterwards observed Oozie service check failed during EU
> Further checked that Oozie logs say the following:
> {code}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'log4j2.debug' to show Log4j2 internal initialization logging.
> log4j:WARN No appenders could be found for logger
> (org.apache.oozie.service.Services).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> ERROR: Oozie could not be started
> REASON: org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> Stacktrace:
> -
> org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> at org.apache.oozie.service.ELService.findMethod(ELService.java:226)
> at
> org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
> at org.apache.oozie.service.ELService.init(ELService.java:135)
> at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
> at org.apache.oozie.service.Services.setService(Services.java:372)
> at org.apache.oozie.service.Services.loadServices(Services.java:305)
> at org.apache.oozie.service.Services.init(Services.java:213)
> at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> {code}
> Need to remove ELService properties during upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24050) Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs
[
https://issues.apache.org/jira/browse/AMBARI-24050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-24050:
Fix Version/s: 2.7.0
> Oozie service check failed during EU on unsecure cluster due to presence of
> "ELService" configs
> ---
>
> Key: AMBARI-24050
> URL: https://issues.apache.org/jira/browse/AMBARI-24050
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed an unsecure cluster with Ambari version: 2.6.2.0-155 and HDP
> version: 2.6.5.0-292 (cluster has Oozie, Falcon installed)
> # Upgrade Ambari to Target Version: 2.7.0.0-652
> # Start an Express Upgrade to HDP-3.0.0.0-1440, Falcon got deleted at one of
> the steps and later Oozie got restarted
> *Result*
> Afterwards observed Oozie service check failed during EU
> Further checked that Oozie logs say the following:
> {code}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'log4j2.debug' to show Log4j2 internal initialization logging.
> log4j:WARN No appenders could be found for logger
> (org.apache.oozie.service.Services).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> ERROR: Oozie could not be started
> REASON: org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> Stacktrace:
> -
> org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> at org.apache.oozie.service.ELService.findMethod(ELService.java:226)
> at
> org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
> at org.apache.oozie.service.ELService.init(ELService.java:135)
> at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
> at org.apache.oozie.service.Services.setService(Services.java:372)
> at org.apache.oozie.service.Services.loadServices(Services.java:305)
> at org.apache.oozie.service.Services.init(Services.java:213)
> at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> {code}
> Need to remove ELService properties during upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24050) Oozie service check failed during EU on unsecure cluster due to presence of "ELService" configs
[
https://issues.apache.org/jira/browse/AMBARI-24050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen reassigned AMBARI-24050:
---
Assignee: Dmytro Sen
> Oozie service check failed during EU on unsecure cluster due to presence of
> "ELService" configs
> ---
>
> Key: AMBARI-24050
> URL: https://issues.apache.org/jira/browse/AMBARI-24050
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Fix For: 2.7.0
>
>
> *STR*
> # Deployed an unsecure cluster with Ambari version: 2.6.2.0-155 and HDP
> version: 2.6.5.0-292 (cluster has Oozie, Falcon installed)
> # Upgrade Ambari to Target Version: 2.7.0.0-652
> # Start an Express Upgrade to HDP-3.0.0.0-1440, Falcon got deleted at one of
> the steps and later Oozie got restarted
> *Result*
> Afterwards observed Oozie service check failed during EU
> Further checked that Oozie logs say the following:
> {code}
> ERROR StatusLogger No log4j2 configuration file found. Using default
> configuration: logging only errors to the console. Set system property
> 'log4j2.debug' to show Log4j2 internal initialization logging.
> log4j:WARN No appenders could be found for logger
> (org.apache.oozie.service.Services).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> ERROR: Oozie could not be started
> REASON: org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> Stacktrace:
> -
> org.apache.oozie.service.ServiceException: E0113: class not found
> [org.apache.oozie.extensions.OozieELExtensions]
> at org.apache.oozie.service.ELService.findMethod(ELService.java:226)
> at
> org.apache.oozie.service.ELService.extractFunctions(ELService.java:104)
> at org.apache.oozie.service.ELService.init(ELService.java:135)
> at
> org.apache.oozie.service.Services.setServiceInternal(Services.java:386)
> at org.apache.oozie.service.Services.setService(Services.java:372)
> at org.apache.oozie.service.Services.loadServices(Services.java:305)
> at org.apache.oozie.service.Services.init(Services.java:213)
> at
> org.apache.oozie.servlet.ServicesLoader.contextInitialized(ServicesLoader.java:46)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4276)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4779)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:803)
> {code}
> Need to remove ELService properties during upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23998) AMS collector RPM configs are empty.
Dmytro Sen created AMBARI-23998: --- Summary: AMS collector RPM configs are empty. Key: AMBARI-23998 URL: https://issues.apache.org/jira/browse/AMBARI-23998 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23929) Stack changes for AMS to help with HDP 2.6 to 3.0 EU.
Dmytro Sen created AMBARI-23929: --- Summary: Stack changes for AMS to help with HDP 2.6 to 3.0 EU. Key: AMBARI-23929 URL: https://issues.apache.org/jira/browse/AMBARI-23929 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 * Add RESTART AMS tasks in HDP 2.6 to 3.0 EU after stack upgrade and before Smartsense. * Add check in HDFS, HBase, YARN, Hive start scripts in HDP 2.6 stack to make sure AMS hadoop sinks are not 2.7.0.0 version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23834) Rebalance HDFS fails
[
https://issues.apache.org/jira/browse/AMBARI-23834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-23834.
-
Resolution: Fixed
> Rebalance HDFS fails
>
>
> Key: AMBARI-23834
> URL: https://issues.apache.org/jira/browse/AMBARI-23834
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Dmytro Sen
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The rebalance HDFS from Ambari is not working.
> DFS Usage before rebalance (threshold of 1%)
> {code:bash}
> [cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ hadoop dfsadmin
> -report | grep 'DFS Used%'
> WARNING: Use of this script to execute dfsadmin is deprecated.
> WARNING: Attempting to execute replacement "hdfs dfsadmin" instead.
> DFS Used%: 4.21%
> DFS Used%: 1.89%
> DFS Used%: 3.40%
> DFS Used%: 7.91%
> DFS Used%: 3.47%
> DFS Used%: 4.67%
> DFS Used%: 3.54%
> DFS Used%: 2.80%
> {code}
> After invoking the rebalance HDFS from Ambari UI, the /system/balancer.id
> file is not present (meaning balancer is not running)
> {code:bash}
> [cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ while true; do echo
> 'checking /system'; hadoop fs -ls /system; sleep 1; done
> checking /system
> ls: `/system': No such file or directory
> checking /system
> ls: `/system': No such file or directory
> checking /system
> ls: `/system': No such file or directory
> checking /system
> ls: `/system': No such file or directory
> checking /system
> ls: `/system': No such file or directory
> checking /system
> ^Cchecking /system
> ls: `/system': No such file or directory
> ^C
> [cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ hadoop dfsadmin
> -report | grep 'DFS Used%'
> WARNING: Use of this script to execute dfsadmin is deprecated.
> WARNING: Attempting to execute replacement "hdfs dfsadmin" instead.
> DFS Used%: 4.21%
> DFS Used%: 1.89%
> DFS Used%: 3.40%
> DFS Used%: 7.91%
> DFS Used%: 3.47%
> DFS Used%: 4.67%
> DFS Used%: 3.54%
> DFS Used%: 2.80%
> [cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23609) Credential store is not working
[ https://issues.apache.org/jira/browse/AMBARI-23609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23609. - Resolution: Fixed > Credential store is not working > --- > > Key: AMBARI-23609 > URL: https://issues.apache.org/jira/browse/AMBARI-23609 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > The command json element "configuration_credentials" are not present in the > command jsons on the agents, though they are present on the server side > command json (at least it is present in the json persisted at > HostRoleCommand.constructExecutionCommandEntity(HostRoleCommand:239)). This > causes that the credential store is not working, as this command json element > is essential. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23751) Ambari ViewFS: Add ability to add XML inclusion node to a configuration file
[ https://issues.apache.org/jira/browse/AMBARI-23751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23751. - Resolution: Fixed > Ambari ViewFS: Add ability to add XML inclusion node to a configuration file > > > Key: AMBARI-23751 > URL: https://issues.apache.org/jira/browse/AMBARI-23751 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > ViewFS mountable as recommended here: > https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ViewFs.html, > should be added as XML inclusion node to core-site. > Currently Ambari does not support this. We should add a special field-type > that can be serialized by the agent as not a key-value but write out the > value as XML node in this case inclusion field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23685) Rename metric tables to support schema upgrade.
[ https://issues.apache.org/jira/browse/AMBARI-23685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23685. - Resolution: Fixed > Rename metric tables to support schema upgrade. > --- > > Key: AMBARI-23685 > URL: https://issues.apache.org/jira/browse/AMBARI-23685 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2h > Remaining Estimate: 0h > > METRIC_RECORD -> METRIC_RECORD_V2 > METRIC_AGGREGATE -> METRIC_AGGREGATE_V2 > and so on... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23493) Decommission Datanode doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-23493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23493. - Resolution: Fixed > Decommission Datanode doesn't work > -- > > Key: AMBARI-23493 > URL: https://issues.apache.org/jira/browse/AMBARI-23493 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > On an Ambari270 cluster, try to decommission a datanode. > You could see bgop is triggerred and shows as sucsessful. > But Datanode seems to be still in started state and Decommission op is still > available in dropdown. > The issue is caused by recent perf changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23835) Port is not cleared for Superset Database type if Mysql is selected than SQLLite is selected in Installer Wizard
[ https://issues.apache.org/jira/browse/AMBARI-23835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23835. - Resolution: Fixed > Port is not cleared for Superset Database type if Mysql is selected than > SQLLite is selected in Installer Wizard > > > Key: AMBARI-23835 > URL: https://issues.apache.org/jira/browse/AMBARI-23835 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1) Launch Installer Wizard and select Superset in services to install > 2) In Databases tab of Customize Services tab , select Superset > 3) By default for , Superset Database type , SQLITE is selected and Port is > empty. > 4) Select MYSQL and then reselect SQLLITE , not port is not cleared and > still shows 3306. It should be cleared . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23835) Port is not cleared for Superset Database type if Mysql is selected than SQLLite is selected in Installer Wizard
Dmytro Sen created AMBARI-23835: --- Summary: Port is not cleared for Superset Database type if Mysql is selected than SQLLite is selected in Installer Wizard Key: AMBARI-23835 URL: https://issues.apache.org/jira/browse/AMBARI-23835 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 1) Launch Installer Wizard and select Superset in services to install 2) In Databases tab of Customize Services tab , select Superset 3) By default for , Superset Database type , SQLITE is selected and Port is empty. 4) Select MYSQL and then reselect SQLLITE , not port is not cleared and still shows 3306. It should be cleared . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23833) viewFS : Blueprint deployed clusters doesn't have xml include content in core-site.xml
Dmytro Sen created AMBARI-23833:
---
Summary: viewFS : Blueprint deployed clusters doesn't have xml
include content in core-site.xml
Key: AMBARI-23833
URL: https://issues.apache.org/jira/browse/AMBARI-23833
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 2.7.0
- Deployed a cluster with NN federation + viewFS via blueprint.
- viewFS is enabled by having all relevant configs in viewfs-mount-table
- Deploy was successful but upon accessing hdfs we got the error as below
{code}
# hdfs dfs -ls /
ls: ViewFs: Cannot initialize: Empty Mount table in config for viewfs://cl1/
{code}
Checked in core-site.xml and none of the core-site.xml has the xml include
content for viewfs
They should have
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23828) Provide a command line utility in AMS scripts to upgrade the schema using the collector's tool.
Dmytro Sen created AMBARI-23828: --- Summary: Provide a command line utility in AMS scripts to upgrade the schema using the collector's tool. Key: AMBARI-23828 URL: https://issues.apache.org/jira/browse/AMBARI-23828 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 * This can look something like _su - ams -c '/usr/sbin/ambari-metrics-collector --config /etc/ambari-metrics-collector/conf/ upgrade '_ * Based on implementation of AMBARI-23780, this command line utility should be able to start and stop upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23777) Change viewfs mountable file and config type name
[ https://issues.apache.org/jira/browse/AMBARI-23777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23777. - Resolution: Fixed > Change viewfs mountable file and config type name > - > > Key: AMBARI-23777 > URL: https://issues.apache.org/jira/browse/AMBARI-23777 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23780) Implement an upgrade helper in Ambari Metrics collector that copies data from the old schema to the new.
Dmytro Sen created AMBARI-23780: --- Summary: Implement an upgrade helper in Ambari Metrics collector that copies data from the old schema to the new. Key: AMBARI-23780 URL: https://issues.apache.org/jira/browse/AMBARI-23780 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 * The upgrade helper can be a main class that is callable through command line. * Inputs to the upgrade helper # Metric list file (Default -> metrics_whitelist file in conf. If not present, copy over all the metrics) # Start timestamp (Default -> Last 1 month) (Max 8640 points per metric in minute table) * The upgrade helper runs a set of SQL queries to fetch data from all aggregate tables except METRIC_AGGREGATE and uses the API to write to the corresponding new tables. * The tool marks the completion of every metric entry by using a marker file (list of processed metric names) or a simple hbase table. * The next time the upgrade tool is invoked, the marker is used to identify whether the metric needs to be copied. * Let's have the upgrade helper log the status to a different file than collector log as a mechanism to monitor the status. We have to make a decision on whether the upgrade tool helper should be *synchronous* or *asynchronous*. If it is asynchronous, we should add the ability for it to '*stop performing upgrade*'. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23777) Change viewfs mountable file and config type name
Dmytro Sen created AMBARI-23777: --- Summary: Change viewfs mountable file and config type name Key: AMBARI-23777 URL: https://issues.apache.org/jira/browse/AMBARI-23777 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23751) Ambari ViewFS: Add ability to add XML inclusion node to a configuration file
Dmytro Sen created AMBARI-23751: --- Summary: Ambari ViewFS: Add ability to add XML inclusion node to a configuration file Key: AMBARI-23751 URL: https://issues.apache.org/jira/browse/AMBARI-23751 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 ViewFS mountable as recommended here: https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/ViewFs.html, should be added as XML inclusion node to core-site. Currently Ambari does not support this. We should add a special field-type that can be serialized by the agent as not a key-value but write out the value as XML node in this case inclusion field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23718) Update repoinfo latest with the link from repository
[ https://issues.apache.org/jira/browse/AMBARI-23718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23718. - Resolution: Fixed > Update repoinfo latest with the link from repository > > > Key: AMBARI-23718 > URL: https://issues.apache.org/jira/browse/AMBARI-23718 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23718) Update repoinfo latest with the link from repository
Dmytro Sen created AMBARI-23718: --- Summary: Update repoinfo latest with the link from repository Key: AMBARI-23718 URL: https://issues.apache.org/jira/browse/AMBARI-23718 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23685) Rename metric tables to support schema upgrade.
Dmytro Sen created AMBARI-23685: --- Summary: Rename metric tables to support schema upgrade. Key: AMBARI-23685 URL: https://issues.apache.org/jira/browse/AMBARI-23685 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 METRIC_RECORD -> METRIC_RECORD_V2 METRIC_AGGREGATE -> METRIC_AGGREGATE_V2 and so on... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23609) Credential store is not working
Dmytro Sen created AMBARI-23609: --- Summary: Credential store is not working Key: AMBARI-23609 URL: https://issues.apache.org/jira/browse/AMBARI-23609 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 The command json element "configuration_credentials" are not present in the command jsons on the agents, though they are present on the server side command json (at least it is present in the json persisted at HostRoleCommand.constructExecutionCommandEntity(HostRoleCommand:239)). This causes that the credential store is not working, as this command json element is essential. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23573) HDFS install fails at before-ANY hook due to no created instances
Dmytro Sen created AMBARI-23573: --- Summary: HDFS install fails at before-ANY hook due to no created instances Key: AMBARI-23573 URL: https://issues.apache.org/jira/browse/AMBARI-23573 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 HDFS install fails with Ambari 3.0.0.0-1527 and HDPCORE-1.0.0-b227 due to: File "/var/lib/ambari-agent/cache/stack-hooks/before-ANY/scripts/hook.py", line 26, in hook import params File "/var/lib/ambari-agent/cache/stack-hooks/before-ANY/scripts/params.py", line 227, in components_instance_type=HADOOP_CLIENT_COMPONENT_TYPE) ValueError: There are no created instances. Use create-mpack-instance command to add them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23493) Decommission Datanode doesn't work
Dmytro Sen created AMBARI-23493: --- Summary: Decommission Datanode doesn't work Key: AMBARI-23493 URL: https://issues.apache.org/jira/browse/AMBARI-23493 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 On an Ambari270 cluster, try to decommission a datanode. You could see bgop is triggerred and shows as sucsessful. But Datanode seems to be still in started state and Decommission op is still available in dropdown. The issue is caused by recent perf changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23449) Agent can not to connect to server during blueprint deploy
[ https://issues.apache.org/jira/browse/AMBARI-23449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428056#comment-16428056 ] Dmytro Sen commented on AMBARI-23449: - [~majorendre], thanks for taking a look at this. I believe the issue is only present on the environment with old python version. > Agent can not to connect to server during blueprint deploy > -- > > Key: AMBARI-23449 > URL: https://issues.apache.org/jira/browse/AMBARI-23449 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Affects Versions: 2.7.0 > Environment: Suse 12 sp3 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Blueprint deploy was hunged on hosts assignments. > ambari-agent.log: > INFO 2018-03-27 15:23:58,132 NetUtil.py:61 - Connecting to > https://ctr-e138-1518143905142-164693-01-02.hwx.site:8440/connection_info > INFO 2018-03-27 15:23:58,155 security.py:59 - Server require two-way SSL > authentication. Use it instead of one-way... > INFO 2018-03-27 15:23:58,155 security.py:61 - Connecting to > wss://ctr-e138-1518143905142-164693-01-02.hwx.site:8441/agent/stomp/v1 > INFO 2018-03-27 15:23:58,155 security.py:207 - Server certicate exists, ok > INFO 2018-03-27 15:23:58,155 security.py:215 - Agent key exists, ok > INFO 2018-03-27 15:23:58,156 security.py:223 - Agent certificate exists, ok > WARNING 2018-03-27 15:23:58,161 security.py:99 - Could not connect to > wss://ctr-e138-1518143905142-164693-01-02.hwx.site:8441/agent/stomp/v1. > [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure > (_ssl.c:661) > INFO 2018-03-27 15:23:58,161 HeartbeatThread.py:99 - Connection error "[SSL: > SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:661)". > Re-running the registration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23458) Creating component instances shouldn't fail if instance already exists when called from the agent
Dmytro Sen created AMBARI-23458:
---
Summary: Creating component instances shouldn't fail if instance
already exists when called from the agent
Key: AMBARI-23458
URL: https://issues.apache.org/jira/browse/AMBARI-23458
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 3.0.0
Reinstall operation fails because the component instance already exists.
ValueError: The instance
/usr/hwx/instances/hdpcore/HDPCORE/default/zookeeper_client already exist. To
change the version use set-mpack-instance command{code}
Need to add fail_if_exists flag to instance creation command and set it to
False when called from mpack_manager_helper.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23458) Creating component instances shouldn't fail if instance already exists when called from the agent
[
https://issues.apache.org/jira/browse/AMBARI-23458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-23458:
Description:
Reinstall operation fails because the component instance already exists.
ValueError: The instance
/usr/hwx/instances/hdpcore/HDPCORE/default/zookeeper_client already exist. To
change the version use set-mpack-instance command
Need to add fail_if_exists flag to instance creation command and set it to
False when called from mpack_manager_helper.
was:
Reinstall operation fails because the component instance already exists.
ValueError: The instance
/usr/hwx/instances/hdpcore/HDPCORE/default/zookeeper_client already exist. To
change the version use set-mpack-instance command{code}
Need to add fail_if_exists flag to instance creation command and set it to
False when called from mpack_manager_helper.
> Creating component instances shouldn't fail if instance already exists when
> called from the agent
> -
>
> Key: AMBARI-23458
> URL: https://issues.apache.org/jira/browse/AMBARI-23458
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Major
> Fix For: 3.0.0
>
>
> Reinstall operation fails because the component instance already exists.
> ValueError: The instance
> /usr/hwx/instances/hdpcore/HDPCORE/default/zookeeper_client already exist. To
> change the version use set-mpack-instance command
> Need to add fail_if_exists flag to instance creation command and set it to
> False when called from mpack_manager_helper.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23449) Agent can not to connect to server during blueprint deploy
Dmytro Sen created AMBARI-23449: --- Summary: Agent can not to connect to server during blueprint deploy Key: AMBARI-23449 URL: https://issues.apache.org/jira/browse/AMBARI-23449 Project: Ambari Issue Type: Task Components: ambari-agent Affects Versions: 2.7.0 Environment: Suse 12 sp3 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.7.0 Blueprint deploy was hunged on hosts assignments. ambari-agent.log: INFO 2018-03-27 15:23:58,132 NetUtil.py:61 - Connecting to https://ctr-e138-1518143905142-164693-01-02.hwx.site:8440/connection_info INFO 2018-03-27 15:23:58,155 security.py:59 - Server require two-way SSL authentication. Use it instead of one-way... INFO 2018-03-27 15:23:58,155 security.py:61 - Connecting to wss://ctr-e138-1518143905142-164693-01-02.hwx.site:8441/agent/stomp/v1 INFO 2018-03-27 15:23:58,155 security.py:207 - Server certicate exists, ok INFO 2018-03-27 15:23:58,155 security.py:215 - Agent key exists, ok INFO 2018-03-27 15:23:58,156 security.py:223 - Agent certificate exists, ok WARNING 2018-03-27 15:23:58,161 security.py:99 - Could not connect to wss://ctr-e138-1518143905142-164693-01-02.hwx.site:8441/agent/stomp/v1. [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:661) INFO 2018-03-27 15:23:58,161 HeartbeatThread.py:99 - Connection error "[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:661)". Re-running the registration -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23308) Ticket cache file is delete before balancer access it during rebalance HDFS operation
[ https://issues.apache.org/jira/browse/AMBARI-23308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-23308: Summary: Ticket cache file is delete before balancer access it during rebalance HDFS operation (was: Tgt cache file is delete before balancer access it during rebalance HDFS operation) > Ticket cache file is delete before balancer access it during rebalance HDFS > operation > - > > Key: AMBARI-23308 > URL: https://issues.apache.org/jira/browse/AMBARI-23308 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Since the rebalance command is run into background without waiting for > finish, delete tgt cache file is executed right after subprocess start. > The subprocess fails due to missing tgt cache file because the file is > deleted before the subprocess access it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23308) Tgt cache file is delete before balancer access it during rebalance HDFS operation
Dmytro Sen created AMBARI-23308: --- Summary: Tgt cache file is delete before balancer access it during rebalance HDFS operation Key: AMBARI-23308 URL: https://issues.apache.org/jira/browse/AMBARI-23308 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.2 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.6.2 Since the rebalance command is run into background without waiting for finish, delete tgt cache file is executed right after subprocess start. The subprocess fails due to missing tgt cache file because the file is deleted before the subprocess access it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23248) Integrate Instance manager into HDPCORE mpack
Dmytro Sen created AMBARI-23248: --- Summary: Integrate Instance manager into HDPCORE mpack Key: AMBARI-23248 URL: https://issues.apache.org/jira/browse/AMBARI-23248 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 HDFS, HADOOP-CLIENTS, Zookeeper and zookeeper clients should use instance manager to determine bin and conf directories location -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23231) Server service_check does not get executed for new mpacks
Dmytro Sen created AMBARI-23231: --- Summary: Server service_check does not get executed for new mpacks Key: AMBARI-23231 URL: https://issues.apache.org/jira/browse/AMBARI-23231 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 During install wizard, service checks for clients were being called but not for servers. We need it to be the other way around. We have disabled the client service check but need to investigate why the server checks are disabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23170) Instance manager json output should have the same structure for both client and server modules
[ https://issues.apache.org/jira/browse/AMBARI-23170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23170. - Resolution: Fixed > Instance manager json output should have the same structure for both client > and server modules > -- > > Key: AMBARI-23170 > URL: https://issues.apache.org/jira/browse/AMBARI-23170 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23170) Instance manager json output should have the same structure for both client and server modules
Dmytro Sen created AMBARI-23170: --- Summary: Instance manager json output should have the same structure for both client and server modules Key: AMBARI-23170 URL: https://issues.apache.org/jira/browse/AMBARI-23170 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23121) Fix few instance manager issues found during ZK deployment
[ https://issues.apache.org/jira/browse/AMBARI-23121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23121. - Resolution: Fixed > Fix few instance manager issues found during ZK deployment > -- > > Key: AMBARI-23121 > URL: https://issues.apache.org/jira/browse/AMBARI-23121 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: ambari-server >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23121) Fix few instance manager issues found during ZK deployment
Dmytro Sen created AMBARI-23121: --- Summary: Fix few instance manager issues found during ZK deployment Key: AMBARI-23121 URL: https://issues.apache.org/jira/browse/AMBARI-23121 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: ambari-server Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23120) Create helper functions for using new instance manager library from the agent scripts
Dmytro Sen created AMBARI-23120: --- Summary: Create helper functions for using new instance manager library from the agent scripts Key: AMBARI-23120 URL: https://issues.apache.org/jira/browse/AMBARI-23120 Project: Ambari Issue Type: Task Components: ambari-agent Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23004) Create initial version of InstanceManager to create instance layout
[ https://issues.apache.org/jira/browse/AMBARI-23004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-23004. - Resolution: Fixed > Create initial version of InstanceManager to create instance layout > > > Key: AMBARI-23004 > URL: https://issues.apache.org/jira/browse/AMBARI-23004 > Project: Ambari > Issue Type: Task > Components: ambari-agent >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 5h 50m > Remaining Estimate: 0h > > We need an instance manager tool for managing the lifecycle of mpack > instances, service instances, component instances. This will be the > replacement for hdp-select, conf-select > Examples of few operations that we will need > # create-mpack-instance > # create-component-instance > # set-component-instance-version > # get-component-instance-version > # get-component-instance-confdir -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23004) Create initial version of InstanceManager to create instance layout
Dmytro Sen created AMBARI-23004: --- Summary: Create initial version of InstanceManager to create instance layout Key: AMBARI-23004 URL: https://issues.apache.org/jira/browse/AMBARI-23004 Project: Ambari Issue Type: Task Components: ambari-agent Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 We need an instance manager tool for managing the lifecycle of mpack instances, service instances, component instances. This will be the replacement for hdp-select, conf-select Examples of few operations that we will need # create-mpack-instance # create-component-instance # set-component-instance-version # get-component-instance-version # get-component-instance-confdir -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22845) Update service metainfo schema
[
https://issues.apache.org/jira/browse/AMBARI-22845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22845:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged PR into branch-feature-AMBARI-14714
> Update service metainfo schema
> --
>
> Key: AMBARI-22845
> URL: https://issues.apache.org/jira/browse/AMBARI-22845
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> An mpack is composed on multiple modules. Modules could be categorized as
> "SERVER" module or a "CLIENT" module. In Ambari an mpack represents a stack
> and a module represents a service definition. We need to update the service
> metainfo schema to be able to specify the module category.
>
> {code}
>
> MODULE-NAME
> LEGACY|SERVER|CLIENT
>
> {code}
> LEGACY category should be the default to support old stacks (HDP-2.6).
> Also an mpack could ship with different version of datanode and namenode
> (hotfix release for a component). Apart from having a service version, we
> should also be able to specify the component version in the mpack. If
> component version is not specified then componentVersion == serviceVersion
> {code}
>
> HDFS
> SERVER
> 3.0.0.0-b123
>
>
> DATANODE
> 3.0.0.0-h7-b5
>
>
> NAMENODE
>
>
>
> {code}
> In the example above DATANODE is 3.0.0.0-h7-b5 whereas all other HDFS
> components are 3.0.0.0-b123.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22854) Fix running service checks with new mpack definitions
[ https://issues.apache.org/jira/browse/AMBARI-22854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22854: Status: Patch Available (was: In Progress) > Fix running service checks with new mpack definitions > - > > Key: AMBARI-22854 > URL: https://issues.apache.org/jira/browse/AMBARI-22854 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > *Background* > # New mpack composition forces us to break down our service definitions into > client and server modules. This is because EDW mpack needs to be composed of > HIVE, HIVE-CLIENT, ZOOKEEPER-CLIENT. EDW mpack doesnt really contain > ZOOKEEPER service just ZOOKEEPER-CLIENT. Hence the new mpack structure we > will have to break the ZOOKEEPER service definition into "zookeeper" server > module and "zookeeper-client" client module definitions. > However, breaking the service definition into client and server modules would > require the logic for calling service check to be updated because now to run > service check for zookeeper, we will need to call > ZOOKEEPER-CLIENT/ZOOKEEPER-CLIENT to run the service check. > cc: [~mradhakrishnan] who has more context on this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22854) Fix running service checks with new mpack definitions
Dmytro Sen created AMBARI-22854: --- Summary: Fix running service checks with new mpack definitions Key: AMBARI-22854 URL: https://issues.apache.org/jira/browse/AMBARI-22854 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 3.0.0 *Background* # New mpack composition forces us to break down our service definitions into client and server modules. This is because EDW mpack needs to be composed of HIVE, HIVE-CLIENT, ZOOKEEPER-CLIENT. EDW mpack doesnt really contain ZOOKEEPER service just ZOOKEEPER-CLIENT. Hence the new mpack structure we will have to break the ZOOKEEPER service definition into "zookeeper" server module and "zookeeper-client" client module definitions. However, breaking the service definition into client and server modules would require the logic for calling service check to be updated because now to run service check for zookeeper, we will need to call ZOOKEEPER-CLIENT/ZOOKEEPER-CLIENT to run the service check. cc: [~mradhakrishnan] who has more context on this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22845) Update service metainfo schema
[
https://issues.apache.org/jira/browse/AMBARI-22845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22845:
Status: Patch Available (was: In Progress)
> Update service metainfo schema
> --
>
> Key: AMBARI-22845
> URL: https://issues.apache.org/jira/browse/AMBARI-22845
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> An mpack is composed on multiple modules. Modules could be categorized as
> "SERVER" module or a "CLIENT" module. In Ambari an mpack represents a stack
> and a module represents a service definition. We need to update the service
> metainfo schema to be able to specify the module category.
>
> {code}
>
> MODULE-NAME
> LEGACY|SERVER|CLIENT
>
> {code}
> LEGACY category should be the default to support old stacks (HDP-2.6).
> Also an mpack could ship with different version of datanode and namenode
> (hotfix release for a component). Apart from having a service version, we
> should also be able to specify the component version in the mpack. If
> component version is not specified then componentVersion == serviceVersion
> {code}
>
> HDFS
> SERVER
> 3.0.0.0-b123
>
>
> DATANODE
> 3.0.0.0-h7-b5
>
>
> NAMENODE
>
>
>
> {code}
> In the example above DATANODE is 3.0.0.0-h7-b5 whereas all other HDFS
> components are 3.0.0.0-b123.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22845) Update service metainfo schema
Dmytro Sen created AMBARI-22845:
---
Summary: Update service metainfo schema
Key: AMBARI-22845
URL: https://issues.apache.org/jira/browse/AMBARI-22845
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 3.0.0
An mpack is composed on multiple modules. Modules could be categorized as
"SERVER" module or a "CLIENT" module. In Ambari an mpack represents a stack and
a module represents a service definition. We need to update the service
metainfo schema to be able to specify the module category.
{code}
MODULE-NAME
LEGACY|SERVER|CLIENT
{code}
LEGACY category should be the default to support old stacks (HDP-2.6).
Also an mpack could ship with different version of datanode and namenode
(hotfix release for a component). Apart from having a service version, we
should also be able to specify the component version in the mpack. If component
version is not specified then componentVersion == serviceVersion
{code}
HDFS
SERVER
3.0.0.0-b123
DATANODE
3.0.0.0-h7-b5
NAMENODE
{code}
In the example above DATANODE is 3.0.0.0-h7-b5 whereas all other HDFS
components are 3.0.0.0-b123.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22815) Change requiredServices in metainfo.xml
[
https://issues.apache.org/jira/browse/AMBARI-22815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22815.
-
Resolution: Fixed
Committed into branch-feature-AMBARI-14714
> Change requiredServices in metainfo.xml
> ---
>
> Key: AMBARI-22815
> URL: https://issues.apache.org/jira/browse/AMBARI-22815
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Today we define requiredServices as follows
> {code}
>
> ZOOKEEPER
>
> {code}
> In the mpack model we need to categorize the scope of service dependency. We
> could have an INSTALL time dependency (i.e. we should also install the
> dependent service) or a RUNTIME dependency (i.e. there should be a running
> instance of the service in the cluster).
> For example HIVE in EDW mpack, will have an install-time dependency on
> ZOOKEEPER-CLIENT but a RUNTIME dependency on ZOOKEEPER.
> {code}
>
>
> ZOOKEEPER-CLIENT
> INSTALL
>
>
> ZOOKEEPER
> RUNTIME
>
>
> {code}
> We should also check how we maintain compatibility with legacy stack
> definitions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22815) Change requiredServices in metainfo.xml
Dmytro Sen created AMBARI-22815:
---
Summary: Change requiredServices in metainfo.xml
Key: AMBARI-22815
URL: https://issues.apache.org/jira/browse/AMBARI-22815
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 3.0.0
Today we define requiredServices as follows
{code}
ZOOKEEPER
{code}
In the mpack model we need to categorize the scope of service dependency. We
could have an INSTALL time dependency (i.e. we should also install the
dependent service) or a RUNTIME dependency (i.e. there should be a running
instance of the service in the cluster).
For example HIVE in EDW mpack, will have an install-time dependency on
ZOOKEEPER-CLIENT but a RUNTIME dependency on ZOOKEEPER.
{code}
ZOOKEEPER-CLIENT
INSTALL
ZOOKEEPER
RUNTIME
{code}
We should also check how we maintain compatibility with legacy stack
definitions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22709) Break down HDP/3.0 role command order to individual service level
Dmytro Sen created AMBARI-22709:
---
Summary: Break down HDP/3.0 role command order to individual
service level
Key: AMBARI-22709
URL: https://issues.apache.org/jira/browse/AMBARI-22709
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
For HDP 3.0, we need to get rid of stack level RCO
{{stacks/HDP/3.0/role_command_order.json}} and break it down to individual
service level RCOs. (ie.
{{common-services/HDFS/3.0.0.3.0/role_command_order.json}}).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22428) Update db schema to use service_id instead of service_name (requests part)
[
https://issues.apache.org/jira/browse/AMBARI-22428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22428.
-
Resolution: Fixed
Committed to branch-feature-AMBARI-14714
> Update db schema to use service_id instead of service_name (requests part)
> --
>
> Key: AMBARI-22428
> URL: https://issues.apache.org/jira/browse/AMBARI-22428
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
>
> As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
> updated tables to use the service_id as foreign key instead of service_name.
> https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> For example:
> {code}
> CREATE TABLE servicecomponentdesiredstate (
> id BIGINT NOT NULL,
> component_name VARCHAR(255) NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_group_id BIGINT NOT NULL,
> service_id BIGINT NOT NULL,
> desired_repo_version_id BIGINT NOT NULL,
> desired_state VARCHAR(255) NOT NULL,
> recovery_enabled SMALLINT NOT NULL DEFAULT 0,
> repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
> CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
> CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
> service_group_id, cluster_id),
> CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
> REFERENCES repo_version (repo_version_id),
> CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
> service_group_id, cluster_id) REFERENCES clusterservices (id,
> service_group_id, cluster_id));
> {code}
> We need to update other DB tables to use service_id instead of service_name.
> For example:
> {code}
> CREATE TABLE serviceconfig (
> service_config_id BIGINT NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_name VARCHAR(255) NOT NULL,
> version BIGINT NOT NULL,
> create_timestamp BIGINT NOT NULL,
> stack_id BIGINT NOT NULL,
> user_name VARCHAR(255) NOT NULL DEFAULT '_db',
> group_id BIGINT,
> note TEXT,
> CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
> CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
> stack(stack_id),
> CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name,
> version));
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22650) Add ability to define packages at stack level
[ https://issues.apache.org/jira/browse/AMBARI-22650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-22650. - Resolution: Fixed Committed into branch-feature-AMBARI-14714 > Add ability to define packages at stack level > - > > Key: AMBARI-22650 > URL: https://issues.apache.org/jira/browse/AMBARI-22650 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > > Today, we define the list of packages to be installed at individual service > level metainfo.xml. > In the new mpack model Ambari will no longer execute (i.e. "yum install > hadoop", "yum install hadoop-client"), but instead Ambari will install > individual mpack meta-rpms (i.e. "yum install hdpcore", "yum install edw") > whenever a component from that mpack is installed. > So we should add ability to define list of packages at the stack level (i.e. > stack/metainfo.xml). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22650) Add ability to define packages at stack level
Dmytro Sen created AMBARI-22650: --- Summary: Add ability to define packages at stack level Key: AMBARI-22650 URL: https://issues.apache.org/jira/browse/AMBARI-22650 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: 3.0.0 Today, we define the list of packages to be installed at individual service level metainfo.xml. In the new mpack model Ambari will no longer execute (i.e. "yum install hadoop", "yum install hadoop-client"), but instead Ambari will install individual mpack meta-rpms (i.e. "yum install hdpcore", "yum install edw") whenever a component from that mpack is installed. So we should add ability to define list of packages at the stack level (i.e. stack/metainfo.xml). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22604) Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization
[ https://issues.apache.org/jira/browse/AMBARI-22604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-22604. - Resolution: Fixed Committed to branch-feature-AMBARI-14714 > Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and > serviceConfigTypes initialization > > > Key: AMBARI-22604 > URL: https://issues.apache.org/jira/browse/AMBARI-22604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: ambari-server >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 3.0.0 > > > 1) HostConfigMappingEntity is not correct. You can't use same field > cluster_id for current entity and for joined columns. Use > ClusterTest.testDesiredConfig() to see this issue. > 2) As you can see in ClusterImpl we are using concurrent maps/lists and locks > in methods. Please do the same for your code chnages. > 3) Initialize map serviceConfigTypes, it will prevent many NPE and additional > check for NULL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22604) Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization
Dmytro Sen created AMBARI-22604: --- Summary: Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization Key: AMBARI-22604 URL: https://issues.apache.org/jira/browse/AMBARI-22604 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: ambari-server Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Critical Fix For: 3.0.0 1) HostConfigMappingEntity is not correct. You can't use same field cluster_id for current entity and for joined columns. Use ClusterTest.testDesiredConfig() to see this issue. 2) As you can see in ClusterImpl we are using concurrent maps/lists and locks in methods. Please do the same for your code chnages. 3) Initialize map serviceConfigTypes, it will prevent many NPE and additional check for NULL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22562) Remove stack metainfo.xml from management pack
[
https://issues.apache.org/jira/browse/AMBARI-22562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22562.
-
Resolution: Fixed
Committed to branch-feature-AMBARI-14714
> Remove stack metainfo.xml from management pack
> --
>
> Key: AMBARI-22562
> URL: https://issues.apache.org/jira/browse/AMBARI-22562
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 3.0.0
>
>
> # The stack metainfo.xml in a management pack is redundant.
> # We can create the stack metainfo.xml when we install the management pack.
> # Update the prereqs in mpack.json to include min-jdk and max-jdk properties
> and then create the metainfo.xml when the mpack is installed.
> {code}
> "prerequisites": {
> "min-ambari-version" : "3.0.0",
> "max-ambari-version" : "",
> "min-jdk" : "1.8",
> "max-jdk" : "1.8"
> },
> {code}
> # Generate the stack metainfo.xml as
> {code}
>
>
> 1.8
> 1.8
>
> true
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22562) Remove stack metainfo.xml from management pack
Dmytro Sen created AMBARI-22562:
---
Summary: Remove stack metainfo.xml from management pack
Key: AMBARI-22562
URL: https://issues.apache.org/jira/browse/AMBARI-22562
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Fix For: 3.0.0
# The stack metainfo.xml in a management pack is redundant.
# We can create the stack metainfo.xml when we install the management pack.
# Update the prereqs in mpack.json to include min-jdk and max-jdk properties
and then create the metainfo.xml when the mpack is installed.
{code}
"prerequisites": {
"min-ambari-version" : "3.0.0",
"max-ambari-version" : "",
"min-jdk" : "1.8",
"max-jdk" : "1.8"
},
{code}
# Generate the stack metainfo.xml as
{code}
1.8
1.8
true
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Resolution: Fixed Status: Resolved (was: Patch Available) > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, AMBARI-22479_2.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: AMBARI-22479_2.patch > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, AMBARI-22479_2.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22509) Fix DatabaseConsistencyCheckHelper in branch-feature-AMBARI-14714 branch
[
https://issues.apache.org/jira/browse/AMBARI-22509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22509.
-
Resolution: Fixed
> Fix DatabaseConsistencyCheckHelper in branch-feature-AMBARI-14714 branch
>
>
> Key: AMBARI-22509
> URL: https://issues.apache.org/jira/browse/AMBARI-22509
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
>
> {noformat:title=/var/log/ambari-server/ambari-server-check-database.log}
> 2017-11-06 22:00:54,125 INFO - Executing query 'GET_SERVICES_WITHOUT_CONFIGS'
> 2017-11-06 22:00:54,129 WARN - Exception occurred during complex service
> check procedure:
> org.postgresql.util.PSQLException: ERROR: column sc.service_name does not
> exist
> Position: 214
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:945)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.runAllDBChecks(DatabaseConsistencyCheckHelper.java:192)
> at
> org.apache.ambari.server.controller.AmbariServer.runDatabaseConsistencyCheck(AmbariServer.java:699)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:325)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1101)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22509) Fix DatabaseConsistencyCheckHelper in branch-feature-AMBARI-14714 branch
Dmytro Sen created AMBARI-22509:
---
Summary: Fix DatabaseConsistencyCheckHelper in
branch-feature-AMBARI-14714 branch
Key: AMBARI-22509
URL: https://issues.apache.org/jira/browse/AMBARI-22509
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
{noformat:title=/var/log/ambari-server/ambari-server-check-database.log}
2017-11-06 22:00:54,125 INFO - Executing query 'GET_SERVICES_WITHOUT_CONFIGS'
2017-11-06 22:00:54,129 WARN - Exception occurred during complex service check
procedure:
org.postgresql.util.PSQLException: ERROR: column sc.service_name does not exist
Position: 214
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283)
at
org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:945)
at
org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.runAllDBChecks(DatabaseConsistencyCheckHelper.java:192)
at
org.apache.ambari.server.controller.AmbariServer.runDatabaseConsistencyCheck(AmbariServer.java:699)
at
org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:325)
at
org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1101)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22471) "yum remove snappy" deletes ambari-metrics-collector
[ https://issues.apache.org/jira/browse/AMBARI-22471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259570#comment-16259570 ] Dmytro Sen commented on AMBARI-22471: - +1 > "yum remove snappy" deletes ambari-metrics-collector > > > Key: AMBARI-22471 > URL: https://issues.apache.org/jira/browse/AMBARI-22471 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Fix For: 2.6.1 > > Attachments: AMBARI-22471.patch > > > There appears to be an invalid dependency in the packaging of snappy. > Ambari-metrics-collector has snappy as a dependency. Yum remove snappy should > fail since it is a dependency but, instead, it removes > ambari-metrics-collector (but shouldn't). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259293#comment-16259293 ] Dmytro Sen commented on AMBARI-22479: - failure is not related to the patch > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: (was: screenshot-1.png) > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Status: Patch Available (was: In Progress) > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: AMBARI-22479.patch > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
[ https://issues.apache.org/jira/browse/AMBARI-22479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-22479: Attachment: screenshot-1.png > After removing force_delete_components option hosts are not deleted > --- > > Key: AMBARI-22479 > URL: https://issues.apache.org/jira/browse/AMBARI-22479 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 3.0.0 > > Attachments: AMBARI-22479.patch, screenshot-1.png > > > After removing force_delete_components from bulk host delete request BE > returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22479) After removing force_delete_components option hosts are not deleted
Dmytro Sen created AMBARI-22479: --- Summary: After removing force_delete_components option hosts are not deleted Key: AMBARI-22479 URL: https://issues.apache.org/jira/browse/AMBARI-22479 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Dmytro Sen Assignee: Dmytro Sen Priority: Blocker Fix For: 3.0.0 After removing force_delete_components from bulk host delete request BE returns "hosts not stopped error" even though the components have been stopped -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22428) Update db schema to use service_id instead of service_name (requests part)
Dmytro Sen created AMBARI-22428:
---
Summary: Update db schema to use service_id instead of
service_name (requests part)
Key: AMBARI-22428
URL: https://issues.apache.org/jira/browse/AMBARI-22428
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
updated tables to use the service_id as foreign key instead of service_name.
https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
For example:
{code}
CREATE TABLE servicecomponentdesiredstate (
id BIGINT NOT NULL,
component_name VARCHAR(255) NOT NULL,
cluster_id BIGINT NOT NULL,
service_group_id BIGINT NOT NULL,
service_id BIGINT NOT NULL,
desired_repo_version_id BIGINT NOT NULL,
desired_state VARCHAR(255) NOT NULL,
recovery_enabled SMALLINT NOT NULL DEFAULT 0,
repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
service_group_id, cluster_id),
CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
REFERENCES repo_version (repo_version_id),
CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
service_group_id, cluster_id) REFERENCES clusterservices (id, service_group_id,
cluster_id));
{code}
We need to update other DB tables to use service_id instead of service_name.
For example:
{code}
CREATE TABLE serviceconfig (
service_config_id BIGINT NOT NULL,
cluster_id BIGINT NOT NULL,
service_name VARCHAR(255) NOT NULL,
version BIGINT NOT NULL,
create_timestamp BIGINT NOT NULL,
stack_id BIGINT NOT NULL,
user_name VARCHAR(255) NOT NULL DEFAULT '_db',
group_id BIGINT,
note TEXT,
CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
stack(stack_id),
CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name, version));
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22363) Update db schema to use service_id instead of service_name (alerts part)
Dmytro Sen created AMBARI-22363:
---
Summary: Update db schema to use service_id instead of
service_name (alerts part)
Key: AMBARI-22363
URL: https://issues.apache.org/jira/browse/AMBARI-22363
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
updated tables to use the service_id as foreign key instead of service_name.
https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
For example:
{code}
CREATE TABLE servicecomponentdesiredstate (
id BIGINT NOT NULL,
component_name VARCHAR(255) NOT NULL,
cluster_id BIGINT NOT NULL,
service_group_id BIGINT NOT NULL,
service_id BIGINT NOT NULL,
desired_repo_version_id BIGINT NOT NULL,
desired_state VARCHAR(255) NOT NULL,
recovery_enabled SMALLINT NOT NULL DEFAULT 0,
repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
service_group_id, cluster_id),
CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
REFERENCES repo_version (repo_version_id),
CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
service_group_id, cluster_id) REFERENCES clusterservices (id, service_group_id,
cluster_id));
{code}
We need to update other DB tables to use service_id instead of service_name.
For example:
{code}
CREATE TABLE serviceconfig (
service_config_id BIGINT NOT NULL,
cluster_id BIGINT NOT NULL,
service_name VARCHAR(255) NOT NULL,
version BIGINT NOT NULL,
create_timestamp BIGINT NOT NULL,
stack_id BIGINT NOT NULL,
user_name VARCHAR(255) NOT NULL DEFAULT '_db',
group_id BIGINT,
note TEXT,
CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
stack(stack_id),
CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name, version));
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22309) Update db schema to use service_id instead of service_name (configs part)
[
https://issues.apache.org/jira/browse/AMBARI-22309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22309.
-
Resolution: Fixed
Committed into branch-feature-AMBARI-14714
> Update db schema to use service_id instead of service_name (configs part)
> -
>
> Key: AMBARI-22309
> URL: https://issues.apache.org/jira/browse/AMBARI-22309
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
>
> As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
> updated tables to use the service_id as foreign key instead of service_name.
> https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> For example:
> {code}
> CREATE TABLE servicecomponentdesiredstate (
> id BIGINT NOT NULL,
> component_name VARCHAR(255) NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_group_id BIGINT NOT NULL,
> service_id BIGINT NOT NULL,
> desired_repo_version_id BIGINT NOT NULL,
> desired_state VARCHAR(255) NOT NULL,
> recovery_enabled SMALLINT NOT NULL DEFAULT 0,
> repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
> CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
> CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
> service_group_id, cluster_id),
> CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
> REFERENCES repo_version (repo_version_id),
> CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
> service_group_id, cluster_id) REFERENCES clusterservices (id,
> service_group_id, cluster_id));
> {code}
> We need to update other DB tables to use service_id instead of service_name.
> For example:
> {code}
> CREATE TABLE serviceconfig (
> service_config_id BIGINT NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_name VARCHAR(255) NOT NULL,
> version BIGINT NOT NULL,
> create_timestamp BIGINT NOT NULL,
> stack_id BIGINT NOT NULL,
> user_name VARCHAR(255) NOT NULL DEFAULT '_db',
> group_id BIGINT,
> note TEXT,
> CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
> CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
> stack(stack_id),
> CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name,
> version));
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22309) Update db schema to use service_id instead of service_name (configs part)
[
https://issues.apache.org/jira/browse/AMBARI-22309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22309:
Summary: Update db schema to use service_id instead of service_name
(configs part) (was: Update db schema to use service_id instead of
service_name)
> Update db schema to use service_id instead of service_name (configs part)
> -
>
> Key: AMBARI-22309
> URL: https://issues.apache.org/jira/browse/AMBARI-22309
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
>
> As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
> updated tables to use the service_id as foreign key instead of service_name.
> https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> For example:
> {code}
> CREATE TABLE servicecomponentdesiredstate (
> id BIGINT NOT NULL,
> component_name VARCHAR(255) NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_group_id BIGINT NOT NULL,
> service_id BIGINT NOT NULL,
> desired_repo_version_id BIGINT NOT NULL,
> desired_state VARCHAR(255) NOT NULL,
> recovery_enabled SMALLINT NOT NULL DEFAULT 0,
> repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
> CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
> CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
> service_group_id, cluster_id),
> CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
> REFERENCES repo_version (repo_version_id),
> CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
> service_group_id, cluster_id) REFERENCES clusterservices (id,
> service_group_id, cluster_id));
> {code}
> We need to update other DB tables to use service_id instead of service_name.
> For example:
> {code}
> CREATE TABLE serviceconfig (
> service_config_id BIGINT NOT NULL,
> cluster_id BIGINT NOT NULL,
> service_name VARCHAR(255) NOT NULL,
> version BIGINT NOT NULL,
> create_timestamp BIGINT NOT NULL,
> stack_id BIGINT NOT NULL,
> user_name VARCHAR(255) NOT NULL DEFAULT '_db',
> group_id BIGINT,
> note TEXT,
> CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
> CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
> stack(stack_id),
> CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name,
> version));
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22309) Update db schema to use service_id instead of service_name
Dmytro Sen created AMBARI-22309:
---
Summary: Update db schema to use service_id instead of service_name
Key: AMBARI-22309
URL: https://issues.apache.org/jira/browse/AMBARI-22309
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
As part of AMBARI-21824, we added {{id}} to {{clusterservices}} table. We
updated tables to use the service_id as foreign key instead of service_name.
https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
For example:
{code}
CREATE TABLE servicecomponentdesiredstate (
id BIGINT NOT NULL,
component_name VARCHAR(255) NOT NULL,
cluster_id BIGINT NOT NULL,
service_group_id BIGINT NOT NULL,
service_id BIGINT NOT NULL,
desired_repo_version_id BIGINT NOT NULL,
desired_state VARCHAR(255) NOT NULL,
recovery_enabled SMALLINT NOT NULL DEFAULT 0,
repo_state VARCHAR(255) NOT NULL DEFAULT 'NOT_REQUIRED',
CONSTRAINT pk_sc_desiredstate PRIMARY KEY (id),
CONSTRAINT UQ_scdesiredstate_name UNIQUE(component_name, service_id,
service_group_id, cluster_id),
CONSTRAINT FK_scds_desired_repo_id FOREIGN KEY (desired_repo_version_id)
REFERENCES repo_version (repo_version_id),
CONSTRAINT srvccmponentdesiredstatesrvcnm FOREIGN KEY (service_id,
service_group_id, cluster_id) REFERENCES clusterservices (id, service_group_id,
cluster_id));
{code}
We need to update other DB tables to use service_id instead of service_name.
For example:
{code}
CREATE TABLE serviceconfig (
service_config_id BIGINT NOT NULL,
cluster_id BIGINT NOT NULL,
service_name VARCHAR(255) NOT NULL,
version BIGINT NOT NULL,
create_timestamp BIGINT NOT NULL,
stack_id BIGINT NOT NULL,
user_name VARCHAR(255) NOT NULL DEFAULT '_db',
group_id BIGINT,
note TEXT,
CONSTRAINT PK_serviceconfig PRIMARY KEY (service_config_id),
CONSTRAINT FK_serviceconfig_stack_id FOREIGN KEY (stack_id) REFERENCES
stack(stack_id),
CONSTRAINT UQ_scv_service_version UNIQUE (cluster_id, service_name, version));
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22276) Ambari trunk builds failing in TestAmbariServer
[
https://issues.apache.org/jira/browse/AMBARI-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22276:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari trunk builds failing in TestAmbariServer
> ---
>
> Key: AMBARI-22276
> URL: https://issues.apache.org/jira/browse/AMBARI-22276
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22276.patch
>
>
> Ambari trunk build jobs on worker node H1 are consistently failing due to the
> following 2 errors. Builds on other nodes are either successful or have
> other issues, but not these two.
> {noformat}
> FAILED (errors=2)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 8005, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> ERROR: test_main_with_preset_dbms (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 486, in test_main_with_preset_dbms
> _ambari_server_.mainBody()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 984, in mainBody
> main(options, args, parser)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 950, in main
> sys.exit(e.code)
> SystemExit: 1
> --
> Total run:1204
> Total errors:2
> Total failures:0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22276) Ambari trunk builds failing in TestAmbariServer
[
https://issues.apache.org/jira/browse/AMBARI-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22276:
Attachment: AMBARI-22276.patch
> Ambari trunk builds failing in TestAmbariServer
> ---
>
> Key: AMBARI-22276
> URL: https://issues.apache.org/jira/browse/AMBARI-22276
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22276.patch
>
>
> Ambari trunk build jobs on worker node H1 are consistently failing due to the
> following 2 errors. Builds on other nodes are either successful or have
> other issues, but not these two.
> {noformat}
> FAILED (errors=2)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 8005, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> ERROR: test_main_with_preset_dbms (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 486, in test_main_with_preset_dbms
> _ambari_server_.mainBody()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 984, in mainBody
> main(options, args, parser)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 950, in main
> sys.exit(e.code)
> SystemExit: 1
> --
> Total run:1204
> Total errors:2
> Total failures:0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22276) Ambari trunk builds failing in TestAmbariServer
[
https://issues.apache.org/jira/browse/AMBARI-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen updated AMBARI-22276:
Status: Patch Available (was: In Progress)
> Ambari trunk builds failing in TestAmbariServer
> ---
>
> Key: AMBARI-22276
> URL: https://issues.apache.org/jira/browse/AMBARI-22276
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22276.patch
>
>
> Ambari trunk build jobs on worker node H1 are consistently failing due to the
> following 2 errors. Builds on other nodes are either successful or have
> other issues, but not these two.
> {noformat}
> FAILED (errors=2)
> --
> Failed tests:
> ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 8005, in test_check_database_name_property
> args = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
> self.error(str(err))
> File "/usr/lib/python2.7/optparse.py", line 1584, in error
> self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
> File "/usr/lib/python2.7/optparse.py", line 1574, in exit
> sys.exit(status)
> SystemExit: 2
> ERROR: test_main_with_preset_dbms (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 486, in test_main_with_preset_dbms
> _ambari_server_.mainBody()
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 984, in mainBody
> main(options, args, parser)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
> line 950, in main
> sys.exit(e.code)
> SystemExit: 1
> --
> Total run:1204
> Total errors:2
> Total failures:0
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-22276) Ambari trunk builds failing in TestAmbariServer
Dmytro Sen created AMBARI-22276:
---
Summary: Ambari trunk builds failing in TestAmbariServer
Key: AMBARI-22276
URL: https://issues.apache.org/jira/browse/AMBARI-22276
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
Fix For: 3.0.0
Ambari trunk build jobs on worker node H1 are consistently failing due to the
following 2 errors. Builds on other nodes are either successful or have other
issues, but not these two.
{noformat}
FAILED (errors=2)
--
Failed tests:
ERROR: test_check_database_name_property (TestAmbariServer.TestAmbariServer)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
line 8005, in test_check_database_name_property
args = parser.parse_args()
File "/usr/lib/python2.7/optparse.py", line 1402, in parse_args
self.error(str(err))
File "/usr/lib/python2.7/optparse.py", line 1584, in error
self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
File "/usr/lib/python2.7/optparse.py", line 1574, in exit
sys.exit(status)
SystemExit: 2
ERROR: test_main_with_preset_dbms (TestAmbariServer.TestAmbariServer)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
line 486, in test_main_with_preset_dbms
_ambari_server_.mainBody()
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
line 984, in mainBody
main(options, args, parser)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari-server.py",
line 950, in main
sys.exit(e.code)
SystemExit: 1
--
Total run:1204
Total errors:2
Total failures:0
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
