[jira] [Resolved] (AMBARI-23934) Next button not enabled in Enable Namenode HA Wizard
[
https://issues.apache.org/jira/browse/AMBARI-23934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23934.
-
Resolution: Done
> Next button not enabled in Enable Namenode HA Wizard
>
>
> Key: AMBARI-23934
> URL: https://issues.apache.org/jira/browse/AMBARI-23934
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Next Button in Create Checkpoint page is not enabled while enabling Namenode
> HA.
> !Screen Shot 2018-05-18 at 10.48.50 PM.png|thumbnail!
> Commands executed:
> {code:bash}
> sjanardhan@HW15613 ~/Developer/backup/qe-ambariautomation # ssh -i
> ~/Documents/ok.txt r...@ctr-e138-1518143905142-318323-01-03.hwx.site
>
> The authenticity of host 'ctr-e138-1518143905142-318323-01-03.hwx.site
> (172.27.65.207)' can't be established.
> ECDSA key fingerprint is SHA256:gkYtB2sQzz5MPaeVeyHHMuvDK4h9ebp6b5krS3IP8eI.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added
> 'ctr-e138-1518143905142-318323-01-03.hwx.site,172.27.65.207' (ECDSA) to
> the list of known hosts.
> Last login: Fri May 18 01:56:54 2018
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> [root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -safemode enter'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Safe mode is ON
> [root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -saveNamespace'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Save namespace successful
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538040#comment-16538040
]
Ishan Bhatt commented on AMBARI-24187:
--
Moving it out to 2.7.1
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 2.7.1
>
>
> It was noticed in the bug bash that there were issues with label names and
> defaults. In an effort to make them easier to read and fix the issues
> identified, the following labels, default values, and spacing before ':'
> changes need to be made. Please make the wizard look just like the text below:
> {code}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538041#comment-16538041
]
Ishan Bhatt commented on AMBARI-24199:
--
Moving it out to 2.7.1
> Fix Atlas HA support in Ambari via blueprint deployment
> ---
>
> Key: AMBARI-24199
> URL: https://issues.apache.org/jira/browse/AMBARI-24199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Robert Nettleton
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently deploying Atlas in HA mode via blueprint is not possible due to
> property
> [{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
> being set by Blueprint Processor, need to remove the property from being
> processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24187:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 2.7.1
>
>
> It was noticed in the bug bash that there were issues with label names and
> defaults. In an effort to make them easier to read and fix the issues
> identified, the following labels, default values, and spacing before ':'
> changes need to be made. Please make the wizard look just like the text below:
> {code}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24199:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Fix Atlas HA support in Ambari via blueprint deployment
> ---
>
> Key: AMBARI-24199
> URL: https://issues.apache.org/jira/browse/AMBARI-24199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Robert Nettleton
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently deploying Atlas in HA mode via blueprint is not possible due to
> property
> [{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
> being set by Blueprint Processor, need to remove the property from being
> processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24004) [Logsearch UI] Add hosts link in log index filter popup is not working
[ https://issues.apache.org/jira/browse/AMBARI-24004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24004: - Resolution: Fixed Status: Resolved (was: Patch Available) > [Logsearch UI] Add hosts link in log index filter popup is not working > -- > > Key: AMBARI-24004 > URL: https://issues.apache.org/jira/browse/AMBARI-24004 > 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: 0.5h > Remaining Estimate: 0h > > Add hosts link in log index filter popup is not working. > STR > 1. Login to Logsearch portal > 2. Click to filter log index from menu, select a valid cluster from the drop > down > 3. Try to add custom filters for host, user should be able to add custom > filter index for additional hosts by clicking add hosts link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538039#comment-16538039 ] Ishan Bhatt commented on AMBARI-24118: -- Moving it out to 2.7.1 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24118: - Fix Version/s: (was: 2.7.0) 2.7.1 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23976) Ambari changes required for YARN are missing
[ https://issues.apache.org/jira/browse/AMBARI-23976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23976: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari changes required for YARN are missing > > > Key: AMBARI-23976 > URL: https://issues.apache.org/jira/browse/AMBARI-23976 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23976.patch, AMBARI-23976.patch, > AMBARI-23976.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24204) Ambari upgrade should set storm kerberos config to correct value
[ https://issues.apache.org/jira/browse/AMBARI-24204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24204: - Fix Version/s: (was: 2.7.0) 2.7.1 > Ambari upgrade should set storm kerberos config to correct value > > > Key: AMBARI-24204 > URL: https://issues.apache.org/jira/browse/AMBARI-24204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23005) Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating slave component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23005: - Resolution: Fixed Status: Resolved (was: Patch Available) > Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating > slave component dependencies > - > > Key: AMBARI-23005 > URL: https://issues.apache.org/jira/browse/AMBARI-23005 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Di Li >Assignee: Di Li >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating > slave component dependencies. > Error printed by Ambari server > Error occured in stack advisor. > Error details: 'StackServiceComponents' > 14 Feb 2018 12:32:54,260 INFO [ambari-client-thread-94] > StackAdvisorRunner:164 - Advisor script stderr: Traceback (most recent call > last): > File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 167, > in > main(sys.argv) > File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 108, > in main > result = stackAdvisor.recommendComponentLayout(services, hosts) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 608, in recommendComponentLayout > layoutRecommendations = self.createComponentLayoutRecommendations(services, > hosts) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 794, in createComponentLayoutRecommendations > filteredHosts = self.getFilteredHostsBasedOnDependencies(services, > component, hostsList, hostsComponentsMap) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 928, in getFilteredHostsBasedOnDependencies > componentName = component["StackServiceComponents"]["component_name"] > KeyError: 'StackServiceComponents' > 14 Feb 2018 12:32:54,260 WARN [ambari-client-thread-94] > AbstractResourceProvider:97 - Error occured during recommendation > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: > Stack Advisor reported an error. Exit Code: 2. Error: KeyError: > 'StackServiceComponents' > StdOut file: /var/run/ambari-server/stack-recommendations/32/stackadvisor.out > StdErr file: /var/run/ambari-server/stack-recommendations/32/stackadvisor.err > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.processLogs(StackAdvisorRunner.java:146) > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:86) > at > org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:345) > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:132) > at > org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296) > at > org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97) > at > org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:45) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:76) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:166) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:130) > at > org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60) > at > com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205) > at > com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75) > at >
[jira] [Updated] (AMBARI-23522) Revert AMBARI-23385
[ https://issues.apache.org/jira/browse/AMBARI-23522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23522: - Resolution: Fixed Status: Resolved (was: Patch Available) > Revert AMBARI-23385 > --- > > Key: AMBARI-23522 > URL: https://issues.apache.org/jira/browse/AMBARI-23522 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24204) Ambari upgrade should set storm kerberos config to correct value
[ https://issues.apache.org/jira/browse/AMBARI-24204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538036#comment-16538036 ] Ishan Bhatt commented on AMBARI-24204: -- Moving it out to 2.7.1 > Ambari upgrade should set storm kerberos config to correct value > > > Key: AMBARI-24204 > URL: https://issues.apache.org/jira/browse/AMBARI-24204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538035#comment-16538035 ] Ishan Bhatt commented on AMBARI-23817: -- Moving it out to 2.7.1 > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.1 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23817: - Fix Version/s: (was: 2.7.0) 2.7.1 > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.1 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24224) Error in persisting web client state at ambari-server in editing a widget of HDFS
[ https://issues.apache.org/jira/browse/AMBARI-24224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24224: - Resolution: Fixed Status: Resolved (was: Patch Available) > Error in persisting web client state at ambari-server in editing a widget of > HDFS > -- > > Key: AMBARI-24224 > URL: https://issues.apache.org/jira/browse/AMBARI-24224 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > STR > # Login as admin to Ambari > # Install a cluster with HDFS, ZK and AMS > # Go to Services / HDFS / Metrics and edit one of the widgets (for instance > change the name of the widget) > # Create a new user with 'Cluster Operator' role > # Logout and login with the newly created user > # Try to edit the previously edit widget > The action will fail due to an authorization issue (403 is thrown). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538033#comment-16538033 ] Ishan Bhatt commented on AMBARI-24192: -- Moving it out to 2.7.1 > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24229) Prevent Configuration Changes During Keytab Regeneration in an Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24229.
--
Resolution: Fixed
> Prevent Configuration Changes During Keytab Regeneration in an Upgrade
> --
>
> Key: AMBARI-24229
> URL: https://issues.apache.org/jira/browse/AMBARI-24229
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Kavan Suresh
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> Certain configuration changes should be avoided when regenerating keytab
> files during different scenarios.
> For example, existing non-Kerberos configurations should not be changed
> during the regenerate keytabs operation performed during an upgrade. However
> it is necessary for Kerberos identity-related configurations (such as keytab
> file paths and principal names) to be added and updated; as well as allow for
> new Kerberos-related configurations to be added.
> To allow for this, a new _update configuration policy_ value has been added
> to the set of directives (*_config_update_policy_*) allowed when issuing a
> call to regenerate keytab files. This directive replaces the less flexible
> *_ignore_config_updates_* directive which only allows a user to enable or
> disable the ability for the operation to change configurations. The values
> allowed for *_config_update_policy_* are as follows:
> * {{none}} - No configurations will be updated
> * {{identities_only}} - New and updated configurations related to Kerberos
> identity information - principal, keytab file, and auth-to-local rule
> properties
> * {{new_and_identities}} - Only new configurations declared by the Kerberos
> descriptor and stack advisor as well as the identity-related changes
> * {{all}} - All configuration changes
> During an upgrade, the _update configuration policy_ is set to
> {{new_and_identities}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24250) Create Checkpoint page stuck while Enabling HA on Namenode
[
https://issues.apache.org/jira/browse/AMBARI-24250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24250:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Create Checkpoint page stuck while Enabling HA on Namenode
> --
>
> Key: AMBARI-24250
> URL: https://issues.apache.org/jira/browse/AMBARI-24250
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Ambari UI stuck at Manual Steps Required: Create Checkpoint on NameNode page
> while Enabling HA after performing the manual steps.
> {code}
> [root@ctr-e138-1518143905142-378399-01-04 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -safemode enter'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Safe mode is ON
> [root@ctr-e138-1518143905142-378399-01-04 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -saveNamespace'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Save namespace successful
> {code}
> The stat result of file /etc/security/keytabs/ambari.server.keytab, looks
> like the final change in the file occured at 2018-07-04 05:53:52.
> {code:java}
> [root@ctr-e138-1518143905142-395357-01-02 ~]# stat
> /etc/security/keytabs/ambari.server.keytab
> File: ‘/etc/security/keytabs/ambari.server.keytab’
> Size: 333 Blocks: 8 IO Block: 4096 regular file
> Device: fd12h/64786d Inode: 16390172Links: 1
> Access: (0400/-r) Uid: ( 1803/agentslava) Gid: ( 1803/agentslava)
> Access: 2018-07-04 03:01:39.282093801 +
> Modify: 2018-07-04 03:01:39.282093801 +
> Change: 2018-07-04 05:53:52.333709142 +
> Birth: -
> {code}
> From the ambari server logs at the same time stamp:
> {code:java}
> 2018-07-04 05:53:52,054 INFO [Server Action Executor Worker 586]
> KerberosServerAction:411 - Processing identities...
> 2018-07-04 05:53:52,322 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:111 - Updated the owner of the keytab file at
> /etc/security/keytabs/ambari.server.keytab to null
> 2018-07-04 05:53:52,323 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:125 - Updated the group of the keytab file at
> /etc/security/keytabs/ambari.server.keytab to null
> 2018-07-04 05:53:52,337 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:142 - Updated the access mode of the keytab file
> at /etc/security/keytabs/ambari.server.keytab to owner:'r' and group:'null'
> 2018-07-04 05:53:52,352 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:111 - Updated the owner of the keytab file at
> /etc/security/keytabs/ams-monitor.keytab to cstm-ams
> 2018-07-04 05:53:52,371 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:125 - Updated the group of the keytab file at
> /etc/security/keytabs/ams-monitor.keytab to hadoop
> 2018-07-04 05:53:52,387 INFO [Server Action Executor Worker 586]
> FinalizeKerberosServerAction:142 - Updated the access mode of the keytab file
> at /etc/security/keytabs/ams-monitor.keytab to owner:'r' and group:''
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24192: - Fix Version/s: (was: 2.7.0) 2.7.1 > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538032#comment-16538032 ] Ishan Bhatt commented on AMBARI-23925: -- Moving it out to 2.7.1 > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.1 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23921) If Kerberos is enabled, then stack upgrade prerequisite check should ensure the KDC admin credential is persisted
[ https://issues.apache.org/jira/browse/AMBARI-23921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23921: - Resolution: Fixed Status: Resolved (was: Patch Available) > If Kerberos is enabled, then stack upgrade prerequisite check should ensure > the KDC admin credential is persisted > - > > Key: AMBARI-23921 > URL: https://issues.apache.org/jira/browse/AMBARI-23921 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Labels: kerberos, pull-request-available, upgrade > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > If Kerberos is enabled and Ambari is managing Kerberos identities, then the > stack upgrade prerequisite check should ensure that the KDC admin credential > is stored in the Ambari persisted credential store. > # The Ambari credential store must be set up (ambari-server setup-security, > option #2) > # The KDC administrator credential is stored in the Ambari credential store > (persisted) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23925: - Fix Version/s: (was: 2.7.0) 2.7.1 > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.1 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23785) Download client configs fails at Oozie client with AttributeError
[
https://issues.apache.org/jira/browse/AMBARI-23785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23785:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Download client configs fails at Oozie client with AttributeError
> -
>
> Key: AMBARI-23785
> URL: https://issues.apache.org/jira/browse/AMBARI-23785
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> - Deploy cluster for ambari-270 and HDP-3.0
> - Download client configs for the cluster
> - This fails with below error
> {code}
> {
> status: 500,
> message: "org.apache.ambari.server.controller.spi.SystemException: Execution
> of "ambari-python-wrap
> /var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/OOZIE_CLIENT2729746438603000677-configuration.json
> /var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1. java.lang.Throwable: 2018-04-30
> 21:20:41,087 - Stack Feature Version Info: Cluster Stack=3.0, Command
> Stack=None, Command Version=None -> 3.0 2018-04-30 21:20:41,109 - Using
> hadoop conf dir: /usr/hdp/3.0.0.0-1279/hadoop/conf 2018-04-30 21:20:41,209 -
> Directory['/var/lib/ambari-server/data/tmp'] \{'create_parents': True}
> 2018-04-30 21:20:41,293 - XmlConfig['oozie-site.xml'] {} Traceback (most
> recent call last): File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_client.py",
> line 74, in OozieClient().execute() File
> "/usr/lib/ambari-server/lib/resource_management/libraries/script/script.py",
> line 353, in execute method(env) File
> "/usr/lib/ambari-server/lib/resource_management/libraries/script/script.py",
> line 1093, in generate_configs Directory(conf_tmp_dir, action="delete") File
> "/usr/lib/ambari-server/lib/resource_management/core/base.py", line 166, in
> __init__ self.env.run() File
> "/usr/lib/ambari-server/lib/resource_management/core/environment.py", line
> 160, in run self.run_action(resource, action) File
> "/usr/lib/ambari-server/lib/resource_management/core/environment.py", line
> 124, in run_action provider_action() File
> "/usr/lib/ambari-server/lib/resource_management/libraries/providers/xml_config.py",
> line 60, in action_create xml_config_dest_file_path =
> os.path.join(xml_config_provider_config_dir, filename) File
> "/usr/lib64/python2.7/posixpath.py", line 77, in join elif path == '' or
> path.endswith('/'): AttributeError: 'NoneType' object has no attribute
> 'endswith' "
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-23026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23026: - Fix Version/s: (was: 2.7.0) 2.7.1 > WEB type alerts authentication in Kerberos secured cluster > -- > > Key: AMBARI-23026 > URL: https://issues.apache.org/jira/browse/AMBARI-23026 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.2, trunk, 2.6.2 > Environment: Ambari 2.5.2 > Hortonworks HDP-2.5.3.0-37 >Reporter: David F. Quiroga >Assignee: Robert Levas >Priority: Minor > Fix For: 2.7.1 > > > In a Kerberized cluster some web endpoints (App Timeline Web UI, > ResourceManger Web UI, etc.) require authentication. Any Ambari alerts > checking those endpoints must then be able to authenticate. > This was addressed in AMBARI-9586, however the default principal and keytab > used in the alerts.json is that of the "bare" SPNEGO principal > HTTP/_HOST@REALM. > My understanding is that the HTTP service principal is used to authenticate > users to a service, not used to authenticate to another service. > 1. Since most endpoints involved are Web UI, would it be more appropriate to > use the smokeuser in the alerts? > 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed > many access denied from HTTP user. [This > post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html] > provided some direction as to where those requests were coming from. We have > updated the ResourceManger Web UI alert definition to use > cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and > this has resolved the initial HTTP access denied. > Would it also be advisable to make the change in the other secure Web UI > alert definitions? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-23026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538029#comment-16538029 ] Ishan Bhatt commented on AMBARI-23026: -- Moving it out to 2.7.1 > WEB type alerts authentication in Kerberos secured cluster > -- > > Key: AMBARI-23026 > URL: https://issues.apache.org/jira/browse/AMBARI-23026 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.2, trunk, 2.6.2 > Environment: Ambari 2.5.2 > Hortonworks HDP-2.5.3.0-37 >Reporter: David F. Quiroga >Assignee: Robert Levas >Priority: Minor > Fix For: 2.7.1 > > > In a Kerberized cluster some web endpoints (App Timeline Web UI, > ResourceManger Web UI, etc.) require authentication. Any Ambari alerts > checking those endpoints must then be able to authenticate. > This was addressed in AMBARI-9586, however the default principal and keytab > used in the alerts.json is that of the "bare" SPNEGO principal > HTTP/_HOST@REALM. > My understanding is that the HTTP service principal is used to authenticate > users to a service, not used to authenticate to another service. > 1. Since most endpoints involved are Web UI, would it be more appropriate to > use the smokeuser in the alerts? > 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed > many access denied from HTTP user. [This > post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html] > provided some direction as to where those requests were coming from. We have > updated the ResourceManger Web UI alert definition to use > cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and > this has resolved the initial HTTP access denied. > Would it also be advisable to make the change in the other secure Web UI > alert definitions? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23890) [Logsearch UI] Column headers are missing in service logs tabular view
[ https://issues.apache.org/jira/browse/AMBARI-23890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23890: - Fix Version/s: (was: 2.7.0) 2.7.1 > [Logsearch UI] Column headers are missing in service logs tabular view > -- > > Key: AMBARI-23890 > URL: https://issues.apache.org/jira/browse/AMBARI-23890 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Minor > Fix For: 2.7.1 > > > Column headers are missing in service logs tabular view. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. Click on Tabular view of logs > 4. Column headers should be displayed similar to the tabular view of Audit > logs page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23890) [Logsearch UI] Column headers are missing in service logs tabular view
[ https://issues.apache.org/jira/browse/AMBARI-23890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538031#comment-16538031 ] Ishan Bhatt commented on AMBARI-23890: -- Moving it out to 2.7.1 > [Logsearch UI] Column headers are missing in service logs tabular view > -- > > Key: AMBARI-23890 > URL: https://issues.apache.org/jira/browse/AMBARI-23890 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Minor > Fix For: 2.7.1 > > > Column headers are missing in service logs tabular view. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. Click on Tabular view of logs > 4. Column headers should be displayed similar to the tabular view of Audit > logs page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24227) Add Namespace: Hive Metastore fails to start because NN is in safemode
[
https://issues.apache.org/jira/browse/AMBARI-24227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538027#comment-16538027
]
Ishan Bhatt commented on AMBARI-24227:
--
Moving it out to 2.7.1
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> --
>
> Key: AMBARI-24227
> URL: https://issues.apache.org/jira/browse/AMBARI-24227
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> {code}
> 18/06/29 10:43:41 INFO retry.RetryInvocationHandler:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RetriableException):
> org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot modify ACL
> entries on /warehouse/tablespace/external/hive. Name node is in safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> NamenodeHostName:
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1441)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.modifyAclEntries(FSNamesystem.java:7112)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.modifyAclEntries(NameNodeRpcServer.java:2045)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.modifyAclEntries(ClientNamenodeProtocolServerSideTranslatorPB.java:1442)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot
> modify ACL entries on /warehouse/tablespace/external/hive. Name node is in
> safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24231) Adding additional jars in classpath of ambari views.
[ https://issues.apache.org/jira/browse/AMBARI-24231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24231: - Fix Version/s: (was: 2.7.0) 2.7.1 > Adding additional jars in classpath of ambari views. > > > Key: AMBARI-24231 > URL: https://issues.apache.org/jira/browse/AMBARI-24231 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24212) Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox
[ https://issues.apache.org/jira/browse/AMBARI-24212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538026#comment-16538026 ] Ishan Bhatt commented on AMBARI-24212: -- Moving it out to 2.7.1 > Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox > > > Key: AMBARI-24212 > URL: https://issues.apache.org/jira/browse/AMBARI-24212 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > STR: > 1) Create hdfs and yarn Config Groups > 2) Override some hdfs-site and yarn-site configs > 3) Now add Knox > After adding knox, Hdfs, Yarn and MR2 have restart indicators but they should > not have them > On deleting knox, this issue was not reproduced > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24231) Adding additional jars in classpath of ambari views.
[ https://issues.apache.org/jira/browse/AMBARI-24231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538028#comment-16538028 ] Ishan Bhatt commented on AMBARI-24231: -- Moving it out to 2.7.1 > Adding additional jars in classpath of ambari views. > > > Key: AMBARI-24231 > URL: https://issues.apache.org/jira/browse/AMBARI-24231 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24227) Add Namespace: Hive Metastore fails to start because NN is in safemode
[
https://issues.apache.org/jira/browse/AMBARI-24227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24227:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> --
>
> Key: AMBARI-24227
> URL: https://issues.apache.org/jira/browse/AMBARI-24227
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> {code}
> 18/06/29 10:43:41 INFO retry.RetryInvocationHandler:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RetriableException):
> org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot modify ACL
> entries on /warehouse/tablespace/external/hive. Name node is in safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> NamenodeHostName:
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1441)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.modifyAclEntries(FSNamesystem.java:7112)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.modifyAclEntries(NameNodeRpcServer.java:2045)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.modifyAclEntries(ClientNamenodeProtocolServerSideTranslatorPB.java:1442)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot
> modify ACL entries on /warehouse/tablespace/external/hive. Name node is in
> safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24211:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like "Your Ambari Server has not been configured to download LZO
> and install it" and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538025#comment-16538025
]
Ishan Bhatt commented on AMBARI-24211:
--
Moving it out to 2.7.1
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like "Your Ambari Server has not been configured to download LZO
> and install it" and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24207) Python unit test failure on 2.7.6
[
https://issues.apache.org/jira/browse/AMBARI-24207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538024#comment-16538024
]
Ishan Bhatt commented on AMBARI-24207:
--
Moving it out to 2.7.1
> Python unit test failure on 2.7.6
> -
>
> Key: AMBARI-24207
> URL: https://issues.apache.org/jira/browse/AMBARI-24207
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.1
>
>
> Python unit tests fail on Python 2.7.6, because
> [SSLContext|https://docs.python.org/2/library/ssl.html#ssl-contexts] was only
> added in 2.7.9.
> {noformat:title=https://builds.apache.org/job/Ambari-trunk-Commit/9543/consoleText}
> ERROR: test_ldap_sync_ssl (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 7804, in test_ldap_sync_ssl
> sync_ldap(options)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupSecurity.py",
> line 405, in sync_ldap
> raise FatalException(1, err)
> FatalException: "Fatal exception: Sync event creation failed. Error details:
> 'module' object has no attribute 'SSLContext', exit code 1"
> ERROR: test_get_ssl_context (TestServerUtils.TestServerUtils)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestServerUtils.py",
> line 124, in test_get_ssl_context
> context = get_ssl_context(properties)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverUtils.py",
> line 274, in get_ssl_context
> context = ssl.SSLContext(protocol)
> AttributeError: 'module' object has no attribute 'SSLContext'
> {noformat}
> CC [~rlevas]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24205) TestHeartbeatHandler.testComponents is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538023#comment-16538023
]
Ishan Bhatt commented on AMBARI-24205:
--
Moving it out to 2.7.1
> TestHeartbeatHandler.testComponents is flaky
>
>
> Key: AMBARI-24205
> URL: https://issues.apache.org/jira/browse/AMBARI-24205
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> {{TestHeartbeatHandler.testComponents}} is failing ~15% of the time.
> {noformat}
> [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 8, Time elapsed:
> 36.768 s <<< FAILURE! - in org.apache.ambari.server.agent.TestHeartbeatHandler
> [ERROR] testComponents(org.apache.ambari.server.agent.TestHeartbeatHandler)
> Time elapsed: 1.203 s <<< FAILURE!
> java.lang.AssertionError: expected:<{HDFS={NAMENODE=MASTER}}> but was:<{}>
> at
> org.apache.ambari.server.agent.TestHeartbeatHandler.testComponents(TestHeartbeatHandler.java:1352)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24205) TestHeartbeatHandler.testComponents is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24205:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> TestHeartbeatHandler.testComponents is flaky
>
>
> Key: AMBARI-24205
> URL: https://issues.apache.org/jira/browse/AMBARI-24205
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> {{TestHeartbeatHandler.testComponents}} is failing ~15% of the time.
> {noformat}
> [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 8, Time elapsed:
> 36.768 s <<< FAILURE! - in org.apache.ambari.server.agent.TestHeartbeatHandler
> [ERROR] testComponents(org.apache.ambari.server.agent.TestHeartbeatHandler)
> Time elapsed: 1.203 s <<< FAILURE!
> java.lang.AssertionError: expected:<{HDFS={NAMENODE=MASTER}}> but was:<{}>
> at
> org.apache.ambari.server.agent.TestHeartbeatHandler.testComponents(TestHeartbeatHandler.java:1352)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24212) Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox
[ https://issues.apache.org/jira/browse/AMBARI-24212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24212: - Fix Version/s: (was: 2.7.0) 2.7.1 > Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox > > > Key: AMBARI-24212 > URL: https://issues.apache.org/jira/browse/AMBARI-24212 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > STR: > 1) Create hdfs and yarn Config Groups > 2) Override some hdfs-site and yarn-site configs > 3) Now add Knox > After adding knox, Hdfs, Yarn and MR2 have restart indicators but they should > not have them > On deleting knox, this issue was not reproduced > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24207) Python unit test failure on 2.7.6
[
https://issues.apache.org/jira/browse/AMBARI-24207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24207:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Python unit test failure on 2.7.6
> -
>
> Key: AMBARI-24207
> URL: https://issues.apache.org/jira/browse/AMBARI-24207
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.1
>
>
> Python unit tests fail on Python 2.7.6, because
> [SSLContext|https://docs.python.org/2/library/ssl.html#ssl-contexts] was only
> added in 2.7.9.
> {noformat:title=https://builds.apache.org/job/Ambari-trunk-Commit/9543/consoleText}
> ERROR: test_ldap_sync_ssl (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 7804, in test_ldap_sync_ssl
> sync_ldap(options)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupSecurity.py",
> line 405, in sync_ldap
> raise FatalException(1, err)
> FatalException: "Fatal exception: Sync event creation failed. Error details:
> 'module' object has no attribute 'SSLContext', exit code 1"
> ERROR: test_get_ssl_context (TestServerUtils.TestServerUtils)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestServerUtils.py",
> line 124, in test_get_ssl_context
> context = get_ssl_context(properties)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverUtils.py",
> line 274, in get_ssl_context
> context = ssl.SSLContext(protocol)
> AttributeError: 'module' object has no attribute 'SSLContext'
> {noformat}
> CC [~rlevas]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24120) cluster version is in invalid state
[
https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538021#comment-16538021
]
Ishan Bhatt commented on AMBARI-24120:
--
Moving it out to 2.7.1
> cluster version is in invalid state
> ---
>
> Key: AMBARI-24120
> URL: https://issues.apache.org/jira/browse/AMBARI-24120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-06-15 at 9.40.16 AM.png
>
>
> Steps to reproduce:
> 1. Make sure you have stable cluster
> 2. add a new host - and make sure it fails with the installation at the end
> step.
> 3. Now go to "stack and versions" screen - you will see the cluster in kind
> of messed up state.
> Usually customers may not see the 3rd step right after adding the host and if
> they observe after few days then it gives very wrong impression that cluster
> is it messed up state though it is not.
> Output for host_version
> {noformat}
> select * from host_version where host_id in ( 301, 551) and repo_version_id =
> 102
> '901','102','301','CURRENT'
> '1052','102','551','OUT_OF_SYNC'
> 2nd row is problematic one.
> {noformat}
> Workaround:
> Remove the host and add it again and make sure installation is not failing
> or
> change the status of host_version to 'CURRENT'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[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 ] Ishan Bhatt updated AMBARI-24047: - Fix Version/s: (was: 2.7.0) 2.7.1 > 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.1 > > > 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] [Updated] (AMBARI-24120) cluster version is in invalid state
[
https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24120:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> cluster version is in invalid state
> ---
>
> Key: AMBARI-24120
> URL: https://issues.apache.org/jira/browse/AMBARI-24120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-06-15 at 9.40.16 AM.png
>
>
> Steps to reproduce:
> 1. Make sure you have stable cluster
> 2. add a new host - and make sure it fails with the installation at the end
> step.
> 3. Now go to "stack and versions" screen - you will see the cluster in kind
> of messed up state.
> Usually customers may not see the 3rd step right after adding the host and if
> they observe after few days then it gives very wrong impression that cluster
> is it messed up state though it is not.
> Output for host_version
> {noformat}
> select * from host_version where host_id in ( 301, 551) and repo_version_id =
> 102
> '901','102','301','CURRENT'
> '1052','102','551','OUT_OF_SYNC'
> 2nd row is problematic one.
> {noformat}
> Workaround:
> Remove the host and add it again and make sure installation is not failing
> or
> change the status of host_version to 'CURRENT'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24173) UI Deploy: Cannot deploy cluster with Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24173:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> UI Deploy: Cannot deploy cluster with Config Groups
> ---
>
> Key: AMBARI-24173
> URL: https://issues.apache.org/jira/browse/AMBARI-24173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> UI Deploy: Cannot deploy cluster with Config Groups
> STR:
> 1) Install cluster via UI
> 2) On Customize services page, create a Config Group and add some hosts to it
> 3) Click Deploy
>
> {code}
> 2018-06-22 23:46:28,174 ERROR [ambari-client-thread-505]
> AbstractResourceProvider:353 - Caught AmbariException when modifying a
> resource
> org.apache.ambari.server.AmbariException: Config group not found, clusterName
> = cl1, groupId = 1529709098419
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:683)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:76)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:351)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:251)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:312)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
> at
> org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:46)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ConfigGroupService.updateConfigGroup(ConfigGroupService.java:186)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
>
[jira] [Commented] (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:comment-tabpanel=16538019#comment-16538019 ] Ishan Bhatt commented on AMBARI-24047: -- Moving it out to 2.7.1 > 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.1 > > > 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] [Commented] (AMBARI-23970) Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails to start because DN's are not up
[
https://issues.apache.org/jira/browse/AMBARI-23970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538018#comment-16538018
]
Ishan Bhatt commented on AMBARI-23970:
--
Moving it out to 2.7.1
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
>
> Key: AMBARI-23970
> URL: https://issues.apache.org/jira/browse/AMBARI-23970
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
> {code}
> { "RemoteException": {"exception": "IOException", "javaClassName":
> "java.io.IOException", "message": "Failed to find datanode, suggest to
> check cluster health. excludeDatanodes=null" }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24173) UI Deploy: Cannot deploy cluster with Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538022#comment-16538022
]
Ishan Bhatt commented on AMBARI-24173:
--
Moving it out to 2.7.1
> UI Deploy: Cannot deploy cluster with Config Groups
> ---
>
> Key: AMBARI-24173
> URL: https://issues.apache.org/jira/browse/AMBARI-24173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> UI Deploy: Cannot deploy cluster with Config Groups
> STR:
> 1) Install cluster via UI
> 2) On Customize services page, create a Config Group and add some hosts to it
> 3) Click Deploy
>
> {code}
> 2018-06-22 23:46:28,174 ERROR [ambari-client-thread-505]
> AbstractResourceProvider:353 - Caught AmbariException when modifying a
> resource
> org.apache.ambari.server.AmbariException: Config group not found, clusterName
> = cl1, groupId = 1529709098419
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:683)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:76)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:351)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:251)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:312)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
> at
> org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:46)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.ConfigGroupService.updateConfigGroup(ConfigGroupService.java:186)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
> at
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
> at
>
[jira] [Commented] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538015#comment-16538015
]
Ishan Bhatt commented on AMBARI-23655:
--
Moving it out to 2.7.1
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23655
> URL: https://issues.apache.org/jira/browse/AMBARI-23655
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
>
> It seems for restart all service operation we do not wait for namenode to
> leave safemode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23708) Sometimes Active and StandBy status is not displayed for default namespace
[ https://issues.apache.org/jira/browse/AMBARI-23708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23708: - Fix Version/s: (was: 2.7.0) 2.7.1 > Sometimes Active and StandBy status is not displayed for default namespace > -- > > Key: AMBARI-23708 > URL: https://issues.apache.org/jira/browse/AMBARI-23708 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > Active and StandBy status is not displayed for default namespace . > On a cluster with namespaces, go to hdfs summary page. For the default > namespace, Active and StandBy status for namenodes is missing. It appears for > a short duration and again disappears -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23970) Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails to start because DN's are not up
[
https://issues.apache.org/jira/browse/AMBARI-23970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23970:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
>
> Key: AMBARI-23970
> URL: https://issues.apache.org/jira/browse/AMBARI-23970
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
> {code}
> { "RemoteException": {"exception": "IOException", "javaClassName":
> "java.io.IOException", "message": "Failed to find datanode, suggest to
> check cluster health. excludeDatanodes=null" }
> }
> {code}
--
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 ] Ishan Bhatt updated AMBARI-23820: - Fix Version/s: (was: 2.7.0) 2.7.1 > [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.1 > > Original Estimate: 48h > Time Spent: 24h > Remaining Estimate: 24h > > 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] [Commented] (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:comment-tabpanel=16538017#comment-16538017 ] Ishan Bhatt commented on AMBARI-23820: -- Moving it out to 2.7.1 > [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.1 > > Original Estimate: 48h > Time Spent: 24h > Remaining Estimate: 24h > > 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] [Commented] (AMBARI-23708) Sometimes Active and StandBy status is not displayed for default namespace
[ https://issues.apache.org/jira/browse/AMBARI-23708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538016#comment-16538016 ] Ishan Bhatt commented on AMBARI-23708: -- Moving it out to 2.7.1 > Sometimes Active and StandBy status is not displayed for default namespace > -- > > Key: AMBARI-23708 > URL: https://issues.apache.org/jira/browse/AMBARI-23708 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > Active and StandBy status is not displayed for default namespace . > On a cluster with namespaces, go to hdfs summary page. For the default > namespace, Active and StandBy status for namenodes is missing. It appears for > a short duration and again disappears -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23468) UI does not render all the configs on selecting non default config group
[ https://issues.apache.org/jira/browse/AMBARI-23468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538012#comment-16538012 ] Ishan Bhatt commented on AMBARI-23468: -- Moving it out to 2.7.1 > UI does not render all the configs on selecting non default config group > > > Key: AMBARI-23468 > URL: https://issues.apache.org/jira/browse/AMBARI-23468 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > UI does not render all the configs on selecting non default config group > > STR: > 1) Create a Config Group > 2) On services page -> Config tab and all the configs are rendered properly > 2) Now select the config group and all the configs do not load properly > UI is not making the call to get all the config groups when we select non > default CG > > [http://:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*|http://172.27.16.212:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23612) Wizards do not load correctly when opening from different browser
[ https://issues.apache.org/jira/browse/AMBARI-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538014#comment-16538014 ] Ishan Bhatt commented on AMBARI-23612: -- Moving it out to 2.7.1 > Wizards do not load correctly when opening from different browser > - > > Key: AMBARI-23612 > URL: https://issues.apache.org/jira/browse/AMBARI-23612 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 > Environment: ambari-server --hash > 5507ee62ae19676fbf35b889b602648a54185289 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot > 2018-04-17 at 2.17.56 PM.png > > > Wizards do not load when opening from different browser > STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. > While in the middle of the wizard, try to open it in another browser > Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538013#comment-16538013
]
Ishan Bhatt commented on AMBARI-23478:
--
Moving it out to 2.7.1
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23478) YARN Cluster CPU Usage Graph Always Shows High CPU Usage
[
https://issues.apache.org/jira/browse/AMBARI-23478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23478:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> YARN Cluster CPU Usage Graph Always Shows High CPU Usage
>
>
> Key: AMBARI-23478
> URL: https://issues.apache.org/jira/browse/AMBARI-23478
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: image-2018-03-19-20-26-44-325.png,
> image-2018-03-19-20-27-19-160.png
>
>
> h3. ISSUE
> In Ambari, YARN's Cluster CPU widget always shows relatively high CPU usage,
> when NodeManager in a cluster is more than one.
> !image-2018-03-19-20-26-44-325.png|thumbnail!
> !image-2018-03-19-20-27-19-160.png|thumbnail!
> (started another node at around 19:00)
> h3. REPRODUCE STEPS
> # Install a cluster with one NodeManager and AMS.
> # Confirm "Cluster CPU" widget looks OK
> # Add one more node with NodeManager, and wait for a while
> h3. INVESTIGATION
> AMS side looks OK
> {code}
> curl -s -k http://sandbox-hdp.hortonworks.com:6188/ws/v1/timeline/metrics -G
> --data-urlencode metricNames=cpu_idle._sum --data-urlencode appId=NODEMANAGER
> --data-urlencode startTime=1521454794 --data-urlencode endTime=1521455394
> --data-urlencode precision=MINUTES
> ...
> {
> "metrics": [
> {
> "appid": "nodemanager",
> "metadata": {},
> "metricname": "cpu_idle._sum",
> "metrics": {
> "152145480": 198.990001,
> "152145510": 192.56
> },
> "starttime": 152145480,
> "timestamp": 152145480
> }
> ]
> }
> {code}
> But via Ambari, cpu_idle._sum becomes *{color:#d04437}100 times{color}*
> smaller
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_idle._sum[1521454950,152140,15]'
> ...(snip)...
> "metrics" : {
> "cpu" : {
> "cpu_idle._sum" : [
> [
> 1.8687,
> 1521454950
> ],
> [
> 1.9843,
> 1521454980
> ],
> [
> 1.9,
> 1521455010
> ],
> [
> 1.9844,
> 1521455040
> ],
> [
> 1.8925,
> 1521455070
> ],
> ...(snip)...
> {code}
> Somehow 'cpu_idle._sum' is always wrong for this Widget:
> {code}
> curl -s -k -u admin:admin
> http://sandbox-hdp.hortonworks.com:8080/api/v1/clusters/Sandbox/services/YARN/components/NODEMANAGER
> -G --data-urlencode
> 'fields=metrics/cpu/cpu_nice._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._avg[1521196167,1521199767,15],metrics/cpu/cpu_wio._sum[1521196167,1521199767,15],metrics/cpu/cpu_idle._sum[1521196167,1521199767,15],metrics/cpu/cpu_user._sum[1521196167,1521199767,15],metrics/cpu/cpu_system._sum[1521196167,1521199767,15]'
> -o ./ambari_NODEMANAGER_metrics.json
> [root@sandbox-hdp ~]# grep -E -B1 '"cpu_|152145'
> ambari_NODEMANAGER_metrics.json | grep -vE -- '(--|\],)'
> "cpu" : {
> "cpu_idle._avg" : [
> 85.549998,
> 1521199500
> "cpu_idle._sum" : [
> 1.7106, <<< need to multiply 100
> 1521199500
> "cpu_nice._sum" : [
> 0.0,
> 1521199500
> "cpu_system._sum" : [
> 21.902,
> 1521199500
> "cpu_user._sum" : [
> 6.666,
> 1521199500
> "cpu_wio._sum" : [
> 0.2,
> 1521199500
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23655:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23655
> URL: https://issues.apache.org/jira/browse/AMBARI-23655
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
>
> It seems for restart all service operation we do not wait for namenode to
> leave safemode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23468) UI does not render all the configs on selecting non default config group
[ https://issues.apache.org/jira/browse/AMBARI-23468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23468: - Fix Version/s: (was: 2.7.0) 2.7.1 > UI does not render all the configs on selecting non default config group > > > Key: AMBARI-23468 > URL: https://issues.apache.org/jira/browse/AMBARI-23468 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > UI does not render all the configs on selecting non default config group > > STR: > 1) Create a Config Group > 2) On services page -> Config tab and all the configs are rendered properly > 2) Now select the config group and all the configs do not load properly > UI is not making the call to get all the config groups when we select non > default CG > > [http://:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*|http://172.27.16.212:8080/api/v1/clusters/cl1/config_groups?ConfigGroup/tag.in(HDFS,RANGER_KMS,AMBARI_METRICS,RANGER,YARN,ZOOKEEPER,HIVE,KAFKA,ATLAS,DRUID,TEZ,AMBARI_INFRA_SOLR,HBASE,SQOOP,STORM,KNOX,MAPREDUCE2,SPARK2)=*] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23612) Wizards do not load correctly when opening from different browser
[ https://issues.apache.org/jira/browse/AMBARI-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23612: - Fix Version/s: (was: 2.7.0) 2.7.1 > Wizards do not load correctly when opening from different browser > - > > Key: AMBARI-23612 > URL: https://issues.apache.org/jira/browse/AMBARI-23612 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 > Environment: ambari-server --hash > 5507ee62ae19676fbf35b889b602648a54185289 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-04-17 at 2.14.29 PM.png, Screen Shot > 2018-04-17 at 2.17.56 PM.png > > > Wizards do not load when opening from different browser > STR: Launch any wizard like Add New HDFS Namespace or Move master wizard. > While in the middle of the wizard, try to open it in another browser > Verified the Move master wizard with ambari 262 build and it works fine there -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23399) PasswordUtilsTest fails if running as 'root'
[ https://issues.apache.org/jira/browse/AMBARI-23399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23399. -- Resolution: Fixed > PasswordUtilsTest fails if running as 'root' > > > Key: AMBARI-23399 > URL: https://issues.apache.org/jira/browse/AMBARI-23399 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > If > org.apache.ambari.server.utils.PasswordUtilsTest.shouldReadDefaultPasswordIfPasswordPropertyIsPasswordFilePathButItIsNotReadable() > is running by _root_ user the File.setReadable does not work -> the build > will fail. > We should consider using > java.nio.file.attribute.PosixFilePermissions > I'll disable this use case until it's fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23341) Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor
[ https://issues.apache.org/jira/browse/AMBARI-23341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23341: - Fix Version/s: (was: 2.7.0) 2.7.1 > Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor > - > > Key: AMBARI-23341 > URL: https://issues.apache.org/jira/browse/AMBARI-23341 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.1 > > > There is a bug in ambari (possibly in UI) which prevents adding > yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor. > This bug should be fixed first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23341) Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor
[ https://issues.apache.org/jira/browse/AMBARI-23341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538011#comment-16538011 ] Ishan Bhatt commented on AMBARI-23341: -- Moving it out to 2.7.1 > Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor > - > > Key: AMBARI-23341 > URL: https://issues.apache.org/jira/browse/AMBARI-23341 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.1 > > > There is a bug in ambari (possibly in UI) which prevents adding > yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor. > This bug should be fixed first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23464) Debian9 is not shown on UI Install Wizard Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-23464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23464. -- Resolution: Fixed > Debian9 is not shown on UI Install Wizard Select Version page > - > > Key: AMBARI-23464 > URL: https://issues.apache.org/jira/browse/AMBARI-23464 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Dhanya Balasundaran >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Debian9 is not coming up on UI where as it should be for Ambari-2.7.0 > h2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23299) Intermittent failure in TestAgentStompResponses
[
https://issues.apache.org/jira/browse/AMBARI-23299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-23299.
--
Resolution: Fixed
> Intermittent failure in TestAgentStompResponses
> ---
>
> Key: AMBARI-23299
> URL: https://issues.apache.org/jira/browse/AMBARI-23299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.0
>
>
> Intermittent unit test failure, probably due to use of threads:
> {noformat}
> FAIL: test_alert_definitions_update_and_delete
> (TestAgentStompResponses.TestAgentStompResponses)
> ...
> -u'uuid':
> u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'}],
> ?
> -
> +u'uuid':
> u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'},
> + {u'clusterId': 2,
> +u'componentName': u'HBASE_MASTER',
> +u'definitionId': 1,
> +u'description': u'This alert is triggered if
> the HBase master processes cannot be confirmed to be up and listening on the
> network for the configured critical threshold, given in seconds.',
> +u'enabled': True,
> +u'ignore_host': False,
> +u'interval': 1,
> +u'label': u'HBase Master Process',
> +u'name': u'hbase_master_process',
> +u'scope': u'ANY',
> +u'serviceName': u'HBASE',
> +u'source': {u'default_port': 6,
> +u'reporting': {u'critical':
> {u'text': u'Connection failed: {0} to {1}:{2}',
> +
> u'value': 5.0},
> + u'ok': {u'text':
> u'TCP OK - {0:.3f}s response on port {1}'},
> + u'warning':
> {u'text': u'TCP OK - {0:.3f}s response on port {1}',
> +
> u'value': 1.5}},
> +u'type': u'PORT',
> +u'uri':
> u'{{hbase-site/hbase.master.port}}'},
> +u'uuid':
> u'ff73ead7-13b4-43ea-a747-d230f17bf230'}],
> u'clusterName': u'cl1',
> ...
> {noformat}
> https://builds.apache.org/job/Ambari-trunk-Commit/8872/
> https://builds.apache.org/job/Ambari-trunk-Commit/8863/
> https://builds.apache.org/job/Ambari-trunk-Commit/8862/
> https://builds.apache.org/job/Ambari-trunk-Commit/8858/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538009#comment-16538009 ] Ishan Bhatt commented on AMBARI-23298: -- Moving it out to 2.7.1 > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23298 > URL: https://issues.apache.org/jira/browse/AMBARI-23298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23327) Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes forever
[ https://issues.apache.org/jira/browse/AMBARI-23327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538010#comment-16538010 ] Ishan Bhatt commented on AMBARI-23327: -- Moving it out to 2.7.1 > Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes > forever > --- > > Key: AMBARI-23327 > URL: https://issues.apache.org/jira/browse/AMBARI-23327 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23298) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23298: - Fix Version/s: (was: 2.7.0) 2.7.1 > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23298 > URL: https://issues.apache.org/jira/browse/AMBARI-23298 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23327) Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes forever
[ https://issues.apache.org/jira/browse/AMBARI-23327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23327: - Fix Version/s: (was: 2.7.0) 2.7.1 > Regression : Adding Atlas Metadata server, Hiveserver2 on an host takes > forever > --- > > Key: AMBARI-23327 > URL: https://issues.apache.org/jira/browse/AMBARI-23327 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23273) Hosts page does not unselect hosts on navigating away from the page
[ https://issues.apache.org/jira/browse/AMBARI-23273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23273: - Fix Version/s: (was: 2.7.0) 2.7.1 > Hosts page does not unselect hosts on navigating away from the page > --- > > Key: AMBARI-23273 > URL: https://issues.apache.org/jira/browse/AMBARI-23273 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: JaySenSharma >Priority: Major > Fix For: 2.7.1 > > > Hosts page does not unselect hosts when navigating away from the page > STR: > -> Go to hosts page and select some hosts > -> Now navigate away and come back to hosts page. Previously selected hosts > are still selected > This causes Selected Hosts in the drop down to be disabled. > Refreshing the page works and it clears the selection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23273) Hosts page does not unselect hosts on navigating away from the page
[ https://issues.apache.org/jira/browse/AMBARI-23273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538008#comment-16538008 ] Ishan Bhatt commented on AMBARI-23273: -- Moving it out to 2.7.1 > Hosts page does not unselect hosts on navigating away from the page > --- > > Key: AMBARI-23273 > URL: https://issues.apache.org/jira/browse/AMBARI-23273 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: JaySenSharma >Priority: Major > Fix For: 2.7.1 > > > Hosts page does not unselect hosts when navigating away from the page > STR: > -> Go to hosts page and select some hosts > -> Now navigate away and come back to hosts page. Previously selected hosts > are still selected > This causes Selected Hosts in the drop down to be disabled. > Refreshing the page works and it clears the selection -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23272) Server Error while Bulk Deleting Hosts
[
https://issues.apache.org/jira/browse/AMBARI-23272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23272:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Server Error while Bulk Deleting Hosts
> --
>
> Key: AMBARI-23272
> URL: https://issues.apache.org/jira/browse/AMBARI-23272
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Server Error while Bulk Deleting Hosts
> STR:
> 1) Create a config group and override a property
> 2) Bulk delete some hosts from UI that are in the config group. Deletion of
> Host fails with.
> UI does not handle this failure and the wizard is stuck
>
> {code}
> 16 Mar 2018 20:26:03,339 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
> Unable to add configurations to alert definition command
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=
>
> 16 Mar 2018 20:26:03,317 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
> Unable to add configurations to alert definition command
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:438)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:188)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:172)
> at
> org.apache.ambari.server.agent.AlertDefinitionCommand.addConfigs(AlertDefinitionCommand.java:141)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:536)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:495)
> at
> org.apache.ambari.server.events.listeners.alerts.AlertHashInvalidationListener.onEvent(AlertHashInvalidationListener.java:127)
> at sun.reflect.GeneratedMethodAccessor593.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
> at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
> at
> com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
> at
> com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> 16 Mar 2018 20:26:03,464 ERROR [ambari-client-thread-8491]
> ContainerResponse:419 - The RuntimeException could not be mapped to a
> response, re-throwing to the HTTP container
> javax.persistence.RollbackException: Transaction "rolled back" because
> transaction was set to RollbackOnly.
> at
> org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:143)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:386)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:383)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.deleteResourcesAuthorized(HostResourceProvider.java:383)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.deleteResources(AbstractAuthorizedResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.deleteResources(ClusterControllerImpl.java:337)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.delete(PersistenceManagerImpl.java:132)
> at
> org.apache.ambari.server.api.handlers.DeleteHandler.persist(DeleteHandler.java:48)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
>
[jira] [Commented] (AMBARI-23272) Server Error while Bulk Deleting Hosts
[
https://issues.apache.org/jira/browse/AMBARI-23272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538007#comment-16538007
]
Ishan Bhatt commented on AMBARI-23272:
--
Moving it out to 2.7.1
> Server Error while Bulk Deleting Hosts
> --
>
> Key: AMBARI-23272
> URL: https://issues.apache.org/jira/browse/AMBARI-23272
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Server Error while Bulk Deleting Hosts
> STR:
> 1) Create a config group and override a property
> 2) Bulk delete some hosts from UI that are in the config group. Deletion of
> Host fails with.
> UI does not handle this failure and the wizard is stuck
>
> {code}
> 16 Mar 2018 20:26:03,339 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
> Unable to add configurations to alert definition command
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=
>
> 16 Mar 2018 20:26:03,317 WARN [pool-4-thread-1] AlertDefinitionHash:538 -
> Unable to add configurations to alert definition command
> org.apache.ambari.server.HostNotFoundException: Host not found,
> hostname=
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:438)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:188)
> at
> org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:172)
> at
> org.apache.ambari.server.agent.AlertDefinitionCommand.addConfigs(AlertDefinitionCommand.java:141)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:536)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionHash.enqueueAgentCommands(AlertDefinitionHash.java:495)
> at
> org.apache.ambari.server.events.listeners.alerts.AlertHashInvalidationListener.onEvent(AlertHashInvalidationListener.java:127)
> at sun.reflect.GeneratedMethodAccessor593.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74)
> at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322)
> at
> com.google.common.eventbus.AsyncEventBus.access$001(AsyncEventBus.java:34)
> at
> com.google.common.eventbus.AsyncEventBus$1.run(AsyncEventBus.java:117)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
>
> 16 Mar 2018 20:26:03,464 ERROR [ambari-client-thread-8491]
> ContainerResponse:419 - The RuntimeException could not be mapped to a
> response, re-throwing to the HTTP container
> javax.persistence.RollbackException: Transaction "rolled back" because
> transaction was set to RollbackOnly.
> at
> org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:143)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:386)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$4.invoke(HostResourceProvider.java:383)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.deleteResourcesAuthorized(HostResourceProvider.java:383)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.deleteResources(AbstractAuthorizedResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.deleteResources(ClusterControllerImpl.java:337)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.delete(PersistenceManagerImpl.java:132)
> at
> org.apache.ambari.server.api.handlers.DeleteHandler.persist(DeleteHandler.java:48)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
>
[jira] [Resolved] (AMBARI-23253) Allow Ambari Server to Setup SSO for the entire stack using the CLI
[
https://issues.apache.org/jira/browse/AMBARI-23253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-23253.
--
Resolution: Fixed
> Allow Ambari Server to Setup SSO for the entire stack using the CLI
> ---
>
> Key: AMBARI-23253
> URL: https://issues.apache.org/jira/browse/AMBARI-23253
> Project: Ambari
> Issue Type: Epic
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: SSO, sso
> Fix For: 2.7.0
>
>
> Today enabling SSO requires visiting each component that supports SSO and
> adding configuration entries to each. This task is to enable a single entry
> point via the Ambari CLI to configure SSO for each service that supports it.
> Changes to the ambari-server setup-sso CLI are needed allow configuration of
> all SSO-capable services using that single CLI. This facility can be used to
> enable, disable, and reconfigure SSO integration.
> *Proposed implementation:*
> Services are to declare they support SSO integration by indicating in the
> service's \{{metainfo.xml}} file as follows:
> {code}
>
> true
> config-type/sso.enabled.property
>
> {code}
> The stack/service advisor will be used to retrieve the recommended
> configurations needed by a service to set up SSO integration. A special stack
> advisor action will be added to ensure only SSO-related recommendations are
> returned upon request. The new action name is
> "{{recommend-configurations-for-sso}}". Ambari (or common) SSO information
> will be provided to the stack advisor via the input data under the label
> "sso-configuration". This information may be used by the stack advisor when
> creating recommendations.
> Ambari will store details on which services should be enabled for SSO so it
> _knows_ how to behave when SSO integration is enabled and new services are
> added. This data will be stored within Ambari's configuration data under the
> category of {{sso-configuration}}. The list of services to have SSO
> integration turned on will be stored in the property named
> {{ambari.sso.enabled_services}}. The value will be a comma-delimited list of
> service names, or "{{*}}" to indicate all services that support SSO
> integration.
> The Ambari REST API entry point for installed services
> ({{/api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME}}) is to be enhance
> by adding the following properties:
> * *\{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> * *\{{sso_integration_enabled}}* - Indicates whether the service is
> configured for SSO integration or not
> * *\{{sso_integration_desired}}* - Indicates whether the service is chosen
> for SSO integration or not
> The Ambari REST API entry point for stack services
> ({{/api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME}}) is
> to be enhance by adding the following properties:
> * *\{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> When producing a list of installed services that support SSO integration in
> the CLI, the Ambari REST API is to be used to query for the relevant service
> names. Once the user selects the set of services to enable SSO for (or all),
> the Ambari REST API is to be used to set the value of the Ambari
> configuration \{{sso-configuration/ambari.sso.enabled_services}}. Upon
> setting this, logic is triggered in the backend to query the stack advisor
> for SSO-related configuration recommendations which will be automatically
> applied. This will potentially yield new configuration versions and require
> services to be manually restarted.
> When adding new services, the
> \{{sso-configuration/ambari.sso.enabled_services}} value is to be checked to
> see if the new service is on the list of services to have SSO integration
> enabled. If so, and the service has a SSO descriptor, its configuration will
> be updated as needed before the service is started.
> In a Blueprint scenario, it is expected that the user first sets up Ambari
> for SSO integration using the {{ambari-server setup-sso}} CLI. The Blueprint
> is expected to set the relevant properties needed to enable SSO integration
> per service. However, if SSO details were set up, the stack advisor may
> recommend relevant changes which may be applied depending on the Blueprint
> settings.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23244) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538005#comment-16538005 ] Ishan Bhatt commented on AMBARI-23244: -- Moving it out to 2.7.1 > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23244 > URL: https://issues.apache.org/jira/browse/AMBARI-23244 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23244) Pass full stack version in recommendation request for 2.7
[ https://issues.apache.org/jira/browse/AMBARI-23244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23244: - Fix Version/s: (was: 2.7.0) 2.7.1 > Pass full stack version in recommendation request for 2.7 > - > > Key: AMBARI-23244 > URL: https://issues.apache.org/jira/browse/AMBARI-23244 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23198) Ambari Agent unit test cannot be run on Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-23198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538004#comment-16538004
]
Ishan Bhatt commented on AMBARI-23198:
--
Moving it out to 2.7.1
> Ambari Agent unit test cannot be run on Python 2.6
> --
>
> Key: AMBARI-23198
> URL: https://issues.apache.org/jira/browse/AMBARI-23198
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> Ambari Agent unit tests cannot be run on centos6 (Python version: 2.6.6).
> {noformat:title=mvn -am -pl ambari-agent -Drat.skip clean test}
> Traceback (most recent call last):
> File "unitTests.py", line 188, in
> main()
> File "unitTests.py", line 142, in main
> suite = all_tests_suite(test_mask)
> File "unitTests.py", line 130, in all_tests_suite
> suite = unittest.TestLoader().loadTestsFromNames(tests_list)
> File "/usr/lib64/python2.6/unittest.py", line 612, in loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "ambari-agent/src/test/python/ambari_agent/TestAgentStompResponses.py", line
> 28, in
> from BaseStompServerTestCase import BaseStompServerTestCase
> File
> "ambari-agent/src/test/python/ambari_agent/BaseStompServerTestCase.py", line
> 41, in
> from coilmq.server.socket_server import StompServer, StompRequestHandler,
> ThreadedStompServer
> File "ambari-common/src/test/python/coilmq/server/socket_server.py", line
> 16, in
> from coilmq.engine import StompEngine
> File "ambari-common/src/test/python/coilmq/engine.py", line 3, in
> from coilmq.protocol import STOMP10
> File "ambari-common/src/test/python/coilmq/protocol/__init__.py", line 253
> SUPPORTED_VERSIONS = {'1.0', '1.1'}
>^
> SyntaxError: invalid syntax
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23198) Ambari Agent unit test cannot be run on Python 2.6
[
https://issues.apache.org/jira/browse/AMBARI-23198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23198:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Ambari Agent unit test cannot be run on Python 2.6
> --
>
> Key: AMBARI-23198
> URL: https://issues.apache.org/jira/browse/AMBARI-23198
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> Ambari Agent unit tests cannot be run on centos6 (Python version: 2.6.6).
> {noformat:title=mvn -am -pl ambari-agent -Drat.skip clean test}
> Traceback (most recent call last):
> File "unitTests.py", line 188, in
> main()
> File "unitTests.py", line 142, in main
> suite = all_tests_suite(test_mask)
> File "unitTests.py", line 130, in all_tests_suite
> suite = unittest.TestLoader().loadTestsFromNames(tests_list)
> File "/usr/lib64/python2.6/unittest.py", line 612, in loadTestsFromNames
> suites = [self.loadTestsFromName(name, module) for name in names]
> File "/usr/lib64/python2.6/unittest.py", line 575, in loadTestsFromName
> module = __import__('.'.join(parts_copy))
> File
> "ambari-agent/src/test/python/ambari_agent/TestAgentStompResponses.py", line
> 28, in
> from BaseStompServerTestCase import BaseStompServerTestCase
> File
> "ambari-agent/src/test/python/ambari_agent/BaseStompServerTestCase.py", line
> 41, in
> from coilmq.server.socket_server import StompServer, StompRequestHandler,
> ThreadedStompServer
> File "ambari-common/src/test/python/coilmq/server/socket_server.py", line
> 16, in
> from coilmq.engine import StompEngine
> File "ambari-common/src/test/python/coilmq/engine.py", line 3, in
> from coilmq.protocol import STOMP10
> File "ambari-common/src/test/python/coilmq/protocol/__init__.py", line 253
> SUPPORTED_VERSIONS = {'1.0', '1.1'}
>^
> SyntaxError: invalid syntax
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)
[ https://issues.apache.org/jira/browse/AMBARI-23079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23079: - Fix Version/s: (was: 2.7.0) 2.7.1 > Log Feeder: support to use load balancer for Solr API (not only cloud client) > -- > > Key: AMBARI-23079 > URL: https://issues.apache.org/jira/browse/AMBARI-23079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23119) Added component does not show up immediately in the Host Detail Page
[ https://issues.apache.org/jira/browse/AMBARI-23119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-23119. -- Resolution: Fixed > Added component does not show up immediately in the Host Detail Page > > > Key: AMBARI-23119 > URL: https://issues.apache.org/jira/browse/AMBARI-23119 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23079) Log Feeder: support to use load balancer for Solr API (not only cloud client)
[ https://issues.apache.org/jira/browse/AMBARI-23079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538003#comment-16538003 ] Ishan Bhatt commented on AMBARI-23079: -- Moving it out to 2.7.1 > Log Feeder: support to use load balancer for Solr API (not only cloud client) > -- > > Key: AMBARI-23079 > URL: https://issues.apache.org/jira/browse/AMBARI-23079 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23075) Log Search: Zookeeper tick time is too low for Config API
[ https://issues.apache.org/jira/browse/AMBARI-23075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23075: - Fix Version/s: (was: 2.7.0) 2.7.1 > Log Search: Zookeeper tick time is too low for Config API > - > > Key: AMBARI-23075 > URL: https://issues.apache.org/jira/browse/AMBARI-23075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23076) Log Search configurable zookeeper usage for config API (zookeeper implementation)
[ https://issues.apache.org/jira/browse/AMBARI-23076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23076: - Fix Version/s: (was: 2.7.0) 2.7.1 > Log Search configurable zookeeper usage for config API (zookeeper > implementation) > - > > Key: AMBARI-23076 > URL: https://issues.apache.org/jira/browse/AMBARI-23076 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23076) Log Search configurable zookeeper usage for config API (zookeeper implementation)
[ https://issues.apache.org/jira/browse/AMBARI-23076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537999#comment-16537999 ] Ishan Bhatt commented on AMBARI-23076: -- Moving it out to 2.7.1 > Log Search configurable zookeeper usage for config API (zookeeper > implementation) > - > > Key: AMBARI-23076 > URL: https://issues.apache.org/jira/browse/AMBARI-23076 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20864) FE: Update User Management View to Manage New Data
[ https://issues.apache.org/jira/browse/AMBARI-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537997#comment-16537997 ] Ishan Bhatt commented on AMBARI-20864: -- Moving it out to 2.7.1 > FE: Update User Management View to Manage New Data > --- > > Key: AMBARI-20864 > URL: https://issues.apache.org/jira/browse/AMBARI-20864 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Yusaku Sako >Priority: Major > Fix For: 2.7.1 > > > Update the User Management view to manage new data associated with user > accounts. > Each user account will have the following _general_ data fields: > * username (essentially the unique user id) > * active/inactive > * locked/unlocked (read-only, based on whether the number of failed > authentication attempts exceeds some configured value or not) > * display name (the name to show in user interfaces or messages) > * local username (the username to use when using Views or services) > Each user account will include a set of authentication _sources_: LOCAL, > LDAP, KERBEROS, PAM, etc... Each source, though linked to the same user can > be managed separately and specifically depending on the type: > *LOCAL* > * One only one LOCAL authentication source is allowed. > * Ambari Administrators should be able to add and modify this source by > setting the "local" password. > * The user should be able to change the password (if the source is available) > *LDAP* > * Multiple LDAP sources may be available - used to represent the same user > found in multiple places in the LDAP tree (or forrest). See > [AMBARI-15554|https://issues.apache.org/jira/browse/AMBARI-15554]. > * Ambari Administrators should be able to add and modify this source by > setting the user's distinguished name (DN). However, the admin should be > warned that incorrectly setting this value will result in authentication > failures. > * Adding entries for this source should be available if and only Ambari is > configured to allow LDAP authentication > * A user may not alter these entries > *KERBEROS* > * Multiple KERBEROS sources may be available - used to represent the same > user with multiple Kerberos identities. > * Ambari Administrators should be able to add and modify this source by > setting the user's principal name. However, the admin should be warned that > incorrectly setting this value will result in authentication failures. > * Adding entries for this source should be available if and only Ambari is > configured to allow Kerberos authentication > * A user may not alter these entries > *PAM* > * Not yet fully supported, more information is needed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23077) LogFeeder: create socket input
[ https://issues.apache.org/jira/browse/AMBARI-23077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538000#comment-16538000 ] Ishan Bhatt commented on AMBARI-23077: -- Moving it out to 2.7.1 > LogFeeder: create socket input > -- > > Key: AMBARI-23077 > URL: https://issues.apache.org/jira/browse/AMBARI-23077 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23075) Log Search: Zookeeper tick time is too low for Config API
[ https://issues.apache.org/jira/browse/AMBARI-23075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537998#comment-16537998 ] Ishan Bhatt commented on AMBARI-23075: -- Moving it out to 2.7.1 > Log Search: Zookeeper tick time is too low for Config API > - > > Key: AMBARI-23075 > URL: https://issues.apache.org/jira/browse/AMBARI-23075 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23077) LogFeeder: create socket input
[ https://issues.apache.org/jira/browse/AMBARI-23077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23077: - Fix Version/s: (was: 2.7.0) 2.7.1 > LogFeeder: create socket input > -- > > Key: AMBARI-23077 > URL: https://issues.apache.org/jira/browse/AMBARI-23077 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20864) FE: Update User Management View to Manage New Data
[ https://issues.apache.org/jira/browse/AMBARI-20864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20864: - Fix Version/s: (was: 2.7.0) 2.7.1 > FE: Update User Management View to Manage New Data > --- > > Key: AMBARI-20864 > URL: https://issues.apache.org/jira/browse/AMBARI-20864 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Yusaku Sako >Priority: Major > Fix For: 2.7.1 > > > Update the User Management view to manage new data associated with user > accounts. > Each user account will have the following _general_ data fields: > * username (essentially the unique user id) > * active/inactive > * locked/unlocked (read-only, based on whether the number of failed > authentication attempts exceeds some configured value or not) > * display name (the name to show in user interfaces or messages) > * local username (the username to use when using Views or services) > Each user account will include a set of authentication _sources_: LOCAL, > LDAP, KERBEROS, PAM, etc... Each source, though linked to the same user can > be managed separately and specifically depending on the type: > *LOCAL* > * One only one LOCAL authentication source is allowed. > * Ambari Administrators should be able to add and modify this source by > setting the "local" password. > * The user should be able to change the password (if the source is available) > *LDAP* > * Multiple LDAP sources may be available - used to represent the same user > found in multiple places in the LDAP tree (or forrest). See > [AMBARI-15554|https://issues.apache.org/jira/browse/AMBARI-15554]. > * Ambari Administrators should be able to add and modify this source by > setting the user's distinguished name (DN). However, the admin should be > warned that incorrectly setting this value will result in authentication > failures. > * Adding entries for this source should be available if and only Ambari is > configured to allow LDAP authentication > * A user may not alter these entries > *KERBEROS* > * Multiple KERBEROS sources may be available - used to represent the same > user with multiple Kerberos identities. > * Ambari Administrators should be able to add and modify this source by > setting the user's principal name. However, the admin should be warned that > incorrectly setting this value will result in authentication failures. > * Adding entries for this source should be available if and only Ambari is > configured to allow Kerberos authentication > * A user may not alter these entries > *PAM* > * Not yet fully supported, more information is needed > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20859) Improve User Account Management Within Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-20859: - Fix Version/s: (was: 2.7.0) 2.7.1 > Improve User Account Management Within Ambari > - > > Key: AMBARI-20859 > URL: https://issues.apache.org/jira/browse/AMBARI-20859 > Project: Ambari > Issue Type: Epic > Components: ambari-server, ambari-web >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Labels: authentication, pull-request-available, security, > user_management > Fix For: 2.7.1 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > As of Ambari 2.4, user management is confusing and tends to lead to > inconsistent results during synchronization and authentication. With the > addition of new mechanisms such as Kerberos and PAM, this will only get > worse. Therefore, there is a need to rework how Ambari manages users to > ensure that new authentication facilities are easily integrated. > The following problems need to be solved: > * *Case-sensitivity* > Some authentication sources are case sensitive and some are not. Ambari > inconsistently handles the case of user names leading to confusing where user > metadata is being created or being overwritten. This issue extends from the > front end through the backend and to the database layer. > * *Username Collisions* > There are several cases where username collisions occur. One is where a > username exists as a local user as well as an external user. For example, > the initial administrator account has is a local user account with the > username of "admin". There may also be an external user account with the > username "admin". In some cases Ambari will treat both accounts as the same > user, converting the local account during synchronization operation to an > LDAP account. However in other cases, Ambari will treat the accounts as > separate users and create a separate account. > * *REST API* > Due to the implementation of the user resource in the REST API, there is no > way to distinguish between user accounts with the same username and different > data sources. For example usera/LOCAL vs usera/LDAP. This is because the > primary key for user resources is only the username field. This make > managing users confusing since the REST API entrypoint for user resources is > /api/v1/users/:USERNAME and there is no way to retrieve or set the details > for a specific user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20859) Improve User Account Management Within Ambari
[ https://issues.apache.org/jira/browse/AMBARI-20859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537996#comment-16537996 ] Ishan Bhatt commented on AMBARI-20859: -- Moving it out to 2.7.1 > Improve User Account Management Within Ambari > - > > Key: AMBARI-20859 > URL: https://issues.apache.org/jira/browse/AMBARI-20859 > Project: Ambari > Issue Type: Epic > Components: ambari-server, ambari-web >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Labels: authentication, pull-request-available, security, > user_management > Fix For: 2.7.1 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > As of Ambari 2.4, user management is confusing and tends to lead to > inconsistent results during synchronization and authentication. With the > addition of new mechanisms such as Kerberos and PAM, this will only get > worse. Therefore, there is a need to rework how Ambari manages users to > ensure that new authentication facilities are easily integrated. > The following problems need to be solved: > * *Case-sensitivity* > Some authentication sources are case sensitive and some are not. Ambari > inconsistently handles the case of user names leading to confusing where user > metadata is being created or being overwritten. This issue extends from the > front end through the backend and to the database layer. > * *Username Collisions* > There are several cases where username collisions occur. One is where a > username exists as a local user as well as an external user. For example, > the initial administrator account has is a local user account with the > username of "admin". There may also be an external user account with the > username "admin". In some cases Ambari will treat both accounts as the same > user, converting the local account during synchronization operation to an > LDAP account. However in other cases, Ambari will treat the accounts as > separate users and create a separate account. > * *REST API* > Due to the implementation of the user resource in the REST API, there is no > way to distinguish between user accounts with the same username and different > data sources. For example usera/LOCAL vs usera/LDAP. This is because the > primary key for user resources is only the username field. This make > managing users confusing since the REST API entrypoint for user resources is > /api/v1/users/:USERNAME and there is no way to retrieve or set the details > for a specific user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23876) Upgrade history arrow does not indicate downwards when expanded
[ https://issues.apache.org/jira/browse/AMBARI-23876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537993#comment-16537993 ] Ishan Bhatt commented on AMBARI-23876: -- Moving it out to 2.7.1 > Upgrade history arrow does not indicate downwards when expanded > --- > > Key: AMBARI-23876 > URL: https://issues.apache.org/jira/browse/AMBARI-23876 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.1 > > Attachments: s2-upg-history.png > > > See s2-upg-history.png, when 'Upgrade History' panel is expanded - the small > arrow to the left of 'Upgrade' text is still pointing to the right instead of > bottom -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23876) Upgrade history arrow does not indicate downwards when expanded
[ https://issues.apache.org/jira/browse/AMBARI-23876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23876: - Fix Version/s: (was: 2.7.0) 2.7.1 > Upgrade history arrow does not indicate downwards when expanded > --- > > Key: AMBARI-23876 > URL: https://issues.apache.org/jira/browse/AMBARI-23876 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.1 > > Attachments: s2-upg-history.png > > > See s2-upg-history.png, when 'Upgrade History' panel is expanded - the small > arrow to the left of 'Upgrade' text is still pointing to the right instead of > bottom -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23915) Upgrade History page shows non-stack services as also being upgraded to new stack version
[ https://issues.apache.org/jira/browse/AMBARI-23915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23915: - Fix Version/s: (was: 2.7.0) 2.7.1 > Upgrade History page shows non-stack services as also being upgraded to new > stack version > - > > Key: AMBARI-23915 > URL: https://issues.apache.org/jira/browse/AMBARI-23915 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Labels: system_test > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-05-17 at 8.04.07 PM.png > > > Upgrade history page shows non-stack services version as also HDP-3.0.0.0-x > (see attached) > We need to add a filter here or show the exact version (same as Ambari-server > version) for non-stack services like AMS, Smartsense, Infra, Logsearch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23915) Upgrade History page shows non-stack services as also being upgraded to new stack version
[ https://issues.apache.org/jira/browse/AMBARI-23915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537995#comment-16537995 ] Ishan Bhatt commented on AMBARI-23915: -- Moving it out to 2.7.1 > Upgrade History page shows non-stack services as also being upgraded to new > stack version > - > > Key: AMBARI-23915 > URL: https://issues.apache.org/jira/browse/AMBARI-23915 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Antonenko Alexander >Priority: Critical > Labels: system_test > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-05-17 at 8.04.07 PM.png > > > Upgrade history page shows non-stack services version as also HDP-3.0.0.0-x > (see attached) > We need to add a filter here or show the exact version (same as Ambari-server > version) for non-stack services like AMS, Smartsense, Infra, Logsearch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23476) Install wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23476: - Fix Version/s: (was: 2.7.0) 2.7.1 > Install wizard issues > - > > Key: AMBARI-23476 > URL: https://issues.apache.org/jira/browse/AMBARI-23476 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-04-05 at 5.35.06 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > In the above cluster, when install wizard is running , reloading Ambari fails > to load the page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23476) Install wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-23476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537992#comment-16537992 ] Ishan Bhatt commented on AMBARI-23476: -- Moving it out to 2.7.1 > Install wizard issues > - > > Key: AMBARI-23476 > URL: https://issues.apache.org/jira/browse/AMBARI-23476 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Attachments: Screen Shot 2018-04-05 at 5.35.06 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > In the above cluster, when install wizard is running , reloading Ambari fails > to load the page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23869) Remove insecure dependencies from Ambari Server
[
https://issues.apache.org/jira/browse/AMBARI-23869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-23869.
--
Resolution: Fixed
> Remove insecure dependencies from Ambari Server
> ---
>
> Key: AMBARI-23869
> URL: https://issues.apache.org/jira/browse/AMBARI-23869
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Remove insecure dependencies from Ambari Server
> *Jetty: Java based HTTP, Servlet, SPDY, WebSocket Server 6.1.26*
> * https://nvd.nist.gov/vuln/detail/CVE-2017-9735
> * https://nvd.nist.gov/vuln/detail/CVE-2011-4461
> * https://nvd.nist.gov/vuln/detail/CVE-2009-1523
> {noformat}
> [INFO]
>
> [INFO] Building Ambari Server 2.0.0.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ ambari-server ---
> [INFO] org.apache.ambari:ambari-server:jar:2.0.0.0-SNAPSHOT
> [INFO] +- org.mortbay.jetty:jsp-api-2.1-glassfish:jar:2.1.v20100127:compile
> [INFO] +- org.mortbay.jetty:jsp-2.1-glassfish:jar:2.1.v20100127:compile
> [INFO] \- org.apache.hadoop:hadoop-common:jar:2.7.2:compile
> [INFO]\- org.mortbay.jetty:jetty:jar:6.1.26:compile{noformat}
> Recommendation is to remove the dependency or upgrade to version 6.1.26.hwx
> or the latest version, if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23083) Missing permission for 'others' when Ambari is configured with two way SSL and https enabled
[
https://issues.apache.org/jira/browse/AMBARI-23083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23083:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Missing permission for 'others' when Ambari is configured with two way SSL
> and https enabled
>
>
> Key: AMBARI-23083
> URL: https://issues.apache.org/jira/browse/AMBARI-23083
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Vivek Sharma
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: system_test
> Fix For: 2.7.1
>
>
> # Deploy Ambari-2.6.2.0 server on machine A
> # Manually install and register agents on other machines (including machine A)
> # Enable 2 way SSL between server and agents
> # Enable https at Ambari server
> # Deploy a cluster via blueprints with HDP-2.6.5.0
> After cluster is deployed, observed that the permission of files such as
> hadoop-env.sh is '-rw-r-'
> Complete output:
> {code}
> [root@ctr-e138-1518143905142-36503-01-02 logs]# ls -lhrt /etc/hadoop/conf/
> total 176K
> -rw-r--r-- 1 cstm-hdfs hadoop 8.9K Feb 22 09:30 core-site.xml
> -rw-r- 1 cstm-hdfs hadoop 333 Feb 22 09:35 hdfs_dn_jaas.conf
> -rw-r- 1 cstm-hdfs hadoop 333 Feb 22 09:35 hdfs_nn_jaas.conf
> -rw-r- 1 cstm-hdfs hadoop 1.3K Feb 22 09:35 hadoop-policy.xml
> -rw-r- 1 cstm-hdfs hadoop 884 Feb 22 09:35 ssl-client.xml
> drwxr-xr-x 2 root hadoop 4.0K Feb 22 09:35 secure
> -rw-r- 1 cstm-hdfs hadoop 1000 Feb 22 09:35 ssl-server.xml
> -rw-r--r-- 1 cstm-hdfs hadoop 8.7K Feb 22 09:35 hdfs-site.xml
> -rw-r--r-- 1 cstm-mr hadoop 7.5K Feb 22 09:37 mapred-site.xml
> -rw-r--r-- 1 cstm-hdfs hadoop 2.3K Feb 22 09:37 capacity-scheduler.xml
> -rw-r--r-- 1 root hadoop 1.1K Feb 22 09:37 container-executor.cfg
> -rwxr-xr-x 1 root root 984 Feb 22 09:37 mapred-env.sh
> -rw-r--r-- 1 root hadoop 947 Feb 22 09:37 taskcontroller.cfg
> -rw-r- 1 cstm-yarn hadoop 571 Feb 22 09:37 yarn_jaas.conf
> -rw-r- 1 cstm-yarn hadoop 337 Feb 22 09:37 yarn_ats_jaas.conf
> -rw-r- 1 cstm-yarn hadoop 333 Feb 22 09:37 yarn_nm_jaas.conf
> -rw-r- 1 cstm-mr hadoop 320 Feb 22 09:37 mapred_jaas.conf
> -rw-r- 1 root root 1020 Feb 22 09:48 commons-logging.properties
> -rw-r- 1 root root 1.6K Feb 22 09:48 health_check
> -rw-r--r-- 1 cstm-hdfs hadoop 11K Feb 22 09:48 log4j.properties
> -rwxr-xr-x 1 root root 4.2K Feb 22 09:48 task-log4j.properties
> -rwxr-xr-x 1 root root 2.4K Feb 22 09:48 topology_script.py
> -rw-r- 1 root root 241 Feb 22 10:10 slaves
> -rw-r- 1 root hadoop 6.3K Feb 22 10:10 hadoop-env.sh
> -rw-r--r-- 1 cstm-yarn hadoop 24K Feb 22 10:10 yarn-site.xml
> -rwxr-xr-x 1 cstm-yarn hadoop 5.5K Feb 22 10:10 yarn-env.sh
> -rw-r- 1 cstm-hdfs hadoop 2.6K Feb 22 10:12 hadoop-metrics2.properties
> -rw-r--r-- 1 cstm-hdfs hadoop 467 Feb 22 10:12 topology_mappings.data
> -rw-r- 1 cstm-hdfs hadoop 1 Feb 22 10:13 dfs.exclude
> {code}
>
> When compared this with a non-SSL cluster the permission is '-rw-r--r--' i.e.
> read permission is available for other users
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23419) Refine pre-check message to remove unsupported services before upgrade to HDP-3.0
[ https://issues.apache.org/jira/browse/AMBARI-23419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23419: - Fix Version/s: (was: 2.7.0) 2.7.1 > Refine pre-check message to remove unsupported services before upgrade to > HDP-3.0 > - > > Key: AMBARI-23419 > URL: https://issues.apache.org/jira/browse/AMBARI-23419 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vivek Sharma >Assignee: Vivek Sharma >Priority: Critical > Labels: upgrade > Fix For: 2.7.1 > > > Services such as Falcon. Flume, Mahout, Slider would be removed from HDP-3.0 > stack. The pre-check message to remove them should be refined to say that the > services would be removed and cannot be re-installed after upgrade -- This message was sent by Atlassian JIRA (v7.6.3#76005)
