[jira] [Updated] (AMBARI-24047) Infra Solr: Changed GC options are lost after Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-24047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24047: Description: at infra-solr env, people can define GC settings, as we are upgrading the whole content during upgrade with on-ambari-update update=true, that can override an already defined settings. it would be good if we could include 2 new properties for infra-solr-env config type (extend gc_log_opts and gc_tune), and put the already defined gc settings there during upgrade. > Infra Solr: Changed GC options are lost after Ambari upgrade > > > Key: AMBARI-24047 > URL: https://issues.apache.org/jira/browse/AMBARI-24047 > Project: Ambari > Issue Type: Bug > Components: infra, solr >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.0 > > > at infra-solr env, people can define GC settings, as we are upgrading the > whole content during upgrade with on-ambari-update update=true, that can > override an already defined settings. > it would be good if we could include 2 new properties for infra-solr-env > config type (extend gc_log_opts and gc_tune), and put the already defined gc > settings there during upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24047) Infra Solr: Changed GC options are lost after Ambari upgrade
Krisztian Kasa created AMBARI-24047: --- Summary: Infra Solr: Changed GC options are lost after Ambari upgrade Key: AMBARI-24047 URL: https://issues.apache.org/jira/browse/AMBARI-24047 Project: Ambari Issue Type: Bug Components: infra, solr Affects Versions: 2.7.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
[
https://issues.apache.org/jira/browse/AMBARI-24046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-24046:
Labels: pull-request-available (was: )
> Fix the incorrect string from "config_name" to "config-name" in
> mpack_advisor.py
>
>
> Key: AMBARI-24046
> URL: https://issues.apache.org/jira/browse/AMBARI-24046
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> *Issue:*
> Call to function toConfigurationValidationProblems() breaks for following :
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 148, in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 126, in main
> result = mpackAdvisor.validateConfigurations()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1149, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1588, in getConfigurationsValidationItems
> self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1563, in validateMinMax
> validatedItems = self.toConfigurationValidationProblems(validationItems,
> configName)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1518, in toConfigurationValidationProblems
> "config_type": siteName, "config_name": validationProblem["config-name"] }
> KeyError: 'config-name'
> {code}
> *Reason :* In *validateMinMax()* fn, when adding to validationItems, the
> string should be "config-name" instead of "config_name".
> *Fix* : Updated "config_name" to "config-name".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
[ https://issues.apache.org/jira/browse/AMBARI-24044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503732#comment-16503732 ] Hudson commented on AMBARI-24044: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9415 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9415/]) AMBARI-24044. Widget Browser add/hide functionality is not working (aleksandrkovalenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=269db6f5f44545225addd1a05fb7985378e4087c]) * (edit) ambari-web/app/controllers/main/service/info/metric.js * (edit) ambari-web/app/templates/common/modal_popups/widget_browser_popup.hbs > Widget Browser add/hide functionality is not working correctly > -- > > Key: AMBARI-24044 > URL: https://issues.apache.org/jira/browse/AMBARI-24044 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Widget browser add/hide widget functionality is not working correctly if > widget is included in several widget_layouts as in case of several NameNode > Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
[
https://issues.apache.org/jira/browse/AMBARI-24046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24046:
-
Description:
Call to function toConfigurationValidationProblems() breaks for following :
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 148, in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 126, in main
result = mpackAdvisor.validateConfigurations()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1149, in validateConfigurations
validationItems = self.getConfigurationsValidationItems()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1588, in getConfigurationsValidationItems
self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1563, in validateMinMax
validatedItems = self.toConfigurationValidationProblems(validationItems,
configName)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1518, in toConfigurationValidationProblems
"config_type": siteName, "config_name": validationProblem["config-name"] }
KeyError: 'config-name'
{code}
*Reason :* In *validateMinMax()* fn, when adding to validationItems, the string
should be "config-name" instead of "config_name".
*Fix* : Updated "config_name" to "config-name".
> Fix the incorrect string from "config_name" to "config-name" in
> mpack_advisor.py
>
>
> Key: AMBARI-24046
> URL: https://issues.apache.org/jira/browse/AMBARI-24046
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
>
> Call to function toConfigurationValidationProblems() breaks for following :
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 148, in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 126, in main
> result = mpackAdvisor.validateConfigurations()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1149, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1588, in getConfigurationsValidationItems
> self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1563, in validateMinMax
> validatedItems = self.toConfigurationValidationProblems(validationItems,
> configName)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1518, in toConfigurationValidationProblems
> "config_type": siteName, "config_name": validationProblem["config-name"] }
> KeyError: 'config-name'
> {code}
> *Reason :* In *validateMinMax()* fn, when adding to validationItems, the
> string should be "config-name" instead of "config_name".
> *Fix* : Updated "config_name" to "config-name".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
[
https://issues.apache.org/jira/browse/AMBARI-24046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-24046:
-
Description:
*Issue:*
Call to function toConfigurationValidationProblems() breaks for following :
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 148, in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 126, in main
result = mpackAdvisor.validateConfigurations()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1149, in validateConfigurations
validationItems = self.getConfigurationsValidationItems()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1588, in getConfigurationsValidationItems
self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1563, in validateMinMax
validatedItems = self.toConfigurationValidationProblems(validationItems,
configName)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1518, in toConfigurationValidationProblems
"config_type": siteName, "config_name": validationProblem["config-name"] }
KeyError: 'config-name'
{code}
*Reason :* In *validateMinMax()* fn, when adding to validationItems, the string
should be "config-name" instead of "config_name".
*Fix* : Updated "config_name" to "config-name".
was:
Call to function toConfigurationValidationProblems() breaks for following :
{code}
Traceback (most recent call last):
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 148, in
main(sys.argv)
File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
line 126, in main
result = mpackAdvisor.validateConfigurations()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1149, in validateConfigurations
validationItems = self.getConfigurationsValidationItems()
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1588, in getConfigurationsValidationItems
self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1563, in validateMinMax
validatedItems = self.toConfigurationValidationProblems(validationItems,
configName)
File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
line 1518, in toConfigurationValidationProblems
"config_type": siteName, "config_name": validationProblem["config-name"] }
KeyError: 'config-name'
{code}
*Reason :* In *validateMinMax()* fn, when adding to validationItems, the string
should be "config-name" instead of "config_name".
*Fix* : Updated "config_name" to "config-name".
> Fix the incorrect string from "config_name" to "config-name" in
> mpack_advisor.py
>
>
> Key: AMBARI-24046
> URL: https://issues.apache.org/jira/browse/AMBARI-24046
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: 3.0.0
>
>
> *Issue:*
> Call to function toConfigurationValidationProblems() breaks for following :
> {code}
> Traceback (most recent call last):
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 148, in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/mpack_advisor_wrapper.py",
> line 126, in main
> result = mpackAdvisor.validateConfigurations()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1149, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems()
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1588, in getConfigurationsValidationItems
> self.validateMinMax(items, itemHead, recommendedDefaults, configurations)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1563, in validateMinMax
> validatedItems = self.toConfigurationValidationProblems(validationItems,
> configName)
> File "/var/lib/ambari-server/resources/scripts/../stacks/mpack_advisor.py",
> line 1518, in toConfigurationValidationProblems
> "config_type": siteName, "config_name": validationProblem["config-name"] }
> KeyError: 'config-name'
> {code}
> *Reason :* In *validateMinMax()* fn, when adding to validationItems, the
> string should be "config-name" instead of "config_name".
> *Fix* : Updated "config_name" to "config-name".
--
This message was sent by Atlassian JIRA
[jira] [Created] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
Swapan Shridhar created AMBARI-24046: Summary: Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py Key: AMBARI-24046 URL: https://issues.apache.org/jira/browse/AMBARI-24046 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Swapan Shridhar Assignee: Scott Duan Fix For: 3.0.0 When called, it breaks with: 'se' and 'serviceList' variables not defined. Refer AMBARI-24030 for further details CC [~jluniya] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
[ https://issues.apache.org/jira/browse/AMBARI-24046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-24046: - Description: (was: When called, it breaks with: 'se' and 'serviceList' variables not defined. Refer AMBARI-24030 for further details CC [~jluniya] ) > Fix the incorrect string from "config_name" to "config-name" in > mpack_advisor.py > > > Key: AMBARI-24046 > URL: https://issues.apache.org/jira/browse/AMBARI-24046 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Scott Duan >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24046) Fix the incorrect string from "config_name" to "config-name" in mpack_advisor.py
[ https://issues.apache.org/jira/browse/AMBARI-24046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar reassigned AMBARI-24046: Assignee: Swapan Shridhar (was: Scott Duan) > Fix the incorrect string from "config_name" to "config-name" in > mpack_advisor.py > > > Key: AMBARI-24046 > URL: https://issues.apache.org/jira/browse/AMBARI-24046 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Blocker > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
[ https://issues.apache.org/jira/browse/AMBARI-24044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24044. -- Resolution: Fixed > Widget Browser add/hide functionality is not working correctly > -- > > Key: AMBARI-24044 > URL: https://issues.apache.org/jira/browse/AMBARI-24044 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Widget browser add/hide widget functionality is not working correctly if > widget is included in several widget_layouts as in case of several NameNode > Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24043) Increase outbound message buffer size
[ https://issues.apache.org/jira/browse/AMBARI-24043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503561#comment-16503561 ] Hudson commented on AMBARI-24043: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9414 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9414/]) AMBARI-24043. Increase outbound message buffer size. (mpapirkovskyy) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=17d1d4fb6db27520487fb2de49bd6e34cde2b1bb]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/spring/AgentStompConfig.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java > Increase outbound message buffer size > - > > Key: AMBARI-24043 > URL: https://issues.apache.org/jira/browse/AMBARI-24043 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Make websocket outbound message buffer size configurable to prevent limit > exceeding for large messages (agent configurations stomp updates). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24045) Ambari schedule LDAP user/group sync to occur periodically instead of requiring manual CLI command with admin creds
[ https://issues.apache.org/jira/browse/AMBARI-24045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-24045: - Summary: Ambari schedule LDAP user/group sync to occur periodically instead of requiring manual CLI command with admin creds (was: Ambari schedule LDAP sync to occur periodically instead of requiring manual CLI command with admin creds) > Ambari schedule LDAP user/group sync to occur periodically instead of > requiring manual CLI command with admin creds > --- > > Key: AMBARI-24045 > URL: https://issues.apache.org/jira/browse/AMBARI-24045 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, security >Affects Versions: 2.6.0 > Environment: HDP 2.6 >Reporter: Hari Sekhon >Priority: Major > > Request to add LDAP user/group sync scheduling to occur automatically > periodically (eg. hourly) rather than requiring a manual external CLI ambari > sync-ldap command which prompts for admin creds which is less safe to > schedule (as it would require embedding admin creds somewhere and in secure > audited environments without the generic 'admin' account this would mean some > admin's personal credentials). > Right now Ambari is a sticking point in environments where everything is AD > integrated as it is the only thing that doesn't pick up the new user in a > group - it waits until one can find somebody with the right admin creds to > grant a new admin access they should automatically inherit to Ambari via > group memberships. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24045) Ambari schedule LDAP sync to occur periodically instead of requiring manual CLI command with admin creds
Hari Sekhon created AMBARI-24045: Summary: Ambari schedule LDAP sync to occur periodically instead of requiring manual CLI command with admin creds Key: AMBARI-24045 URL: https://issues.apache.org/jira/browse/AMBARI-24045 Project: Ambari Issue Type: Improvement Components: ambari-server, security Affects Versions: 2.6.0 Environment: HDP 2.6 Reporter: Hari Sekhon Request to add LDAP user/group sync scheduling to occur automatically periodically (eg. hourly) rather than requiring a manual external CLI ambari sync-ldap command which prompts for admin creds which is less safe to schedule (as it would require embedding admin creds somewhere and in secure audited environments without the generic 'admin' account this would mean some admin's personal credentials). Right now Ambari is a sticking point in environments where everything is AD integrated as it is the only thing that doesn't pick up the new user in a group - it waits until one can find somebody with the right admin creds to grant a new admin access they should automatically inherit to Ambari via group memberships. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
[ https://issues.apache.org/jira/browse/AMBARI-24044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24044: Labels: pull-request-available (was: ) > Widget Browser add/hide functionality is not working correctly > -- > > Key: AMBARI-24044 > URL: https://issues.apache.org/jira/browse/AMBARI-24044 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Widget browser add/hide widget functionality is not working correctly if > widget is included in several widget_layouts as in case of several NameNode > Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24043) Increase outbound message buffer size
[ https://issues.apache.org/jira/browse/AMBARI-24043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myroslav Papirkovskyi resolved AMBARI-24043. Resolution: Fixed Merged to trunk > Increase outbound message buffer size > - > > Key: AMBARI-24043 > URL: https://issues.apache.org/jira/browse/AMBARI-24043 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Make websocket outbound message buffer size configurable to prevent limit > exceeding for large messages (agent configurations stomp updates). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
Aleksandr Kovalenko created AMBARI-24044: Summary: Widget Browser add/hide functionality is not working correctly Key: AMBARI-24044 URL: https://issues.apache.org/jira/browse/AMBARI-24044 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Widget browser add/hide widget functionality is not working correctly if widget is included in several widget_layouts as in case of several NameNode Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24042) Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. Error : Failed to check that topic exists
[ https://issues.apache.org/jira/browse/AMBARI-24042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503418#comment-16503418 ] Hudson commented on AMBARI-24042: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9413 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9413/]) AMBARI-24042. Kafka Service Check failed on https enabled/WE cluster (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=1bd7cdb96df0db47c9ce94732051e32fdaa9435b]) * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/KAFKA/0.8.1/package/scripts/service_check.py > Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. > Error : Failed to check that topic exists > -- > > Key: AMBARI-24042 > URL: https://issues.apache.org/jira/browse/AMBARI-24042 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When delete.topic.enable is set to false, ambari service check is not able to > delete the topic and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23945) Infra Solr migration: use less params for migration steps (make it easier to use)
[ https://issues.apache.org/jira/browse/AMBARI-23945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503417#comment-16503417 ] Hudson commented on AMBARI-23945: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9413 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9413/]) AMBARI-23945. Update Solr migration README.md (fix port flag) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7ff9098f78aabbac8915c394a10eb0168813217b]) * (edit) ambari-infra/ambari-infra-solr-client/README.md > Infra Solr migration: use less params for migration steps (make it easier to > use) > - > > Key: AMBARI-23945 > URL: https://issues.apache.org/jira/browse/AMBARI-23945 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24042) Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. Error : Failed to check that topic exists
[ https://issues.apache.org/jira/browse/AMBARI-24042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-24042. Resolution: Fixed > Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. > Error : Failed to check that topic exists > -- > > Key: AMBARI-24042 > URL: https://issues.apache.org/jira/browse/AMBARI-24042 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When delete.topic.enable is set to false, ambari service check is not able to > delete the topic and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24043) Increase outbound message buffer size
[ https://issues.apache.org/jira/browse/AMBARI-24043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24043: Labels: pull-request-available (was: ) > Increase outbound message buffer size > - > > Key: AMBARI-24043 > URL: https://issues.apache.org/jira/browse/AMBARI-24043 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > Make websocket outbound message buffer size configurable to prevent limit > exceeding for large messages (agent configurations stomp updates). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24043) Increase outbound message buffer size
Myroslav Papirkovskyi created AMBARI-24043: -- Summary: Increase outbound message buffer size Key: AMBARI-24043 URL: https://issues.apache.org/jira/browse/AMBARI-24043 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.0 Make websocket outbound message buffer size configurable to prevent limit exceeding for large messages (agent configurations stomp updates). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24042) Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. Error : Failed to check that topic exists
[ https://issues.apache.org/jira/browse/AMBARI-24042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-24042: Labels: pull-request-available (was: ) > Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. > Error : Failed to check that topic exists > -- > > Key: AMBARI-24042 > URL: https://issues.apache.org/jira/browse/AMBARI-24042 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > When delete.topic.enable is set to false, ambari service check is not able to > delete the topic and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24042) Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. Error : Failed to check that topic exists
Attila Magyar created AMBARI-24042: -- Summary: Kafka Service Check failed on https enabled/WE cluster after Ambari Upgrade. Error : Failed to check that topic exists Key: AMBARI-24042 URL: https://issues.apache.org/jira/browse/AMBARI-24042 Project: Ambari Issue Type: Improvement Components: ambari-agent Affects Versions: 2.7.0 Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 2.7.0 When delete.topic.enable is set to false, ambari service check is not able to delete the topic and fails. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24040) Infra Solr start/stop should be idempotent
[ https://issues.apache.org/jira/browse/AMBARI-24040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503134#comment-16503134 ] Hudson commented on AMBARI-24040: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9411 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9411/]) AMBARI-24040. Infra Solr start/stop should be idempotent. (#1473) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2727730f243895762d51a35c09846b612bdd646b]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/infra_solr.py > Infra Solr start/stop should be idempotent > -- > > Key: AMBARI-24040 > URL: https://issues.apache.org/jira/browse/AMBARI-24040 > Project: Ambari > Issue Type: Bug > Components: ambari-infra, ambari-server >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24038) HDFS Metrics shows all blocks as 'Corrupt Replicas'
[ https://issues.apache.org/jira/browse/AMBARI-24038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503135#comment-16503135 ] Hudson commented on AMBARI-24038: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9411 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9411/]) AMBARI-24038 HDFS Metrics shows all blocks as 'Corrupt Replicas'. (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=3bffd3c2c6902481b36ff9d15fb3bd2d0710ea64]) * (edit) ambari-web/app/views/main/service/info/summary/hdfs/widgets.js > HDFS Metrics shows all blocks as 'Corrupt Replicas' > --- > > Key: AMBARI-24038 > URL: https://issues.apache.org/jira/browse/AMBARI-24038 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > *STR* > # Deployed a cluster with HDP-3.0 and Ambari-2.7 (or upgrade from HDP-2.6 to > HDP-3.0) > # Go to HDFS Summary page > # Observe the count of blocks under 'Corrupt Replica' > *Result* > All blocks show as corrupt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24037) Alerts label isn't clickable at the service page after turning on mm for service
[ https://issues.apache.org/jira/browse/AMBARI-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503098#comment-16503098 ] Hudson commented on AMBARI-24037: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9410 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9410/]) AMBARI-24037 Alerts label isn't clickable at the service page after (ababiichuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=009cd2bf675f0ea567a84db2ab681d990f748ffa]) * (edit) ambari-web/app/models/alerts/alert_definition.js > Alerts label isn't clickable at the service page after turning on mm for > service > > > Key: AMBARI-24037 > URL: https://issues.apache.org/jira/browse/AMBARI-24037 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Alerts label isn't clickable at the service page after turning on mm for > service > STR: > # Go to the service page > # Enable mm for service > # Try to click alerts(bell) icon for the current service > Expected: > Will open alerts window > Actual > Nothing happens -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24038) HDFS Metrics shows all blocks as 'Corrupt Replicas'
[ https://issues.apache.org/jira/browse/AMBARI-24038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24038: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk > HDFS Metrics shows all blocks as 'Corrupt Replicas' > --- > > Key: AMBARI-24038 > URL: https://issues.apache.org/jira/browse/AMBARI-24038 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > *STR* > # Deployed a cluster with HDP-3.0 and Ambari-2.7 (or upgrade from HDP-2.6 to > HDP-3.0) > # Go to HDFS Summary page > # Observe the count of blocks under 'Corrupt Replica' > *Result* > All blocks show as corrupt -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24037) Alerts label isn't clickable at the service page after turning on mm for service
[ https://issues.apache.org/jira/browse/AMBARI-24037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-24037: -- Resolution: Fixed Status: Resolved (was: Patch Available) Merged to trunk > Alerts label isn't clickable at the service page after turning on mm for > service > > > Key: AMBARI-24037 > URL: https://issues.apache.org/jira/browse/AMBARI-24037 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Alerts label isn't clickable at the service page after turning on mm for > service > STR: > # Go to the service page > # Enable mm for service > # Try to click alerts(bell) icon for the current service > Expected: > Will open alerts window > Actual > Nothing happens -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24018) Log Search component log url does not work on Ambari web UI
[ https://issues.apache.org/jira/browse/AMBARI-24018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-24018: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Log Search component log url does not work on Ambari web UI > --- > > Key: AMBARI-24018 > URL: https://issues.apache.org/jira/browse/AMBARI-24018 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, ambari-web >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Original Estimate: 48h > Time Spent: 19.7h > Remaining Estimate: 28.3h > > on ambari-web, if you clinck on the Hosts -> select one host -> Logs, you can > see the component list log, and if you click on Open In Log Search, it > navigates you to logsearch UI with proper hash additions. > But if you click on the log itself, there is an another Open in LogSearch > link there, that one uses the old query parameters. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23996) Ambari server installation failing on debian cluster with mysql db
[
https://issues.apache.org/jira/browse/AMBARI-23996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23996:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari server installation failing on debian cluster with mysql db
> --
>
> Key: AMBARI-23996
> URL: https://issues.apache.org/jira/browse/AMBARI-23996
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Ambari server install is failing at db create phase
> {noformat}
> 2018-05-28
> 09:49:40,565|executor.py.165|DEBUG|13917|MainThread|172.27.17.22|executing
> the command='mysql --user=ambaricustomuser --password=bigdatacustom <
> /tmp/createDB.sql'
> 2018-05-28 09:49:40,822|executor.py.165|DEBUG|13917|Thread-165|stdout: mysql:
> [Warning] Using a password on the command line interface can be insecure.
> 2018-05-28 09:49:40,822|executor.py.165|DEBUG|13917|Thread-165|stdout: ERROR
> 1067 (42000) at line 330 in file: '/tmp/Ambari-DDL-MySQL-CREATE.sql': Invalid
> default value for 'update_time'
> 2018-05-28 09:49:40,822|executor.py.128|ERROR|13917|MainThread|command='mysql
> --user=ambaricustomuser --password=bigdatacustom < /tmp/createDB.sql'
> execution failed with exitcode=1
> 2018-05-28 09:49:40,823|executor.py.116|INFO|13917|MainThread|command='mysql
> --user=ambaricustomuser --password=bigdatacustom < /tmp/createDB.sql'
> execution re-try #1
> 2018-05-28 09:49:41,250|executor.py.165|DEBUG|13917|Thread-166|stdout: mysql:
> [Warning] Using a password on the command line interface can be insecure.
> 2018-05-28 09:49:41,250|executor.py.165|DEBUG|13917|Thread-166|stdout: ERROR
> 1067 (42000) at line 330 in file: '/tmp/Ambari-DDL-MySQL-CREATE.sql': Invalid
> default value for 'update_time'
> 2018-05-28 09:49:41,251|executor.py.128|ERROR|13917|MainThread|command='mysql
> --user=ambaricustomuser --password=bigdatacustom < /tmp/createDB.sql'
> execution failed with exitcode=1
> 2018-05-28 09:49:41,252|executor.py.116|INFO|13917|MainThread|command='mysql
> --user=ambaricustomuser --password=bigdatacustom < /tmp/createDB.sql'
> execution re-try #2
> 2018-05-28 09:49:41,561|executor.py.165|DEBUG|13917|Thread-167|stdout: mysql:
> [Warning] Using a password on the command line interface can be insecure.
> 2018-05-28 09:49:41,561|executor.py.165|DEBUG|13917|Thread-167|stdout: ERROR
> 1067 (42000) at line 330 in file: '/tmp/Ambari-DDL-MySQL-CREATE.sql': Invalid
> default value for 'update_time'
> 2018-05-28 09:49:41,561|executor.py.128|ERROR|13917|MainThread|command='mysql
> --user=ambaricustomuser --password=bigdatacustom < /tmp/createDB.sql'
> execution failed with exitcode=1
> {noformat}
> Ambari server version - 2.7.0.0-568
> Mysql version - 5.7.21
> The root cause is (per documentation):
> {noformat}
> NOW() (or its synonyms) can be used as the default value for TIMESTAMP
> columns as well as,
> since MariaDB 10.0.1, DATETIME columns. Before MariaDB 10.0.1, it was only
> possible for a single TIMESTAMP
> column per table to contain the CURRENT_TIMESTAMP as its default.
> {noformat}
> In _user_authentication_ there is another TIMESTAMP column with default value
> of CURRENT_TIMESTAMP called '_create_time_' and this causes the issue in
> older versions (< v10).
> For the sake of consistency the following columns' type should be changed to
> BIGINT (defaulting to 0):
> * users.create_time
> * user_authentication.create_time
> * user_authentication.update_time
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24024) Logsearch: service advisor does not set recommended number of shards
[ https://issues.apache.org/jira/browse/AMBARI-24024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24024: Resolution: Fixed Status: Resolved (was: Patch Available) > Logsearch: service advisor does not set recommended number of shards > > > Key: AMBARI-24024 > URL: https://issues.apache.org/jira/browse/AMBARI-24024 > Project: Ambari > Issue Type: Bug > Components: logsearch >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24035) Autostart is not obeying Maintenance Mode
[ https://issues.apache.org/jira/browse/AMBARI-24035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-24035: Resolution: Fixed Status: Resolved (was: Patch Available) > Autostart is not obeying Maintenance Mode > - > > Key: AMBARI-24035 > URL: https://issues.apache.org/jira/browse/AMBARI-24035 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps to reproduce:- > 1. enable autostart for all the components. > 2. enable Maintenance Mode for a host > 3. reboot the host > 4. wait for the autostart to take an effect > If the maintenance mode is enabled then autostart should not take an effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
