[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sindhu Subhas updated AMBARI-23179:
---
Attachment: Screen Shot 2018-02-28 at 1.02.44 AM.png
Screen Shot 2018-02-28 at 5.05.55 PM.png
Screen Shot 2018-02-28 at 5.06.47 PM.png
Screen Shot 2018-02-28 at 5.07.30 PM.png
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Priority: Major
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
> AD
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
>
[jira] [Updated] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
[
https://issues.apache.org/jira/browse/AMBARI-23179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sindhu Subhas updated AMBARI-23179:
---
Attachment: datatab.tsv
> Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload
> Table'
> ---
>
> Key: AMBARI-23179
> URL: https://issues.apache.org/jira/browse/AMBARI-23179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.6.0
> Environment: HDP 2.6.3
> Ambari 2.6.0
>Reporter: Sindhu Subhas
>Priority: Major
> Attachments: Screen Shot 2018-02-28 at 1.02.44 AM.png, Screen Shot
> 2018-02-28 at 5.05.55 PM.png, Screen Shot 2018-02-28 at 5.06.47 PM.png,
> Screen Shot 2018-02-28 at 5.07.30 PM.png, datatab.tsv
>
>
> Problem:
> When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
> data is not parsed as expected.
> Same feature works as expected in Hive view 1.5.0.
> Attached output from Hive view 2.0 and output from Hive view 1.5.0.
> From the code, we do see difference in the code for
> src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
> Debug from Hive view 2.0:
> {code:java}
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
> 27 Feb 2018 20:27:28,169 DEBUG
> [HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
> 927343c0-5ed6-435c-be60-37448ac1a8b0
> 27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
> inputFileType : CSV
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
> HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp
> string column1 column2 column3
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
> 27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
> AUTO_HIVE20_INSTANCE] Parser:159 - return headers :
> [ColumnInfo{name='column1', type='STRING', precision=null, scale=null,
> comment='null'}]
> {code}
> Debug from Hive view 1.5.0:
> {code:java}
> 27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true,
> inputFileType : CSV
> 27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
> 27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
> 27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
> ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
> HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
> 27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied
> null
> 27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
> AD
> java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
> hh:mm:ss[.f]
> at java.sql.Timestamp.valueOf(Timestamp.java:204)
> .
> 27 Feb 2018 20:13:15,961 INFO [ambari-client-thread-38] [HIVE 1.5.0
> AUTO_HIVE_INSTANCE] Parser:149 - datatype detected for
[jira] [Created] (AMBARI-23179) Hive view 2.0 does not parse the TAB delimited CSV files while using 'Upload Table'
Sindhu Subhas created AMBARI-23179:
--
Summary: Hive view 2.0 does not parse the TAB delimited CSV files
while using 'Upload Table'
Key: AMBARI-23179
URL: https://issues.apache.org/jira/browse/AMBARI-23179
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.6.0
Environment: HDP 2.6.3
Ambari 2.6.0
Reporter: Sindhu Subhas
Problem:
When trying to Upload table from Hive view 2.0 from a TAB delimited file, the
data is not parsed as expected.
Same feature works as expected in Hive view 1.5.0.
Attached output from Hive view 2.0 and output from Hive view 1.5.0.
>From the code, we do see difference in the code for
>src/main/java/org/apache/ambari/view/hive20/resources/uploads/UploadService.java.
Debug from Hive view 2.0:
{code:java}
27 Feb 2018 20:27:28,169 DEBUG
[HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] OperationController:53 - } java.util.HashMap
27 Feb 2018 20:27:28,169 DEBUG
[HiveViewActorSystem-akka.actor.default-dispatcher-4] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] HiveActor:41 - Message submitted:
927343c0-5ed6-435c-be60-37448ac1a8b0
27 Feb 2018 20:27:30,925 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] UploadService:484 - isFirstRowHeader : false,
inputFileType : CSV
27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] OpenCSVParser:50 - setting delimiter as T
27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] OpenCSVParser:56 - setting Quote char : "
27 Feb 2018 20:27:30,934 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
27 Feb 2018 20:27:30,939 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] Parser:75 - generating preview for :
ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER=T,
HEADER=NONE, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
27 Feb 2018 20:27:30,939 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] Parser:83 - Illegal number of preview columns supplied
null
27 Feb 2018 20:27:30,943 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] ParseUtils:152 - error while parsing as timestamp string
column1 column2 column3
java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
hh:mm:ss[.f]
at java.sql.Timestamp.valueOf(Timestamp.java:204)
.
27 Feb 2018 20:27:30,948 INFO [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] Parser:149 - datatype detected for column 0 : STRING
27 Feb 2018 20:27:30,949 DEBUG [ambari-client-thread-38] [HIVE 2.0.0
AUTO_HIVE20_INSTANCE] Parser:159 - return headers : [ColumnInfo{name='column1',
type='STRING', precision=null, scale=null, comment='null'}]
{code}
Debug from Hive view 1.5.0:
{code:java}
27 Feb 2018 20:13:15,881 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] UploadService:499 - isFirstRowHeader : true, inputFileType
: CSV
27 Feb 2018 20:13:15,918 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] OpenCSVParser:50 - setting delimiter as
27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] OpenCSVParser:56 - setting Quote char : "
27 Feb 2018 20:13:15,919 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] OpenCSVParser:62 - setting escapeChar : \
27 Feb 2018 20:13:15,928 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] Parser:75 - generating preview for :
ParseOptions{options={OPTIONS_CSV_QUOTE=", OPTIONS_CSV_DELIMITER= ,
HEADER=FIRST_RECORD, FILE_TYPE=CSV, OPTIONS_CSV_ESCAPE_CHAR=\}}
27 Feb 2018 20:13:15,929 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] Parser:83 - Illegal number of preview columns supplied null
27 Feb 2018 20:13:15,936 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] ParseUtils:152 - error while parsing as timestamp string AD
java.lang.IllegalArgumentException: Timestamp format must be -mm-dd
hh:mm:ss[.f]
at java.sql.Timestamp.valueOf(Timestamp.java:204)
.
27 Feb 2018 20:13:15,961 INFO [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] Parser:149 - datatype detected for column 2 : STRING
27 Feb 2018 20:13:15,962 DEBUG [ambari-client-thread-38] [HIVE 1.5.0
AUTO_HIVE_INSTANCE] Parser:159 - return headers : [ColumnDescriptionImpl[name :
column1, type : STRING, position : 0, precision : null, scale : null],
ColumnDescriptionImpl[name : column2, type : STRING, position : 1, precision :
null, scale : null], ColumnDescriptionImpl[name : column3, type : STRING,
position : 2, precision : null, scale : null]]
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23103) Adding Stack feature constant for Ranger and Ranger KMS services
[
https://issues.apache.org/jira/browse/AMBARI-23103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mugdha Varadkar updated AMBARI-23103:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Adding Stack feature constant for Ranger and Ranger KMS services
>
>
> Key: AMBARI-23103
> URL: https://issues.apache.org/jira/browse/AMBARI-23103
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Attachments: AMBARI-23103.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Need to add a constant in Stack feature for {{RANGER}} and {{RANGER_KMS}}
> services. This constant will be used during upgrade of stack 2.6 to 3.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
[ https://issues.apache.org/jira/browse/AMBARI-23174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390773#comment-16390773 ] Hudson commented on AMBARI-23174: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #648 (See [https://builds.apache.org/job/Ambari-branch-2.6/648/]) AMBARI-23174 : Add storm topology metric expressions for custom (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b55567c4411bf4257f3610e00ba92d20c7d4c039]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml > Add storm topology metric expressions for custom downsampling config. > - > > Key: AMBARI-23174 > URL: https://issues.apache.org/jira/browse/AMBARI-23174 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 40m > Remaining Estimate: 0h > > This is a minor config change that needs to be made for the work done in > AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
[ https://issues.apache.org/jira/browse/AMBARI-23174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-23174. Resolution: Fixed Pushed to branch-2.6. > Add storm topology metric expressions for custom downsampling config. > - > > Key: AMBARI-23174 > URL: https://issues.apache.org/jira/browse/AMBARI-23174 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 40m > Remaining Estimate: 0h > > This is a minor config change that needs to be made for the work done in > AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23178) AMS restart failed in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-23178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-23178: - Attachment: AMBARI-23178.patch > AMS restart failed in embedded mode > --- > > Key: AMBARI-23178 > URL: https://issues.apache.org/jira/browse/AMBARI-23178 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: wangjianfei >Assignee: wangjianfei >Priority: Major > Fix For: trunk > > Attachments: AMBARI-23178.patch, ams-embedded-error.png > > > While ams use embedded mode,you can start it for the first time.But,when you > restart it,it starts failed.The log of hbase master is shown above.The reason > is due to the existed hbase.zookeeper.property.dataDir before.So,we must > delete it everytime before you want to restart ams in embedded mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23178) AMS restart failed in embedded mode
[ https://issues.apache.org/jira/browse/AMBARI-23178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangjianfei updated AMBARI-23178: - Attachment: ams-embedded-error.png > AMS restart failed in embedded mode > --- > > Key: AMBARI-23178 > URL: https://issues.apache.org/jira/browse/AMBARI-23178 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: wangjianfei >Assignee: wangjianfei >Priority: Major > Fix For: trunk > > Attachments: ams-embedded-error.png > > > While ams use embedded mode,you can start it for the first time.But,when you > restart it,it starts failed.The log of hbase master is shown above.The reason > is due to the existed hbase.zookeeper.property.dataDir before.So,we must > delete it everytime before you want to restart ams in embedded mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23178) AMS restart failed in embedded mode
wangjianfei created AMBARI-23178: Summary: AMS restart failed in embedded mode Key: AMBARI-23178 URL: https://issues.apache.org/jira/browse/AMBARI-23178 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: wangjianfei Assignee: wangjianfei Fix For: trunk Attachments: ams-embedded-error.png While ams use embedded mode,you can start it for the first time.But,when you restart it,it starts failed.The log of hbase master is shown above.The reason is due to the existed hbase.zookeeper.property.dataDir before.So,we must delete it everytime before you want to restart ams in embedded mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package
[ https://issues.apache.org/jira/browse/AMBARI-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14160: Description: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. was: I was validating some fix for Slider hbase with Gour. A new Slider hbase app package was built and moved to under: /var/lib/ambari-server/resources/apps We tried naming the new app package ending with -ted.zip -999.zip After 'ambari-server restart', the new app package was not picked up by Ambari. Ambari Slider View should be able to accommodate more than one version of app package. > Ambari Slider View should pick up multiple versions of the same app package > --- > > Key: AMBARI-14160 > URL: https://issues.apache.org/jira/browse/AMBARI-14160 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > I was validating some fix for Slider hbase with Gour. > A new Slider hbase app package was built and moved to under: > /var/lib/ambari-server/resources/apps > We tried naming the new app package ending with -ted.zip -999.zip > After 'ambari-server restart', the new app package was not picked up by > Ambari. > Ambari Slider View should be able to accommodate more than one version of app > package. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21822) Implement CodeCache related configuration change for HBase master
[ https://issues.apache.org/jira/browse/AMBARI-21822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-21822: Description: AMBARI-21326 applied the code cache directive to region server daemons. This issue is to apply the same fix to hbase master process. was: AMBARI-21326 applied the code cache directive to region server daemons. This issue is to apply the same fix to hbase master process. > Implement CodeCache related configuration change for HBase master > - > > Key: AMBARI-21822 > URL: https://issues.apache.org/jira/browse/AMBARI-21822 > Project: Ambari > Issue Type: Task >Reporter: Ted Yu >Priority: Major > Labels: hbase > > AMBARI-21326 applied the code cache directive to region server daemons. > This issue is to apply the same fix to hbase master process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23176) Some Minor Fixes For Failing Tests Due to Repo Version Refactor
[ https://issues.apache.org/jira/browse/AMBARI-23176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-23176. -- Resolution: Fixed > Some Minor Fixes For Failing Tests Due to Repo Version Refactor > --- > > Key: AMBARI-23176 > URL: https://issues.apache.org/jira/browse/AMBARI-23176 > Project: Ambari > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The ongoing work for AMBARI-14714 has left the feature branch tests in a > wreck. This is a commit which fixes a bunch of tests temporarily to help us > prepare for a merge with trunk in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23177) Remove hardcoded values of yarn and mapreduce in UI code
[ https://issues.apache.org/jira/browse/AMBARI-23177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23177: Labels: pull-request-available (was: ) > Remove hardcoded values of yarn and mapreduce in UI code > > > Key: AMBARI-23177 > URL: https://issues.apache.org/jira/browse/AMBARI-23177 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23177) Remove hardcoded values of yarn and mapreduce in UI code
Madhuvanthi Radhakrishnan created AMBARI-23177: -- Summary: Remove hardcoded values of yarn and mapreduce in UI code Key: AMBARI-23177 URL: https://issues.apache.org/jira/browse/AMBARI-23177 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23176) Some Minor Fixes For Failing Tests Due to Repo Version Refactor
[ https://issues.apache.org/jira/browse/AMBARI-23176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23176: Labels: pull-request-available (was: ) > Some Minor Fixes For Failing Tests Due to Repo Version Refactor > --- > > Key: AMBARI-23176 > URL: https://issues.apache.org/jira/browse/AMBARI-23176 > Project: Ambari > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > The ongoing work for AMBARI-14714 has left the feature branch tests in a > wreck. This is a commit which fixes a bunch of tests temporarily to help us > prepare for a merge with trunk in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23176) Some Minor Fixes For Failing Tests Due to Repo Version Refactor
Jonathan Hurley created AMBARI-23176: Summary: Some Minor Fixes For Failing Tests Due to Repo Version Refactor Key: AMBARI-23176 URL: https://issues.apache.org/jira/browse/AMBARI-23176 Project: Ambari Issue Type: Task Affects Versions: 3.0.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Fix For: 3.0.0 The ongoing work for AMBARI-14714 has left the feature branch tests in a wreck. This is a commit which fixes a bunch of tests temporarily to help us prepare for a merge with trunk in the future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23175) Fix for PUT Host Component API failing because validation check fails.
[ https://issues.apache.org/jira/browse/AMBARI-23175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-23175. -- Resolution: Fixed > Fix for PUT Host Component API failing because validation check fails. > -- > > Key: AMBARI-23175 > URL: https://issues.apache.org/jira/browse/AMBARI-23175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > - Validation check for HOST COMPONENT PUT API looks for having cluster_name, > component_name, component_type, service_name, service_group_name, and > host_name. > - But, as of now, *service_name*, *service_group* names are not fetched/set > during find operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23175) Fix for PUT Host Component API failing because validation check fails.
[ https://issues.apache.org/jira/browse/AMBARI-23175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23175: Labels: pull-request-available (was: ) > Fix for PUT Host Component API failing because validation check fails. > -- > > Key: AMBARI-23175 > URL: https://issues.apache.org/jira/browse/AMBARI-23175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > - Validation check for HOST COMPONENT PUT API looks for having cluster_name, > component_name, component_type, service_name, service_group_name, and > host_name. > - But, as of now, *service_name*, *service_group* names are not fetched/set > during find operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23175) Fix for PUT Host Component API failing because validation check fails.
[ https://issues.apache.org/jira/browse/AMBARI-23175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23175: - Description: - Validation check for HOST COMPONENT PUT API looks for having cluster_name, component_name, component_type, service_name, service_group_name, and host_name. - But, as of now, *service_name*, *service_group* names are not fetched/set during find operation. > Fix for PUT Host Component API failing because validation check fails. > -- > > Key: AMBARI-23175 > URL: https://issues.apache.org/jira/browse/AMBARI-23175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 3.0.0 > > > - Validation check for HOST COMPONENT PUT API looks for having cluster_name, > component_name, component_type, service_name, service_group_name, and > host_name. > - But, as of now, *service_name*, *service_group* names are not fetched/set > during find operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23175) Fix for PUT Host Component API failing because validation check fails.
[ https://issues.apache.org/jira/browse/AMBARI-23175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23175: - Summary: Fix for PUT Host Component API failing because validation check fails. (was: Fix for PUT Host Component API failing because service_name, service_group names are not fetched during find operation. ) > Fix for PUT Host Component API failing because validation check fails. > -- > > Key: AMBARI-23175 > URL: https://issues.apache.org/jira/browse/AMBARI-23175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23175) Fix for PUT Host Component API failing because service_name, service_group names are not fetched during find operation.
[ https://issues.apache.org/jira/browse/AMBARI-23175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23175: - Summary: Fix for PUT Host Component API failing because service_name, service_group names are not fetched during find operation.(was: Fix for PUT Host Component API failing because service_name, service_group names are not fetched. ) > Fix for PUT Host Component API failing because service_name, service_group > names are not fetched during find operation. > - > > Key: AMBARI-23175 > URL: https://issues.apache.org/jira/browse/AMBARI-23175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Critical > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23175) Fix for PUT Host Component API failing because service_name, service_group names are not fetched.
Swapan Shridhar created AMBARI-23175: Summary: Fix for PUT Host Component API failing because service_name, service_group names are not fetched. Key: AMBARI-23175 URL: https://issues.apache.org/jira/browse/AMBARI-23175 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
[ https://issues.apache.org/jira/browse/AMBARI-23174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23174: Labels: pull-request-available (was: ) > Add storm topology metric expressions for custom downsampling config. > - > > Key: AMBARI-23174 > URL: https://issues.apache.org/jira/browse/AMBARI-23174 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > > This is a minor config change that needs to be made for the work done in > AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
[ https://issues.apache.org/jira/browse/AMBARI-23174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-23174: -- Assignee: Aravindan Vijayan > Add storm topology metric expressions for custom downsampling config. > - > > Key: AMBARI-23174 > URL: https://issues.apache.org/jira/browse/AMBARI-23174 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.6.2 > > > This is a minor config change that needs to be made for the work done in > AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
Aravindan Vijayan created AMBARI-23174: -- Summary: Add storm topology metric expressions for custom downsampling config. Key: AMBARI-23174 URL: https://issues.apache.org/jira/browse/AMBARI-23174 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.6.2 Reporter: Aravindan Vijayan This is a minor config change that needs to be made for the work done in AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23174) Add storm topology metric expressions for custom downsampling config.
[ https://issues.apache.org/jira/browse/AMBARI-23174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-23174: --- Fix Version/s: 2.6.2 > Add storm topology metric expressions for custom downsampling config. > - > > Key: AMBARI-23174 > URL: https://issues.apache.org/jira/browse/AMBARI-23174 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.6.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Fix For: 2.6.2 > > > This is a minor config change that needs to be made for the work done in > AMBARI-23008 to have storm metrics aggregated differently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23172) Build fails for Debian (jdeb plugin not found)
[
https://issues.apache.org/jira/browse/AMBARI-23172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390276#comment-16390276
]
Hudson commented on AMBARI-23172:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8824 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8824/])
AMBARI-23172. Build fails for Debian (jdeb plugin not found). (swagle) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e5e10cd81fcf48cbcee82456769145ad8c954e1e])
* (edit) ambari-serviceadvisor/pom.xml
> Build fails for Debian (jdeb plugin not found)
> --
>
> Key: AMBARI-23172
> URL: https://issues.apache.org/jira/browse/AMBARI-23172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] No plugin found for prefix 'jdeb'
> in the current project and in the plugin groups [org.sonatype.plugins,
> org.apache.maven.plugins, org.codehaus.mojo] available from the repositories
> [local (/grid/0/jenkins/.m2/repository), public
> (http://nexus-private.hortonworks.com/nexus/content/groups/public)] -> [Help
> 1]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] To see the full stack trace of
> the errors, re-run Maven with the -e switch.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] Re-run Maven using the -X switch
> to enable full debug logging.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] For more information about the
> errors and possible solutions, please read the following articles:
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23173) Assign Client/Slaves page pagination control static
[ https://issues.apache.org/jira/browse/AMBARI-23173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23173: Labels: pull-request-available (was: ) > Assign Client/Slaves page pagination control static > --- > > Key: AMBARI-23173 > URL: https://issues.apache.org/jira/browse/AMBARI-23173 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > pagination controls should not be hidden behind the horizontal scroll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23173) Assign Client/Slaves page pagination control static
[ https://issues.apache.org/jira/browse/AMBARI-23173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23173: - Summary: Assign Client/Slaves page pagination control static (was: Assign Client/Slaves page pagination freeze) > Assign Client/Slaves page pagination control static > --- > > Key: AMBARI-23173 > URL: https://issues.apache.org/jira/browse/AMBARI-23173 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Fix For: trunk > > > pagination controls should not be hidden behind the horizontal scroll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23173) Assign Client/Slaves page pagination freeze
Ishan Bhatt created AMBARI-23173: Summary: Assign Client/Slaves page pagination freeze Key: AMBARI-23173 URL: https://issues.apache.org/jira/browse/AMBARI-23173 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk pagination controls should not be hidden behind the horizontal scroll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23172) Build fails for Debian (jdeb plugin not found)
[
https://issues.apache.org/jira/browse/AMBARI-23172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23172:
Labels: pull-request-available (was: )
> Build fails for Debian (jdeb plugin not found)
> --
>
> Key: AMBARI-23172
> URL: https://issues.apache.org/jira/browse/AMBARI-23172
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Siddharth Wagle
>Assignee: Siddharth Wagle
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> {code:java}
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] No plugin found for prefix 'jdeb'
> in the current project and in the plugin groups [org.sonatype.plugins,
> org.apache.maven.plugins, org.codehaus.mojo] available from the repositories
> [local (/grid/0/jenkins/.m2/repository), public
> (http://nexus-private.hortonworks.com/nexus/content/groups/public)] -> [Help
> 1]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] To see the full stack trace of
> the errors, re-run Maven with the -e switch.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] Re-run Maven using the -X switch
> to enable full debug logging.
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] For more information about the
> errors and possible solutions, please read the following articles:
> 22:08:15 2018/03/07 06:08:14 INFO : [ERROR] [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23172) Build fails for Debian (jdeb plugin not found)
Siddharth Wagle created AMBARI-23172:
Summary: Build fails for Debian (jdeb plugin not found)
Key: AMBARI-23172
URL: https://issues.apache.org/jira/browse/AMBARI-23172
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Siddharth Wagle
Assignee: Siddharth Wagle
Fix For: 2.7.0
{code:java}
22:08:15 2018/03/07 06:08:14 INFO : [ERROR] No plugin found for prefix 'jdeb'
in the current project and in the plugin groups [org.sonatype.plugins,
org.apache.maven.plugins, org.codehaus.mojo] available from the repositories
[local (/grid/0/jenkins/.m2/repository), public
(http://nexus-private.hortonworks.com/nexus/content/groups/public)] -> [Help 1]
22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
22:08:15 2018/03/07 06:08:14 INFO : [ERROR] To see the full stack trace of the
errors, re-run Maven with the -e switch.
22:08:15 2018/03/07 06:08:14 INFO : [ERROR] Re-run Maven using the -X switch to
enable full debug logging.
22:08:15 2018/03/07 06:08:14 INFO : [ERROR]
22:08:15 2018/03/07 06:08:14 INFO : [ERROR] For more information about the
errors and possible solutions, please read the following articles:
22:08:15 2018/03/07 06:08:14 INFO : [ERROR] [Help 1]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization
[
https://issues.apache.org/jira/browse/AMBARI-22803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-22803:
---
Status: Patch Available (was: In Progress)
> Update Hadoop RPC Encryption Properties During Kerberization
>
>
> Key: AMBARI-22803
> URL: https://issues.apache.org/jira/browse/AMBARI-22803
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Sandor Molnar
>Priority: Critical
> Fix For: 2.7.0
>
> Attachments: AMBARI-22803.patch
>
>
> When *HDP 3.0.0* is installed, clients should have the ability to choose
> encrypted communication over RPC when talking to core hadoop components.
> Today, the properties that control this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization, the above two properties should be automatically
> reconfigured.
> - During a stack upgrade to any version of *HDP 3.0.0* is covered by
> AMBARI-22981
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23171) Ambari logo is missing.
Myroslav Papirkovskyi created AMBARI-23171: -- Summary: Ambari logo is missing. Key: AMBARI-23171 URL: https://issues.apache.org/jira/browse/AMBARI-23171 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.0 Attachments: Screen Shot.png See the screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23169) Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390125#comment-16390125 ] Hudson commented on AMBARI-23169: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8823 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8823/]) AMBARI-23169: Remove upgrade packs from HDP-2.6 stack definition in (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a57d6ccef6b8d45ba51a322808d51e43dd966642]) * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-3.0.xml * (delete) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/host-upgrade-2.6.xml > Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari > --- > > Key: AMBARI-23169 > URL: https://issues.apache.org/jira/browse/AMBARI-23169 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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 ] ASF GitHub Bot updated AMBARI-23170: Labels: pull-request-available (was: ) > 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 > > -- 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-23169) Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-23169. Resolution: Fixed > Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari > --- > > Key: AMBARI-23169 > URL: https://issues.apache.org/jira/browse/AMBARI-23169 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23169) Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-23169: --- Issue Type: Task (was: Bug) > Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari > --- > > Key: AMBARI-23169 > URL: https://issues.apache.org/jira/browse/AMBARI-23169 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23169) Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23169: Labels: pull-request-available (was: ) > Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari > --- > > Key: AMBARI-23169 > URL: https://issues.apache.org/jira/browse/AMBARI-23169 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22755) Show OneFS JMX metrics on the UI
[
https://issues.apache.org/jira/browse/AMBARI-22755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-22755:
---
Summary: Show OneFS JMX metrics on the UI (was: Show JMX based metrics on
UI)
> Show OneFS JMX metrics on the UI
>
>
> Key: AMBARI-22755
> URL: https://issues.apache.org/jira/browse/AMBARI-22755
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Fix For: 3.0.0
>
>
> There are some metrics like a (NameNode uptime/StartTime and HDFS disk
> usage/Capacity*) which cannot be shown in a widget because widgets only
> support AMS based metrics.
> Normally these metrics are shown in a service specific dashboard which is
> hardcoded in the ui (summary.js/serviceCustomViewsMap).
> {code}
> serviceCustomViewsMap: function() {
> return {
> HBASE: App.MainDashboardServiceHbaseView,
> HDFS: App.MainDashboardServiceHdfsView,
> STORM: App.MainDashboardServiceStormView,
> YARN: App.MainDashboardServiceYARNView,
> RANGER: App.MainDashboardServiceRangerView,
> FLUME: App.MainDashboardServiceFlumeView,
> HIVE: App.MainDashboardServiceHiveView
> }
> }.property('serviceName'),
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23169) Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari
Jayush Luniya created AMBARI-23169: -- Summary: Remove upgrade packs from HDP-2.6 stack definition in Apache Ambari Key: AMBARI-23169 URL: https://issues.apache.org/jira/browse/AMBARI-23169 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23167) StackOverflowError thrown during cluster creation
[
https://issues.apache.org/jira/browse/AMBARI-23167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-23167.
--
Resolution: Fixed
> StackOverflowError thrown during cluster creation
> -
>
> Key: AMBARI-23167
> URL: https://issues.apache.org/jira/browse/AMBARI-23167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seeing a StackOverflowException when creating clusters from blueprints:
> {code}
> .springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:201)
> at
> org.apache.ambari.server.security.authentication.AmbariBasicAuthenticationFilter.doFilter(AmbariBasicAuthenticationFilter.java:116)
> at
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:121)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:73)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:53)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:130)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
> at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
> at
>
[jira] [Created] (AMBARI-23168) Kubernetes integration
Hari Sekhon created AMBARI-23168: Summary: Kubernetes integration Key: AMBARI-23168 URL: https://issues.apache.org/jira/browse/AMBARI-23168 Project: Ambari Issue Type: New Feature Components: ambari-agent, ambari-server, infra Affects Versions: 2.5.0 Reporter: Hari Sekhon Feature Request for Kubernetes integration to deploy all components via Kubernetes. Hadoop is targeting Docker integration in 3.1 and MapR is moving towards full Kubernetes deployment support. Also the market in general seems to be moving in the Kubernetes direction outside of the Hadoop ecosystem so they are going to converge eventually so may as well start working towards towards this convergence earlier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23167) StackOverflowError thrown during cluster creation
[
https://issues.apache.org/jira/browse/AMBARI-23167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23167:
Labels: pull-request-available (was: )
> StackOverflowError thrown during cluster creation
> -
>
> Key: AMBARI-23167
> URL: https://issues.apache.org/jira/browse/AMBARI-23167
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Seeing a StackOverflowException when creating clusters from blueprints:
> {code}
> .springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:201)
> at
> org.apache.ambari.server.security.authentication.AmbariBasicAuthenticationFilter.doFilter(AmbariBasicAuthenticationFilter.java:116)
> at
> org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:121)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
> at
> org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
> at
> org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
> at
> org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
> at
> org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:73)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:53)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:130)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
> at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
> at
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
> at
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
> at
>
[jira] [Created] (AMBARI-23167) StackOverflowError thrown during cluster creation
Jonathan Hurley created AMBARI-23167:
Summary: StackOverflowError thrown during cluster creation
Key: AMBARI-23167
URL: https://issues.apache.org/jira/browse/AMBARI-23167
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 3.0.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 3.0.0
Seeing a StackOverflowException when creating clusters from blueprints:
{code}
.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:201)
at
org.apache.ambari.server.security.authentication.AmbariBasicAuthenticationFilter.doFilter(AmbariBasicAuthenticationFilter.java:116)
at
org.apache.ambari.server.security.authentication.AmbariDelegatingAuthenticationFilter.doFilter(AmbariDelegatingAuthenticationFilter.java:121)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.apache.ambari.server.security.authorization.AmbariUserAuthorizationFilter.doFilter(AmbariUserAuthorizationFilter.java:95)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192)
at
org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160)
at
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237)
at
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
at
org.apache.ambari.server.api.MethodOverrideFilter.doFilter(MethodOverrideFilter.java:73)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
at
org.apache.ambari.server.api.AmbariPersistFilter.doFilter(AmbariPersistFilter.java:53)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
at
org.apache.ambari.server.security.AbstractSecurityHeaderFilter.doFilter(AbstractSecurityHeaderFilter.java:130)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
at
org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:82)
at org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:294)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1478)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:427)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.apache.ambari.server.controller.AmbariHandlerList.processHandlers(AmbariHandlerList.java:210)
at
[jira] [Updated] (AMBARI-23143) Failure while starting Spark2 service after performing ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23143:
Labels: pull-request-available (was: )
> Failure while starting Spark2 service after performing ambari upgrade
> -
>
> Key: AMBARI-23143
> URL: https://issues.apache.org/jira/browse/AMBARI-23143
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
> Environment: ambari-server --version 2.6.2.0-82
> HDP-2.6.1.0-129
>Reporter: Supreeth Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
>
> Test steps :
> 1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129
> 2) Upgrade ambari to 2.6.2.0-82
> 3) Now try to restart all the services. The operation is failing with below
> exception while trying to start Spark2
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 37, in
> AfterInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 375, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 31, in hook
> setup_stack_symlinks(self.stroutfile)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py",
> line 49, in setup_stack_symlinks
> stack_packages =
> stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py",
> line 235, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package livy2-client is not
> supported by this version of the stack-select tool.{code}
> livy2-client package was added in HDP 2.6.3 and was not present before that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23143) Failure while starting Spark2 service after performing ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-23143:
Description:
Test steps :
1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129
2) Upgrade ambari to 2.6.2.0-82
3) Now try to restart all the services. The operation is failing with below
exception while trying to start Spark2
{code:java}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
line 37, in
AfterInstallHook().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
line 31, in hook
setup_stack_symlinks(self.stroutfile)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py",
line 49, in setup_stack_symlinks
stack_packages =
stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py",
line 235, in get_packages
raise Fail("The package {0} is not supported by this version of the
stack-select tool.".format(package))
resource_management.core.exceptions.Fail: The package livy2-client is not
supported by this version of the stack-select tool.{code}
livy2-client package was added in HDP 2.6.3 and was not present before that.
was:
Test steps :
1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129
2) Upgrade ambari to 2.6.2.0-82
3) Now try to restart all the services. The operation is failing with below
exception while trying to start Spark2
{code:java}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
line 37, in
AfterInstallHook().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
line 31, in hook
setup_stack_symlinks(self.stroutfile)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py",
line 49, in setup_stack_symlinks
stack_packages =
stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py",
line 235, in get_packages
raise Fail("The package {0} is not supported by this version of the
stack-select tool.".format(package))
resource_management.core.exceptions.Fail: The package livy2-client is not
supported by this version of the stack-select tool.{code}
> Failure while starting Spark2 service after performing ambari upgrade
> -
>
> Key: AMBARI-23143
> URL: https://issues.apache.org/jira/browse/AMBARI-23143
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
> Environment: ambari-server --version 2.6.2.0-82
> HDP-2.6.1.0-129
>Reporter: Supreeth Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
>
> Test steps :
> 1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129
> 2) Upgrade ambari to 2.6.2.0-82
> 3) Now try to restart all the services. The operation is failing with below
> exception while trying to start Spark2
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 37, in
> AfterInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 375, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 31, in hook
> setup_stack_symlinks(self.stroutfile)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py",
> line 49, in setup_stack_symlinks
> stack_packages =
> stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py",
> line 235, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package livy2-client is not
> supported by this version of the stack-select tool.{code}
> livy2-client package was added in HDP 2.6.3 and was not present before that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-23143) Failure while starting Spark2 service after performing ambari upgrade
[
https://issues.apache.org/jira/browse/AMBARI-23143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko reassigned AMBARI-23143:
---
Assignee: Dmitry Lysnichenko
> Failure while starting Spark2 service after performing ambari upgrade
> -
>
> Key: AMBARI-23143
> URL: https://issues.apache.org/jira/browse/AMBARI-23143
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
> Environment: ambari-server --version 2.6.2.0-82
> HDP-2.6.1.0-129
>Reporter: Supreeth Sharma
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.6.2
>
>
> Test steps :
> 1) Deploy a cluster with ambari-2.5.1.0-159 + HDP-2.6.1.0-129
> 2) Upgrade ambari to 2.6.2.0-82
> 3) Now try to restart all the services. The operation is failing with below
> exception while trying to start Spark2
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 37, in
> AfterInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 375, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/hook.py",
> line 31, in hook
> setup_stack_symlinks(self.stroutfile)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/after-INSTALL/scripts/shared_initialization.py",
> line 49, in setup_stack_symlinks
> stack_packages =
> stack_select.get_packages(stack_select.PACKAGE_SCOPE_INSTALL)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/functions/stack_select.py",
> line 235, in get_packages
> raise Fail("The package {0} is not supported by this version of the
> stack-select tool.".format(package))
> resource_management.core.exceptions.Fail: The package livy2-client is not
> supported by this version of the stack-select tool.{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22981) Update Hadoop RPC Encryption Properties During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389802#comment-16389802
]
Hudson commented on AMBARI-22981:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8822 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8822/])
[AMBARI-22981] Updating Hadoop RPC Encryption Properties During Upgrade
(rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ce7237cc4a2f1dd78b929c83a6db5ef62018bd84])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-3.0.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit) ambari-web/app/data/configs/wizards/secure_mapping.js
> Update Hadoop RPC Encryption Properties During Upgrade
> --
>
> Key: AMBARI-22981
> URL: https://issues.apache.org/jira/browse/AMBARI-22981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When *HDP 3.0.0* is installed, clients should have the ability to choose
> encrypted communication over RPC when talking to core hadoop components.
> Today, the properties that control this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization (this case is covered by AMBARI-22803)
> - During a stack upgrade to any version of *HDP 3.0.0*, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23166) NN Federation Wizard: implement step4
[ https://issues.apache.org/jira/browse/AMBARI-23166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23166: Labels: pull-request-available (was: ) > NN Federation Wizard: implement step4 > - > > Key: AMBARI-23166 > URL: https://issues.apache.org/jira/browse/AMBARI-23166 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > Provide step4 with ability to see progress of operations performed to add new > namespace. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23166) NN Federation Wizard: implement step4
Aleksandr Kovalenko created AMBARI-23166: Summary: NN Federation Wizard: implement step4 Key: AMBARI-23166 URL: https://issues.apache.org/jira/browse/AMBARI-23166 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Provide step4 with ability to see progress of operations performed to add new namespace. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23165: Labels: pull-request-available (was: ) > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
Antonenko Alexander created AMBARI-23165: Summary: Install Wizard/Customise Services - Clear Filters is not working Key: AMBARI-23165 URL: https://issues.apache.org/jira/browse/AMBARI-23165 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23165) Install Wizard/Customise Services - Clear Filters is not working
[ https://issues.apache.org/jira/browse/AMBARI-23165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23165: Assignee: Antonenko Alexander > Install Wizard/Customise Services - Clear Filters is not working > > > Key: AMBARI-23165 > URL: https://issues.apache.org/jira/browse/AMBARI-23165 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
[
https://issues.apache.org/jira/browse/AMBARI-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389689#comment-16389689
]
Hudson commented on AMBARI-23163:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8821 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8821/])
AMBARI-23163 Unable to add a service in second go from Ambari-UI
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=cf3da47e07cd178fd4f606ee6d0c4522e21c142c])
* (edit)
ambari-web/app/views/common/modal_popups/config_validation/config_validation_popup.js
> Unable to add a service in second go from Ambari-UI
> ---
>
> Key: AMBARI-23163
> URL: https://issues.apache.org/jira/browse/AMBARI-23163
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: add-service-stuck.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
> Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
> Now trying to Add Knox / Ranger, after customizing the configurations and
> clicked on the {{Next}} button UI is stuck and unable to reach the deploy
> screen.
> Browser console shows error {{unable to load modification handler for
> RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23161) Invalid storage property value for zeppelin in stack HDP 2.6
[
https://issues.apache.org/jira/browse/AMBARI-23161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389672#comment-16389672
]
Hudson commented on AMBARI-23161:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #647 (See
[https://builds.apache.org/job/Ambari-branch-2.6/647/])
[AMBARI-23161] Invalid storage property value for zeppelin in stack H… (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=ef1aace01ed1181c5ede4950d7551cd3aead019c])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/stack_advisor.py
> Invalid storage property value for zeppelin in stack HDP 2.6
>
>
> Key: AMBARI-23161
> URL: https://issues.apache.org/jira/browse/AMBARI-23161
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> For stacks lower than HDP 2.6.3, property {{zeppelin.notebook.storage}}
> should have value {{org.apache.zeppelin.notebook.repo.VFSNotebookRepo}}. For
> stacks HDP 2.6.3 and higher this property should have value
> {{org.apache.zeppelin.notebook.repo.FileSystemNotebookRepo}}. As of now for
> all stacks HDP 2.6.x by default storage property will have value
> FileSystemNotebookRepo, it's not correct. So it should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23055) GPL repo is not hidden when default version is chosen in UI
[
https://issues.apache.org/jira/browse/AMBARI-23055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389643#comment-16389643
]
Hudson commented on AMBARI-23055:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8820 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8820/])
AMBARI-23055. GPL repo is not hidden when default version is chosen in
(mpapirkovskyy:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7d388adad9bc4736a711c5e7fefeca525f78dcff])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> GPL repo is not hidden when default version is chosen in UI
> ---
>
> Key: AMBARI-23055
> URL: https://issues.apache.org/jira/browse/AMBARI-23055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Ambari server has gpl license disabled i.e.
> {code}
> cat /etc/ambari-server/conf/ambari.properties | grep -i gpl
> gpl.license.accepted=false
> {code}
> - On register version page, upon choosing HDP-2.6.4.0 from the drop-down, the
> GPL repo field is not masked (see default-version.png)
> - However upon choosing to upload the version from VDF URL, the GPL field is
> correctly masked (see version-via-vdf.png)
> Looks like the problem is
> [showRepo()|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L50]
> function which calls
> [isGPLRepo|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L46]
> function where if we do not load version fromVDF URL the showRepo return true
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
[
https://issues.apache.org/jira/browse/AMBARI-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389642#comment-16389642
]
Andrii Tkach commented on AMBARI-23163:
---
committed to trunk
> Unable to add a service in second go from Ambari-UI
> ---
>
> Key: AMBARI-23163
> URL: https://issues.apache.org/jira/browse/AMBARI-23163
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: add-service-stuck.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
> Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
> Now trying to Add Knox / Ranger, after customizing the configurations and
> clicked on the {{Next}} button UI is stuck and unable to reach the deploy
> screen.
> Browser console shows error {{unable to load modification handler for
> RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
[
https://issues.apache.org/jira/browse/AMBARI-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach resolved AMBARI-23163.
---
Resolution: Fixed
> Unable to add a service in second go from Ambari-UI
> ---
>
> Key: AMBARI-23163
> URL: https://issues.apache.org/jira/browse/AMBARI-23163
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: add-service-stuck.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
> Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
> Now trying to Add Knox / Ranger, after customizing the configurations and
> clicked on the {{Next}} button UI is stuck and unable to reach the deploy
> screen.
> Browser console shows error {{unable to load modification handler for
> RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23055) GPL repo is not hidden when default version is chosen in UI
[
https://issues.apache.org/jira/browse/AMBARI-23055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389634#comment-16389634
]
Hudson commented on AMBARI-23055:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #646 (See
[https://builds.apache.org/job/Ambari-branch-2.6/646/])
AMBARI-23055. GPL repo is not hidden when default version is chosen in
(mpapirkovskyy:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1ec645afbda1a0d5fdb4507c62aa26eb46be98c7])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
> GPL repo is not hidden when default version is chosen in UI
> ---
>
> Key: AMBARI-23055
> URL: https://issues.apache.org/jira/browse/AMBARI-23055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Ambari server has gpl license disabled i.e.
> {code}
> cat /etc/ambari-server/conf/ambari.properties | grep -i gpl
> gpl.license.accepted=false
> {code}
> - On register version page, upon choosing HDP-2.6.4.0 from the drop-down, the
> GPL repo field is not masked (see default-version.png)
> - However upon choosing to upload the version from VDF URL, the GPL field is
> correctly masked (see version-via-vdf.png)
> Looks like the problem is
> [showRepo()|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L50]
> function which calls
> [isGPLRepo|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L46]
> function where if we do not load version fromVDF URL the showRepo return true
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23164) Config dependencies alert bar not displayed properly while scrolling down the page
[ https://issues.apache.org/jira/browse/AMBARI-23164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23164: Labels: pull-request-available (was: ) > Config dependencies alert bar not displayed properly while scrolling down the > page > -- > > Key: AMBARI-23164 > URL: https://issues.apache.org/jira/browse/AMBARI-23164 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-06 at 5.02.14 PM.png > > > Config dependencies alert bar not displayed properly while scrolling down the > page. > Attaching screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23055) GPL repo is not hidden when default version is chosen in UI
[
https://issues.apache.org/jira/browse/AMBARI-23055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi resolved AMBARI-23055.
Resolution: Fixed
Merged to trunk and branch-2.6
> GPL repo is not hidden when default version is chosen in UI
> ---
>
> Key: AMBARI-23055
> URL: https://issues.apache.org/jira/browse/AMBARI-23055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Labels: pull-request-available, system_test
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Ambari server has gpl license disabled i.e.
> {code}
> cat /etc/ambari-server/conf/ambari.properties | grep -i gpl
> gpl.license.accepted=false
> {code}
> - On register version page, upon choosing HDP-2.6.4.0 from the drop-down, the
> GPL repo field is not masked (see default-version.png)
> - However upon choosing to upload the version from VDF URL, the GPL field is
> correctly masked (see version-via-vdf.png)
> Looks like the problem is
> [showRepo()|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L50]
> function which calls
> [isGPLRepo|https://github.com/apache/ambari/blob/branch-2.6/ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js#L46]
> function where if we do not load version fromVDF URL the showRepo return true
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23164) Config dependencies alert bar not displayed properly while scrolling down the page
[ https://issues.apache.org/jira/browse/AMBARI-23164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23164: -- Description: Config dependencies alert bar not displayed properly while scrolling down the page. Attaching screenshot was: Config dependencies alert bar not displayed properly while scrolling down the page. Attaching screenshot !Screen Shot 2018-03-06 at 5.02.14 PM.png|thumbnail! > Config dependencies alert bar not displayed properly while scrolling down the > page > -- > > Key: AMBARI-23164 > URL: https://issues.apache.org/jira/browse/AMBARI-23164 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-06 at 5.02.14 PM.png > > > Config dependencies alert bar not displayed properly while scrolling down the > page. > Attaching screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23164) Config dependencies alert bar not displayed properly while scrolling down the page
[ https://issues.apache.org/jira/browse/AMBARI-23164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23164: -- Attachment: Screen Shot 2018-03-06 at 5.02.14 PM.png > Config dependencies alert bar not displayed properly while scrolling down the > page > -- > > Key: AMBARI-23164 > URL: https://issues.apache.org/jira/browse/AMBARI-23164 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-06 at 5.02.14 PM.png > > > Config dependencies alert bar not displayed properly while scrolling down the > page. > Attaching screenshot > !Screen Shot 2018-03-06 at 5.02.14 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23164) Config dependencies alert bar not displayed properly while scrolling down the page
Andrii Tkach created AMBARI-23164: - Summary: Config dependencies alert bar not displayed properly while scrolling down the page Key: AMBARI-23164 URL: https://issues.apache.org/jira/browse/AMBARI-23164 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Attachments: Screen Shot 2018-03-06 at 5.02.14 PM.png Config dependencies alert bar not displayed properly while scrolling down the page. Attaching screenshot !Screen Shot 2018-03-06 at 5.02.14 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23162) Pass full stack version in recommendation request
[ https://issues.apache.org/jira/browse/AMBARI-23162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389566#comment-16389566 ] Hudson commented on AMBARI-23162: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #645 (See [https://builds.apache.org/job/Ambari-branch-2.6/645/]) AMBARI-23162. Pass full stack version in recommendation request (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3f74eda882fdd324dbc0b08d848a29e4324cb259]) * (edit) ambari-web/app/config.js * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/app.js * (edit) ambari-web/app/controllers/installer.js * (edit) ambari-web/app/models/repository.js > Pass full stack version in recommendation request > - > > Key: AMBARI-23162 > URL: https://issues.apache.org/jira/browse/AMBARI-23162 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23162) Pass full stack version in recommendation request
[ https://issues.apache.org/jira/browse/AMBARI-23162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23162: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to master > Pass full stack version in recommendation request > - > > Key: AMBARI-23162 > URL: https://issues.apache.org/jira/browse/AMBARI-23162 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-23162) Pass full stack version in recommendation request
[ https://issues.apache.org/jira/browse/AMBARI-23162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16389519#comment-16389519 ] Antonenko Alexander edited comment on AMBARI-23162 at 3/7/18 1:05 PM: -- Committed to branch-2.6 was (Author: aantonenko): Committed to master > Pass full stack version in recommendation request > - > > Key: AMBARI-23162 > URL: https://issues.apache.org/jira/browse/AMBARI-23162 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23162) Pass full stack version in recommendation request
[ https://issues.apache.org/jira/browse/AMBARI-23162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23162: Assignee: Antonenko Alexander > Pass full stack version in recommendation request > - > > Key: AMBARI-23162 > URL: https://issues.apache.org/jira/browse/AMBARI-23162 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
[
https://issues.apache.org/jira/browse/AMBARI-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23163:
Labels: pull-request-available (was: )
> Unable to add a service in second go from Ambari-UI
> ---
>
> Key: AMBARI-23163
> URL: https://issues.apache.org/jira/browse/AMBARI-23163
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: add-service-stuck.png
>
>
> Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
> Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
> Now trying to Add Knox / Ranger, after customizing the configurations and
> clicked on the {{Next}} button UI is stuck and unable to reach the deploy
> screen.
> Browser console shows error {{unable to load modification handler for
> RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
[
https://issues.apache.org/jira/browse/AMBARI-23163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-23163:
--
Attachment: add-service-stuck.png
> Unable to add a service in second go from Ambari-UI
> ---
>
> Key: AMBARI-23163
> URL: https://issues.apache.org/jira/browse/AMBARI-23163
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: add-service-stuck.png
>
>
> Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
> Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
> Now trying to Add Knox / Ranger, after customizing the configurations and
> clicked on the {{Next}} button UI is stuck and unable to reach the deploy
> screen.
> Browser console shows error {{unable to load modification handler for
> RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23163) Unable to add a service in second go from Ambari-UI
Andrii Tkach created AMBARI-23163:
-
Summary: Unable to add a service in second go from Ambari-UI
Key: AMBARI-23163
URL: https://issues.apache.org/jira/browse/AMBARI-23163
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.7.0
Installed Ambari using build 2.7.0.2-70 and HDP-3.0.0.2-150.
Added services HDFS, Yarn, Hive, HBase, Zookeeper and Solr.
Now trying to Add Knox / Ranger, after customizing the configurations and
clicked on the {{Next}} button UI is stuck and unable to reach the deploy
screen.
Browser console shows error {{unable to load modification handler for RANGER}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23162) Pass full stack version in recommendation request
[ https://issues.apache.org/jira/browse/AMBARI-23162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23162: Labels: pull-request-available (was: ) > Pass full stack version in recommendation request > - > > Key: AMBARI-23162 > URL: https://issues.apache.org/jira/browse/AMBARI-23162 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23162) Pass full stack version in recommendation request
Antonenko Alexander created AMBARI-23162: Summary: Pass full stack version in recommendation request Key: AMBARI-23162 URL: https://issues.apache.org/jira/browse/AMBARI-23162 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23150) Configurations attributes reset after running Add Service wizard
[ https://issues.apache.org/jira/browse/AMBARI-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23150: -- Fix Version/s: 2.6.2 > Configurations attributes reset after running Add Service wizard > > > Key: AMBARI-23150 > URL: https://issues.apache.org/jira/browse/AMBARI-23150 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2, 2.7.0 > > Attachments: image-2018-02-27-19-55-19-261.png, > image-2018-02-27-20-00-12-533.png > > Time Spent: 20m > Remaining Estimate: 0h > > h3. STEPS TO REPRODUCE > # Install the latest Sandbox docker (to re-reproduce the issue docker is > easier) > # Add "hadoop.security.group.mapping.ldap.bind.password" in Custom core-site > with the value "admin-password" with Property Type *"PASSWORD"*, and save > !image-2018-02-27-20-00-12-533.png|thumbnail! > # From Add Service Wizard, add some service (I tested with Nifi and Solr but > any service should be OK) > # After Wizard, go to HDFS => Configs and search ldap.bind.password, it shows > text input box rather than password input box -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23150) Configurations attributes reset after running Add Service wizard
[ https://issues.apache.org/jira/browse/AMBARI-23150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23150: Labels: pull-request-available (was: ) > Configurations attributes reset after running Add Service wizard > > > Key: AMBARI-23150 > URL: https://issues.apache.org/jira/browse/AMBARI-23150 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: image-2018-02-27-19-55-19-261.png, > image-2018-02-27-20-00-12-533.png > > > h3. STEPS TO REPRODUCE > # Install the latest Sandbox docker (to re-reproduce the issue docker is > easier) > # Add "hadoop.security.group.mapping.ldap.bind.password" in Custom core-site > with the value "admin-password" with Property Type *"PASSWORD"*, and save > !image-2018-02-27-20-00-12-533.png|thumbnail! > # From Add Service Wizard, add some service (I tested with Nifi and Solr but > any service should be OK) > # After Wizard, go to HDFS => Configs and search ldap.bind.password, it shows > text input box rather than password input box -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23130) Implement persistence support for the cluster creation template
[ https://issues.apache.org/jira/browse/AMBARI-23130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári resolved AMBARI-23130. Resolution: Fixed > Implement persistence support for the cluster creation template > --- > > Key: AMBARI-23130 > URL: https://issues.apache.org/jira/browse/AMBARI-23130 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Implement persistence for the cluster creation template. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
