[jira] [Created] (AMBARI-15345) Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
Dmytro Grinenko created AMBARI-15345:
Summary: Multiple issues during EU from HDP 2.4.0.0-157 to
2.4.0.0-169 on SLES 11
Key: AMBARI-15345
URL: https://issues.apache.org/jira/browse/AMBARI-15345
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: 2.2.2
{code}
Following operations reported errors:
2016-03-03
01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting HCat Client on 4 hosts : HOLDING_FAILED
2016-03-03
01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Nimbus on 3 hosts : HOLDING_FAILED
2016-03-03
01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Oozie Server on 3 hosts : HOLDING_FAILED
2016-03-03
01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Atlas Metadata Server on
os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
2016-03-03
01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Ranger Admin on 2 hosts : HOLDING_FAILED
2016-03-03
01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Preparing Oozie Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal :
HOLDING_FAILED
2016-03-03
01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Ranger Usersync on os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal
: HOLDING_FAILED
2016-03-03
01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Sqoop on 4 hosts : HOLDING_FAILED
2016-03-03
01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Pig on 4 hosts : HOLDING_FAILED
2016-03-03
01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Slider on 4 hosts : HOLDING_FAILED
2016-03-03
01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Flume on 4 hosts : HOLDING_FAILED
2016-03-03
01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting WebHCat Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal
(Batch 1 of 3) : HOLDING_FAILED
2016-03-03
01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Preparing Oozie Server on 3 hosts : HOLDING_FAILED
2016-03-03
01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO: Check
Component Versions : HOLDING_FAILED
2016-03-03
01:14:14,916|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
Restarting Supervisor on 4 hosts : HOLDING_FAILED
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15345) Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
[
https://issues.apache.org/jira/browse/AMBARI-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15345:
-
Attachment: AMBARI-15345.patch
> Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
>
>
> Key: AMBARI-15345
> URL: https://issues.apache.org/jira/browse/AMBARI-15345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15345.patch
>
>
> {code}
> Following operations reported errors:
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting HCat Client on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Nimbus on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Atlas Metadata Server on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Admin on 2 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal :
> HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Usersync on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Sqoop on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Pig on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Slider on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Flume on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting WebHCat Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal
> (Batch 1 of 3) : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO: Check
> Component Versions : HOLDING_FAILED
> 2016-03-03
> 01:14:14,916|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Supervisor on 4 hosts : HOLDING_FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15345) Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
[
https://issues.apache.org/jira/browse/AMBARI-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186916#comment-15186916
]
Dmytro Grinenko commented on AMBARI-15345:
--
patch doesn't change any logic, as result no test change required.
> Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
>
>
> Key: AMBARI-15345
> URL: https://issues.apache.org/jira/browse/AMBARI-15345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15345.patch
>
>
> {code}
> Following operations reported errors:
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting HCat Client on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Nimbus on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Atlas Metadata Server on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Admin on 2 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal :
> HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Usersync on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Sqoop on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Pig on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Slider on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Flume on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting WebHCat Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal
> (Batch 1 of 3) : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO: Check
> Component Versions : HOLDING_FAILED
> 2016-03-03
> 01:14:14,916|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Supervisor on 4 hosts : HOLDING_FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15345) Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
[
https://issues.apache.org/jira/browse/AMBARI-15345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15345:
-
Status: Patch Available (was: Open)
> Multiple issues during EU from HDP 2.4.0.0-157 to 2.4.0.0-169 on SLES 11
>
>
> Key: AMBARI-15345
> URL: https://issues.apache.org/jira/browse/AMBARI-15345
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15345.patch
>
>
> {code}
> Following operations reported errors:
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting HCat Client on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,911|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Nimbus on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Atlas Metadata Server on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,912|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Admin on 2 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal :
> HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Ranger Usersync on
> os-s11-3-ymqfms-dalm21tom21nextsecha-5.novalocal : HOLDING_FAILED
> 2016-03-03
> 01:14:14,913|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Sqoop on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Pig on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Slider on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,914|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Flume on 4 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting WebHCat Server on os-s11-3-ymqfms-dalm21tom21nextsecha-3.novalocal
> (Batch 1 of 3) : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Preparing Oozie Server on 3 hosts : HOLDING_FAILED
> 2016-03-03
> 01:14:14,915|beaver.machine|INFO|30895|140578454144768|MainThread|INFO: Check
> Component Versions : HOLDING_FAILED
> 2016-03-03
> 01:14:14,916|beaver.machine|INFO|30895|140578454144768|MainThread|INFO:
> Restarting Supervisor on 4 hosts : HOLDING_FAILED
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15397) Rolling Upgrade: incorrect display_status of upgrade groups
Dmytro Grinenko created AMBARI-15397:
Summary: Rolling Upgrade: incorrect display_status of upgrade
groups
Key: AMBARI-15397
URL: https://issues.apache.org/jira/browse/AMBARI-15397
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: 2.2.2
Upgrade display_status does not correspond to status of its upgrade items.
Upgrade group must have display_status IN_PROGRESS instead of COMPLETE:
{code:java}
{
"UpgradeGroup" : {
"completed_task_count" : 1,
"display_status" : "COMPLETED",
"group_id" : 53,
"in_progress_task_count" : 2,
"name" : "ZOOKEEPER",
"progress_percent" : 45.0,
"request_id" : 24,
"status" : "IN_PROGRESS",
"title" : "ZooKeeper",
"total_task_count" : 3
},
"upgrade_items" : [
{
"UpgradeItem" : {
"context" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
(Batch 1 of 3)",
"display_status" : "COMPLETED",
"group_id" : 53,
"progress_percent" : 100.0,
"request_id" : 24,
"skippable" : true,
"stage_id" : 20,
"status" : "COMPLETED",
"text" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
(Batch 1 of 3)"
}
},
{
"UpgradeItem" : {
"context" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
(Batch 2 of 3)",
"display_status" : "IN_PROGRESS",
"group_id" : 53,
"progress_percent" : 35.0,
"request_id" : 24,
"skippable" : true,
"stage_id" : 21,
"status" : "IN_PROGRESS",
"text" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
(Batch 2 of 3)"
}
},
{
"UpgradeItem" : {
"context" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
(Batch 3 of 3)",
"display_status" : "PENDING",
"group_id" : 53,
"progress_percent" : 0.0,
"request_id" : 24,
"skippable" : true,
"stage_id" : 22,
"status" : "PENDING",
"text" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
(Batch 3 of 3)"
}
}
]
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15397) Rolling Upgrade: incorrect display_status of upgrade groups
[
https://issues.apache.org/jira/browse/AMBARI-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15397:
-
Attachment: AMBARI-15397.patch
> Rolling Upgrade: incorrect display_status of upgrade groups
> ---
>
> Key: AMBARI-15397
> URL: https://issues.apache.org/jira/browse/AMBARI-15397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15397.patch
>
>
> Upgrade display_status does not correspond to status of its upgrade items.
> Upgrade group must have display_status IN_PROGRESS instead of COMPLETE:
> {code:java}
> {
> "UpgradeGroup" : {
> "completed_task_count" : 1,
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "in_progress_task_count" : 2,
> "name" : "ZOOKEEPER",
> "progress_percent" : 45.0,
> "request_id" : 24,
> "status" : "IN_PROGRESS",
> "title" : "ZooKeeper",
> "total_task_count" : 3
> },
> "upgrade_items" : [
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6401.ambari.apache.org (Batch 1 of 3)",
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "progress_percent" : 100.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 20,
> "status" : "COMPLETED",
> "text" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
> (Batch 1 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6402.ambari.apache.org (Batch 2 of 3)",
> "display_status" : "IN_PROGRESS",
> "group_id" : 53,
> "progress_percent" : 35.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 21,
> "status" : "IN_PROGRESS",
> "text" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
> (Batch 2 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6403.ambari.apache.org (Batch 3 of 3)",
> "display_status" : "PENDING",
> "group_id" : 53,
> "progress_percent" : 0.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 22,
> "status" : "PENDING",
> "text" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
> (Batch 3 of 3)"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15397) Rolling Upgrade: incorrect display_status of upgrade groups
[
https://issues.apache.org/jira/browse/AMBARI-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15397:
-
Status: Patch Available (was: Open)
> Rolling Upgrade: incorrect display_status of upgrade groups
> ---
>
> Key: AMBARI-15397
> URL: https://issues.apache.org/jira/browse/AMBARI-15397
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15397.patch
>
>
> Upgrade display_status does not correspond to status of its upgrade items.
> Upgrade group must have display_status IN_PROGRESS instead of COMPLETE:
> {code:java}
> {
> "UpgradeGroup" : {
> "completed_task_count" : 1,
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "in_progress_task_count" : 2,
> "name" : "ZOOKEEPER",
> "progress_percent" : 45.0,
> "request_id" : 24,
> "status" : "IN_PROGRESS",
> "title" : "ZooKeeper",
> "total_task_count" : 3
> },
> "upgrade_items" : [
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6401.ambari.apache.org (Batch 1 of 3)",
> "display_status" : "COMPLETED",
> "group_id" : 53,
> "progress_percent" : 100.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 20,
> "status" : "COMPLETED",
> "text" : "Restarting ZooKeeper Server on c6401.ambari.apache.org
> (Batch 1 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6402.ambari.apache.org (Batch 2 of 3)",
> "display_status" : "IN_PROGRESS",
> "group_id" : 53,
> "progress_percent" : 35.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 21,
> "status" : "IN_PROGRESS",
> "text" : "Restarting ZooKeeper Server on c6402.ambari.apache.org
> (Batch 2 of 3)"
> }
> },
> {
> "UpgradeItem" : {
> "context" : "Restarting ZooKeeper Server on
> c6403.ambari.apache.org (Batch 3 of 3)",
> "display_status" : "PENDING",
> "group_id" : 53,
> "progress_percent" : 0.0,
> "request_id" : 24,
> "skippable" : true,
> "stage_id" : 22,
> "status" : "PENDING",
> "text" : "Restarting ZooKeeper Server on c6403.ambari.apache.org
> (Batch 3 of 3)"
> }
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15398) Disable HDP 2.5 stack in Ambari 2.2.2
Dmytro Grinenko created AMBARI-15398: Summary: Disable HDP 2.5 stack in Ambari 2.2.2 Key: AMBARI-15398 URL: https://issues.apache.org/jira/browse/AMBARI-15398 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Dmytro Grinenko Fix For: 2.2.2 Disable the HDP 2.5 stack option from Ambari in Ambari 2.2.2 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15398) Disable HDP 2.5 stack in Ambari 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15398: - Attachment: AMBARI-15398.patch > Disable HDP 2.5 stack in Ambari 2.2.2 > - > > Key: AMBARI-15398 > URL: https://issues.apache.org/jira/browse/AMBARI-15398 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko > Fix For: 2.2.2 > > Attachments: AMBARI-15398.patch > > > Disable the HDP 2.5 stack option from Ambari in Ambari 2.2.2 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15398) Disable HDP 2.5 stack in Ambari 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192914#comment-15192914 ] Dmytro Grinenko commented on AMBARI-15398: -- Review Board: https://reviews.apache.org/r/44781/ > Disable HDP 2.5 stack in Ambari 2.2.2 > - > > Key: AMBARI-15398 > URL: https://issues.apache.org/jira/browse/AMBARI-15398 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko > Fix For: 2.2.2 > > Attachments: AMBARI-15398.patch > > > Disable the HDP 2.5 stack option from Ambari in Ambari 2.2.2 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15398) Disable HDP 2.5 stack in Ambari 2.2.2
[ https://issues.apache.org/jira/browse/AMBARI-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15398: - Status: Patch Available (was: Open) > Disable HDP 2.5 stack in Ambari 2.2.2 > - > > Key: AMBARI-15398 > URL: https://issues.apache.org/jira/browse/AMBARI-15398 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko > Fix For: 2.2.2 > > Attachments: AMBARI-15398.patch > > > Disable the HDP 2.5 stack option from Ambari in Ambari 2.2.2 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15439) Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+
Dmytro Grinenko created AMBARI-15439: Summary: Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ Key: AMBARI-15439 URL: https://issues.apache.org/jira/browse/AMBARI-15439 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.2.2 Reporter: Dmytro Grinenko Priority: Critical Fix For: trunk, 2.2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15439) Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+
[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15439: - Description: Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does is not kerberized (because Kafka in HDP 2.2 did not support Kerb). In HDP 2.3, Kafka supports Kerb. Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get Kerberized unintentionally. We need to an a pre-upgrade check to warn the user this will happen. - If cluster is HDP 2.2 - If kerberos is enabled - If cluster is kerb'd - If target upgrade is to HDP 2.3 (or later) - Warning for both EU and RU upgrades It's a warning check, not a required check. Should inform the user that since their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. > Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ > --- > > Key: AMBARI-15439 > URL: https://issues.apache.org/jira/browse/AMBARI-15439 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.2.2 > > > Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does > is not kerberized (because Kafka in HDP 2.2 did not support Kerb). > In HDP 2.3, Kafka supports Kerb. > Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get > Kerberized unintentionally. > We need to an a pre-upgrade check to warn the user this will happen. > - If cluster is HDP 2.2 > - If kerberos is enabled > - If cluster is kerb'd > - If target upgrade is to HDP 2.3 (or later) > - Warning for both EU and RU upgrades > It's a warning check, not a required check. Should inform the user that since > their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15439) Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+
[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15439: - Attachment: AMBARI-15439.patch > Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ > --- > > Key: AMBARI-15439 > URL: https://issues.apache.org/jira/browse/AMBARI-15439 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15439.patch > > > Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does > is not kerberized (because Kafka in HDP 2.2 did not support Kerb). > In HDP 2.3, Kafka supports Kerb. > Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get > Kerberized unintentionally. > We need to an a pre-upgrade check to warn the user this will happen. > - If cluster is HDP 2.2 > - If kerberos is enabled > - If cluster is kerb'd > - If target upgrade is to HDP 2.3 (or later) > - Warning for both EU and RU upgrades > It's a warning check, not a required check. Should inform the user that since > their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15439) Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+
[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15439: - Status: Patch Available (was: Open) > Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ > --- > > Key: AMBARI-15439 > URL: https://issues.apache.org/jira/browse/AMBARI-15439 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15439.patch > > > Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does > is not kerberized (because Kafka in HDP 2.2 did not support Kerb). > In HDP 2.3, Kafka supports Kerb. > Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get > Kerberized unintentionally. > We need to an a pre-upgrade check to warn the user this will happen. > - If cluster is HDP 2.2 > - If kerberos is enabled > - If cluster is kerb'd > - If target upgrade is to HDP 2.3 (or later) > - Warning for both EU and RU upgrades > It's a warning check, not a required check. Should inform the user that since > their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15439) Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+
[ https://issues.apache.org/jira/browse/AMBARI-15439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15439: - Attachment: AMBARI-15439.patch.1 > Add Upgrade Check for Kafka Kerb on HDP 2.2 -> 2.3+ > --- > > Key: AMBARI-15439 > URL: https://issues.apache.org/jira/browse/AMBARI-15439 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15439.patch, AMBARI-15439.patch.1 > > > Users that are running HDP 2.2 with Kafka and Kerberos is enabled, Kafka does > is not kerberized (because Kafka in HDP 2.2 did not support Kerb). > In HDP 2.3, Kafka supports Kerb. > Therefore, when that HDP 2.2 user upgrades to HDP 2.3, their Kafka will get > Kerberized unintentionally. > We need to an a pre-upgrade check to warn the user this will happen. > - If cluster is HDP 2.2 > - If kerberos is enabled > - If cluster is kerb'd > - If target upgrade is to HDP 2.3 (or later) > - Warning for both EU and RU upgrades > It's a warning check, not a required check. Should inform the user that since > their cluster has Kerberos enabled, after upgrade, Kafka will be Kerberized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
Dmytro Grinenko created AMBARI-15505: Summary: Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site Key: AMBARI-15505 URL: https://issues.apache.org/jira/browse/AMBARI-15505 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: Dmytro Grinenko Fix For: trunk This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15505: - Status: Patch Available (was: Open) > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15505: - Attachment: AMBARI-15505.patch > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
Dmytro Grinenko created AMBARI-15513:
Summary: Download Client Configurations failed with "Cannot open:
No such file or directorydoes not exist"
Key: AMBARI-15513
URL: https://issues.apache.org/jira/browse/AMBARI-15513
Project: Ambari
Issue Type: Bug
Reporter: Dmytro Grinenko
Priority: Critical
{code}
19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
Reading password from existing file
19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
generate_configs
/var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
/var/lib/ambari-server/data/tmp/structured-out.json INFO
/var/lib/ambari-server/data/tmp" returned 1.
java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
generate_configs
/var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
/var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
/var/lib/ambari-server/data/tmp/structured-out.json INFO
/var/lib/ambari-server/data/tmp" returned 1.
at
org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
at
org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
at
org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
at
org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
at
org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
at
org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
at
org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
at
org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at
com.sun.jersey.spi.container.servlet.WebComponent.service(WebC
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Component/s: ambari-server
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClasse
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Affects Version/s: 2.2.2
trunk
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRul
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Attachment: AMBARI-15513.patch
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceCl
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Fix Version/s: 2.2.2
trunk
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Status: Patch Available (was: Open)
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootReso
[jira] [Updated] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15505: - Attachment: (was: AMBARI-15505.patch) > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15505: - Attachment: AMBARI-15505.patch > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Attachment: AMBARI-15513-trunk.patch
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513-trunk.patch, AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.s
[jira] [Commented] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206802#comment-15206802
]
Dmytro Grinenko commented on AMBARI-15513:
--
Local testing done:
[10:47:20][org.apache.ambari:ambari-server] Total run:942
[10:47:20][org.apache.ambari:ambari-server] Total errors:0
[10:47:20][org.apache.ambari:ambari-server] Total failures:0
[10:47:20][org.apache.ambari:ambari-server] OK
[10:47:33][org.apache.ambari:ambari-agent] Ran 422 tests in 12.588s
[10:47:33][org.apache.ambari:ambari-agent]
[10:47:33][org.apache.ambari:ambari-agent] OK
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513-trunk.patch, AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.je
[jira] [Updated] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15505: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15505) Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value from ranger-site
[ https://issues.apache.org/jira/browse/AMBARI-15505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206804#comment-15206804 ] Dmytro Grinenko commented on AMBARI-15505: -- Local testing done: [08:23:33][Step 1/1] [INFO] Reactor Summary: [08:23:33][Step 1/1] [INFO] [08:23:33][Step 1/1] [INFO] Ambari Views .. SUCCESS [4.033s] [08:23:33][Step 1/1] [INFO] Ambari Metrics Common . SUCCESS [2.844s] [08:23:33][Step 1/1] [INFO] Ambari Server . SUCCESS [1:02:32.063s] [08:23:33][Step 1/1] [INFO] [08:23:33][Step 1/1] [INFO] BUILD SUCCESS [08:23:33][Step 1/1] [INFO] [08:23:33][Step 1/1] [INFO] Total time: 1:02:39.578s [08:23:33][Step 1/1] [INFO] Finished at: Tue Mar 22 08:23:33 UTC 2016 [08:23:33][Step 1/1] [INFO] Final Memory: 60M/734M [08:23:33][Step 1/1] [INFO] > Ambari upgrade for 2.0.x version to 2.1.x doesn't retain properties value > from ranger-site > -- > > Key: AMBARI-15505 > URL: https://issues.apache.org/jira/browse/AMBARI-15505 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Sen > Fix For: trunk > > Attachments: AMBARI-15505.patch > > > This is not handled in any previous Ambari Upgrade catalog -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15513) Download Client Configurations failed with "Cannot open: No such file or directorydoes not exist"
[
https://issues.apache.org/jira/browse/AMBARI-15513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15513:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Download Client Configurations failed with "Cannot open: No such file or
> directorydoes not exist"
> -
>
> Key: AMBARI-15513
> URL: https://issues.apache.org/jira/browse/AMBARI-15513
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15513-trunk.patch, AMBARI-15513.patch
>
>
> {code}
> 19 Mar 2016 01:49:26,174 INFO [qtp-ambari-client-520] Configuration:785 -
> Reading password from existing file
> 19 Mar 2016 01:49:26,657 ERROR [qtp-ambari-client-520]
> ClientConfigResourceProvider:413 - Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> java.util.concurrent.ExecutionException: Execution of "ambari-python-wrap
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/HDFS_CLIENT-configuration.json
> /var/lib/ambari-server/resources/common-services/HDFS/2.1.0.2.0/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1.
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.executeCommand(ClientConfigResourceProvider.java:489)
> at
> org.apache.ambari.server.controller.internal.ClientConfigResourceProvider.getResources(ClientConfigResourceProvider.java:405)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:945)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:132)
> at
> org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:508)
> at
> org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:380)
> at
> org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:216)
> at
> org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:75)
> at
> org.apache.ambari.server.api.services.ComponentService.createClientConfigResource(ComponentService.java:226)
> at
> org.apache.ambari.server.api.services.ComponentService.getComponent(ComponentService.java:79)
> at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>
[jira] [Created] (AMBARI-15557) YARN service check fails if there is no queue named "default"
Dmytro Grinenko created AMBARI-15557:
Summary: YARN service check fails if there is no queue named
"default"
Key: AMBARI-15557
URL: https://issues.apache.org/jira/browse/AMBARI-15557
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: trunk, 2.2.2
Service check for yarn will fail in case if
{{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"
[
https://issues.apache.org/jira/browse/AMBARI-15557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15557:
-
Attachment: AMBARI-15557.patch
> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15557.patch
>
>
> Service check for yarn will fail in case if
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
> caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"
[
https://issues.apache.org/jira/browse/AMBARI-15557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15557:
-
Status: Patch Available (was: Open)
> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15557.patch
>
>
> Service check for yarn will fail in case if
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
> caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"
[
https://issues.apache.org/jira/browse/AMBARI-15557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15557:
-
Attachment: AMBARI-15557.patch.1
> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15557.patch, AMBARI-15557.patch.1
>
>
> Service check for yarn will fail in case if
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
> caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15557) YARN service check fails if there is no queue named "default"
[
https://issues.apache.org/jira/browse/AMBARI-15557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15557:
-
Attachment: AMBARI-15557-trunk.patch
> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15557-trunk.patch, AMBARI-15557.patch,
> AMBARI-15557.patch.1
>
>
> Service check for yarn will fail in case if
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
> caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15583) YARN service check fails due to syntax error
Dmytro Grinenko created AMBARI-15583: Summary: YARN service check fails due to syntax error Key: AMBARI-15583 URL: https://issues.apache.org/jira/browse/AMBARI-15583 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.2.2 Reporter: Dmytro Grinenko Priority: Blocker Fix For: trunk, 2.2.2 Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 155, in ServiceCheck().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 239, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 117, in service_check user=params.smokeuser, File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, in checked_call tries=tries, try_sleep=try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 293, in _call raise Fail(err_msg) resource_management.core.exceptions.Fail: Execution of 'yarn org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls -num_containers 1 -jar /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar -timeout 30--queue default' returned 255. 16/03/25 05:07:47 INFO impl.TimelineClientImpl: Timeline service address: http://c6401.ambari.apache.org:8188/ws/v1/timeline/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15583) YARN service check fails due to syntax error
[ https://issues.apache.org/jira/browse/AMBARI-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15583: - Description: Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 155, in ServiceCheck().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 239, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 117, in service_check user=params.smokeuser, File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, in checked_call tries=tries, try_sleep=try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 293, in _call raise Fail(err_msg) resource_management.core.exceptions.Fail: Execution of 'yarn org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls -num_containers 1 -jar /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar -timeout 30--queue default' returned 255. was: Traceback (most recent call last): File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 155, in ServiceCheck().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 239, in execute method(env) File "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", line 117, in service_check user=params.smokeuser, File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 70, in inner result = function(command, **kwargs) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 92, in checked_call tries=tries, try_sleep=try_sleep) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 140, in _call_wrapper result = _call(command, **kwargs_copy) File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 293, in _call raise Fail(err_msg) resource_management.core.exceptions.Fail: Execution of 'yarn org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls -num_containers 1 -jar /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar -timeout 30--queue default' returned 255. 16/03/25 05:07:47 INFO impl.TimelineClientImpl: Timeline service address: http://c6401.ambari.apache.org:8188/ws/v1/timeline/ > YARN service check fails due to syntax error > > > Key: AMBARI-15583 > URL: https://issues.apache.org/jira/browse/AMBARI-15583 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.2.2 > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 155, in > ServiceCheck().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 239, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 117, in service_check > user=params.smokeuser, > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 70, in inner > result = function(command, **kwargs) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 92, in checked_call > tries=tries, try_sleep=try_sleep) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 140, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 293, in _call > raise Fail(err_msg) > resource_management.core.exceptions.Fail: Execution of 'yarn > org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls > -num_containers 1 -jar > /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar > -timeout 30--queue default' returned 255. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15583) YARN service check fails due to syntax error
[ https://issues.apache.org/jira/browse/AMBARI-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15583: - Attachment: AMBARI-15583-trunk.patch AMBARI-15583.patch > YARN service check fails due to syntax error > > > Key: AMBARI-15583 > URL: https://issues.apache.org/jira/browse/AMBARI-15583 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15583-trunk.patch, AMBARI-15583.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 155, in > ServiceCheck().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 239, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 117, in service_check > user=params.smokeuser, > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 70, in inner > result = function(command, **kwargs) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 92, in checked_call > tries=tries, try_sleep=try_sleep) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 140, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 293, in _call > raise Fail(err_msg) > resource_management.core.exceptions.Fail: Execution of 'yarn > org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls > -num_containers 1 -jar > /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar > -timeout 30--queue default' returned 255. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15583) YARN service check fails due to syntax error
[ https://issues.apache.org/jira/browse/AMBARI-15583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15583: - Status: Patch Available (was: Open) > YARN service check fails due to syntax error > > > Key: AMBARI-15583 > URL: https://issues.apache.org/jira/browse/AMBARI-15583 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: trunk, 2.2.2 > > Attachments: AMBARI-15583-trunk.patch, AMBARI-15583.patch > > > Traceback (most recent call last): > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 155, in > ServiceCheck().execute() > File > "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", > line 239, in execute > method(env) > File > "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py", > line 117, in service_check > user=params.smokeuser, > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 70, in inner > result = function(command, **kwargs) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 92, in checked_call > tries=tries, try_sleep=try_sleep) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 140, in _call_wrapper > result = _call(command, **kwargs_copy) > File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", > line 293, in _call > raise Fail(err_msg) > resource_management.core.exceptions.Fail: Execution of 'yarn > org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls > -num_containers 1 -jar > /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar > -timeout 30--queue default' returned 255. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15557) YARN service check fails if there is no queue named "default"
[
https://issues.apache.org/jira/browse/AMBARI-15557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211818#comment-15211818
]
Dmytro Grinenko commented on AMBARI-15557:
--
[~dgergely] Fixed in AMBARI-15583
> YARN service check fails if there is no queue named "default"
> -
>
> Key: AMBARI-15557
> URL: https://issues.apache.org/jira/browse/AMBARI-15557
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15557-trunk.patch, AMBARI-15557.patch,
> AMBARI-15557.patch.1
>
>
> Service check for yarn will fail in case if
> {{yarn.scheduler.capacity.root.queues}} doesn't declare default queue. This
> caused due to usage of yarn distributed shell, which use default queue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15627) Ambari is expecting hadoop client package and configuration, even if no HDFS components are installed on this host
Dmytro Grinenko created AMBARI-15627:
Summary: Ambari is expecting hadoop client package and
configuration, even if no HDFS components are installed on this host
Key: AMBARI-15627
URL: https://issues.apache.org/jira/browse/AMBARI-15627
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Dmytro Grinenko
Priority: Critical
Fix For: 2.2.2
This happens during an ugprade from HDP 2.3.0 to 2.3.4.7. Couple nodes have
Kafka broker/Zookeeper installed with no clients or any other components.
Hence, during the installation, there is no HDFS package installed on this
node. However, during the start up Ambari expects this node to have
/usr/hdp/current/hadoop-client/conf' during the start up:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 39, in
BeforeStartHook().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 219, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
line 36, in hook
create_topology_script_and_mapping()
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
line 69, in create_topology_script_and_mapping
create_topology_mapping()
File
"/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
line 36, in create_topology_mapping
group=params.user_group)
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line
154, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 158, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 121, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 152, in action_create
sudo.makedirs(path, self.resource.mode or 0755)
File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py", line
55, in makedirs
os.makedirs(path, mode)
File "/usr/lib64/python2.6/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 2] No such file or directory:
'/usr/hdp/current/hadoop-client/conf'
Error: Error: Unable to run the custom hook script ['/usr/bin/python2',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
'START', '/var/lib/ambari-agent/data/command-3343.json',
'/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
'/var/lib/ambari-agent/data/structured-out-3343.json', 'INFO',
'/var/lib/ambari-agent/tmp']
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15627) Ambari is expecting hadoop client package and configuration, even if no HDFS components are installed on this host
[
https://issues.apache.org/jira/browse/AMBARI-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15627:
-
Attachment: AMBARI-15627.patch
> Ambari is expecting hadoop client package and configuration, even if no HDFS
> components are installed on this host
> --
>
> Key: AMBARI-15627
> URL: https://issues.apache.org/jira/browse/AMBARI-15627
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15627.patch
>
>
> This happens during an ugprade from HDP 2.3.0 to 2.3.4.7. Couple nodes have
> Kafka broker/Zookeeper installed with no clients or any other components.
> Hence, during the installation, there is no HDFS package installed on this
> node. However, during the start up Ambari expects this node to have
> /usr/hdp/current/hadoop-client/conf' during the start up:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 39, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 36, in hook
> create_topology_script_and_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 69, in create_topology_script_and_mapping
> create_topology_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 36, in create_topology_mapping
> group=params.user_group)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 158, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 121, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 152, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py",
> line 55, in makedirs
> os.makedirs(path, mode)
> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory:
> '/usr/hdp/current/hadoop-client/conf'
> Error: Error: Unable to run the custom hook script ['/usr/bin/python2',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-3343.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-3343.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15627) Ambari is expecting hadoop client package and configuration, even if no HDFS components are installed on this host
[
https://issues.apache.org/jira/browse/AMBARI-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15627:
-
Status: Patch Available (was: Open)
> Ambari is expecting hadoop client package and configuration, even if no HDFS
> components are installed on this host
> --
>
> Key: AMBARI-15627
> URL: https://issues.apache.org/jira/browse/AMBARI-15627
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15627.patch
>
>
> This happens during an ugprade from HDP 2.3.0 to 2.3.4.7. Couple nodes have
> Kafka broker/Zookeeper installed with no clients or any other components.
> Hence, during the installation, there is no HDFS package installed on this
> node. However, during the start up Ambari expects this node to have
> /usr/hdp/current/hadoop-client/conf' during the start up:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 39, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 36, in hook
> create_topology_script_and_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 69, in create_topology_script_and_mapping
> create_topology_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 36, in create_topology_mapping
> group=params.user_group)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 158, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 121, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 152, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py",
> line 55, in makedirs
> os.makedirs(path, mode)
> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory:
> '/usr/hdp/current/hadoop-client/conf'
> Error: Error: Unable to run the custom hook script ['/usr/bin/python2',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-3343.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-3343.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15627) Ambari is expecting hadoop client package and configuration, even if no HDFS components are installed on this host
[
https://issues.apache.org/jira/browse/AMBARI-15627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-15627:
-
Attachment: AMBARI-15627-branch-2.2.patch
AMBARI-15627.patch.1
> Ambari is expecting hadoop client package and configuration, even if no HDFS
> components are installed on this host
> --
>
> Key: AMBARI-15627
> URL: https://issues.apache.org/jira/browse/AMBARI-15627
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15627-branch-2.2.patch, AMBARI-15627.patch,
> AMBARI-15627.patch.1
>
>
> This happens during an ugprade from HDP 2.3.0 to 2.3.4.7. Couple nodes have
> Kafka broker/Zookeeper installed with no clients or any other components.
> Hence, during the installation, there is no HDFS package installed on this
> node. However, during the start up Ambari expects this node to have
> /usr/hdp/current/hadoop-client/conf' during the start up:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 39, in
> BeforeStartHook().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py",
> line 36, in hook
> create_topology_script_and_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 69, in create_topology_script_and_mapping
> create_topology_mapping()
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/rack_awareness.py",
> line 36, in create_topology_mapping
> group=params.user_group)
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 154, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 158, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 121, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 152, in action_create
> sudo.makedirs(path, self.resource.mode or 0755)
> File "/usr/lib/python2.6/site-packages/resource_management/core/sudo.py",
> line 55, in makedirs
> os.makedirs(path, mode)
> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 2] No such file or directory:
> '/usr/hdp/current/hadoop-client/conf'
> Error: Error: Unable to run the custom hook script ['/usr/bin/python2',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START/scripts/hook.py',
> 'START', '/var/lib/ambari-agent/data/command-3343.json',
> '/var/lib/ambari-agent/cache/stacks/HDP/2.0.6/hooks/before-START',
> '/var/lib/ambari-agent/data/structured-out-3343.json', 'INFO',
> '/var/lib/ambari-agent/tmp']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15772) HBase masters go offline after kerberization on 2.2.9.0
Dmytro Grinenko created AMBARI-15772: Summary: HBase masters go offline after kerberization on 2.2.9.0 Key: AMBARI-15772 URL: https://issues.apache.org/jira/browse/AMBARI-15772 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.2.2 Reporter: Dmytro Grinenko Priority: Blocker Fix For: 2.2.2 STR: - deploy Ambari with 2.2.9 stack (select hbase, hive and dependency) - add ranger after - start kerberization Observe the status of HBase masters All three report down -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15772) HBase masters go offline after kerberization on 2.2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-15772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15772: - Status: Patch Available (was: Open) > HBase masters go offline after kerberization on 2.2.9.0 > --- > > Key: AMBARI-15772 > URL: https://issues.apache.org/jira/browse/AMBARI-15772 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: 2.2.2 > > > STR: > - deploy Ambari with 2.2.9 stack (select hbase, hive and dependency) > - add ranger after > - start kerberization > Observe the status of HBase masters > All three report down -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15772) HBase masters go offline after kerberization on 2.2.9.0
[ https://issues.apache.org/jira/browse/AMBARI-15772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15772: - Attachment: AMBARI-15772.patch > HBase masters go offline after kerberization on 2.2.9.0 > --- > > Key: AMBARI-15772 > URL: https://issues.apache.org/jira/browse/AMBARI-15772 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.2 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: 2.2.2 > > Attachments: AMBARI-15772.patch > > > STR: > - deploy Ambari with 2.2.9 stack (select hbase, hive and dependency) > - add ranger after > - start kerberization > Observe the status of HBase masters > All three report down -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15808) Create upgrade packs for HDP 2.5
Dmytro Grinenko created AMBARI-15808: Summary: Create upgrade packs for HDP 2.5 Key: AMBARI-15808 URL: https://issues.apache.org/jira/browse/AMBARI-15808 Project: Ambari Issue Type: Story Components: ambari-server Affects Versions: 2.4.0 Reporter: Dmytro Grinenko Priority: Blocker Fix For: 2.4.0 RU from HDP 2.3->2.5 RU from HDP 2.4->2.5 RU from HDP 2.5->2.5.* EU from HDP 2.3->2.5 EU from HDP 2.4->2.5 EU from HDP 2.5->2.5.* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15808) Create upgrade packs for HDP 2.5
[ https://issues.apache.org/jira/browse/AMBARI-15808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15808: - Status: Patch Available (was: Open) > Create upgrade packs for HDP 2.5 > > > Key: AMBARI-15808 > URL: https://issues.apache.org/jira/browse/AMBARI-15808 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko >Priority: Blocker > Fix For: 2.4.0 > > > RU from HDP 2.3->2.5 > RU from HDP 2.4->2.5 > RU from HDP 2.5->2.5.* > EU from HDP 2.3->2.5 > EU from HDP 2.4->2.5 > EU from HDP 2.5->2.5.* -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15830) Atlas Upgrade Check
Dmytro Grinenko created AMBARI-15830: Summary: Atlas Upgrade Check Key: AMBARI-15830 URL: https://issues.apache.org/jira/browse/AMBARI-15830 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.4.0 Reporter: Dmytro Grinenko Fix For: 2.4.0 Atlas for HDP 2.5 will need to be a new install. Atlas does not support upgrade (rolling upgrade or otherwise) from prior versions. It is only from HDP 2.5 on that Atlas support express and rolling upgrades. Because of this, it is necessary to have a pre upgrade check in Ambari that handles this case by asking the user to uninstall Atlas prior to upgrade. After the cluster has been upgraded, Atlas can be added to the cluster using the Ambari add service mechanism. This will result in a clean/new install of Atlas that will from this point on support rolling and express upgrades. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15830) Atlas Upgrade Check
[ https://issues.apache.org/jira/browse/AMBARI-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15830: - Attachment: AMBARI-15830.patch > Atlas Upgrade Check > --- > > Key: AMBARI-15830 > URL: https://issues.apache.org/jira/browse/AMBARI-15830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko > Fix For: 2.4.0 > > Attachments: AMBARI-15830.patch > > > Atlas for HDP 2.5 will need to be a new install. Atlas does not support > upgrade (rolling upgrade or otherwise) from prior versions. It is only from > HDP 2.5 on that Atlas support express and rolling upgrades. > Because of this, it is necessary to have a pre upgrade check in Ambari that > handles this case by asking the user to uninstall Atlas prior to upgrade. > After the cluster has been upgraded, Atlas can be added to the cluster using > the Ambari add service mechanism. This will result in a clean/new install of > Atlas that will from this point on support rolling and express upgrades. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15830) Atlas Upgrade Check
[ https://issues.apache.org/jira/browse/AMBARI-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15830: - Status: Patch Available (was: Open) > Atlas Upgrade Check > --- > > Key: AMBARI-15830 > URL: https://issues.apache.org/jira/browse/AMBARI-15830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko > Fix For: 2.4.0 > > Attachments: AMBARI-15830.patch > > > Atlas for HDP 2.5 will need to be a new install. Atlas does not support > upgrade (rolling upgrade or otherwise) from prior versions. It is only from > HDP 2.5 on that Atlas support express and rolling upgrades. > Because of this, it is necessary to have a pre upgrade check in Ambari that > handles this case by asking the user to uninstall Atlas prior to upgrade. > After the cluster has been upgraded, Atlas can be added to the cluster using > the Ambari add service mechanism. This will result in a clean/new install of > Atlas that will from this point on support rolling and express upgrades. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15830) Atlas Upgrade Check
[ https://issues.apache.org/jira/browse/AMBARI-15830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-15830: - Attachment: AMBARI-15830.patch.1 > Atlas Upgrade Check > --- > > Key: AMBARI-15830 > URL: https://issues.apache.org/jira/browse/AMBARI-15830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: Dmytro Grinenko > Fix For: 2.4.0 > > Attachments: AMBARI-15830.patch, AMBARI-15830.patch.1 > > > Atlas for HDP 2.5 will need to be a new install. Atlas does not support > upgrade (rolling upgrade or otherwise) from prior versions. It is only from > HDP 2.5 on that Atlas support express and rolling upgrades. > Because of this, it is necessary to have a pre upgrade check in Ambari that > handles this case by asking the user to uninstall Atlas prior to upgrade. > After the cluster has been upgraded, Atlas can be added to the cluster using > the Ambari add service mechanism. This will result in a clean/new install of > Atlas that will from this point on support rolling and express upgrades. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-25070) Remove old stack versions
Dmytro Grinenko created AMBARI-25070: Summary: Remove old stack versions Key: AMBARI-25070 URL: https://issues.apache.org/jira/browse/AMBARI-25070 Project: Ambari Issue Type: Epic Components: ambari-agent, ambari-server Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk Add possibility to Ambari to clean/remove rolling upgrade leftovers after the cluster upgrade has been tested. In addition to 'yum erase', need to consider any hdp-select operation that needs to be performed as well as the version needs to be de-registered from Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25071) The way to determine if repository is removable
Dmytro Grinenko created AMBARI-25071: Summary: The way to determine if repository is removable Key: AMBARI-25071 URL: https://issues.apache.org/jira/browse/AMBARI-25071 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk With possibility to removing no needed or not yet already used repositories, we need to provide to the world the information about it "removability". Previously we had 1 factor, which tells that repo could be removed - it were not installed and not present on any host. Now it would be more complex: - We will allow to uninstall any non-current repo except revertable things like hotfixes, patches incl. base branch to which they were applied Due to more complex nature of remove possibility, we need to provide this info alongside with the repositories information through API, so UI would be able to not hard-code this logic on own side. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25072) Remove stack packages and installed by them dependencies ( yum; centos/rhel 7)
Dmytro Grinenko created AMBARI-25072: Summary: Remove stack packages and installed by them dependencies ( yum; centos/rhel 7) Key: AMBARI-25072 URL: https://issues.apache.org/jira/browse/AMBARI-25072 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-server Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk Goals: - Determine a best way to remove installed with stack packages and their dependencies - Enable stack removal for yum enabled distros - Enable stack removal feature API -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25073) Enable stack removal through web client (UI)
Dmytro Grinenko created AMBARI-25073: Summary: Enable stack removal through web client (UI) Key: AMBARI-25073 URL: https://issues.apache.org/jira/browse/AMBARI-25073 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk Change the way how Admin View determine that stack could be removed. For that, ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js#isDeletable should be changed to consume changes made in AMBARI-25071 (i.e. use new provided flag with the repository) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25074) Enable repository removal for apt and zypper base systems
Dmytro Grinenko created AMBARI-25074: Summary: Enable repository removal for apt and zypper base systems Key: AMBARI-25074 URL: https://issues.apache.org/jira/browse/AMBARI-25074 Project: Ambari Issue Type: Task Components: ambari-agent, ambari-sever Affects Versions: trunk Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk Enable stack package removal with their dependencies for APT and ZYPPER based systems -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25207) The Ubuntu repository id for the cached apt package list is generated wrong in case if were used URL with https protocol
Dmytro Grinenko created AMBARI-25207: Summary: The Ubuntu repository id for the cached apt package list is generated wrong in case if were used URL with https protocol Key: AMBARI-25207 URL: https://issues.apache.org/jira/browse/AMBARI-25207 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk, 2.6.2, 2.7.4 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: trunk, 2.6.2, 2.7.4 When user would try to install files from the repository, which pointing to target location using https protocol, Ambari will fail to generate proper Repository Id for the cached package list of apt manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25207) The Ubuntu repository id for the cached apt package list is generated wrong in case if were used URL with https protocol
[ https://issues.apache.org/jira/browse/AMBARI-25207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25207: - Status: Patch Available (was: In Progress) > The Ubuntu repository id for the cached apt package list is generated wrong > in case if were used URL with https protocol > > > Key: AMBARI-25207 > URL: https://issues.apache.org/jira/browse/AMBARI-25207 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.6.2, 2.7.4 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2, 2.7.4 > > Time Spent: 20m > Remaining Estimate: 0h > > When user would try to install files from the repository, which pointing to > target location using https protocol, Ambari will fail to generate proper > Repository Id for the cached package list of apt manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25216) Updating com.fasterxml.jackson.core:jackson-core version
Dmytro Grinenko created AMBARI-25216: Summary: Updating com.fasterxml.jackson.core:jackson-core version Key: AMBARI-25216 URL: https://issues.apache.org/jira/browse/AMBARI-25216 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.2 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2 Due to security issues with currently used version of lib, used version should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25217) Updating commons-codec:commons-codec version
Dmytro Grinenko created AMBARI-25217: Summary: Updating commons-codec:commons-codec version Key: AMBARI-25217 URL: https://issues.apache.org/jira/browse/AMBARI-25217 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.2 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2 Due to security issues with currently used version of lib, used version should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25218) Updating com.google.guava:guava version
Dmytro Grinenko created AMBARI-25218: Summary: Updating com.google.guava:guava version Key: AMBARI-25218 URL: https://issues.apache.org/jira/browse/AMBARI-25218 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.2 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2 Due to security issues with currently used version of lib, used version should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25217) Updating commons-codec:commons-codec version
[ https://issues.apache.org/jira/browse/AMBARI-25217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25217: - Status: Patch Available (was: In Progress) > Updating commons-codec:commons-codec version > > > Key: AMBARI-25217 > URL: https://issues.apache.org/jira/browse/AMBARI-25217 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25216) Updating com.fasterxml.jackson.core:jackson-core version
[ https://issues.apache.org/jira/browse/AMBARI-25216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25216: - Status: Patch Available (was: In Progress) > Updating com.fasterxml.jackson.core:jackson-core version > > > Key: AMBARI-25216 > URL: https://issues.apache.org/jira/browse/AMBARI-25216 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25218) Updating com.google.guava:guava version
[ https://issues.apache.org/jira/browse/AMBARI-25218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25218: - Fix Version/s: (was: 2.6.2) 2.7.4 > Updating com.google.guava:guava version > --- > > Key: AMBARI-25218 > URL: https://issues.apache.org/jira/browse/AMBARI-25218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.7.4 > > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25217) Updating commons-codec:commons-codec version
[ https://issues.apache.org/jira/browse/AMBARI-25217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25217: - Resolution: Fixed Status: Resolved (was: Patch Available) > Updating commons-codec:commons-codec version > > > Key: AMBARI-25217 > URL: https://issues.apache.org/jira/browse/AMBARI-25217 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25216) Updating com.fasterxml.jackson.core:jackson-core version
[ https://issues.apache.org/jira/browse/AMBARI-25216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25216: - Resolution: Fixed Status: Resolved (was: Patch Available) > Updating com.fasterxml.jackson.core:jackson-core version > > > Key: AMBARI-25216 > URL: https://issues.apache.org/jira/browse/AMBARI-25216 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25203) Upgrade jackson-databind to version 2.9.8 and bouncycastle libraries to 1.61
[ https://issues.apache.org/jira/browse/AMBARI-25203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25203. -- Resolution: Fixed > Upgrade jackson-databind to version 2.9.8 and bouncycastle libraries to 1.61 > > > Key: AMBARI-25203 > URL: https://issues.apache.org/jira/browse/AMBARI-25203 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-metrics, ambari-server, infra >Reporter: Balázs Bence Sári >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2, 2.7.4 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25207) The Ubuntu repository id for the cached apt package list is generated wrong in case if were used URL with https protocol
[ https://issues.apache.org/jira/browse/AMBARI-25207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25207: - Resolution: Fixed Status: Resolved (was: Patch Available) > The Ubuntu repository id for the cached apt package list is generated wrong > in case if were used URL with https protocol > > > Key: AMBARI-25207 > URL: https://issues.apache.org/jira/browse/AMBARI-25207 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.6.2, 2.7.4 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: pull-request-available > Fix For: trunk, 2.6.2, 2.7.4 > > Time Spent: 1h > Remaining Estimate: 0h > > When user would try to install files from the repository, which pointing to > target location using https protocol, Ambari will fail to generate proper > Repository Id for the cached package list of apt manager. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25242) Add module based dependency with custom version for the excluded transitiend modules
Dmytro Grinenko created AMBARI-25242: Summary: Add module based dependency with custom version for the excluded transitiend modules Key: AMBARI-25242 URL: https://issues.apache.org/jira/browse/AMBARI-25242 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.2, 2.7.4 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2, 2.7.4 Add module based dependency with custom version for the excluded transitiend modules -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25246) Add module based dependency with custom version for the excluded transitiend modules
Dmytro Grinenko created AMBARI-25246: Summary: Add module based dependency with custom version for the excluded transitiend modules Key: AMBARI-25246 URL: https://issues.apache.org/jira/browse/AMBARI-25246 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.2, 2.7.4 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.2, 2.7.4 Add module based dependency with custom version for the excluded transitiend modules -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25246) Add module based dependency with custom version for the excluded transitiend modules
[ https://issues.apache.org/jira/browse/AMBARI-25246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25246: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add module based dependency with custom version for the excluded transitiend > modules > > > Key: AMBARI-25246 > URL: https://issues.apache.org/jira/browse/AMBARI-25246 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.2, 2.7.4 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.4 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add module based dependency with custom version for the excluded transitiend > modules -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25246) Add module based dependency with custom version for the excluded transitiend modules
[ https://issues.apache.org/jira/browse/AMBARI-25246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25246: - Status: Patch Available (was: In Progress) > Add module based dependency with custom version for the excluded transitiend > modules > > > Key: AMBARI-25246 > URL: https://issues.apache.org/jira/browse/AMBARI-25246 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.2, 2.7.4 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.4 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Add module based dependency with custom version for the excluded transitiend > modules -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21001) Hive 1.5.0 view does not load in Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-21001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21001: - Fix Version/s: 2.6.2 > Hive 1.5.0 view does not load in Internet Explorer 11 > - > > Key: AMBARI-21001 > URL: https://issues.apache.org/jira/browse/AMBARI-21001 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: trunk, 2.5.1 >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.6.2 > > Attachments: AMBARI-21001.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1. Create a Hive 1.5.0 view instance execute it in IE 11. > 2. A blank page is displayed with the following error message in the web > console: > SCRIPT1002: Syntax error > File: hive.js, Line: 8374, Column: 23 > This is because the ES6 arrow (=>) functions are not supported in IE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25279) Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to latest jackson v2
Dmytro Grinenko created AMBARI-25279: Summary: Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to latest jackson v2 Key: AMBARI-25279 URL: https://issues.apache.org/jira/browse/AMBARI-25279 Project: Ambari Issue Type: Bug Components: ambari-sever Affects Versions: 2.6.0 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.6.0 Move away from jackson v1 to the latest jackson v2 components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25279) Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to latest jackson v2
[ https://issues.apache.org/jira/browse/AMBARI-25279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25279: - Status: Patch Available (was: In Progress) > Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to > latest jackson v2 > -- > > Key: AMBARI-25279 > URL: https://issues.apache.org/jira/browse/AMBARI-25279 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Move away from jackson v1 to the latest jackson v2 components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25279) Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to latest jackson v2
[ https://issues.apache.org/jira/browse/AMBARI-25279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25279: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move Ambari from using jackson-databind-asl and jackson-core-asl (v1) to > latest jackson v2 > -- > > Key: AMBARI-25279 > URL: https://issues.apache.org/jira/browse/AMBARI-25279 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.0 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Move away from jackson v1 to the latest jackson v2 components -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25287) Persistent Cross Site Scripting (XSS) in Ambari
[
https://issues.apache.org/jira/browse/AMBARI-25287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko resolved AMBARI-25287.
--
Resolution: Fixed
> Persistent Cross Site Scripting (XSS) in Ambari
> ---
>
> Key: AMBARI-25287
> URL: https://issues.apache.org/jira/browse/AMBARI-25287
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Below is the HTTP Request and Response issued when a user submits a note
> containing a JavaScript
> after modifying some configuration in "Tez" service.
> HTTP Request:
> PUT /api/v1/clusters/ HTTP/1.1
> Host: xyz601:8080
> Content-Length: 199
> Accept: application/json, text/javascript, /; q=0.01
> Origin: http://xyz601:8080
> X-Requested-With: XMLHttpRequest
> X-Requested-By: X-Requested-By
> User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
> (KHTML,
> like Gecko) Chrome/70.0.3538.102 Safari/537.36
> Content-Type: application/x-www-form-urlencoded; charset=UTF-8
> Referer: http://xyz:8080/
> Accept-Encoding: gzip, deflate
> Accept-Language: en-US,en;q=0.9
> Cookie: AMBARISESSIONID=vfiy4336mxwl1k5ehd6jrz43i
> Connection: close
> {"Clusters":{"desired_service_config_versions":
> {"service_config_version":4,"service_name":"TEZ","service_config_version_note":"Creat
> ed from service config version V4\n"}
> }}
> Remediation Recommendations
> Restrict all input passed to the application to valid, whitelisted content,
> and ensure that all
> response/output sent by the server is HTML/URL/JavaScript encoded, depending
> on the context in
> which the data is used by the application.
> The remediation should not attempt to blacklist content and remove, filter,
> or sanitize it. There are
> too many types of encoding it to get around filters for such content.
> We strongly recommend a positive security policy that specifies what is
> allowed.
> Negative or attack signature based policies are difficult to maintain and are
> likely to be incomplete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
[
https://issues.apache.org/jira/browse/AMBARI-24992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko reopened AMBARI-24992:
--
Assignee: Dmytro Grinenko (was: Sandor Molnar)
> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to
> long certificate
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using command : *ambari-server
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is :
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO
> ambari_configuration (property_name, category_name, property_value) VALUES
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having :
> {code:java}
> CREATE TABLE ambari_configuration (
> category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL,
> property_value VARCHAR(2048),
> CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name,
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is
> not accepting it.
> this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
[
https://issues.apache.org/jira/browse/AMBARI-24992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-24992:
-
Fix Version/s: 2.7.4
> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to
> long certificate
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0, 2.7.4
>
> Time Spent: 3h 10m
> Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using command : *ambari-server
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is :
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO
> ambari_configuration (property_name, category_name, property_value) VALUES
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having :
> {code:java}
> CREATE TABLE ambari_configuration (
> category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL,
> property_value VARCHAR(2048),
> CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name,
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is
> not accepting it.
> this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
[
https://issues.apache.org/jira/browse/AMBARI-24992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-24992:
-
Status: Patch Available (was: In Progress)
> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to
> long certificate
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0, 2.7.4
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using command : *ambari-server
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is :
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO
> ambari_configuration (property_name, category_name, property_value) VALUES
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having :
> {code:java}
> CREATE TABLE ambari_configuration (
> category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL,
> property_value VARCHAR(2048),
> CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name,
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is
> not accepting it.
> this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24992) Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
[
https://issues.apache.org/jira/browse/AMBARI-24992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-24992:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to
> long certificate
> -
>
> Key: AMBARI-24992
> URL: https://issues.apache.org/jira/browse/AMBARI-24992
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Akhil S Naik
>Assignee: Dmytro Grinenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0, 2.7.4
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> I am trying to upgrade to ambari-2.7.0 using command : *ambari-server
> upgrade*
> the upgrade operation is failing on Schema upgrade phase
> The exception is :
> {code:java}
> Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO
> ambari_configuration (property_name, category_name, property_value) VALUES
> ('ambari.sso.provider.certificate','sso-configuration', VALUE>') was aborted: ERROR: value too long for type character varying(2048)
> Call getNextException to see other errors in the batch.
> {code}
> and i see as per
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql#L125
> ambari is having :
> {code:java}
> CREATE TABLE ambari_configuration (
> category_name VARCHAR(100) NOT NULL,
> property_name VARCHAR(100) NOT NULL,
> property_value VARCHAR(2048),
> CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name,
> property_name));
> {code}
> property_value as 2048 but i am having certificate length 2050 and ambari is
> not accepting it.
> this should be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25218) Updating com.google.guava:guava version
[ https://issues.apache.org/jira/browse/AMBARI-25218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25218: - Fix Version/s: 2.6.2 > Updating com.google.guava:guava version > --- > > Key: AMBARI-25218 > URL: https://issues.apache.org/jira/browse/AMBARI-25218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: 2.6.2, 2.7.4 > > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25218) Updating com.google.guava:guava version
[ https://issues.apache.org/jira/browse/AMBARI-25218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25218: - Status: Patch Available (was: In Progress) > Updating com.google.guava:guava version > --- > > Key: AMBARI-25218 > URL: https://issues.apache.org/jira/browse/AMBARI-25218 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2, 2.7.4 > > Time Spent: 10m > Remaining Estimate: 0h > > Due to security issues with currently used version of lib, used version > should be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25332) Kerberos keytab regeneration working slow
Dmytro Grinenko created AMBARI-25332: Summary: Kerberos keytab regeneration working slow Key: AMBARI-25332 URL: https://issues.apache.org/jira/browse/AMBARI-25332 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.7.4 Regeneration keytab on big clusters during upgrade takes a lot of time. Cheking the logs show that Kerberos and hosts with the Ambari are in good shape and have no CPU or Memory spikes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-25166) Modifying the value of node memory in the YARN service will affect the maximum value of container memory, but the modification cannot be saved.
[ https://issues.apache.org/jira/browse/AMBARI-25166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko reassigned AMBARI-25166: Assignee: Dmytro Grinenko > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. > --- > > Key: AMBARI-25166 > URL: https://issues.apache.org/jira/browse/AMBARI-25166 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.3 >Reporter: shanyingying >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-25166.patch, image-2019-02-26-10-10-28-807.png, > image-2019-02-26-10-12-50-621.png > > Time Spent: 20m > Remaining Estimate: 0h > > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (AMBARI-25166) Modifying the value of node memory in the YARN service will affect the maximum value of container memory, but the modification cannot be saved.
[ https://issues.apache.org/jira/browse/AMBARI-25166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25166: - Status: Patch Available (was: In Progress) > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. > --- > > Key: AMBARI-25166 > URL: https://issues.apache.org/jira/browse/AMBARI-25166 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.3 >Reporter: shanyingying >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-25166.patch, image-2019-02-26-10-10-28-807.png, > image-2019-02-26-10-12-50-621.png > > Time Spent: 40m > Remaining Estimate: 0h > > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (AMBARI-25166) Modifying the value of node memory in the YARN service will affect the maximum value of container memory, but the modification cannot be saved.
[ https://issues.apache.org/jira/browse/AMBARI-25166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25166: - Resolution: Fixed Status: Resolved (was: Patch Available) the patch has been committed to fix version branch. > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. > --- > > Key: AMBARI-25166 > URL: https://issues.apache.org/jira/browse/AMBARI-25166 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.3 >Reporter: shanyingying >Assignee: Dmytro Grinenko >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-25166.patch, image-2019-02-26-10-10-28-807.png, > image-2019-02-26-10-12-50-621.png > > Time Spent: 40m > Remaining Estimate: 0h > > Modifying the value of node memory in the YARN service will affect the > maximum value of container memory, but the modification cannot be saved. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (AMBARI-25349) Move Ambari metrics to guava 28.0-jre
Dmytro Grinenko created AMBARI-25349: Summary: Move Ambari metrics to guava 28.0-jre Key: AMBARI-25349 URL: https://issues.apache.org/jira/browse/AMBARI-25349 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.4 Reporter: Dmytro Grinenko Assignee: Dmytro Grinenko Fix For: 2.7.4 The new HDP stack have moved to the new and latest version of guava. Because Ambari Metrics depends on those components, it need to be moved to the same guava version -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (AMBARI-25360) Disable Kerberos failed at hive with CNF exception
Dmytro Grinenko created AMBARI-25360:
Summary: Disable Kerberos failed at hive with CNF exception
Key: AMBARI-25360
URL: https://issues.apache.org/jira/browse/AMBARI-25360
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.4
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Fix For: 2.7.4
ZKMigration tool doesn't bundled with zookeeper-jute, what caused the issue on
de-Kerberization of the cluster
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 143, in
HiveServer().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 352, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
line 124, in disable_security
zkmigrator.set_acls(self._base_node(params.hive_cluster_token_zkstore),
'world:anyone:crdwa')
File
"/usr/lib/ambari-agent/lib/resource_management/core/resources/zkmigrator.py",
line 43, in set_acls
tries=tries)
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 314,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/lib/jvm/java-openjdk/bin/java
-Djava.security.auth.login.config=/usr/hdp/current/hive-server2/conf/zkmigrator_jaas.conf
-jar /var/lib/ambari-agent/tools/zkmigrator.jar -connection-string ctr-e141
-znode /hive -acl world:anyone:crdwa' returned 1.
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/jute/Record
tat org.apache.ambari.tools.zk.ZkConnection.open(ZkConnection.java:43)
tat org.apache.ambari.tools.zk.ZkMigrator.setAcls(ZkMigrator.java:111)
tat org.apache.ambari.tools.zk.ZkMigrator.main(ZkMigrator.java:45)
Caused by: java.lang.ClassNotFoundException: org.apache.jute.Record
tat java.net.URLClassLoader.findClass(URLClassLoader.java:381)
tat java.lang.ClassLoader.loadClass(ClassLoader.java:424)
tat sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
tat java.lang.ClassLoader.loadClass(ClassLoader.java:357)
t... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AMBARI-25360) Disable Kerberos failed at hive with CNF exception
[
https://issues.apache.org/jira/browse/AMBARI-25360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-25360:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Disable Kerberos failed at hive with CNF exception
> --
>
> Key: AMBARI-25360
> URL: https://issues.apache.org/jira/browse/AMBARI-25360
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.4
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ZKMigration tool doesn't bundled with zookeeper-jute, what caused the issue
> on de-Kerberization of the cluster
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 143, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 352, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 124, in disable_security
> zkmigrator.set_acls(self._base_node(params.hive_cluster_token_zkstore),
> 'world:anyone:crdwa')
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/resources/zkmigrator.py",
> line 43, in set_acls
> tries=tries)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/lib/jvm/java-openjdk/bin/java
> -Djava.security.auth.login.config=/usr/hdp/current/hive-server2/conf/zkmigrator_jaas.conf
> -jar /var/lib/ambari-agent/tools/zkmigrator.jar -connection-string ctr-e141
> -znode /hive -acl world:anyone:crdwa' returned 1.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/jute/Record
> tat org.apache.ambari.tools.zk.ZkConnection.open(ZkConnection.java:43)
> tat org.apache.ambari.tools.zk.ZkMigrator.setAcls(ZkMigrator.java:111)
> tat org.apache.ambari.tools.zk.ZkMigrator.main(ZkMigrator.java:45)
> Caused by: java.lang.ClassNotFoundException: org.apache.jute.Record
> tat java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> tat java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> tat sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> tat java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> t... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (AMBARI-25360) Disable Kerberos failed at hive with CNF exception
[
https://issues.apache.org/jira/browse/AMBARI-25360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-25360:
-
Status: Patch Available (was: In Progress)
> Disable Kerberos failed at hive with CNF exception
> --
>
> Key: AMBARI-25360
> URL: https://issues.apache.org/jira/browse/AMBARI-25360
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.4
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ZKMigration tool doesn't bundled with zookeeper-jute, what caused the issue
> on de-Kerberization of the cluster
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 143, in
> HiveServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 352, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/HIVE/package/scripts/hive_server.py",
> line 124, in disable_security
> zkmigrator.set_acls(self._base_node(params.hive_cluster_token_zkstore),
> 'world:anyone:crdwa')
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/resources/zkmigrator.py",
> line 43, in set_acls
> tries=tries)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/lib/jvm/java-openjdk/bin/java
> -Djava.security.auth.login.config=/usr/hdp/current/hive-server2/conf/zkmigrator_jaas.conf
> -jar /var/lib/ambari-agent/tools/zkmigrator.jar -connection-string ctr-e141
> -znode /hive -acl world:anyone:crdwa' returned 1.
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/jute/Record
> tat org.apache.ambari.tools.zk.ZkConnection.open(ZkConnection.java:43)
> tat org.apache.ambari.tools.zk.ZkMigrator.setAcls(ZkMigrator.java:111)
> tat org.apache.ambari.tools.zk.ZkMigrator.main(ZkMigrator.java:45)
> Caused by: java.lang.ClassNotFoundException: org.apache.jute.Record
> tat java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> tat java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> tat sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:338)
> tat java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> t... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (AMBARI-25372) Ambari v2.7.1 Main Compilation error
[
https://issues.apache.org/jira/browse/AMBARI-25372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923887#comment-16923887
]
Dmytro Grinenko commented on AMBARI-25372:
--
I see such error
{code}
bower bootstrap#3.3.7 ENOGIT *git* is not installed or not in the PATH
{code}
Also i found, that was used Java higher than version 1.8
> Ambari v2.7.1 Main Compilation error
>
>
> Key: AMBARI-25372
> URL: https://issues.apache.org/jira/browse/AMBARI-25372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.7.1
> Environment: Debian 9 with all requirements installed.
>Reporter: Cleyson Barros
>Priority: Blocker
> Labels: AmbariAdminView2.7.1.0.0, AmbariMain2.7.1.0.0
>
> root@hgclusterambari:/home/ambari/apache-ambari-2.7.1-src# mvn versions:set
> -DnewVersion=2.7.1.0.0
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/usr/share/maven/lib/guice.jar) to method
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Ambari Main [pom]
> [INFO] Apache Ambari Project POM [pom]
> [INFO] Ambari Web [pom]
> [INFO] Ambari Views [jar]
> [INFO] Ambari Admin View [jar]
> [INFO] ambari-utility [jar]
> [INFO] ambari-metrics [pom]
> [INFO] Ambari Metrics Common [jar]
> [INFO] Ambari Metrics Hadoop Sink [jar]
> [INFO] Ambari Metrics Flume Sink [jar]
> [INFO] Ambari Metrics Kafka Sink [jar]
> [INFO] Ambari Metrics Storm Sink [jar]
> [INFO] Ambari Metrics Storm Sink (Legacy) [jar]
> [INFO] Ambari Metrics Collector [jar]
> [INFO] Ambari Metrics Monitor [pom]
> [INFO] Ambari Metrics Grafana [pom]
> [INFO] Ambari Metrics Host Aggregator [jar]
> [INFO] Ambari Metrics Assembly [pom]
> [INFO] Ambari Service Advisor [jar]
> [INFO] Ambari Server [jar]
> [INFO] Ambari Functional Tests [jar]
> [INFO] Ambari Agent [jar]
> [INFO] ambari-logsearch [pom]
> [INFO] Ambari Logsearch Appender [jar]
> [INFO] Ambari Logsearch Config Api [jar]
> [INFO] Ambari Logsearch Config JSON [jar]
> [INFO] Ambari Logsearch Config Solr [jar]
> [INFO] Ambari Logsearch Config Zookeeper [jar]
> [INFO] Ambari Logsearch Config Local [jar]
> [INFO] Ambari Logsearch Log Feeder Plugin Api [jar]
> [INFO] Ambari Logsearch Log Feeder Container Registry [jar]
> [INFO] Ambari Logsearch Log Feeder [jar]
> [INFO] Ambari Logsearch Web [jar]
> [INFO] Ambari Logsearch Server [jar]
> [INFO] Ambari Logsearch Assembly [jar]
> [INFO] Ambari Logsearch Integration Test [jar]
> [INFO] ambari-infra [pom]
> [INFO] Ambari Infra Solr Client [jar]
> [INFO] Ambari Infra Solr Plugin [jar]
> [INFO] Ambari Infra Manager [jar]
> [INFO] Ambari Infra Assembly [jar]
> [INFO] Ambari Infra Manager Integration Tests [jar]
> [INFO]
> [INFO] --< org.apache.ambari:ambari
> >--
> [INFO] Building Ambari Main 2.7.1.0.0 [1/42]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- versions-maven-plugin:2.7:set (default-cli) @ ambari ---
> [INFO] Searching for local aggregator root...
> [INFO] Local aggregation root: /home/ambari/apache-ambari-2.7.1-src
> [INFO] Processing change of org.apache.ambari:ambari:2.7.1.0.0 -> 2.7.1.0.0
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.7.1.0.0 .. SUCCESS [ 4.538 s]
> [INFO] Apache Ambari Project POM 2.7.1.0.0 SKIPPED
> [INFO] Ambari Web 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari Views 2.7.1.0.0 . SKIPPED
> [INFO] Ambari Admin View 2.7.1.0.0 SKIPPED
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SKIPPED
> [INFO] ambari-metrics 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari Metrics Common 2.7.1.0.0 SKIPPED
> [INFO] Ambari Metrics Hadoop Sink 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari Metrics Flume Sink 2.7.1.0.0 SKIPPED
> [INFO] Ambari Metrics Kafka Sink 2.7.1.0.0 SKIPPED
> [INFO] Ambari Metrics Storm Sink 2.7.1.0.0 SKIPPED
> [INFO] Ambari Metrics Storm Sink (Legacy
[jira] [Updated] (AMBARI-25373) the provate repo is blocking our build
[ https://issues.apache.org/jira/browse/AMBARI-25373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25373: - Fix Version/s: 2.7.4 > the provate repo is blocking our build > -- > > Key: AMBARI-25373 > URL: https://issues.apache.org/jira/browse/AMBARI-25373 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Rurui Ye >Priority: Blocker > Fix For: 2.7.4 > > > nexus-private.hortonworks.com is not accessible from outside, and it's block > the maven resolve process. I spend two days and it's still not able to build. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (AMBARI-25373) the provate repo is blocking our build
[ https://issues.apache.org/jira/browse/AMBARI-25373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-25373. -- Resolution: Duplicate Issue fixed in AMBARI-25348. For the instant fix on 2.7.3, the patch here could be used: https://github.com/apache/ambari/commit/bca762eeb578054dc219120a54984a4ad58a9fbb > the provate repo is blocking our build > -- > > Key: AMBARI-25373 > URL: https://issues.apache.org/jira/browse/AMBARI-25373 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Rurui Ye >Priority: Blocker > Fix For: 2.7.4 > > > nexus-private.hortonworks.com is not accessible from outside, and it's block > the maven resolve process. I spend two days and it's still not able to build. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25348) Change apache-hadoop repository from private nexus to public in AMS
[ https://issues.apache.org/jira/browse/AMBARI-25348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-25348: - Affects Version/s: (was: 2.7.4) 2.7.3 > Change apache-hadoop repository from private nexus to public in AMS > --- > > Key: AMBARI-25348 > URL: https://issues.apache.org/jira/browse/AMBARI-25348 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.3 >Reporter: Ihor Lukianov >Assignee: Ihor Lukianov >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.4 > > Time Spent: 20m > Remaining Estimate: 0h > > Change > [https://github.com/apache/ambari/blob/branch-2.7/ambari-metrics/pom.xml#L77] > to > [https://repo.hortonworks.com/content/groups/public/] -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Comment Edited] (AMBARI-25372) Ambari v2.7.1 Main Compilation error
[
https://issues.apache.org/jira/browse/AMBARI-25372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923887#comment-16923887
]
Dmytro Grinenko edited comment on AMBARI-25372 at 9/6/19 3:09 AM:
--
I see such error
{code}
bower bootstrap#3.3.7 ENOGIT *git* is not installed or not in the PATH
{code}
Also i found, that was used JDK version higher than 1.8
was (Author: dgrinenko):
I see such error
{code}
bower bootstrap#3.3.7 ENOGIT *git* is not installed or not in the PATH
{code}
Also i found, that was used Java higher than version 1.8
> Ambari v2.7.1 Main Compilation error
>
>
> Key: AMBARI-25372
> URL: https://issues.apache.org/jira/browse/AMBARI-25372
> Project: Ambari
> Issue Type: Bug
> Components: ambari-admin
>Affects Versions: 2.7.1
> Environment: Debian 9 with all requirements installed.
>Reporter: Cleyson Barros
>Priority: Blocker
> Labels: AmbariAdminView2.7.1.0.0, AmbariMain2.7.1.0.0
>
> root@hgclusterambari:/home/ambari/apache-ambari-2.7.1-src# mvn versions:set
> -DnewVersion=2.7.1.0.0
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/usr/share/maven/lib/guice.jar) to method
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Ambari Main [pom]
> [INFO] Apache Ambari Project POM [pom]
> [INFO] Ambari Web [pom]
> [INFO] Ambari Views [jar]
> [INFO] Ambari Admin View [jar]
> [INFO] ambari-utility [jar]
> [INFO] ambari-metrics [pom]
> [INFO] Ambari Metrics Common [jar]
> [INFO] Ambari Metrics Hadoop Sink [jar]
> [INFO] Ambari Metrics Flume Sink [jar]
> [INFO] Ambari Metrics Kafka Sink [jar]
> [INFO] Ambari Metrics Storm Sink [jar]
> [INFO] Ambari Metrics Storm Sink (Legacy) [jar]
> [INFO] Ambari Metrics Collector [jar]
> [INFO] Ambari Metrics Monitor [pom]
> [INFO] Ambari Metrics Grafana [pom]
> [INFO] Ambari Metrics Host Aggregator [jar]
> [INFO] Ambari Metrics Assembly [pom]
> [INFO] Ambari Service Advisor [jar]
> [INFO] Ambari Server [jar]
> [INFO] Ambari Functional Tests [jar]
> [INFO] Ambari Agent [jar]
> [INFO] ambari-logsearch [pom]
> [INFO] Ambari Logsearch Appender [jar]
> [INFO] Ambari Logsearch Config Api [jar]
> [INFO] Ambari Logsearch Config JSON [jar]
> [INFO] Ambari Logsearch Config Solr [jar]
> [INFO] Ambari Logsearch Config Zookeeper [jar]
> [INFO] Ambari Logsearch Config Local [jar]
> [INFO] Ambari Logsearch Log Feeder Plugin Api [jar]
> [INFO] Ambari Logsearch Log Feeder Container Registry [jar]
> [INFO] Ambari Logsearch Log Feeder [jar]
> [INFO] Ambari Logsearch Web [jar]
> [INFO] Ambari Logsearch Server [jar]
> [INFO] Ambari Logsearch Assembly [jar]
> [INFO] Ambari Logsearch Integration Test [jar]
> [INFO] ambari-infra [pom]
> [INFO] Ambari Infra Solr Client [jar]
> [INFO] Ambari Infra Solr Plugin [jar]
> [INFO] Ambari Infra Manager [jar]
> [INFO] Ambari Infra Assembly [jar]
> [INFO] Ambari Infra Manager Integration Tests [jar]
> [INFO]
> [INFO] --< org.apache.ambari:ambari
> >--
> [INFO] Building Ambari Main 2.7.1.0.0 [1/42]
> [INFO] [ pom
> ]-
> [INFO]
> [INFO] --- versions-maven-plugin:2.7:set (default-cli) @ ambari ---
> [INFO] Searching for local aggregator root...
> [INFO] Local aggregation root: /home/ambari/apache-ambari-2.7.1-src
> [INFO] Processing change of org.apache.ambari:ambari:2.7.1.0.0 -> 2.7.1.0.0
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Ambari Main 2.7.1.0.0 .. SUCCESS [ 4.538 s]
> [INFO] Apache Ambari Project POM 2.7.1.0.0 SKIPPED
> [INFO] Ambari Web 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari Views 2.7.1.0.0 . SKIPPED
> [INFO] Ambari Admin View 2.7.1.0.0 SKIPPED
> [INFO] ambari-utility 1.0.0.0-SNAPSHOT SKIPPED
> [INFO] ambari-metrics 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari Metrics Common 2.7.1.0.0 SKIPPED
> [INFO] Ambari Metrics Hadoop Sink 2.7.1.0.0 ... SKIPPED
> [INFO] Ambari
