[jira] [Created] (AMBARI-25841) Ambari agent failed to connect server
chenqiang created AMBARI-25841:
--
Summary: Ambari agent failed to connect server
Key: AMBARI-25841
URL: https://issues.apache.org/jira/browse/AMBARI-25841
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.5
Environment: OS: openEuler 22.03
openSSL: 1.1.1m
JDK: openjdk 1.8
python: 3.9.9
DB: MariaDB
Reporter: chenqiang
Attachments: ambari-agent启动timeout.log
# The setup status of Ambari server is successful, the status of ambari-server
status is normal by using the *ambari-server status* command{*}.{*}
# Failed to start ambari agent，the error log is:
*raise ConnectionResponseTimeout("Waiting for connection confirmation
timed out")*
*ambari_stomp.adapter.websocket.ConnectionResponseTimeout: Waiting for
connection confirmation timed out*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-25840: Labels: pull-request-available (was: ) > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Assigned] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
[ https://issues.apache.org/jira/browse/AMBARI-25840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yu Hou reassigned AMBARI-25840: --- Assignee: Yu Hou > Optimized rpm packaging for the Ambari-Metric-Collector > --- > > Key: AMBARI-25840 > URL: https://issues.apache.org/jira/browse/AMBARI-25840 > Project: Ambari > Issue Type: Sub-task > Components: ambari-metrics >Affects Versions: 2.8.0 > Environment: Centos7 > Ambari-2.8.0 >Reporter: Yu Hou >Assignee: Yu Hou >Priority: Major > Fix For: 2.8.0 > > Attachments: image-2023-01-12-10-55-23-747.png > > > The hadoop and hbase versions of the ambari-metric-Collector are inconsistent > with the pom.xml. > We should get it from the hadoop and hbase tarball. > !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25840) Optimized rpm packaging for the Ambari-Metric-Collector
Yu Hou created AMBARI-25840: --- Summary: Optimized rpm packaging for the Ambari-Metric-Collector Key: AMBARI-25840 URL: https://issues.apache.org/jira/browse/AMBARI-25840 Project: Ambari Issue Type: Sub-task Components: ambari-metrics Affects Versions: 2.8.0 Environment: Centos7 Ambari-2.8.0 Reporter: Yu Hou Fix For: 2.8.0 Attachments: image-2023-01-12-10-55-23-747.png The hadoop and hbase versions of the ambari-metric-Collector are inconsistent with the pom.xml. We should get it from the hadoop and hbase tarball. !image-2023-01-12-10-55-23-747.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Description:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
org.apache.kafka.common.config.ConfigException: Only one of
inter.broker.listener.name and security.inter.broker.protocol should be set.
at
kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
at
kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
{code}
2. Remove the DEPRECATED attribute port
!screenshot-1.png!
was:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.ser
[jira] [Updated] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Description:
1. When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
org.apache.kafka.common.config.ConfigException: Only one of
inter.broker.listener.name and security.inter.broker.protocol should be set.
at
kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
at
kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
[2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
at kafka.Kafka$.buildServer(Kafka.scala:67)
at kafka.Kafka$.main(Kafka.scala:87)
at kafka.Kafka.main(Kafka.scala)
{code}
2. Remove the DEPRECATED attribute port
was:
When kerberos enabled, kafka failed to start.
The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
when kerberos is enabled, an attribute controlled by kafka_listeners.
{code:java}
[2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
(kafka.server.KafkaServer)
[2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
MBean (kafka.utils.Log4jControllerRegistration$)
[2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
(kafka.Kafka$)
java.lang.IllegalArgumentException: requirement failed:
inter.broker.listener.name must be a listener name defined in
advertised.listeners. The valid options based on currently configured listeners
are PLAINTEXT
at scala.Predef$.require(Predef.scala:281)
at kafka.server.KafkaConfig.validate
[jira] [Updated] (AMBARI-25838) Add kafka_listeners to kafka to fix startup failures on kerberos enabled
[
https://issues.apache.org/jira/browse/AMBARI-25838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Hou updated AMBARI-25838:
Attachment: screenshot-1.png
> Add kafka_listeners to kafka to fix startup failures on kerberos enabled
>
>
> Key: AMBARI-25838
> URL: https://issues.apache.org/jira/browse/AMBARI-25838
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.8.0
> Environment: Centos7
> Ambari-2.8.0
>Reporter: Yu Hou
>Assignee: Yu Hou
>Priority: Major
> Fix For: 2.8.0
>
> Attachments: screenshot-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1. When kerberos enabled, kafka failed to start.
> The listeners' protocol needs to be changed from PLAINTEXT to SASL_PLAINTEXT
> when kerberos is enabled, an attribute controlled by kafka_listeners.
> {code:java}
> [2023-01-10 08:40:18,783] INFO [KafkaServer id=1001] shut down completed
> (kafka.server.KafkaServer)
> [2023-01-10 08:43:13,215] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:43:14,230] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:53:37,390] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:53:38,214] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:57:26,554] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:57:27,377] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> org.apache.kafka.common.config.ConfigException: Only one of
> inter.broker.listener.name and security.inter.broker.protocol should be set.
> at
> kafka.server.KafkaConfig.getInterBrokerListenerNameAndSecurityProtocol(KafkaConfig.scala:1851)
> at
> kafka.server.KafkaConfig.interBrokerListenerName(KafkaConfig.scala:1722)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1932)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> [2023-01-10 08:59:21,462] INFO Registered kafka:type=kafka.Log4jController
> MBean (kafka.utils.Log4jControllerRegistration$)
> [2023-01-10 08:59:22,239] ERROR Exiting Kafka due to fatal exception
> (kafka.Kafka$)
> java.lang.IllegalArgumentException: requirement failed:
> inter.broker.listener.name must be a listener name defined in
> advertised.listeners. The valid options based on currently configured
> listeners are PLAINTEXT
> at scala.Predef$.require(Predef.scala:281)
> at kafka.server.KafkaConfig.validateValues(KafkaConfig.scala:1933)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1896)
> at kafka.server.KafkaConfig.(KafkaConfig.scala:1389)
> at kafka.server.KafkaConfig$.fromProps(KafkaConfig.scala:1327)
> at kafka.Kafka$.buildServer(Kafka.scala:67)
> at kafka.Kafka$.main(Kafka.scala:87)
> at kafka.Kafka.main(Kafka.scala)
> {code}
> 2. Remove the DEPRECATED attribute port
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
[jira] [Updated] (AMBARI-25839) Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after completion
[ https://issues.apache.org/jira/browse/AMBARI-25839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijayakumar Govindasamy updated AMBARI-25839: - Status: Patch Available (was: Open) https://github.com/apache/ambari/pull/3628 > Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after > completion > --- > > Key: AMBARI-25839 > URL: https://issues.apache.org/jira/browse/AMBARI-25839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.5 > Environment: UI issue, Applicable to all the envs >Reporter: Vijayakumar Govindasamy >Priority: Major > Attachments: Screenshot 2023-01-11 at 2.28.29 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > Problem: > After enabling Ranger HA, Ambari UI shows " Enable Ranger Admin HA Wizard in > Progress | Initiated by admin" and all the actions are disabled for other > users. > Ex: If Ambari has 2 users, User1 and User2, If User1 initiate Ranger HA > enable wizard and completes the wizard(Not cancel), Even after completion > User2 sees above mentioned message and not able to perform any > action(Basically read only) > Note: This problem comes only for wizard completion. If user cancel the > wizard, wizard-data properly gets reset > Root Cause: wizard-data is not reset after completion of Ranger HA flow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Commented] (AMBARI-25839) Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after completion
[ https://issues.apache.org/jira/browse/AMBARI-25839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17672246#comment-17672246 ] Vijayakumar Govindasamy commented on AMBARI-25839: -- Feel free to assign the ticket to me. I have the fix and raise the PR > Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after > completion > --- > > Key: AMBARI-25839 > URL: https://issues.apache.org/jira/browse/AMBARI-25839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.5 > Environment: UI issue, Applicable to all the envs >Reporter: Vijayakumar Govindasamy >Priority: Major > Attachments: Screenshot 2023-01-11 at 2.28.29 PM.png > > > Problem: > After enabling Ranger HA, Ambari UI shows " Enable Ranger Admin HA Wizard in > Progress | Initiated by admin" and all the actions are disabled for other > users. > Ex: If Ambari has 2 users, User1 and User2, If User1 initiate Ranger HA > enable wizard and completes the wizard(Not cancel), Even after completion > User2 sees above mentioned message and not able to perform any > action(Basically read only) > Note: This problem comes only for wizard completion. If user cancel the > wizard, wizard-data properly gets reset > Root Cause: wizard-data is not reset after completion of Ranger HA flow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-25839) Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after completion
[ https://issues.apache.org/jira/browse/AMBARI-25839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijayakumar Govindasamy updated AMBARI-25839: - Attachment: Screenshot 2023-01-11 at 2.28.29 PM.png > Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after > completion > --- > > Key: AMBARI-25839 > URL: https://issues.apache.org/jira/browse/AMBARI-25839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.5 > Environment: UI issue, Applicable to all the envs >Reporter: Vijayakumar Govindasamy >Priority: Major > Attachments: Screenshot 2023-01-11 at 2.28.29 PM.png > > > Problem: > After enabling Ranger HA, Ambari UI shows " Enable Ranger Admin HA Wizard in > Progress | Initiated by admin" and all the actions are disabled for other > users. > Ex: If Ambari has 2 users, User1 and User2, If User1 initiate Ranger HA > enable wizard and completes the wizard(Not cancel), Even after completion > User2 sees above mentioned message and not able to perform any > action(Basically read only) > Note: This problem comes only for wizard completion. If user cancel the > wizard, wizard-data properly gets reset > Root Cause: wizard-data is not reset after completion of Ranger HA flow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Created] (AMBARI-25839) Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after completion
Vijayakumar Govindasamy created AMBARI-25839: Summary: Ambari UI shows Enable Ranger Admin HA Wizard in Progress even after completion Key: AMBARI-25839 URL: https://issues.apache.org/jira/browse/AMBARI-25839 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.5 Environment: UI issue, Applicable to all the envs Reporter: Vijayakumar Govindasamy Problem: After enabling Ranger HA, Ambari UI shows " Enable Ranger Admin HA Wizard in Progress | Initiated by admin" and all the actions are disabled for other users. Ex: If Ambari has 2 users, User1 and User2, If User1 initiate Ranger HA enable wizard and completes the wizard(Not cancel), Even after completion User2 sees above mentioned message and not able to perform any action(Basically read only) Note: This problem comes only for wizard completion. If user cancel the wizard, wizard-data properly gets reset Root Cause: wizard-data is not reset after completion of Ranger HA flow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
