[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[
https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-21122:
-
Description:
*Jave Codes Part*
Now we can use property *ambari.dispatch-property.script.filename* in alert
target to tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts directory. We can also change this
directory in ambari.properties by ambari.dispatch-property.script.directory
property.
Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
{code}
was:
Jave Codes Part
Now we can use property *ambari.dispatch-property.script.filename* in alert
target to tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts. We can also change the directory in
ambari.properties by ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
{code}
> Part One: Specify the script directly in alert target for script-based alert
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
> Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> *Jave Codes Part*
> Now we can use property *ambari.dispatch-property.script.filename* in alert
> target to tell AlertScriptDispatcher to lookup script by filename,default in
> /var/lib/ambari-server/resources/scripts directory. We can also change this
> directory in ambari.properties by ambari.dispatch-property.script.directory
> property.
> Execute a command manually like following to create an alert target:
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[
https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-21122:
-
Description:
Jave Codes Part
Now we can use property *ambari.dispatch-property.script.filename* in alert
target to tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts. We can also change the directory in
ambari.properties by ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
{code}
was:
Jave Codes Part
Now we can use property {code}ambari.dispatch-property.script.filename{code} to
tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts.
We can change the directory in ambari.properties by
ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
{code}
> Part One: Specify the script directly in alert target for script-based alert
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
> Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> Jave Codes Part
> Now we can use property *ambari.dispatch-property.script.filename* in alert
> target to tell AlertScriptDispatcher to lookup script by filename,default in
> /var/lib/ambari-server/resources/scripts. We can also change the directory in
> ambari.properties by ambari.dispatch-property.script.directory property.
> Execute a command manually like following to create an alert target:
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[
https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-21122:
-
Description:
Jave Codes Part
Now we can use property {code}ambari.dispatch-property.script.filename{code} to
tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts.
We can change the directory in ambari.properties by
ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
{code}
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
{code}
was:
Jave Codes Part
Now we can use property ambari.dispatch-property.script.filename
to tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts.
We can change the directory in ambari.properties by
ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
> Part One: Specify the script directly in alert target for script-based alert
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
> Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> Jave Codes Part
> Now we can use property {code}ambari.dispatch-property.script.filename{code}
> to tell AlertScriptDispatcher to lookup script by filename,default in
> /var/lib/ambari-server/resources/scripts.
> We can change the directory in ambari.properties by
> ambari.dispatch-property.script.directory property.
> Execute a command manually like following to create an alert target:
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[
https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yao Lei updated AMBARI-21122:
-
Description:
Jave Codes Part
Now we can use property ambari.dispatch-property.script.filename
to tell AlertScriptDispatcher to lookup script by filename,default in
/var/lib/ambari-server/resources/scripts.
We can change the directory in ambari.properties by
ambari.dispatch-property.script.directory property.
Execute a command manually like following to create an alert target:
POST api/v1/alert_targets
{
"AlertTarget": {
"name": "syslogger",
"description": "Syslog Target",
"notification_type": "ALERT_SCRIPT",
"global": false,
"groups":[1,3]
"alert_states":["WARNING","CRITICAL","UNKNOWN"],
"properties": {
"ambari.dispatch-property.script.filename": "foo.py"
}
}
}
was:Jave Codes Part
> Part One: Specify the script directly in alert target for script-based alert
> dispatchers
> -
>
> Key: AMBARI-21122
> URL: https://issues.apache.org/jira/browse/AMBARI-21122
> Project: Ambari
> Issue Type: Technical task
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: AMBARI-21122.patch
>
>
> Jave Codes Part
> Now we can use property ambari.dispatch-property.script.filename
> to tell AlertScriptDispatcher to lookup script by filename,default in
> /var/lib/ambari-server/resources/scripts.
> We can change the directory in ambari.properties by
> ambari.dispatch-property.script.directory property.
> Execute a command manually like following to create an alert target:
>
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
>"ambari.dispatch-property.script.filename": "foo.py"
> }
> }
> }
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21124) Used Average Memory in Ambari dashborad is different from Used Average got from free command in RHEL 7
Nisanth Simon created AMBARI-21124:
--
Summary: Used Average Memory in Ambari dashborad is different from
Used Average got from free command in RHEL 7
Key: AMBARI-21124
URL: https://issues.apache.org/jira/browse/AMBARI-21124
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.2.0
Environment: RHEL 7
Reporter: Nisanth Simon
Priority: Minor
There is a change in formula for calculating memory_used in "free command" for
RHEL 6 & RHEL 7.
In RHEL 6, memory_used = ( total - free). You can use "man free" on RHEL 6, to
get this formula.
[root@host1 ~]# free
total usedfreeshared
buffers cached
Mem: 246075961799392 22808204 6368
95624 608592
-/+ buffers/cache:1095176 23512420
Swap: 4194300 04194300
[root@host1 ~]#
In the above output, [used = total -free = 24607596 - 22808204 = 1799392]
>From RHEL 7 onwards, there is an extra attribute (MemAvailable) in
>/proc/meminfo. In RHEL 7, the memory_used = (total - free - buffers - cache).
>Refer the link for more details - https://access.redhat.com/solutions/406773
>for formula.
[root@host2 ~]# free
total usedfreeshared
buff/cache available
Mem: 24524432 100264022724020 28232 79777223247360
Swap: 4194300 0 4194300
[root@host2 ~]#
In the above output, [used = total - free - buffers - cache = 24524432 -
22724020 - 797772 = 22724020]
The Ambari Code calculate the memory used using the formula (mem_used =
psutil.virtual_memory().used) . Refer the code,
/usr/lib/python2.6/site-packages/resource_monitoring/core/host_info.py
def get_mem_info(self):
"""
Return memory statistics at current time
"""
mem_stats = psutil.virtual_memory()
swap_stats = psutil.swap_memory()
disk_usage = self.get_combined_disk_usage()
mem_total = self.__host_static_info.get('mem_total')
bytes2kilobytes = lambda x: x / 1024
return {
'mem_total': bytes2kilobytes(mem_total) if mem_total else 0,
'mem_used': bytes2kilobytes(mem_stats.used) if hasattr(mem_stats, 'used')
else 0,
'mem_free': bytes2kilobytes(mem_stats.free) if hasattr(mem_stats, 'free')
else 0,
'mem_shared': bytes2kilobytes(mem_stats.shared) if hasattr(mem_stats,
'shared') else 0,
'mem_buffered': bytes2kilobytes(mem_stats.buffers) if hasattr(mem_stats,
'buffers') else 0,
'mem_cached': bytes2kilobytes(mem_stats.cached) if hasattr(mem_stats,
'cached') else 0,
'swap_free': bytes2kilobytes(swap_stats.free) if hasattr(swap_stats,
'free') else 0,
'disk_free' : disk_usage.get("disk_free"),
# todo: cannot send string
#'part_max_used' : disk_usage.get("max_part_used")[0],
'disk_total' : disk_usage.get("disk_total")
}
pass
The Ambari Code psutil.virtual_memory() calculates the memory_used using the
formula (total -free). In the code,
/usr/lib/python2.6/site-packages/resource_monitoring/psutil/psutil/_pslinux.py
def virtual_memory():
total, free, buffers, shared, _, _ = cext.linux_sysinfo()
cached = active = inactive = None
f = open('/proc/meminfo', 'rb')
CACHED, ACTIVE, INACTIVE = b("Cached:"), b("Active:"), b("Inactive:")
try:
for line in f:
if line.startswith(CACHED):
cached = int(line.split()[1]) * 1024
elif line.startswith(ACTIVE):
active = int(line.split()[1]) * 1024
elif line.startswith(INACTIVE):
inactive = int(line.split()[1]) * 1024
if (cached is not None
and active is not None
and inactive is not None):
break
else:
# we might get here when dealing with exotic Linux flavors, see:
# http://code.google.com/p/psutil/issues/detail?id=313
msg = "'cached', 'active' and 'inactive' memory stats couldn't " \
"be determined and were set to 0"
warnings.warn(msg, RuntimeWarning)
cached = active = inactive = 0
finally:
f.close()
avail = free + buffers + cached
used = total - free
percent = usage_percent((total - avail), total, _round=1)
return svmem(total, avail, percent, used, free,
active, inactive, buffers, cached)
>From the above, we can conclude that the memory_used_average displayed in
>Ambari dashboard will be same with free command average for the cluster for
>RHEL 6.
In RHEL 7, the memory_used_average displayed in Ambari dashboard will be
different from free command average for the cluster.
Ambari adheres to the formula used by free command of RHEL 6 not of RHEL 7.
[jira] [Updated] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-21123: - Attachment: script_alert_notification_2.png script_alert_notification_1.png > Part Two: Specify the script directly in alert target for script-based alert > dispatchers > > > Key: AMBARI-21123 > URL: https://issues.apache.org/jira/browse/AMBARI-21123 > Project: Ambari > Issue Type: Technical task > Components: alerts, ambari-web >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: script_alert_notification_1.png, > script_alert_notification_2.png > > > Web Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Attachment: (was: script_alert_notification_2.png) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Attachment: (was: script_alert_notification_1.png) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Status: Open (was: Patch Available) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Attachment: (was: AMBARI-20739.patch) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-21122: - Attachment: AMBARI-21122.patch > Part One: Specify the script directly in alert target for script-based alert > dispatchers > - > > Key: AMBARI-21122 > URL: https://issues.apache.org/jira/browse/AMBARI-21122 > Project: Ambari > Issue Type: Technical task >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-21122.patch > > > Jave Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei reassigned AMBARI-21123: Assignee: Yao Lei > Part Two: Specify the script directly in alert target for script-based alert > dispatchers > > > Key: AMBARI-21123 > URL: https://issues.apache.org/jira/browse/AMBARI-21123 > Project: Ambari > Issue Type: Technical task > Components: alerts, ambari-web >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > > Web Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei reassigned AMBARI-21122: Assignee: Yao Lei > Part One: Specify the script directly in alert target for script-based alert > dispatchers > - > > Key: AMBARI-21122 > URL: https://issues.apache.org/jira/browse/AMBARI-21122 > Project: Ambari > Issue Type: Technical task >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > > Jave Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers
Yao Lei created AMBARI-21123: Summary: Part Two: Specify the script directly in alert target for script-based alert dispatchers Key: AMBARI-21123 URL: https://issues.apache.org/jira/browse/AMBARI-21123 Project: Ambari Issue Type: Technical task Reporter: Yao Lei Fix For: 3.0.0 Web Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-21122: - Issue Type: Technical task (was: Bug) Parent: AMBARI-20739 > Part One: Specify the script directly in alert target for script-based alert > dispatchers > - > > Key: AMBARI-21122 > URL: https://issues.apache.org/jira/browse/AMBARI-21122 > Project: Ambari > Issue Type: Technical task >Reporter: Yao Lei > Fix For: 3.0.0 > > > Jave Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21122) Part One: Specify the script directly in alert target for script-based alert dispatchers
Yao Lei created AMBARI-21122: Summary: Part One: Specify the script directly in alert target for script-based alert dispatchers Key: AMBARI-21122 URL: https://issues.apache.org/jira/browse/AMBARI-21122 Project: Ambari Issue Type: Bug Reporter: Yao Lei Fix For: 3.0.0 Jave Codes Part -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions
[
https://issues.apache.org/jira/browse/AMBARI-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024104#comment-16024104
]
Hadoop QA commented on AMBARI-21120:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12869782/AMBARI-21120.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/11612//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11612//console
This message is automatically generated.
> Roles below Cluster Administrator should not be allowed to edit repositories
> and install stack versions
> ---
>
> Key: AMBARI-21120
> URL: https://issues.apache.org/jira/browse/AMBARI-21120
> Project: Ambari
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Sangeeta Ravindran
>Assignee: Sangeeta Ravindran
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-21120.patch
>
>
> Login as a user with a role below Cluster Administrator. For e.g. Service
> Admnistrator.
> Click on Stack and Versions.
> 1. Try to edit a stack version that is not yet installed on the cluster.
> Click on Save. The UI reloads and returns to Services Dashboard.
> On the browser console, you can see a HTTP 403 because the user does not have
> the privilege to edit stack versions.
> 2. Click on Install. When you click on on the popup confirming that the
> packages will be installed on all hosts, you get a popup with an error
> "Packages could not be installed. You do not have permissions to access this
> resource".
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions
[ https://issues.apache.org/jira/browse/AMBARI-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-21120: Fix Version/s: trunk Status: Patch Available (was: In Progress) > Roles below Cluster Administrator should not be allowed to edit repositories > and install stack versions > --- > > Key: AMBARI-21120 > URL: https://issues.apache.org/jira/browse/AMBARI-21120 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21120.patch > > > Login as a user with a role below Cluster Administrator. For e.g. Service > Admnistrator. > Click on Stack and Versions. > 1. Try to edit a stack version that is not yet installed on the cluster. > Click on Save. The UI reloads and returns to Services Dashboard. > On the browser console, you can see a HTTP 403 because the user does not have > the privilege to edit stack versions. > 2. Click on Install. When you click on on the popup confirming that the > packages will be installed on all hosts, you get a popup with an error > "Packages could not be installed. You do not have permissions to access this > resource". > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions
[ https://issues.apache.org/jira/browse/AMBARI-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeeta Ravindran updated AMBARI-21120: Attachment: AMBARI-21120.patch > Roles below Cluster Administrator should not be allowed to edit repositories > and install stack versions > --- > > Key: AMBARI-21120 > URL: https://issues.apache.org/jira/browse/AMBARI-21120 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: Sangeeta Ravindran >Assignee: Sangeeta Ravindran >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21120.patch > > > Login as a user with a role below Cluster Administrator. For e.g. Service > Admnistrator. > Click on Stack and Versions. > 1. Try to edit a stack version that is not yet installed on the cluster. > Click on Save. The UI reloads and returns to Services Dashboard. > On the browser console, you can see a HTTP 403 because the user does not have > the privilege to edit stack versions. > 2. Click on Install. When you click on on the popup confirming that the > packages will be installed on all hosts, you get a popup with an error > "Packages could not be installed. You do not have permissions to access this > resource". > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated AMBARI-21121: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024046#comment-16024046 ] Mahadev konar commented on AMBARI-21121: +1 for the patch. > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21114) Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
[
https://issues.apache.org/jira/browse/AMBARI-21114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21114:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
> ---
>
> Key: AMBARI-21114
> URL: https://issues.apache.org/jira/browse/AMBARI-21114
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-21114.patch
>
>
> The following unit tests are failing in the patch upgrade feature branch:
> {noformat}
> Failed tests:
>
> StackUpgradeConfigurationMergeTest.testMergedConfigurationsDoNotAddExplicitelyRemovedProperties:261
> Nothing captured yet
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipAll:430
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipManualVerification:383
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testUpdateSkipFailures:1328->testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testUpgradeHistory:1622 Implement me!
> UpgradeActionTest.testExpressUpgradeUpdateDesiredStackAction:455 null
> UpgradeActionTest.testFinalizeDowngradeAcrossStacks:742
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
>
> UpgradeActionTest.testFinalizeDowngradeWhenDidNotFinalizePreviousUpgrade:535
> expected:<[FAIL]ED> but was:<[COMPLET]ED>
> UpgradeActionTest.testFinalizeUpgradeAcrossStacks:665
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeActionTest.testFinalizeUpgradeWithClusterStateInconsistencies:832
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeHelperTest.testCompleteUpgradeOrchestration:377 expected:<[Service
> Check Zk]> but was:<[Completing ZooKeeper1 Server2 on 192.168.64.1]>
> UpgradeHelperTest.testPartialUpgradeOrchestration:312 expected:<3> but
> was:<0>
> UpgradeHelperTest.testServiceCheckUpgradeStages:1073 expected:<6> but
> was:<7>
> Tests in error:
> UpgradeResourceProviderTest.testCreatePartialDowngrade:649 » NoSuchElement
> UpgradeResourceProviderTest.testMergeConfigurations:1201 » IllegalState
> missin...
>
> ComponentVersionCheckActionTest.testMixedComponentVersions:341->createNewRepoVersion:273
> » Ambari
>
> UpgradeActionTest.testFinalizeUpgrade:548->createUpgradeClusterTargetRepo:303
> » Ambari
>
> UpgradeActionTest.testFinalizeWithHostsAlreadyCurrent:589->createUpgradeClusterTargetRepo:303
> » Ambari
> UpgradeHelperTest.testHostGroupingOrchestration:2133 » IllegalState missing
> be...
> UpgradeHelperTest.testOrchestrationNoServerSideOnDowngrade:1851 »
> IllegalState
> UpgradeHelperTest.testResolverBadJmx:1713 » IllegalState missing behavior
> defi...
> UpgradeHelperTest.testResolverCaseInsensitive:1644 » IllegalState missing
> beha...
> UpgradeHelperTest.testResolverWithFailedUpgrade:1569 » IllegalState missing
> be...
> UpgradeHelperTest.testUpgradeOrchestrationWithHostsInMM:465 » IllegalState
> mis...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21114) Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
[
https://issues.apache.org/jira/browse/AMBARI-21114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21114:
-
Attachment: AMBARI-21114.patch
> Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
> ---
>
> Key: AMBARI-21114
> URL: https://issues.apache.org/jira/browse/AMBARI-21114
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-21114.patch
>
>
> The following unit tests are failing in the patch upgrade feature branch:
> {noformat}
> Failed tests:
>
> StackUpgradeConfigurationMergeTest.testMergedConfigurationsDoNotAddExplicitelyRemovedProperties:261
> Nothing captured yet
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipAll:430
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipManualVerification:383
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testUpdateSkipFailures:1328->testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testUpgradeHistory:1622 Implement me!
> UpgradeActionTest.testExpressUpgradeUpdateDesiredStackAction:455 null
> UpgradeActionTest.testFinalizeDowngradeAcrossStacks:742
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
>
> UpgradeActionTest.testFinalizeDowngradeWhenDidNotFinalizePreviousUpgrade:535
> expected:<[FAIL]ED> but was:<[COMPLET]ED>
> UpgradeActionTest.testFinalizeUpgradeAcrossStacks:665
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeActionTest.testFinalizeUpgradeWithClusterStateInconsistencies:832
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeHelperTest.testCompleteUpgradeOrchestration:377 expected:<[Service
> Check Zk]> but was:<[Completing ZooKeeper1 Server2 on 192.168.64.1]>
> UpgradeHelperTest.testPartialUpgradeOrchestration:312 expected:<3> but
> was:<0>
> UpgradeHelperTest.testServiceCheckUpgradeStages:1073 expected:<6> but
> was:<7>
> Tests in error:
> UpgradeResourceProviderTest.testCreatePartialDowngrade:649 » NoSuchElement
> UpgradeResourceProviderTest.testMergeConfigurations:1201 » IllegalState
> missin...
>
> ComponentVersionCheckActionTest.testMixedComponentVersions:341->createNewRepoVersion:273
> » Ambari
>
> UpgradeActionTest.testFinalizeUpgrade:548->createUpgradeClusterTargetRepo:303
> » Ambari
>
> UpgradeActionTest.testFinalizeWithHostsAlreadyCurrent:589->createUpgradeClusterTargetRepo:303
> » Ambari
> UpgradeHelperTest.testHostGroupingOrchestration:2133 » IllegalState missing
> be...
> UpgradeHelperTest.testOrchestrationNoServerSideOnDowngrade:1851 »
> IllegalState
> UpgradeHelperTest.testResolverBadJmx:1713 » IllegalState missing behavior
> defi...
> UpgradeHelperTest.testResolverCaseInsensitive:1644 » IllegalState missing
> beha...
> UpgradeHelperTest.testResolverWithFailedUpgrade:1569 » IllegalState missing
> be...
> UpgradeHelperTest.testUpgradeOrchestrationWithHostsInMM:465 » IllegalState
> mis...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21114) Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
[
https://issues.apache.org/jira/browse/AMBARI-21114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21114:
-
Status: Patch Available (was: Open)
> Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
> ---
>
> Key: AMBARI-21114
> URL: https://issues.apache.org/jira/browse/AMBARI-21114
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
> Fix For: trunk
>
> Attachments: AMBARI-21114.patch
>
>
> The following unit tests are failing in the patch upgrade feature branch:
> {noformat}
> Failed tests:
>
> StackUpgradeConfigurationMergeTest.testMergedConfigurationsDoNotAddExplicitelyRemovedProperties:261
> Nothing captured yet
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipAll:430
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipManualVerification:383
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
>
> UpgradeResourceProviderTest.testUpdateSkipFailures:1328->testCreateResourcesWithAutoSkipFailures:333
> expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
> Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
> UpgradeResourceProviderTest.testUpgradeHistory:1622 Implement me!
> UpgradeActionTest.testExpressUpgradeUpdateDesiredStackAction:455 null
> UpgradeActionTest.testFinalizeDowngradeAcrossStacks:742
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
>
> UpgradeActionTest.testFinalizeDowngradeWhenDidNotFinalizePreviousUpgrade:535
> expected:<[FAIL]ED> but was:<[COMPLET]ED>
> UpgradeActionTest.testFinalizeUpgradeAcrossStacks:665
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeActionTest.testFinalizeUpgradeWithClusterStateInconsistencies:832
> expected:<[COMPLET]ED> but was:<[FAIL]ED>
> UpgradeHelperTest.testCompleteUpgradeOrchestration:377 expected:<[Service
> Check Zk]> but was:<[Completing ZooKeeper1 Server2 on 192.168.64.1]>
> UpgradeHelperTest.testPartialUpgradeOrchestration:312 expected:<3> but
> was:<0>
> UpgradeHelperTest.testServiceCheckUpgradeStages:1073 expected:<6> but
> was:<7>
> Tests in error:
> UpgradeResourceProviderTest.testCreatePartialDowngrade:649 » NoSuchElement
> UpgradeResourceProviderTest.testMergeConfigurations:1201 » IllegalState
> missin...
>
> ComponentVersionCheckActionTest.testMixedComponentVersions:341->createNewRepoVersion:273
> » Ambari
>
> UpgradeActionTest.testFinalizeUpgrade:548->createUpgradeClusterTargetRepo:303
> » Ambari
>
> UpgradeActionTest.testFinalizeWithHostsAlreadyCurrent:589->createUpgradeClusterTargetRepo:303
> » Ambari
> UpgradeHelperTest.testHostGroupingOrchestration:2133 » IllegalState missing
> be...
> UpgradeHelperTest.testOrchestrationNoServerSideOnDowngrade:1851 »
> IllegalState
> UpgradeHelperTest.testResolverBadJmx:1713 » IllegalState missing behavior
> defi...
> UpgradeHelperTest.testResolverCaseInsensitive:1644 » IllegalState missing
> beha...
> UpgradeHelperTest.testResolverWithFailedUpgrade:1569 » IllegalState missing
> be...
> UpgradeHelperTest.testUpgradeOrchestrationWithHostsInMM:465 » IllegalState
> mis...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21121: Status: Patch Available (was: Open) > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
[ https://issues.apache.org/jira/browse/AMBARI-21121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani updated AMBARI-21121: Attachment: AMBARI-21121.patch > Missing storm-site.xml in HDP-2.6 stack > --- > > Key: AMBARI-21121 > URL: https://issues.apache.org/jira/browse/AMBARI-21121 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21121.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21121) Missing storm-site.xml in HDP-2.6 stack
Sriharsha Chintalapani created AMBARI-21121: --- Summary: Missing storm-site.xml in HDP-2.6 stack Key: AMBARI-21121 URL: https://issues.apache.org/jira/browse/AMBARI-21121 Project: Ambari Issue Type: Bug Reporter: Sriharsha Chintalapani Assignee: Sriharsha Chintalapani Priority: Blocker Fix For: 2.5.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
[ https://issues.apache.org/jira/browse/AMBARI-21090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16024005#comment-16024005 ] Hudson commented on AMBARI-21090: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7533 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7533/]) AMBARI-21090 Add Log Feeder input config to HDP 3.0 hooks too (mgergely) (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2f73315356551224b69bf7e9d1c9c914107ac6df]) * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/shared_initialization.py * (edit) ambari-server/src/main/resources/stacks/HDP/3.0/hooks/after-INSTALL/scripts/params.py > Add Log Feeder input config to HDP 3.0 hooks too > > > Key: AMBARI-21090 > URL: https://issues.apache.org/jira/browse/AMBARI-21090 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21090.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Status: Open (was: Patch Available) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-20739.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Status: Patch Available (was: Open) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-20739.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21119) Log Search REST API validate input configurations and log level filters
[ https://issues.apache.org/jira/browse/AMBARI-21119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21119: Status: Patch Available (was: In Progress) > Log Search REST API validate input configurations and log level filters > --- > > Key: AMBARI-21119 > URL: https://issues.apache.org/jira/browse/AMBARI-21119 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21119.patch > > > Log Search server REST API should validate that the received input > configuration / log level filter is in the valid format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21119) Log Search REST API validate input configurations and log level filters
[ https://issues.apache.org/jira/browse/AMBARI-21119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21119: Attachment: AMBARI-21119.patch > Log Search REST API validate input configurations and log level filters > --- > > Key: AMBARI-21119 > URL: https://issues.apache.org/jira/browse/AMBARI-21119 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21119.patch > > > Log Search server REST API should validate that the received input > configuration / log level filter is in the valid format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
[ https://issues.apache.org/jira/browse/AMBARI-21090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21090: Resolution: Fixed Status: Resolved (was: Patch Available) > Add Log Feeder input config to HDP 3.0 hooks too > > > Key: AMBARI-21090 > URL: https://issues.apache.org/jira/browse/AMBARI-21090 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21090.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
[
https://issues.apache.org/jira/browse/AMBARI-21090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023965#comment-16023965
]
Miklos Gergely commented on AMBARI-21090:
-
committed to trunk:
{code:java}
commit 2f73315356551224b69bf7e9d1c9c914107ac6df
Author: Miklos Gergely
Date: Thu May 25 02:52:29 2017 +0200
AMBARI-21090 Add Log Feeder input config to HDP 3.0 hooks too (mgergely)
Change-Id: I83da4d1987e224cf54bd352aa1731d4cf5b26174
{code}
> Add Log Feeder input config to HDP 3.0 hooks too
>
>
> Key: AMBARI-21090
> URL: https://issues.apache.org/jira/browse/AMBARI-21090
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21090.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21120) Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions
Sangeeta Ravindran created AMBARI-21120: --- Summary: Roles below Cluster Administrator should not be allowed to edit repositories and install stack versions Key: AMBARI-21120 URL: https://issues.apache.org/jira/browse/AMBARI-21120 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: Sangeeta Ravindran Assignee: Sangeeta Ravindran Priority: Minor Login as a user with a role below Cluster Administrator. For e.g. Service Admnistrator. Click on Stack and Versions. 1. Try to edit a stack version that is not yet installed on the cluster. Click on Save. The UI reloads and returns to Services Dashboard. On the browser console, you can see a HTTP 403 because the user does not have the privilege to edit stack versions. 2. Click on Install. When you click on on the popup confirming that the packages will be installed on all hosts, you get a popup with an error "Packages could not be installed. You do not have permissions to access this resource". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21119) Log Search REST API validate input configurations and log level filters
Miklos Gergely created AMBARI-21119: --- Summary: Log Search REST API validate input configurations and log level filters Key: AMBARI-21119 URL: https://issues.apache.org/jira/browse/AMBARI-21119 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 3.0.0 Log Search server REST API should validate that the received input configuration / log level filter is in the valid format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs
[
https://issues.apache.org/jira/browse/AMBARI-21118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21118:
-
Attachment: AMBARI-21118.2.5-maint.patch
> HDP + HDF cluster cannot save configs for Storm when Streamline is installed
> due to missing configs
> ---
>
> Key: AMBARI-21118
> URL: https://issues.apache.org/jira/browse/AMBARI-21118
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21118.2.5-maint.patch
>
>
> STR:
> * Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF
> MPack)
> * Attempt to change configs for Storm
> Ambari: 2.5.1.0-146
> HDF: 3.0.0.0-358
> HDP: 2.6.1.0-110
> This is happening because Storm does not have Streamline as a dependent
> service, so the UI does not pass the Streamline configs to the
> recommendations endpoint when calling Stack Advisor for Storm.
> {code}
> '), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'),
> ('yarn.scheduler.capacity.root.capacity', '100'),
> ('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'),
> ('yarn.scheduler.capacity.maximum-applications', '1'),
> ('yarn.scheduler.capacity.root.de
> fault.user-limit-factor', '1'),
> ('yarn.scheduler.capacity.node-locality-delay', '40'),
> ('yarn.scheduler.capacity.root.default.acl_submit_applications', 'yarn'),
> ('yarn.scheduler.capacity.root.default.state', 'RUNNING'),
> ('yarn.scheduler.capacity.root.default.capacity', '1
> 00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'),
> ('yarn.scheduler.capacity.root.default.maximum-capacity', '100'),
> ('yarn.scheduler.capacity.root.queues', 'default'),
> ('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''),
> ('yarn.schedu
> ler.capacity.root.default.acl_administer_jobs', 'yarn'),
> ('yarn.scheduler.capacity.resource-calculator',
> 'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
> Error occured in stack advisor.
> Error details: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 INFO [ambari-client-thread-31]
> StackAdvisorRunner:71 - advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 775, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
> line 68, in recommendSTORMConfigurations
> _streamline_principal_name = streamline_env['streamline_principal_name']
> if 'streamline_principal_name' in streamline_env else None
> TypeError: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 WARN [ambari-client-thread-31]
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: argument of type 'NoneType' is
> not iterable
> StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
>
[jira] [Commented] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs
[
https://issues.apache.org/jira/browse/AMBARI-21118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023934#comment-16023934
]
Sriharsha Chintalapani commented on AMBARI-21118:
-
+1
> HDP + HDF cluster cannot save configs for Storm when Streamline is installed
> due to missing configs
> ---
>
> Key: AMBARI-21118
> URL: https://issues.apache.org/jira/browse/AMBARI-21118
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: 2.5.2
>
> Attachments: AMBARI-21118.2.5-maint.patch
>
>
> STR:
> * Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF
> MPack)
> * Attempt to change configs for Storm
> Ambari: 2.5.1.0-146
> HDF: 3.0.0.0-358
> HDP: 2.6.1.0-110
> This is happening because Storm does not have Streamline as a dependent
> service, so the UI does not pass the Streamline configs to the
> recommendations endpoint when calling Stack Advisor for Storm.
> {code}
> '), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'),
> ('yarn.scheduler.capacity.root.capacity', '100'),
> ('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'),
> ('yarn.scheduler.capacity.maximum-applications', '1'),
> ('yarn.scheduler.capacity.root.de
> fault.user-limit-factor', '1'),
> ('yarn.scheduler.capacity.node-locality-delay', '40'),
> ('yarn.scheduler.capacity.root.default.acl_submit_applications', 'yarn'),
> ('yarn.scheduler.capacity.root.default.state', 'RUNNING'),
> ('yarn.scheduler.capacity.root.default.capacity', '1
> 00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'),
> ('yarn.scheduler.capacity.root.default.maximum-capacity', '100'),
> ('yarn.scheduler.capacity.root.queues', 'default'),
> ('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''),
> ('yarn.schedu
> ler.capacity.root.default.acl_administer_jobs', 'yarn'),
> ('yarn.scheduler.capacity.resource-calculator',
> 'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
> Error occured in stack advisor.
> Error details: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 INFO [ambari-client-thread-31]
> StackAdvisorRunner:71 - advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116,
> in main
> result = stackAdvisor.recommendConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 775, in recommendConfigurations
> calculation(configurations, clusterSummary, services, hosts)
> File
> "/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
> line 68, in recommendSTORMConfigurations
> _streamline_principal_name = streamline_env['streamline_principal_name']
> if 'streamline_principal_name' in streamline_env else None
> TypeError: argument of type 'NoneType' is not iterable
> 24 May 2017 19:43:17,686 WARN [ambari-client-thread-31]
> AbstractResourceProvider:97 - Error occured during recommendation
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Stack Advisor reported an error: TypeError: argument of type 'NoneType' is
> not iterable
> StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
> StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
>
[jira] [Commented] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023923#comment-16023923 ] Sangeeta Ravindran commented on AMBARI-21095: - Failure is inrelated to the commit. Test Result (1 failure / +1) org.apache.ambari.server.state.cluster.ClusterDeadlockTest.testDeadlockWhileRestartingComponents > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21118) HDP + HDF cluster cannot save configs for Storm when Streamline is installed due to missing configs
Alejandro Fernandez created AMBARI-21118:
Summary: HDP + HDF cluster cannot save configs for Storm when
Streamline is installed due to missing configs
Key: AMBARI-21118
URL: https://issues.apache.org/jira/browse/AMBARI-21118
Project: Ambari
Issue Type: Bug
Components: stacks
Affects Versions: 2.5.1
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: 2.5.2
STR:
* Install Ambari 2.5.1 with HDP 2.6.1 plus Storm and Streamline (from HDF MPack)
* Attempt to change configs for Storm
Ambari: 2.5.1.0-146
HDF: 3.0.0.0-358
HDP: 2.6.1.0-110
This is happening because Storm does not have Streamline as a dependent
service, so the UI does not pass the Streamline configs to the recommendations
endpoint when calling Stack Advisor for Storm.
{code}
'), ('yarn.scheduler.capacity.root.accessible-node-labels', '*'),
('yarn.scheduler.capacity.root.capacity', '100'),
('yarn.scheduler.capacity.maximum-am-resource-percent', '0.2'),
('yarn.scheduler.capacity.maximum-applications', '1'),
('yarn.scheduler.capacity.root.de
fault.user-limit-factor', '1'), ('yarn.scheduler.capacity.node-locality-delay',
'40'), ('yarn.scheduler.capacity.root.default.acl_submit_applications',
'yarn'), ('yarn.scheduler.capacity.root.default.state', 'RUNNING'),
('yarn.scheduler.capacity.root.default.capacity', '1
00'), ('yarn.scheduler.capacity.root.acl_administer_queue', 'yarn'),
('yarn.scheduler.capacity.root.default.maximum-capacity', '100'),
('yarn.scheduler.capacity.root.queues', 'default'),
('yarn.scheduler.capacity.root.acl_administer_jobs', 'yarn'), ('', ''),
('yarn.schedu
ler.capacity.root.default.acl_administer_jobs', 'yarn'),
('yarn.scheduler.capacity.resource-calculator',
'org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator')]
Error occured in stack advisor.
Error details: argument of type 'NoneType' is not iterable
24 May 2017 19:43:17,686 INFO [ambari-client-thread-31] StackAdvisorRunner:71
- advisor script stderr: Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 166,
in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 116,
in main
result = stackAdvisor.recommendConfigurations(services, hosts)
File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
line 775, in recommendConfigurations
calculation(configurations, clusterSummary, services, hosts)
File
"/var/lib/ambari-server/resources/scripts/./../stacks/HDP/2.6/services/stack_advisor.py",
line 68, in recommendSTORMConfigurations
_streamline_principal_name = streamline_env['streamline_principal_name'] if
'streamline_principal_name' in streamline_env else None
TypeError: argument of type 'NoneType' is not iterable
24 May 2017 19:43:17,686 WARN [ambari-client-thread-31]
AbstractResourceProvider:97 - Error occured during recommendation
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: Stack
Advisor reported an error: TypeError: argument of type 'NoneType' is not
iterable
StdOut file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.out
StdErr file: /var/run/ambari-server/stack-recommendations/30/stackadvisor.err
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:96)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:295)
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:113)
at
org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:37)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:73)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023913#comment-16023913 ] Hudson commented on AMBARI-21095: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7532 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7532/]) AMBARI-21095 - Enable opening views in a new tab (Anita Jebaraj via (sangeetar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=42be8ce798172757b8b0967b309baf73fe0a5212]) * (edit) ambari-web/test/controllers/main/views_controller_test.js * (edit) ambari-web/app/models/view_instance.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/ambariViews/edit.html * (edit) ambari-web/test/models/view_instance_test.js * (edit) ambari-web/app/controllers/main/views_controller.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/index.html > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21117) Existing hosts state didn't save after host was added
[
https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023896#comment-16023896
]
Hadoop QA commented on AMBARI-21117:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12869740/AMBARI-21117.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11611//console
This message is automatically generated.
> Existing hosts state didn't save after host was added
> -
>
> Key: AMBARI-21117
> URL: https://issues.apache.org/jira/browse/AMBARI-21117
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.1
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.2
>
> Attachments: AMBARI-21117.patch
>
>
> Existing hosts state didn't save after host was added. In next test add host
> wizard stay open.
> When we connect to cluster - automatically redirect on add host wizard.
> (attached screenshot)
> First step validation passed and host registered successfully.
> On Review Page, when we clicked Deploy we had popup with error that this host
> already part of cluster.
> If we cluster wizard and try it again - validation on first step not passed
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023850#comment-16023850 ] Sangeeta Ravindran commented on AMBARI-21095: - Pushed to trunk as commit 42be8ce798172757b8b0967b309baf73fe0a5212 > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21117) Existing hosts state didn't save after host was added
[ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023845#comment-16023845 ] Denys Buzhor commented on AMBARI-21117: --- +1 for patch > Existing hosts state didn't save after host was added > - > > Key: AMBARI-21117 > URL: https://issues.apache.org/jira/browse/AMBARI-21117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.2 > > Attachments: AMBARI-21117.patch > > > Existing hosts state didn't save after host was added. In next test add host > wizard stay open. > When we connect to cluster - automatically redirect on add host wizard. > (attached screenshot) > First step validation passed and host registered successfully. > On Review Page, when we clicked Deploy we had popup with error that this host > already part of cluster. > If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21079) Add ability to sink Raw metrics to external system via Http
[ https://issues.apache.org/jira/browse/AMBARI-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21079: - Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-3.0-ams > Add ability to sink Raw metrics to external system via Http > --- > > Key: AMBARI-21079 > URL: https://issues.apache.org/jira/browse/AMBARI-21079 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 3.0.0, branch-3.0-ams > > Attachments: AMBARI-21079.patch > > > - Define interface to add MetricsSources to AMS > - Define sink interfaces > - Add caching layer to allow flush interval to be different from sink > interval. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21079) Add ability to sink Raw metrics to external system via Http
[ https://issues.apache.org/jira/browse/AMBARI-21079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-21079: - Fix Version/s: branch-3.0-ams > Add ability to sink Raw metrics to external system via Http > --- > > Key: AMBARI-21079 > URL: https://issues.apache.org/jira/browse/AMBARI-21079 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle > Fix For: 3.0.0, branch-3.0-ams > > Attachments: AMBARI-21079.patch > > > - Define interface to add MetricsSources to AMS > - Define sink interfaces > - Add caching layer to allow flush interval to be different from sink > interval. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup
[ https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21097: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Edit notifications options are always grey but can click and open a popup > - > > Key: AMBARI-21097 > URL: https://issues.apache.org/jira/browse/AMBARI-21097 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 2.5.2 > > Attachments: AMBARI-21097.patch, notification.png > > > STR: > 1.Open Alerts / Actions / Manage Alert Notifications > 2.Create an alert notification named test > 3.Select the created notification and click gear icon, you will find > Edit/Duplicate items are always grey but you can click and open a popup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21045) Enable Storm's AutoTGT configs in secure mode
[ https://issues.apache.org/jira/browse/AMBARI-21045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-21045: --- Fix Version/s: (was: 2.5.1) 2.5.2 > Enable Storm's AutoTGT configs in secure mode > - > > Key: AMBARI-21045 > URL: https://issues.apache.org/jira/browse/AMBARI-21045 > Project: Ambari > Issue Type: Bug >Reporter: Sriharsha Chintalapani >Assignee: Sriharsha Chintalapani >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21045.branch-2.5.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21097) Edit notifications options are always grey but can click and open a popup
[ https://issues.apache.org/jira/browse/AMBARI-21097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023834#comment-16023834 ] Aravindan Vijayan commented on AMBARI-21097: Moving this out since 2.5.2 RC is out. > Edit notifications options are always grey but can click and open a popup > - > > Key: AMBARI-21097 > URL: https://issues.apache.org/jira/browse/AMBARI-21097 > Project: Ambari > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 2.5.2 > > Attachments: AMBARI-21097.patch, notification.png > > > STR: > 1.Open Alerts / Actions / Manage Alert Notifications > 2.Create an alert notification named test > 3.Select the created notification and click gear icon, you will find > Edit/Duplicate items are always grey but you can click and open a popup. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21053) Reverting Beacon stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-21053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21053: - Priority: Major (was: Blocker) > Reverting Beacon stack advisor recommendation > - > > Key: AMBARI-21053 > URL: https://issues.apache.org/jira/browse/AMBARI-21053 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.5.2 > > Attachments: AMBARI-21053.patch, AMBARI-21053-trunk.patch > > > Beacon is an add-on-service installed via management pack. For services > installed via mpack need to use service advisor recommendation, which should > be provided in mpack. > Because of the stack_advisor [code > available|https://github.com/apache/ambari/commit/777eacd2be2c9477405ae53bd5faaa8b53b88aec], > service_advisor.py code logic from mpack is not getting executed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21053) Reverting Beacon stack advisor recommendation
[ https://issues.apache.org/jira/browse/AMBARI-21053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21053: - Fix Version/s: (was: 2.5.1) 2.5.2 > Reverting Beacon stack advisor recommendation > - > > Key: AMBARI-21053 > URL: https://issues.apache.org/jira/browse/AMBARI-21053 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar > Fix For: 2.5.2 > > Attachments: AMBARI-21053.patch, AMBARI-21053-trunk.patch > > > Beacon is an add-on-service installed via management pack. For services > installed via mpack need to use service advisor recommendation, which should > be provided in mpack. > Because of the stack_advisor [code > available|https://github.com/apache/ambari/commit/777eacd2be2c9477405ae53bd5faaa8b53b88aec], > service_advisor.py code logic from mpack is not getting executed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21117) Existing hosts state didn't save after host was added
[ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21117: - Fix Version/s: (was: 2.5.1) 2.5.2 > Existing hosts state didn't save after host was added > - > > Key: AMBARI-21117 > URL: https://issues.apache.org/jira/browse/AMBARI-21117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.2 > > Attachments: AMBARI-21117.patch > > > Existing hosts state didn't save after host was added. In next test add host > wizard stay open. > When we connect to cluster - automatically redirect on add host wizard. > (attached screenshot) > First step validation passed and host registered successfully. > On Review Page, when we clicked Deploy we had popup with error that this host > already part of cluster. > If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21117) Existing hosts state didn't save after host was added
[ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-21117: - Priority: Major (was: Blocker) > Existing hosts state didn't save after host was added > - > > Key: AMBARI-21117 > URL: https://issues.apache.org/jira/browse/AMBARI-21117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.5.2 > > Attachments: AMBARI-21117.patch > > > Existing hosts state didn't save after host was added. In next test add host > wizard stay open. > When we connect to cluster - automatically redirect on add host wizard. > (attached screenshot) > First step validation passed and host registered successfully. > On Review Page, when we clicked Deploy we had popup with error that this host > already part of cluster. > If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21117) Existing hosts state didn't save after host was added
[ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21117: - Status: Patch Available (was: Open) > Existing hosts state didn't save after host was added > - > > Key: AMBARI-21117 > URL: https://issues.apache.org/jira/browse/AMBARI-21117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21117.patch > > > Existing hosts state didn't save after host was added. In next test add host > wizard stay open. > When we connect to cluster - automatically redirect on add host wizard. > (attached screenshot) > First step validation passed and host registered successfully. > On Review Page, when we clicked Deploy we had popup with error that this host > already part of cluster. > If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21117) Existing hosts state didn't save after host was added
[ https://issues.apache.org/jira/browse/AMBARI-21117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21117: - Attachment: AMBARI-21117.patch > Existing hosts state didn't save after host was added > - > > Key: AMBARI-21117 > URL: https://issues.apache.org/jira/browse/AMBARI-21117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-21117.patch > > > Existing hosts state didn't save after host was added. In next test add host > wizard stay open. > When we connect to cluster - automatically redirect on add host wizard. > (attached screenshot) > First step validation passed and host registered successfully. > On Review Page, when we clicked Deploy we had popup with error that this host > already part of cluster. > If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21117) Existing hosts state didn't save after host was added
Antonenko Alexander created AMBARI-21117: Summary: Existing hosts state didn't save after host was added Key: AMBARI-21117 URL: https://issues.apache.org/jira/browse/AMBARI-21117 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Blocker Fix For: 2.5.1 Existing hosts state didn't save after host was added. In next test add host wizard stay open. When we connect to cluster - automatically redirect on add host wizard. (attached screenshot) First step validation passed and host registered successfully. On Review Page, when we clicked Deploy we had popup with error that this host already part of cluster. If we cluster wizard and try it again - validation on first step not passed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-21104.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: (was: AMBARI-21104_1.patch) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: (was: AMBARI-21104.patch) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Open (was: Patch Available) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21112) HDP 3.0 TP - create Service Advisor for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023649#comment-16023649 ] Hudson commented on AMBARI-21112: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7531 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7531/]) AMBARI-21112. HDP 3.0 TP - create Service Advisor for (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=56f019081b7de00504c87c8c075524a656466487]) * (add) ambari-server/src/main/resources/common-services/ZEPPELIN/0.6.0.3.0/service_advisor.py > HDP 3.0 TP - create Service Advisor for Zeppelin > > > Key: AMBARI-21112 > URL: https://issues.apache.org/jira/browse/AMBARI-21112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21112.patch > > > create Service Advisor for Zeppelin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023648#comment-16023648
]
Hudson commented on AMBARI-21116:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7531 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7531/])
AMBARI-21116. Setting yarn.node-labels.fs-store.root-dir to a "path" (aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4405d4982842a729ebfbd4c000c5ffb023a5])
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/package/scripts/yarn.py
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
> Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
> other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21110) ambari-server setup fails with default postgres
[ https://issues.apache.org/jira/browse/AMBARI-21110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023647#comment-16023647 ] Hudson commented on AMBARI-21110: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7531 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7531/]) AMBARI-21110. ambari-server setup fails with default postgres (aonishuk) (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b9ecb1fa5c5e602d2ea1ae70be2dbbca8368a59f]) * (edit) ambari-server/src/main/python/ambari_server/dbConfiguration_linux.py * (edit) ambari-common/src/main/python/ambari_commons/inet_utils.py > ambari-server setup fails with default postgres > --- > > Key: AMBARI-21110 > URL: https://issues.apache.org/jira/browse/AMBARI-21110 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21110.patch > > > Thisis the first run with oracle12. Initially infra sets up Ambari with > default postgres and later on ambari setup happens with Oracle12. But now the > first setup with default postgres is failing with below error > > > > root@172.27.24.11 "ambari-server setup > --java-home=/base/tools/jdk1.8.0_112 -s" > 2017-05-22 10:57:54.032 Using python /usr/bin/python > 2017-05-22 10:57:54.032 Setup ambari-server > 2017-05-22 10:58:14.299 Checking SELinux... > 2017-05-22 10:58:14.299 SELinux status is 'disabled' > 2017-05-22 10:58:14.299 Customize user account for ambari-server daemon > [y/n] (n)? > 2017-05-22 10:58:14.299 Adjusting ambari-server permissions and > ownership... > 2017-05-22 10:58:14.299 Checking firewall status... > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `nat': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `filter': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 WARNING: iptables is running. Confirm the > necessary Ambari ports are accessible. Refer to the Ambari documentation for > more details on ports. > 2017-05-22 10:58:14.299 OK to continue [y/n] (y)? > 2017-05-22 10:58:14.299 Checking JDK... > 2017-05-22 10:58:14.299 WARNING: JAVA_HOME /base/tools/jdk1.8.0_112 must > be valid on ALL hosts > 2017-05-22 10:58:14.299 WARNING: JCE Policy files are required for > configuring Kerberos security. If you plan to use Kerberos,please make sure > JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts. > 2017-05-22 10:58:14.299 Completing setup... > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Enter advanced database configuration [y/n] (n)? > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Default properties detected. Using built-in > database. > 2017-05-22 10:58:14.299 Configuring ambari database... > 2017-05-22 10:58:14.299 Checking PostgreSQL... > 2017-05-22 10:58:14.299 Running initdb: This may take up to a minute. > 2017-05-22 10:58:14.299 Initializing database: [ OK ] > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 About to start PostgreSQL > 2017-05-22 10:58:14.299 Configuring local database... > 2017-05-22 10:58:14.299 Configuring PostgreSQL... > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f > /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v > username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"'] > 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to > "/root" > 2017-05-22 10:58:14.299 psql: could not connect to server: No such file > or directory > 2017-05-22 10:58:14.299 Is the server running locally and accepting > 2017-05-22 10:58:14.299 connections on Unix domain socket > "/tmp/.s.PGSQL.5432"? > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 ERROR: stdout: > 2017-05-22 10:58:14.299 failed to execute queries ...retrying (1) > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-',
[jira] [Updated] (AMBARI-21083) Create custom admin user during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-21083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21083: -- Attachment: AMBARI-21083-May24.patch > Create custom admin user during ambari server setup > --- > > Key: AMBARI-21083 > URL: https://issues.apache.org/jira/browse/AMBARI-21083 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21083-May24.patch, AMBARI-21083.patch, > AMBARI-21083-updated.patch, custom_admin.PNG > > > Provide the ability to create custom admin user during ambari server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21111) Ambari 3.0: Outstanding navigation issues
[ https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023505#comment-16023505 ] Denys Buzhor commented on AMBARI-2: --- +1 for patch > Ambari 3.0: Outstanding navigation issues > - > > Key: AMBARI-2 > URL: https://issues.apache.org/jira/browse/AMBARI-2 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 3.0.0 > > Attachments: Action Bar.png, AMBARI-2.patch, Ambari metrics not > complete by default. .png, logo color and bar not same.png, Navigation > changes.png, two dark bar color not consistent .png > > > Following are the outstanding issues with Ambari navigation: > * Remove the Service status icon > * Alert icon should be circle and positioned in front of service name > * Do we need the green indicator for the selected menu? > * Services with master down should be indicated by red (service name is red > and show the original tooltip on hovering "Namenode is stopped" .etc) > Other issues: > * Make sure "Ambari Metrics" text is displaying completely without ellipsis > after the above changes. If still not visible (as attached), should increase > the width of side navigation. > * On Service configs page, the black horizontal bar and side navigation are > not consistent in color. One is black, the other is navy. > * On Manage Ambari page, ambari logo is not the same color as the background. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21112) HDP 3.0 TP - create Service Advisor for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21112: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 TP - create Service Advisor for Zeppelin > > > Key: AMBARI-21112 > URL: https://issues.apache.org/jira/browse/AMBARI-21112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21112.patch > > > create Service Advisor for Zeppelin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21110) ambari-server setup fails with default postgres
[ https://issues.apache.org/jira/browse/AMBARI-21110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023455#comment-16023455 ] Andrew Onischuk commented on AMBARI-21110: -- Committed to trunk > ambari-server setup fails with default postgres > --- > > Key: AMBARI-21110 > URL: https://issues.apache.org/jira/browse/AMBARI-21110 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21110.patch > > > Thisis the first run with oracle12. Initially infra sets up Ambari with > default postgres and later on ambari setup happens with Oracle12. But now the > first setup with default postgres is failing with below error > > > > root@172.27.24.11 "ambari-server setup > --java-home=/base/tools/jdk1.8.0_112 -s" > 2017-05-22 10:57:54.032 Using python /usr/bin/python > 2017-05-22 10:57:54.032 Setup ambari-server > 2017-05-22 10:58:14.299 Checking SELinux... > 2017-05-22 10:58:14.299 SELinux status is 'disabled' > 2017-05-22 10:58:14.299 Customize user account for ambari-server daemon > [y/n] (n)? > 2017-05-22 10:58:14.299 Adjusting ambari-server permissions and > ownership... > 2017-05-22 10:58:14.299 Checking firewall status... > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `nat': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `filter': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 WARNING: iptables is running. Confirm the > necessary Ambari ports are accessible. Refer to the Ambari documentation for > more details on ports. > 2017-05-22 10:58:14.299 OK to continue [y/n] (y)? > 2017-05-22 10:58:14.299 Checking JDK... > 2017-05-22 10:58:14.299 WARNING: JAVA_HOME /base/tools/jdk1.8.0_112 must > be valid on ALL hosts > 2017-05-22 10:58:14.299 WARNING: JCE Policy files are required for > configuring Kerberos security. If you plan to use Kerberos,please make sure > JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts. > 2017-05-22 10:58:14.299 Completing setup... > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Enter advanced database configuration [y/n] (n)? > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Default properties detected. Using built-in > database. > 2017-05-22 10:58:14.299 Configuring ambari database... > 2017-05-22 10:58:14.299 Checking PostgreSQL... > 2017-05-22 10:58:14.299 Running initdb: This may take up to a minute. > 2017-05-22 10:58:14.299 Initializing database: [ OK ] > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 About to start PostgreSQL > 2017-05-22 10:58:14.299 Configuring local database... > 2017-05-22 10:58:14.299 Configuring PostgreSQL... > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f > /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v > username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"'] > 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to > "/root" > 2017-05-22 10:58:14.299 psql: could not connect to server: No such file > or directory > 2017-05-22 10:58:14.299 Is the server running locally and accepting > 2017-05-22 10:58:14.299 connections on Unix domain socket > "/tmp/.s.PGSQL.5432"? > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 ERROR: stdout: > 2017-05-22 10:58:14.299 failed to execute queries ...retrying (1) > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f > /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v > username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"'] > 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to > "/root" > 2017-05-22 10:58:14.299 psql: could not connect to server: No such file > or directory > 2017-05-22 10:58:14.299 Is the server running locally and accepting >
[jira] [Resolved] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-21116.
--
Resolution: Fixed
Committed to trunk
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
> Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
> other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk reopened AMBARI-21116:
--
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
> Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
> other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-21116:
-
Fix Version/s: 2.5.2
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
> Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
> Fix For: 2.5.2
>
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
> other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk reassigned AMBARI-21116:
Assignee: Andrew Onischuk
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21116
> URL: https://issues.apache.org/jira/browse/AMBARI-21116
> Project: Ambari
> Issue Type: Bug
>Reporter: Sumana Sathish
>Assignee: Andrew Onischuk
>Priority: Critical
>
> 1. Set the following configs to run nodeLabels test via Ambari Rest Call
> {code}
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
> {code}
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
> other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21115) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-21115:
-
Resolution: Duplicate
Status: Resolved (was: Patch Available)
AMBARI-21116
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21115
> URL: https://issues.apache.org/jira/browse/AMBARI-21115
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21115.patch
>
>
> 1\. Set the following configs to run nodeLabels test via Ambari Rest Call
>
>
>
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
>
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3\. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop]BUG/drwx-
> -+++-+yarn+++hadoop) from [drwxrwxrwx - hdfs hadoop
> drwxrwxrwx+++-+hdfs+++hadoop) causing other tests to
> fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21116) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
Sumana Sathish created AMBARI-21116:
---
Summary: Setting yarn.node-labels.fs-store.root-dir to a "path"
changes the permission of the "root path"
Key: AMBARI-21116
URL: https://issues.apache.org/jira/browse/AMBARI-21116
Project: Ambari
Issue Type: Bug
Reporter: Sumana Sathish
Priority: Critical
1. Set the following configs to run nodeLabels test via Ambari Rest Call
{code}
yarnProperties = {'yarn.acl.enable': 'true',
'yarn.node-labels.enabled' : "True",
'yarn.node-labels.fs-store.root-dir':
NODE_LABEL_STORE_DIR,
'yarn.admin.acl': yarn_user + ',' + qa_user}
{code}
where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
2Restart ResourceManager and NodeManagers via ambari
3. After running these commands, /tmp directory's permission changes to
[drwx-- - yarn hadoop] from [drwxrwxrwx - hdfs hadoop] causing
other tests to fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21115) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-21115:
-
Fix Version/s: (was: 2.5.1)
2.5.2
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21115
> URL: https://issues.apache.org/jira/browse/AMBARI-21115
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21115.patch
>
>
> 1\. Set the following configs to run nodeLabels test via Ambari Rest Call
>
>
>
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
>
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3\. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop]BUG/drwx-
> -+++-+yarn+++hadoop) from [drwxrwxrwx - hdfs hadoop
> drwxrwxrwx+++-+hdfs+++hadoop) causing other tests to
> fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21115) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-21115:
-
Attachment: AMBARI-21115.patch
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21115
> URL: https://issues.apache.org/jira/browse/AMBARI-21115
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-21115.patch
>
>
> 1\. Set the following configs to run nodeLabels test via Ambari Rest Call
>
>
>
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
>
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3\. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop]BUG/drwx-
> -+++-+yarn+++hadoop) from [drwxrwxrwx - hdfs hadoop
> drwxrwxrwx+++-+hdfs+++hadoop) causing other tests to
> fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21115) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
[
https://issues.apache.org/jira/browse/AMBARI-21115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-21115:
-
Status: Patch Available (was: Open)
> Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission
> of the "root path"
>
>
> Key: AMBARI-21115
> URL: https://issues.apache.org/jira/browse/AMBARI-21115
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.1
>
> Attachments: AMBARI-21115.patch
>
>
> 1\. Set the following configs to run nodeLabels test via Ambari Rest Call
>
>
>
> yarnProperties = {'yarn.acl.enable': 'true',
> 'yarn.node-labels.enabled' : "True",
> 'yarn.node-labels.fs-store.root-dir':
> NODE_LABEL_STORE_DIR,
> 'yarn.admin.acl': yarn_user + ',' + qa_user}
>
> where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
> 2Restart ResourceManager and NodeManagers via ambari
> 3\. After running these commands, /tmp directory's permission changes to
> [drwx-- - yarn hadoop]BUG/drwx-
> -+++-+yarn+++hadoop) from [drwxrwxrwx - hdfs hadoop
> drwxrwxrwx+++-+hdfs+++hadoop) causing other tests to
> fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21115) Setting yarn.node-labels.fs-store.root-dir to a "path" changes the permission of the "root path"
Andrew Onischuk created AMBARI-21115:
Summary: Setting yarn.node-labels.fs-store.root-dir to a "path"
changes the permission of the "root path"
Key: AMBARI-21115
URL: https://issues.apache.org/jira/browse/AMBARI-21115
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.5.1
Attachments: AMBARI-21115.patch
1\. Set the following configs to run nodeLabels test via Ambari Rest Call
yarnProperties = {'yarn.acl.enable': 'true',
'yarn.node-labels.enabled' : "True",
'yarn.node-labels.fs-store.root-dir':
NODE_LABEL_STORE_DIR,
'yarn.admin.acl': yarn_user + ',' + qa_user}
where NODE_LABEL_STORE_DIR = "/tmp/node-labels"
2Restart ResourceManager and NodeManagers via ambari
3\. After running these commands, /tmp directory's permission changes to
[drwx-- - yarn hadoop]BUG/drwx-
-+++-+yarn+++hadoop) from [drwxrwxrwx - hdfs hadoop
drwxrwxrwx+++-+hdfs+++hadoop) causing other tests to
fail since it cannot access /tmp
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21110) ambari-server setup fails with default postgres
[ https://issues.apache.org/jira/browse/AMBARI-21110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21110: - Fix Version/s: 2.5.2 > ambari-server setup fails with default postgres > --- > > Key: AMBARI-21110 > URL: https://issues.apache.org/jira/browse/AMBARI-21110 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21110.patch > > > Thisis the first run with oracle12. Initially infra sets up Ambari with > default postgres and later on ambari setup happens with Oracle12. But now the > first setup with default postgres is failing with below error > > > > root@172.27.24.11 "ambari-server setup > --java-home=/base/tools/jdk1.8.0_112 -s" > 2017-05-22 10:57:54.032 Using python /usr/bin/python > 2017-05-22 10:57:54.032 Setup ambari-server > 2017-05-22 10:58:14.299 Checking SELinux... > 2017-05-22 10:58:14.299 SELinux status is 'disabled' > 2017-05-22 10:58:14.299 Customize user account for ambari-server daemon > [y/n] (n)? > 2017-05-22 10:58:14.299 Adjusting ambari-server permissions and > ownership... > 2017-05-22 10:58:14.299 Checking firewall status... > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `nat': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 FATAL: Could not load > /lib/modules/3.10.0-327.13.1.el7.x86_64/modules.dep: No such file or directory > 2017-05-22 10:58:14.299 iptables v1.4.7: can't initialize iptables table > `filter': Permission denied (you must be root) > 2017-05-22 10:58:14.299 Perhaps iptables or your kernel needs to be > upgraded. > 2017-05-22 10:58:14.299 WARNING: iptables is running. Confirm the > necessary Ambari ports are accessible. Refer to the Ambari documentation for > more details on ports. > 2017-05-22 10:58:14.299 OK to continue [y/n] (y)? > 2017-05-22 10:58:14.299 Checking JDK... > 2017-05-22 10:58:14.299 WARNING: JAVA_HOME /base/tools/jdk1.8.0_112 must > be valid on ALL hosts > 2017-05-22 10:58:14.299 WARNING: JCE Policy files are required for > configuring Kerberos security. If you plan to use Kerberos,please make sure > JCE Unlimited Strength Jurisdiction Policy Files are valid on all hosts. > 2017-05-22 10:58:14.299 Completing setup... > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Enter advanced database configuration [y/n] (n)? > 2017-05-22 10:58:14.299 Configuring database... > 2017-05-22 10:58:14.299 Default properties detected. Using built-in > database. > 2017-05-22 10:58:14.299 Configuring ambari database... > 2017-05-22 10:58:14.299 Checking PostgreSQL... > 2017-05-22 10:58:14.299 Running initdb: This may take up to a minute. > 2017-05-22 10:58:14.299 Initializing database: [ OK ] > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 About to start PostgreSQL > 2017-05-22 10:58:14.299 Configuring local database... > 2017-05-22 10:58:14.299 Configuring PostgreSQL... > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f > /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v > username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"'] > 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to > "/root" > 2017-05-22 10:58:14.299 psql: could not connect to server: No such file > or directory > 2017-05-22 10:58:14.299 Is the server running locally and accepting > 2017-05-22 10:58:14.299 connections on Unix domain socket > "/tmp/.s.PGSQL.5432"? > 2017-05-22 10:58:14.299 > 2017-05-22 10:58:14.299 ERROR: stdout: > 2017-05-22 10:58:14.299 failed to execute queries ...retrying (1) > 2017-05-22 10:58:14.299 Creating schema and user... > 2017-05-22 10:58:14.299 ERROR: Failed to execute > command:['ambari-sudo.sh', 'su', 'postgres', '-', '--command=psql -f > /var/lib/ambari-server/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql -v > username=\'"ambari"\' -v password="\'bigdata\'" -v dbname="ambari"'] > 2017-05-22 10:58:14.299 ERROR: stderr:could not change directory to > "/root" > 2017-05-22 10:58:14.299 psql: could not connect to server: No such file > or directory > 2017-05-22 10:58:14.299 Is the server running locally and accepting > 2017-05-22 10:58:14.299 connections on
[jira] [Commented] (AMBARI-21109) After decommission of a Nodemanager, the state of the Nodemanager shows "Decommissioning" instead of decommissioned
[ https://issues.apache.org/jira/browse/AMBARI-21109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023412#comment-16023412 ] Hudson commented on AMBARI-21109: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7530 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7530/]) AMBARI-21109. After decommission of a Nodemanager, the state of the (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ff0c5253e9554af52517303a5775e16d7836a246]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelperTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/ExecuteCommandJson.java > After decommission of a Nodemanager, the state of the Nodemanager shows > "Decommissioning" instead of decommissioned > --- > > Key: AMBARI-21109 > URL: https://issues.apache.org/jira/browse/AMBARI-21109 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21109-trunk.patch > > > Nodemanager going to real decommission only with next command -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21114) Fix Unit Test Failures From Prior Patch/Service Upgrade Commits
Jonathan Hurley created AMBARI-21114:
Summary: Fix Unit Test Failures From Prior Patch/Service Upgrade
Commits
Key: AMBARI-21114
URL: https://issues.apache.org/jira/browse/AMBARI-21114
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: trunk
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: trunk
The following unit tests are failing in the patch upgrade feature branch:
{noformat}
Failed tests:
StackUpgradeConfigurationMergeTest.testMergedConfigurationsDoNotAddExplicitelyRemovedProperties:261
Nothing captured yet
UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipAll:430
expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipFailures:333
expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
UpgradeResourceProviderTest.testCreateResourcesWithAutoSkipManualVerification:383
expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
UpgradeResourceProviderTest.testUpdateSkipFailures:1328->testCreateResourcesWithAutoSkipFailures:333
expected:<[Updating configuration zookeeper-newconfig]> but was:<[Skipping
Configuration Task hdp_2_1_1_zookeeper_new_config_type]>
UpgradeResourceProviderTest.testUpgradeHistory:1622 Implement me!
UpgradeActionTest.testExpressUpgradeUpdateDesiredStackAction:455 null
UpgradeActionTest.testFinalizeDowngradeAcrossStacks:742
expected:<[COMPLET]ED> but was:<[FAIL]ED>
UpgradeActionTest.testFinalizeDowngradeWhenDidNotFinalizePreviousUpgrade:535
expected:<[FAIL]ED> but was:<[COMPLET]ED>
UpgradeActionTest.testFinalizeUpgradeAcrossStacks:665 expected:<[COMPLET]ED>
but was:<[FAIL]ED>
UpgradeActionTest.testFinalizeUpgradeWithClusterStateInconsistencies:832
expected:<[COMPLET]ED> but was:<[FAIL]ED>
UpgradeHelperTest.testCompleteUpgradeOrchestration:377 expected:<[Service
Check Zk]> but was:<[Completing ZooKeeper1 Server2 on 192.168.64.1]>
UpgradeHelperTest.testPartialUpgradeOrchestration:312 expected:<3> but was:<0>
UpgradeHelperTest.testServiceCheckUpgradeStages:1073 expected:<6> but was:<7>
Tests in error:
UpgradeResourceProviderTest.testCreatePartialDowngrade:649 » NoSuchElement
UpgradeResourceProviderTest.testMergeConfigurations:1201 » IllegalState
missin...
ComponentVersionCheckActionTest.testMixedComponentVersions:341->createNewRepoVersion:273
» Ambari
UpgradeActionTest.testFinalizeUpgrade:548->createUpgradeClusterTargetRepo:303
» Ambari
UpgradeActionTest.testFinalizeWithHostsAlreadyCurrent:589->createUpgradeClusterTargetRepo:303
» Ambari
UpgradeHelperTest.testHostGroupingOrchestration:2133 » IllegalState missing
be...
UpgradeHelperTest.testOrchestrationNoServerSideOnDowngrade:1851 » IllegalState
UpgradeHelperTest.testResolverBadJmx:1713 » IllegalState missing behavior
defi...
UpgradeHelperTest.testResolverCaseInsensitive:1644 » IllegalState missing
beha...
UpgradeHelperTest.testResolverWithFailedUpgrade:1569 » IllegalState missing
be...
UpgradeHelperTest.testUpgradeOrchestrationWithHostsInMM:465 » IllegalState
mis...
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21109) After decommission of a Nodemanager, the state of the Nodemanager shows "Decommissioning" instead of decommissioned
[ https://issues.apache.org/jira/browse/AMBARI-21109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21109: - Resolution: Fixed Status: Resolved (was: Patch Available) > After decommission of a Nodemanager, the state of the Nodemanager shows > "Decommissioning" instead of decommissioned > --- > > Key: AMBARI-21109 > URL: https://issues.apache.org/jira/browse/AMBARI-21109 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21109-trunk.patch > > > Nodemanager going to real decommission only with next command -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-21109) After decommission of a Nodemanager, the state of the Nodemanager shows "Decommissioning" instead of decommissioned
[ https://issues.apache.org/jira/browse/AMBARI-21109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023295#comment-16023295 ] Dmytro Grinenko edited comment on AMBARI-21109 at 5/24/17 5:38 PM: --- Committed: 7bb2aba..ff0c525 trunk -> trunk was (Author: dgrinenko): Committed to trunk 7bb2aba..ff0c525 trunk -> trunk > After decommission of a Nodemanager, the state of the Nodemanager shows > "Decommissioning" instead of decommissioned > --- > > Key: AMBARI-21109 > URL: https://issues.apache.org/jira/browse/AMBARI-21109 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21109-trunk.patch > > > Nodemanager going to real decommission only with next command -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21109) After decommission of a Nodemanager, the state of the Nodemanager shows "Decommissioning" instead of decommissioned
[ https://issues.apache.org/jira/browse/AMBARI-21109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023295#comment-16023295 ] Dmytro Grinenko commented on AMBARI-21109: -- Committed to trunk 7bb2aba..ff0c525 trunk -> trunk > After decommission of a Nodemanager, the state of the Nodemanager shows > "Decommissioning" instead of decommissioned > --- > > Key: AMBARI-21109 > URL: https://issues.apache.org/jira/browse/AMBARI-21109 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21109-trunk.patch > > > Nodemanager going to real decommission only with next command -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Attachment: AMBARI-21104_1.patch > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Patch Available (was: In Progress) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21104) Add Confirmation pop up for 'Generate Blueprint' button
[ https://issues.apache.org/jira/browse/AMBARI-21104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21104: --- Status: Open (was: Patch Available) > Add Confirmation pop up for 'Generate Blueprint' button > --- > > Key: AMBARI-21104 > URL: https://issues.apache.org/jira/browse/AMBARI-21104 > Project: Ambari > Issue Type: Technical task > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21104_1.patch, AMBARI-21104.patch > > > Add Confirmation pop up for 'Generate Blueprint' button. > Notify user that two files will be downloaded and provide information on how > to use those files. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21093) Nimbus fails to start due to AutoHDFS CNF on a cluster after Ambari is upgraded
[
https://issues.apache.org/jira/browse/AMBARI-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez resolved AMBARI-21093.
--
Resolution: Duplicate
Dup of AMBARI-21045
> Nimbus fails to start due to AutoHDFS CNF on a cluster after Ambari is
> upgraded
> ---
>
> Key: AMBARI-21093
> URL: https://issues.apache.org/jira/browse/AMBARI-21093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Priority: Blocker
> Labels: regression, upgrade
> Fix For: 2.5.1
>
>
> *STR*
> # Deploy HDP2.6 cluster with Ambari-2.5.0 (secure cluster)
> # Upgrade Ambari to 2.5.1.0-140 and then 'Regenerate keytabs' from Ambari UI
> # Observe Nimbus state
> *Alternate STR*
> # Deploy HDP2.6 cluster with Ambari-2.5.0 (unsecure cluster)
> # Upgrade Ambari to 2.5.1.0-140 and then Express Upgrade to 2.6.1.0
> # Kerberize the cluster
> # Observe Nimbus state
> *Result*
> {code}
> 2017-05-22 12:12:57.768 o.a.s.d.nimbus main [ERROR] Error on initialization
> of server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException:
> org.apache.storm.hdfs.security.AutoHDFS
> at
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at
> org.apache.storm.daemon.nimbus$fn__9768$exec_fn__3648__auto9769.invoke(nimbus.clj:2416)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
> at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
> at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$fn__9768$service_handler__9801.doInvoke(nimbus.clj:2413)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21101) HDP 3.0 install fails due to 'Script' has no attribute 'get_force_https_protocol' because function was renamed
[ https://issues.apache.org/jira/browse/AMBARI-21101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023144#comment-16023144 ] Hudson commented on AMBARI-21101: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7529 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7529/]) AMBARI-21101. HDP 3.0 install fails due to 'Script' has no attribute (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7bb2aba5cc67e65e586352efdf307cf67dbfd416]) * (edit) ambari-server/src/main/resources/common-services/HDFS/3.0.0.3.0/package/scripts/utils.py > HDP 3.0 install fails due to 'Script' has no attribute > 'get_force_https_protocol' because function was renamed > -- > > Key: AMBARI-21101 > URL: https://issues.apache.org/jira/browse/AMBARI-21101 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21101.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21101) HDP 3.0 install fails due to 'Script' has no attribute 'get_force_https_protocol' because function was renamed
[ https://issues.apache.org/jira/browse/AMBARI-21101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023094#comment-16023094 ] Eugene Chekanskiy commented on AMBARI-21101: 90abffd..7bb2aba trunk -> trunk > HDP 3.0 install fails due to 'Script' has no attribute > 'get_force_https_protocol' because function was renamed > -- > > Key: AMBARI-21101 > URL: https://issues.apache.org/jira/browse/AMBARI-21101 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21101.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21101) HDP 3.0 install fails due to 'Script' has no attribute 'get_force_https_protocol' because function was renamed
[ https://issues.apache.org/jira/browse/AMBARI-21101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21101: --- Resolution: Fixed Status: Resolved (was: Patch Available) > HDP 3.0 install fails due to 'Script' has no attribute > 'get_force_https_protocol' because function was renamed > -- > > Key: AMBARI-21101 > URL: https://issues.apache.org/jira/browse/AMBARI-21101 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21101.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21113) hdfs_user_nofile_limit is not picking as expected for datanode process in a secure cluster
[
https://issues.apache.org/jira/browse/AMBARI-21113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21113:
-
Fix Version/s: trunk
> hdfs_user_nofile_limit is not picking as expected for datanode process in a
> secure cluster
> --
>
> Key: AMBARI-21113
> URL: https://issues.apache.org/jira/browse/AMBARI-21113
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk, 2.5.2
>
>
> such code snipped were not added to the hadoop-env after Ambari upgrade
> {code}
> if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
> "$HADOOP_SECURE_DN_USER" ]; then
> ulimit -n {{hdfs_user_nofile_limit}}
> fi
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21113) hdfs_user_nofile_limit is not picking as expected for datanode process in a secure cluster
Dmytro Grinenko created AMBARI-21113:
Summary: hdfs_user_nofile_limit is not picking as expected for
datanode process in a secure cluster
Key: AMBARI-21113
URL: https://issues.apache.org/jira/browse/AMBARI-21113
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: 2.5.2
such code snipped were not added to the hadoop-env after Ambari upgrade
{code}
if [ "$command" == "datanode" ] && [ "$EUID" -eq 0 ] && [ -n
"$HADOOP_SECURE_DN_USER" ]; then
ulimit -n {{hdfs_user_nofile_limit}}
fi
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21112) HDP 3.0 TP - create Service Advisor for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21112: --- Status: Patch Available (was: Open) > HDP 3.0 TP - create Service Advisor for Zeppelin > > > Key: AMBARI-21112 > URL: https://issues.apache.org/jira/browse/AMBARI-21112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21112.patch > > > create Service Advisor for Zeppelin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21112) HDP 3.0 TP - create Service Advisor for Zeppelin
[ https://issues.apache.org/jira/browse/AMBARI-21112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21112: --- Attachment: AMBARI-21112.patch > HDP 3.0 TP - create Service Advisor for Zeppelin > > > Key: AMBARI-21112 > URL: https://issues.apache.org/jira/browse/AMBARI-21112 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21112.patch > > > create Service Advisor for Zeppelin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21112) HDP 3.0 TP - create Service Advisor for Zeppelin
Vitaly Brodetskyi created AMBARI-21112: -- Summary: HDP 3.0 TP - create Service Advisor for Zeppelin Key: AMBARI-21112 URL: https://issues.apache.org/jira/browse/AMBARI-21112 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 create Service Advisor for Zeppelin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21059) Reduce Dependency on Cluster Desired Stack ID
[
https://issues.apache.org/jira/browse/AMBARI-21059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Cole updated AMBARI-21059:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Reduce Dependency on Cluster Desired Stack ID
> -
>
> Key: AMBARI-21059
> URL: https://issues.apache.org/jira/browse/AMBARI-21059
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-21059.patch
>
>
> With the advent of {{PATCH}} and {{CLUSTER}} upgrades, there is no longer the
> notion of a cluster being bound to a specific stack. Instead, the stack ID is
> being pushed down to the service and component level.
> Currently, upgrades tries to set the cluster desired stack ID on
> finalization. Eventually there will be a complete decouple of the cluster
> from a singular stack id. This jira covers a majority of cases in code.
> Until configs are refactored, we can't remove the associated stack id in its
> entirety.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
[ https://issues.apache.org/jira/browse/AMBARI-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21108: --- Status: Patch Available (was: Open) > Unable to upload table via Ambari Hive view if user does not have permission > on default database > > > Key: AMBARI-21108 > URL: https://issues.apache.org/jira/browse/AMBARI-21108 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21108_branch-2.5.patch > > > Hive View : upload table code runs queries against 'default' database. which > requires users to have permission on this database even though table is being > uploaded in another database. > Its a bug in hive view 1.5. > This bug is also present in hive view 1.5 of ambari release 2.5. > It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21108) Unable to upload table via Ambari Hive view if user does not have permission on default database
[ https://issues.apache.org/jira/browse/AMBARI-21108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitiraj Singh Rathore updated AMBARI-21108: --- Attachment: AMBARI-21108_branch-2.5.patch Hive view 1.5 was using default DB for use statement in upload table feature. corrected it to use selected database > Unable to upload table via Ambari Hive view if user does not have permission > on default database > > > Key: AMBARI-21108 > URL: https://issues.apache.org/jira/browse/AMBARI-21108 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore > Fix For: 2.5.2 > > Attachments: AMBARI-21108_branch-2.5.patch > > > Hive View : upload table code runs queries against 'default' database. which > requires users to have permission on this database even though table is being > uploaded in another database. > Its a bug in hive view 1.5. > This bug is also present in hive view 1.5 of ambari release 2.5. > It will not occur in hive view 2.0 which is release with ambari 2.5. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21098) Integrate Titan into Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022852#comment-16022852 ] Di Li commented on AMBARI-21098: Hello Hui, Do you have design doc on what you are trying to accomplish ? > Integrate Titan into Ambari > --- > > Key: AMBARI-21098 > URL: https://issues.apache.org/jira/browse/AMBARI-21098 > Project: Ambari > Issue Type: Story >Affects Versions: trunk, 2.5.1 >Reporter: Hui Cao >Assignee: Hui Cao > Labels: titan > Fix For: trunk > > Original Estimate: 504h > Remaining Estimate: 504h > > Titan is designed to support the processing of graphs so large that they > require storage and computational capacities beyond what a single machine can > provide. Scaling graph data processing for real time traversals and > analytical queries is Titan’s foundational benefit. > This story is aimed to integrate Titan into Ambari so that it can be > installed and managed by Ambari from web UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21111) Ambari 3.0: Outstanding navigation issues
[
https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022756#comment-16022756
]
Hadoop QA commented on AMBARI-2:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12869632/AMBARI-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-admin ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11609//console
This message is automatically generated.
> Ambari 3.0: Outstanding navigation issues
> -
>
> Key: AMBARI-2
> URL: https://issues.apache.org/jira/browse/AMBARI-2
> Project: Ambari
> Issue Type: Task
> Components: ambari-admin, ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: Action Bar.png, AMBARI-2.patch, Ambari metrics not
> complete by default. .png, logo color and bar not same.png, Navigation
> changes.png, two dark bar color not consistent .png
>
>
> Following are the outstanding issues with Ambari navigation:
> * Remove the Service status icon
> * Alert icon should be circle and positioned in front of service name
> * Do we need the green indicator for the selected menu?
> * Services with master down should be indicated by red (service name is red
> and show the original tooltip on hovering "Namenode is stopped" .etc)
> Other issues:
> * Make sure "Ambari Metrics" text is displaying completely without ellipsis
> after the above changes. If still not visible (as attached), should increase
> the width of side navigation.
> * On Service configs page, the black horizontal bar and side navigation are
> not consistent in color. One is black, the other is navy.
> * On Manage Ambari page, ambari logo is not the same color as the background.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
