[jira] [Resolved] (AMBARI-23800) Regenerate Keytabs/Reenable security After Ambari Upgrade modifies hadoop.proxyuser.HTTP.hosts to an incorrect value
[ https://issues.apache.org/jira/browse/AMBARI-23800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Molnar resolved AMBARI-23800. Resolution: Fixed > Regenerate Keytabs/Reenable security After Ambari Upgrade modifies > hadoop.proxyuser.HTTP.hosts to an incorrect value > > > Key: AMBARI-23800 > URL: https://issues.apache.org/jira/browse/AMBARI-23800 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jasmeen Kaur >Assignee: Sandor Molnar >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > value of the property hadoop.proxyuser.HTTP.hosts in HDFS is set to an > incorrect value after regenerate keytabs operation or disable and then enable > security is done post Ambari Upgrade to 2.7.0.0 > The value contains hostnames repeated twice with "\" at the end. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21609) Unable to view HDP or HDF stack version.
[
https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473709#comment-16473709
]
Hajime Osako commented on AMBARI-21609:
---
Had similar issue with Spacewalk, and needed to modify not only
[^AMBARI-21609.patch,] but also below:
/var/lib/ambari-server/resources/views/work/ADMIN_VIEW\{2.5.2.0}/scripts/main.js,
around line 8110:
{code:java}
ambari_managed_repositories:
(data.repository_versions[0].operating_systems.length == 0) ? false :
data.repository_versions[0].operating_systems[0].OperatingSystems.ambari_managed_repositories
!== false,
{code}
Also /usr/lib/ambari-server/web/javascripts/app.js
{code:java}
grep 'operating_systems.0.OperatingSystems.ambari_managed_repositories' -n
/usr/lib/ambari-server/web/javascripts/app.js -B 1
60300- //repo.use_redhat_satellite =
item.operating_systems[0].OperatingSystems.ambari_managed_repositories ===
false;
60301: repo.use_redhat_satellite = Em.get(item,
'operating_systems.0.OperatingSystems.ambari_managed_repositories') === false;
--
61595- //stack.use_redhat_satellite =
item.operating_systems[0].OperatingSystems.ambari_managed_repositories ===
false;
61596: stack.use_redhat_satellite = Em.get(item,
'operating_systems.0.OperatingSystems.ambari_managed_repositories') === false;
{code}
> Unable to view HDP or HDF stack version.
>
>
> Key: AMBARI-21609
> URL: https://issues.apache.org/jira/browse/AMBARI-21609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Major
> Fix For: 2.6.1
>
> Attachments: AMBARI-21609.patch
>
>
> The problem is that we get empty "operating_systems" section when the cluster
> is installed through installer AND using RedHat Satellite. Blueprint install
> or installation without using RedHat Satellite does not have this problem.
> The javascript console show an exception after a call to an API endpoint:
> app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of
> undefined
> at Class.
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64)
> at Array.forEach (native)
> at Class.map
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18)
> at Class.newFunc as map
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16)
> at Class.
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33)
> at Array.forEach (native)
> at Class.map
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18)
> at Class.newFunc as map
> (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16)
> at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23820) [Log Search UI] add different options of hostname display
[ https://issues.apache.org/jira/browse/AMBARI-23820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23820: --- Remaining Estimate: 48h (was: 24h) Original Estimate: 48h (was: 24h) > [Log Search UI] add different options of hostname display > - > > Key: AMBARI-23820 > URL: https://issues.apache.org/jira/browse/AMBARI-23820 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Fix For: 2.7.0 > > Original Estimate: 48h > Remaining Estimate: 48h > > Provide a setting to show FQDN or short hostname: > FQDN: logsearch-demo-1.c.pramod-thangali.internal > Short Hostname: logsearch-demo-1 > If shortname is preferred then show: FQDN.split(“.”)[0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23757) [Logsearch UI] Component filter 'All' not refreshing logs after selecting an individual component
[ https://issues.apache.org/jira/browse/AMBARI-23757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Tobias updated AMBARI-23757: --- Resolution: Fixed Status: Resolved (was: Patch Available) > [Logsearch UI] Component filter 'All' not refreshing logs after selecting an > individual component > - > > Key: AMBARI-23757 > URL: https://issues.apache.org/jira/browse/AMBARI-23757 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 24.5h > Remaining Estimate: 0h > > [Logsearch UI] Component filter 'All' not refreshing logs after selecting an > individual component > STR: > 1. Login to logsearch portal and select a valid date range > 2. From the Component filter drop down, select an individual component e.g > Ambari-agent > 3. Now ambari-agent logs are filtered and displayed > 4. Now select the 'All' from the drop down > 5. The logs table should now refresh with logs from all components, but fails > to refresh and displays only previously selected logs. User need to refresh > the page or navigate away and come back to refresh the table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23097) Log Search: knox proxy support
[ https://issues.apache.org/jira/browse/AMBARI-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473617#comment-16473617 ] Hudson commented on AMBARI-23097: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9240 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9240/]) AMBARI-23097. Upgrade KNOX version to 1.0.0 for Log Search docker dev (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=de78779996b6f3fe4222abdc3a4d345845f44b88]) * (edit) ambari-logsearch/docker/Dockerfile * (edit) ambari-logsearch/docker/knox/logsearch/1.0.0/service.xml > Log Search: knox proxy support > -- > > Key: AMBARI-23097 > URL: https://issues.apache.org/jira/browse/AMBARI-23097 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >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: 0.5h > Remaining Estimate: 0h > > Add knox proxy support and update knox docker env with that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23822) Infra Solr: Migration script does not backup/restore all of the cores
[ https://issues.apache.org/jira/browse/AMBARI-23822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473609#comment-16473609 ] Hudson commented on AMBARI-23822: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9239 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9239/]) AMBARI-23822. Infra Solr: Migration script does not backup/restore all (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=a3c06c4495f40783b3630f8c5aa5f85137646001]) * (edit) ambari-logsearch/docker/knox/logsearch/1.0.0/service.xml * (edit) ambari-infra/ambari-infra-solr-client/src/main/python/migrationHelper.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/command_commons.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/templates/infra-solr-security.json.j2 * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/collection.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/migrate.py AMBARI-23822. Infra Solr: Add restore support if index is on HDFS. (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=c17b9f8d093447274ac2a9b90f705f3b5a943b17]) * (edit) ambari-infra/ambari-infra-solr-client/src/main/python/migrationHelper.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/command_commons.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/collection.py * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/metainfo.xml > Infra Solr: Migration script does not backup/restore all of the cores > - > > Key: AMBARI-23822 > URL: https://issues.apache.org/jira/browse/AMBARI-23822 > 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)
