[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
The blueprints API, when taking & responding with json, is only accepting
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
The blueprints API, when taking & responding with json, is only accepting
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15336443#comment-15336443
]
Sean Roberts commented on AMBARI-9016:
--
Bump.
> API not taking or responding with application/json
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
The stack advisor API does not accept application/json even though it expects
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
Sean Roberts created AMBARI-18558:
-
Summary: StackAdvisor recommending wrong port for Ambari
Key: AMBARI-18558
URL: https://issues.apache.org/jira/browse/AMBARI-18558
Project: Ambari
Issue
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-18558:
--
Description:
Configuration Recommendations are recommending port :8080 when the Ambari port
[
https://issues.apache.org/jira/browse/AMBARI-23932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23932:
--
Summary: Ambari Metrics reports incorrect values in aggregated host metric
data when
Sean Roberts created AMBARI-23932:
-
Summary: Ambari Metrics reports incorrect numbers in aggregated
host metric data when requesting "avg"
Key: AMBARI-23932
URL: https://issues.apache.org/jira/browse/AMBARI-23932
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a *Content-Type:text/plain* when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Priority: Blocker (was: Minor)
> Ambari API send HTTP Header with "Content-Type=text/plain"
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Summary: Ambari API send HTTP Header with "Content-Type=text/plain" when
the content is JSON.
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Affects Version/s: 2.6.2
> Ambari API send HTTP Header with "Content-Type=text/plain" when the
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Summary: Ambari API send HTTP Header "Content-Type=text/plain" when the
content is JSON. (was:
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Summary: Ambari API uses HTTP Header "Content-Type=text/plain" when the
content is JSON. (was:
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a "Content-Type:text/plain" when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a "Content-Type:text/plain" when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Summary: Ambari API uses HTTP Header Content-Type:text/plain when the
content is JSON. (was:
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Summary: Ambari API uses HTTP Header "Content-Type:text/plain" when the
content is JSON. (was:
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a *Content-Type:text/plain* when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a "Content-Type:text/plain" when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a "Content-Type"="text/plain" when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Description:
Ambari responds with a *Content-Type:text/plain* when the content is actually
[
https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23971:
--
Attachment: (was: image-2018-05-29-20-28-04-845.png)
> Capacity Scheduler View: Not
Sean Roberts created AMBARI-23971:
-
Summary: Capacity Scheduler View: Not allowed to set a sub-queue
to 0% capacity
Key: AMBARI-23971
URL: https://issues.apache.org/jira/browse/AMBARI-23971
Project:
[
https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23971:
--
Attachment: (was: image-2018-05-29-20-28-14-975.png)
> Capacity Scheduler View: Not
[
https://issues.apache.org/jira/browse/AMBARI-23971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23971:
--
Summary: Capacity Scheduler View: Not allowed to set a queue/leafs to 0%
capacity (was:
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Affects Version/s: 2.7.0
> Ambari API uses HTTP Header Content-Type:text/plain when the content
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Labels: (was: newbie)
> Ambari API uses HTTP Header Content-Type:text/plain when the content
Sean Roberts created AMBARI-24152:
-
Summary: Ambari Workflow Manager (wfmanager) sends plaintext
content when it should send json
Key: AMBARI-24152
URL: https://issues.apache.org/jira/browse/AMBARI-24152
[
https://issues.apache.org/jira/browse/AMBARI-24152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24152:
--
Summary: Ambari Workflow Manager (wfmanager) sends plaintext content over
API. JSON is
Sean Roberts created AMBARI-23702:
-
Summary: Ambari: migrate to log4j2
Key: AMBARI-23702
URL: https://issues.apache.org/jira/browse/AMBARI-23702
Project: Ambari
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/AMBARI-22715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-22715:
--
Affects Version/s: 2.5.2
> Kafka broken by auth_to_local rules when
Sean Roberts created AMBARI-22715:
-
Summary: Kafka broken by auth_to_local rules when
case_insensitive_username_rules=true
Key: AMBARI-22715
URL: https://issues.apache.org/jira/browse/AMBARI-22715
[
https://issues.apache.org/jira/browse/AMBARI-22715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-22715:
--
Description:
https://issues.apache.org/jira/browse/AMBARI-22715
Kafka brokers will fail to
[
https://issues.apache.org/jira/browse/AMBARI-22715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-22715:
--
Description:
https://issues.apache.org/jira/browse/AMBARI-22715
Kafka brokers will fail to
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516921#comment-16516921
]
Sean Roberts commented on AMBARI-9016:
--
Bump. This is causing a cascade of issues in Apache Knox
[
https://issues.apache.org/jira/browse/AMBARI-24448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24448:
--
Labels: common-services druid (was: )
> "Druid Historical" default MaxDirectMemorySize=1TB
Sean Roberts created AMBARI-24448:
-
Summary: "Druid Historical" default MaxDirectMemorySize=1TB
Key: AMBARI-24448
URL: https://issues.apache.org/jira/browse/AMBARI-24448
Project: Ambari
[
https://issues.apache.org/jira/browse/AMBARI-24536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591599#comment-16591599
]
Sean Roberts commented on AMBARI-24536:
---
[~rlevas] As discussed on Chat, Auth Negotiation is a
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591531#comment-16591531
]
Sean Roberts commented on AMBARI-24528:
---
[~rlevas] Yeah, that's why I proposed moving "Additional
Sean Roberts created AMBARI-24536:
-
Summary: Ambari SPNEGO breaks SSO redirect
Key: AMBARI-24536
URL: https://issues.apache.org/jira/browse/AMBARI-24536
Project: Ambari
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMBARI-24536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24536:
--
Description:
When SPNEGO is enabled (`ambari-server setup-kerberos`), the SSO
Sean Roberts created AMBARI-24528:
-
Summary: Kerberos "Additional Realms" does not require keytab
re-generation
Key: AMBARI-24528
URL: https://issues.apache.org/jira/browse/AMBARI-24528
Project:
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
The 'Admin -> Kerberos -> "Additonal Realms"' configuration:
* Currently
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Summary: Kerberos "Additional Realms" should not require keytab
re-generation (was:
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Description:
"Admin -> Kerberos -> Additonal Realms"
* Currently requires keytab
[
https://issues.apache.org/jira/browse/AMBARI-24528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24528:
--
Summary: Kerberos "Additional Realms" should not require keytab
re-generation and cluster
[
https://issues.apache.org/jira/browse/AMBARI-23095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23095:
--
Description:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
Sean Roberts created AMBARI-23095:
-
Summary: knoxsso.redirect.whitelist.regex should not require a
port number
Key: AMBARI-23095
URL: https://issues.apache.org/jira/browse/AMBARI-23095
Project:
[
https://issues.apache.org/jira/browse/AMBARI-23095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-23095:
--
Description:
The default 'knoxsso.redirect.whitelist.regex' is set to require a port number
[
https://issues.apache.org/jira/browse/AMBARI-24209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24209:
--
Description:
Ambari Alerts in the "UNKNOWN" state do not show in the alert count
Sean Roberts created AMBARI-24209:
-
Summary: Unknown Alerts do not show in the alert count
Key: AMBARI-24209
URL: https://issues.apache.org/jira/browse/AMBARI-24209
Project: Ambari
Issue
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16518079#comment-16518079
]
Sean Roberts commented on AMBARI-9016:
--
For reference, this is due to ambari-server API explicitly
[
https://issues.apache.org/jira/browse/AMBARI-25104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748167#comment-16748167
]
Sean Roberts commented on AMBARI-25104:
---
After reviewing we don't think it is defaulting to
Sean Roberts created AMBARI-24963:
-
Summary: HDFS Quicklinks should use https:// if
dfs.http.policy=HTTP_AND_HTTPS
Key: AMBARI-24963
URL: https://issues.apache.org/jira/browse/AMBARI-24963
Project:
[
https://issues.apache.org/jira/browse/AMBARI-24963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-24963:
--
Description:
With dfs.http.policy=HTTP_AND_HTTPS the quicklinks are using http://.
They
Sean Roberts created AMBARI-25093:
-
Summary: "Spark2 Thrift Server" alert does not work with HTTPS
(SSL)
Key: AMBARI-25093
URL: https://issues.apache.org/jira/browse/AMBARI-25093
Project: Ambari
Sean Roberts created AMBARI-25124:
-
Summary: ambari-audit.log entries span multiple lines
Key: AMBARI-25124
URL: https://issues.apache.org/jira/browse/AMBARI-25124
Project: Ambari
Issue
[
https://issues.apache.org/jira/browse/AMBARI-25127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809915#comment-16809915
]
Sean Roberts commented on AMBARI-25127:
---
Robert - Correct. The act of turning it on doesn't cause
[
https://issues.apache.org/jira/browse/AMBARI-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-9016:
-
Affects Version/s: 2.7.3
> Ambari API uses HTTP Header Content-Type:text/plain when the content
Sean Roberts created AMBARI-25161:
-
Summary: Cluster deploy fails due to Ambari attempting to create
`tez.am.view-acls` as users/groups in the OS.
Key: AMBARI-25161
URL:
[
https://issues.apache.org/jira/browse/AMBARI-25127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-25127:
--
Description:
With SPNEGO enabled for Ambari-Server, ambari-server.log is flooded with every
Sean Roberts created AMBARI-25127:
-
Summary: ambari-server.log flooded if client not able to
authenticate through kerberos
Key: AMBARI-25127
URL: https://issues.apache.org/jira/browse/AMBARI-25127
[
https://issues.apache.org/jira/browse/AMBARI-25239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-25239:
--
Description:
When Oozie SSL (https) is configured, the Workflow Manager view cannot complete
[
https://issues.apache.org/jira/browse/AMBARI-25239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-25239:
--
Description:
When Oozie SSL (https) is configured, the Workflow Manager view cannot complete
[
https://issues.apache.org/jira/browse/AMBARI-25239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Roberts updated AMBARI-25239:
--
Description:
When Oozie SSL (https) is configured, the Workflow Manager view cannot complete
Sean Roberts created AMBARI-25239:
-
Summary: Ambari Workflow Manager View (wfmanager) does not detect
Oozie using https
Key: AMBARI-25239
URL: https://issues.apache.org/jira/browse/AMBARI-25239
79 matches
Mail list logo
