[jira] [Updated] (AMBARI-25069) Ambari writes Empty baseurl values written to Repo Files when using a local repository causing stack installation failure
[
https://issues.apache.org/jira/browse/AMBARI-25069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-25069:
---
Fix Version/s: 2.8.0
> Ambari writes Empty baseurl values written to Repo Files when using a local
> repository causing stack installation failure
> -
>
> Key: AMBARI-25069
> URL: https://issues.apache.org/jira/browse/AMBARI-25069
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.3
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Attachments: Screen Shot 2018-12-26 at 10.12.29 AM.png, Screen Shot
> 2018-12-26 at 10.13.14 AM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> when using a local repository, installation fails due to empty baseurls being
> written to the Ambari repository (even though local repository baseurl values
> were provided). The installation fails with below error :
> {code:java}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 37, in
> BeforeInstallHook().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 352, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/hook.py",
> line 33, in hook
> install_packages()
> File
> "/var/lib/ambari-agent/cache/stack-hooks/before-INSTALL/scripts/shared_initialization.py",
> line 37, in install_packages
> retry_count=params.agent_stack_retry_count)
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/packaging.py",
> line 30, in action_install
> self._pkg_manager.install_package(package_name, self.__create_context())
> File
> "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/yum_manager.py", line
> 219, in install_package
> shell.repository_manager_executor(cmd, self.properties, context)
> File "/usr/lib/ambari-agent/lib/ambari_commons/shell.py", line 753, in
> repository_manager_executor
> raise RuntimeError(message)
> RuntimeError: Failed to execute command '/usr/bin/yum -y install hdp-select',
> exited with code '1', message: 'Repository InstallMedia is listed more than
> once in the configuration
>
> One of the configured repositories failed (Unknown),
> and yum doesn't have enough cached data to continue. At this point the only
> safe thing yum can do is fail. There are a few ways to work "fix" this:
>
> 1. Contact the upstream for the repository and get them to fix the
> problem.
>
> 2. Reconfigure the baseurl/etc. for the repository, to point to a working
>
>upstream. This is most often useful if you are using a newer
> distribution release than is supported by the repository (and the packages
> for the previous distribution release still work).
>
> 3. Run the command with the repository temporarily disabled
>
> yum --disablerepo= ...
>
> 4. Disable the repository permanently, so yum won't use it by default.
> Yum will then just ignore the repository until you permanently enable it
> again or use --enablerepo for temporary usage:
> yum-config-manager --disable
> or
> subscription-manager repos --disable=
> 5. Configure the failing repository to be skipped, if it is unavailable.
> Note that yum will try to contact the repo. when it runs most
> commands,so will have to try and fail each time (and thus. yum will be be
> much slower). If it is a very temporary problem though, this is often a nice
> compromise:
> yum-config-manager --save
> --setopt=.skip_if_unavailable=true
>
> Cannot find a valid baseurl for repo: HDP-3.1-repo-1
> '
> Command aborted. Reason: 'Server considered task failed and automatically
> aborted it'
> stdout:
> {code}
> We can See that Ambari UI shows the empty baseURL in review step
> !Screen Shot 2018-12-26 at 10.12.29 AM.png|height=350,width=850!
> It also sends the empty Repo version while deploy stage
> !Screen Shot 2018-12-26 at 10.13.14 AM.png|height=350,width=850!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24784) Ambari-agent cannot register sometimes
[
https://issues.apache.org/jira/browse/AMBARI-24784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24784:
---
Fix Version/s: (was: 2.8.0)
2.7.3
> Ambari-agent cannot register sometimes
> --
>
> Key: AMBARI-24784
> URL: https://issues.apache.org/jira/browse/AMBARI-24784
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: AMBARI-24784.patch, AMBARI-24784.patch,
> AMBARI-24784.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> ERROR 2018-10-11 13:45:57,401 HeartbeatThread.py:108 - Exception in
> HeartbeatThread. Re-running the registration
> Traceback (most recent call last):
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 95, in run
> self.register()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 163, in register
> self.force_component_status_update()
> File "/usr/lib/ambari-agent/lib/ambari_agent/HeartbeatThread.py", line
> 173, in force_component_status_update
> self.component_status_executor.force_send_component_statuses()
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/ComponentStatusExecutor.py", line
> 206, in force_send_component_statuses
> service_name, component_name = service_and_component_name.split("/")
> ValueError: need more than 1 value to unpack
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24594) ams keystore password logged in clear text
[ https://issues.apache.org/jira/browse/AMBARI-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24594. Resolution: Invalid HDP-3.0 stack only change. > ams keystore password logged in clear text > -- > > Key: AMBARI-24594 > URL: https://issues.apache.org/jira/browse/AMBARI-24594 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.8.0 > > > We execute a command to convert truststore from JKS to PKCS12 before > starting up the AMS component. That command takes in the password as an > argument. The command output contains the password, need to replace it with a > placeholder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-24594) ams keystore password logged in clear text
[ https://issues.apache.org/jira/browse/AMBARI-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665615#comment-16665615 ] Jayush Luniya edited comment on AMBARI-24594 at 10/26/18 7:48 PM: -- HDP-3.0 stack only change. cc: [~avijayan] was (Author: jluniya): HDP-3.0 stack only change. > ams keystore password logged in clear text > -- > > Key: AMBARI-24594 > URL: https://issues.apache.org/jira/browse/AMBARI-24594 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.8.0 > > > We execute a command to convert truststore from JKS to PKCS12 before > starting up the AMS component. That command takes in the password as an > argument. The command output contains the password, need to replace it with a > placeholder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24764) StackMerger utility tool for flattening stack definitions
[ https://issues.apache.org/jira/browse/AMBARI-24764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya resolved AMBARI-24764. Resolution: Fixed > StackMerger utility tool for flattening stack definitions > - > > Key: AMBARI-24764 > URL: https://issues.apache.org/jira/browse/AMBARI-24764 > Project: Ambari > Issue Type: Task > Components: ambari-server, stacks >Affects Versions: 2.7.3 >Reporter: Jayush Luniya >Assignee: Jayush Luniya >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 2h 50m > Remaining Estimate: 0h > > Add StackMerger utility tool to flatten HDP-2.6 stack definition from > Ambari-2.7 and export the flattened stack definition for use in Ambari 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24669) Component status can stuck in starting/stopping status on heartbeat lost
[ https://issues.apache.org/jira/browse/AMBARI-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24669: --- Fix Version/s: (was: 2.8.0) 2.7.3 > Component status can stuck in starting/stopping status on heartbeat lost > > > Key: AMBARI-24669 > URL: https://issues.apache.org/jira/browse/AMBARI-24669 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > > Now server sets components statuses to UNKNOWN and saves last actual state on > heartbeat lost. After agent re-registering server restores saved state, but > in case "in progress" state request is already aborted and agent status > updates can not be applied. Agent should always send component statuses after > registering, not only on status changes. Also last actual state logic should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-24669) Component status can stuck in starting/stopping status on heartbeat lost
[ https://issues.apache.org/jira/browse/AMBARI-24669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reopened AMBARI-24669: > Component status can stuck in starting/stopping status on heartbeat lost > > > Key: AMBARI-24669 > URL: https://issues.apache.org/jira/browse/AMBARI-24669 > Project: Ambari > Issue Type: Bug > Components: ambari-agent, ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Now server sets components statuses to UNKNOWN and saves last actual state on > heartbeat lost. After agent re-registering server restores saved state, but > in case "in progress" state request is already aborted and agent status > updates can not be applied. Agent should always send component statuses after > registering, not only on status changes. Also last actual state logic should > be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-20390: --- Resolution: Not A Problem Status: Resolved (was: Patch Available) > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Assignee: Jayush Luniya >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya reassigned AMBARI-20390: -- Assignee: Jayush Luniya > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Assignee: Jayush Luniya >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20390) Inappropriate kafka log4j configuration results in too much kafka logs
[ https://issues.apache.org/jira/browse/AMBARI-20390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16661001#comment-16661001 ] Jayush Luniya commented on AMBARI-20390: The configs defined in the stack definitions are only the default values and can be changed by the end user when deploying the cluster. You can change the log4j properties from the UI without having to change the default. > Inappropriate kafka log4j configuration results in too much kafka logs > --- > > Key: AMBARI-20390 > URL: https://issues.apache.org/jira/browse/AMBARI-20390 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.7.0, 2.7.1, 2.7.2 >Reporter: WangJie >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Attachments: AMBARI-20390.patch, screenshot-1.png > > Time Spent: 1h > Remaining Estimate: 0h > > Inappropriate kafka log4j configuration results in too much kafka logs which > are constantly increasing and never be removed. > Besides,DailyRollingFileAppender does not support property:maxBackupIndex and > maxFileSize, Only RollingFileAppender supports it. > Suggestion: > Change kafka log4j appender mode from DailyRollingFileAppender to > RollingFileAppender. > In this way, it will automatically remove the useless kafka log file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24614) deploy-gce-perf-cluster.py script does not work
[ https://issues.apache.org/jira/browse/AMBARI-24614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24614: --- Fix Version/s: (was: 2.7.2) 2.7.3 > deploy-gce-perf-cluster.py script does not work > --- > > Key: AMBARI-24614 > URL: https://issues.apache.org/jira/browse/AMBARI-24614 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24614.patch, AMBARI-24614.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- 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 ] Jayush Luniya updated AMBARI-23026: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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: Sandor Molnar >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > 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-24599) Post user creation script sets invalid owner to HDFS dirs with secure cluster
[ https://issues.apache.org/jira/browse/AMBARI-24599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24599: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Post user creation script sets invalid owner to HDFS dirs with secure cluster > - > > Key: AMBARI-24599 > URL: https://issues.apache.org/jira/browse/AMBARI-24599 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Gabor Boros >Assignee: Gabor Boros >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1.5h > Remaining Estimate: 0h > > During LDAP user sync the post-user-creation-hook.sh is called which creates > directory for the given user in hdfs://user/username. The owner of this > directory is set to the username (shortname) which does not work for some > HDFS implementations. To fix this the script now sets the full username > (including the realm) as the owner of the dir. -- 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 ] Jayush Luniya updated AMBARI-24231: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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.3 > > Time Spent: 4.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24631) [Log Search UI] styles and layout fixes
[ https://issues.apache.org/jira/browse/AMBARI-24631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24631: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [Log Search UI] styles and layout fixes > --- > > Key: AMBARI-24631 > URL: https://issues.apache.org/jira/browse/AMBARI-24631 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 24h > Time Spent: 50h 10m > Remaining Estimate: 0h > > # Move number of events up on the page higher so it’s centered between the > top of the gray area and the beginning of the Histogram frame > # The message about triggering auto-refresh should be displayed in modal > dialog > # Filters panel should be a bit less transparent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24426) [Log Search UI] Show user friendly component names in Log Index Filter screen
[ https://issues.apache.org/jira/browse/AMBARI-24426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24426: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [Log Search UI] Show user friendly component names in Log Index Filter screen > - > > Key: AMBARI-24426 > URL: https://issues.apache.org/jira/browse/AMBARI-24426 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 6h > Time Spent: 1h > Remaining Estimate: 5h > > Show the user friendly component names on the screen of the Log Index Filter, > where the filter level can be set up. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24522) Cannot connect to MIT KDC admin server when port is specified in kerberos-env/admin_server_host
[
https://issues.apache.org/jira/browse/AMBARI-24522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24522:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cannot connect to MIT KDC admin server when port is specified in
> kerberos-env/admin_server_host
> ---
>
> Key: AMBARI-24522
> URL: https://issues.apache.org/jira/browse/AMBARI-24522
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, pull-request-available, regression
> Fix For: 2.7.3
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Cannot connect to MIT KDC admin server when port is specified in
> {{kerberos-env/admin_server_host}}. The following error is seen when
> validating the KDC admin credentials:
> {noformat}
> kinit: Server not found in Kerberos database while getting initial credentials
> {noformat}
> The reason for this is due to how the credentials are created for accessing
> the MIT KDC administration server.
> {noformat}
> kinit -c -S kadmin/
> {noformat}
> If a port was added to the {{kerberos-env/admin_server_host}} value then the
> server principal will be generated like {{kadmin/kdc.example.com:4749}}
> rather than {{kadmin/kdc.example.com}}. Therefore the server principal is not
> found.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24524) Unable to validate password complexity for properties rangertagsync_user_password, rangerusersync_user_password
[
https://issues.apache.org/jira/browse/AMBARI-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24524:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Unable to validate password complexity for properties
> rangertagsync_user_password, rangerusersync_user_password
> ---
>
> Key: AMBARI-24524
> URL: https://issues.apache.org/jira/browse/AMBARI-24524
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: ui_glitches.PNG
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> STR
> - perform UI deploy with selecting Ranger & Ranger KMS
> Used password: {{78C%4KwS5J$&}} or any other, created by password generator
> with defined complexity
> Additionally, check on glitches picture 1 & 2. Additionally, I believe it is
> best to put special characters to grayed/dashed box to make user attention to
> them.
--
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 ] Jayush Luniya updated AMBARI-23419: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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.3 > > > 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)
[jira] [Updated] (AMBARI-24611) Disabling an Alert Does Not Clear It in the Web UI
[ https://issues.apache.org/jira/browse/AMBARI-24611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24611: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Disabling an Alert Does Not Clear It in the Web UI > -- > > Key: AMBARI-24611 > URL: https://issues.apache.org/jira/browse/AMBARI-24611 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > When you disable an alert, the web client shows that the instance of the > alert was removed immediately, however, the red badges indicating a critical > alert do not disappear. -- 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
]
Jayush Luniya updated AMBARI-23655:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> 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.3
>
>
> 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-24520) Fix set KDC admin credentials section in enable Kerberos doc
[
https://issues.apache.org/jira/browse/AMBARI-24520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24520:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Fix set KDC admin credentials section in enable Kerberos doc
>
>
> Key: AMBARI-24520
> URL: https://issues.apache.org/jira/browse/AMBARI-24520
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Fix set KDC admin credentials section in enable Kerberos doc
> The current documentation at
> https://github.com/apache/ambari/blob/branch-2.7/ambari-server/docs/security/kerberos/enabling_kerberos.md#set-the-kdc-administrator-credentials
> indicates an incorrect URL for the API call.
> It should read:
> {noformat}
> http://AMBARI_SERVER:8080/api/v1/clusters/CLUSTER_NAME/credentials/kdc.admin.credential
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22949) Kerberos identities are not removed for components that exist in multiple hosts
[
https://issues.apache.org/jira/browse/AMBARI-22949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-22949:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Kerberos identities are not removed for components that exist in multiple
> hosts
> ---
>
> Key: AMBARI-22949
> URL: https://issues.apache.org/jira/browse/AMBARI-22949
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.3
>
>
> Kerberos identities are not removed for components that exist on multiple
> hosts.
> For example, if {{SERVICEA/COMPONENT1}} is installed on {{HOST1}} and
> {{HOST2}} and its relevant principal is named {{component1/\_HOST@REALM}},
> then the host-specific principal and keytab file will not be removed if
> {{SERVICEA/COMPONENT1}} is removed from {{HOST1}} *_or_* {{HOST2}}. It will
> be removed if {{SERVICEA/COMPONENT1}} is removed from {{HOST1}} *_and_*
> {{HOST2}}.
> This is due to the incorrect principal name comparison when determine whether
> a Kerberos identity is to be removed or not. See
> {{org.apache.ambari.server.controller.utilities.UsedIdentities#contains}}.
--
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
]
Jayush Luniya updated AMBARI-24205:
---
Fix Version/s: (was: 2.7.2)
(was: 3.0.0)
2.7.3
> 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.3
>
>
> {{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-24533) Ambari Server Ldap Sync Failed upon subject alternative DNS name check
[
https://issues.apache.org/jira/browse/AMBARI-24533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24533:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Ambari Server Ldap Sync Failed upon subject alternative DNS name check
> --
>
> Key: AMBARI-24533
> URL: https://issues.apache.org/jira/browse/AMBARI-24533
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> STR:
> 1. Install Ambari
> 2. Get certificate for secure LDAP (LDAPS) connection to your AD server.
> 3. Generate ambari truststore with LDAPS certificate.
> 4. Setup Ambari to use LDAPS with providing truststore.
> {code:java}
> 2018-08-20 18:38:04,763 DEBUG
> com.hw.commonuifrm.impl.commands.CommandExecutorImpl.executeCommand():
> Sending command [(echo "admin" ; echo "admin") | ambari-server sync-ldap
> --users /tmp/users.txt --groups /tmp/groups.txt]
> 2018-08-20 18:38:05,666 DEBUG
> com.hw.commonuifrm.impl.commands.ProcessDataImpl.buildOutputAndErrorStreamData():
> /usr/lib64/python2.7/getpass.py:83: GetPassWarning: Can not control echo on
> the terminal.
> passwd = fallback_getpass(prompt, stream)
> Warning: Password input may be echoed.
> Enter Ambari Admin password:
> 2018-08-20 18:38:07,169 INFO
> com.hw.ambari.ui.util.cluster_managers.LDAPClusterManager.ambariServerSyncLDAPWithAD():
> Result: Using python /usr/bin/python
> Syncing with LDAP...
> Enter Ambari Admin login:
> Fetching LDAP configuration from DB.
> Syncing specified users and groups...ERROR: Exiting with exit code 1.
> REASON: Caught exception running LDAP sync. ***.com:636; nested exception is
> javax.naming.CommunicationException: ***.com:636 [Root exception is
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching ***.com found.]
> 2018-08-20 18:38:07,170 INFO
> com.hw.ambari.ui.tests.console.ldap.TestLDAPSOnAD.test010_AmbariSynchronizeWithADThroughLDAPS():
> AMBARI LDAPS synchronization result: Using python /usr/bin/python
> Syncing with LDAP...
> Enter Ambari Admin login:
> Fetching LDAP configuration from DB.
> Syncing specified users and groups...ERROR: Exiting with exit code 1.
> REASON: Caught exception running LDAP sync. ***.com:636; nested exception is
> javax.naming.CommunicationException: ***.com:636 [Root exception is
> javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException:
> No subject alternative DNS name matching ***.com found.]{code}
> The issue is that the AD server's certificate contains a section:
> {noformat}
> X509v3 Subject Alternative Name: othername:,
> DNS:***-2.COM{noformat}
> As you can see this is not the same that we use to connect to the AD server
> (***.com:636). Even if this is a certificate issue the connection could be
> open and we should be able to sync LDAP users/groups.
> *Important note*: it's reproducible only with OpenJDK (I used
> openjdk-1.8.0.181-3.b13.el7_5.x86_64); working properly with Oracle's JDK.
> +*Recommended solution*+
> We can disable endpoint identification when the client is negotiating with
> the server during SSL handshake by setting
> _com.sun.jndi.ldap.object.disableEndpointIdentification_ to _true_ (see
> [https://github.com/ojdkbuild/lookaside_java-1.8.0-openjdk/blob/master/jdk/src/share/classes/com/sun/jndi/ldap/Connection.java#L386]).
> By default this should not be the case but end users may set this up when
> configuring LDAP if they face this issue.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24577: --- Fix Version/s: (was: 2.7.2) (was: trunk) 2.7.3 > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24542) Rename LDAP configuration ambari.ldap.advance.collision_behavior
[ https://issues.apache.org/jira/browse/AMBARI-24542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24542: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Rename LDAP configuration ambari.ldap.advance.collision_behavior > > > Key: AMBARI-24542 > URL: https://issues.apache.org/jira/browse/AMBARI-24542 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0, 2.7.1 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 3h 40m > Remaining Estimate: 0h > > In Ambari 2.7 we moved LDAP configuration into the Ambari DB and introduced > common naming pattern. However a typo has been made in > _'ambari.ldap.*advance*.collision_behavior_'. This should be renamed to > _'ambari.ldap.*advanced*.collision_behavior_' -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24573) Clarify the warning message during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-24573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24573: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Clarify the warning message during ambari server setup > -- > > Key: AMBARI-24573 > URL: https://issues.apache.org/jira/browse/AMBARI-24573 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 40m > Remaining Estimate: 0h > > Change > WARNING: Before starting Ambari Server, you must run the following DDL > against the database to create the schema: > /var/lib/ambari-server/resources/Ambari-DDL-MySQL-CREATE.sql > so that it's clear that the dll script should be run from the DB console. -- 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 ] Jayush Luniya updated AMBARI-23925: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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: Critical > Fix For: 2.7.3 > > > 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-24626) Log Search: some solr fields are missing from service log / audit log response
[ https://issues.apache.org/jira/browse/AMBARI-24626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24626: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Log Search: some solr fields are missing from service log / audit log response > -- > > Key: AMBARI-24626 > URL: https://issues.apache.org/jira/browse/AMBARI-24626 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24624) Log Search: Field type 'key_lower_case' not found - in Solr
[
https://issues.apache.org/jira/browse/AMBARI-24624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24624:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Log Search: Field type 'key_lower_case' not found - in Solr
> ---
>
> Key: AMBARI-24624
> URL: https://issues.apache.org/jira/browse/AMBARI-24624
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> in managed-schema of the service logs, key_lower_case was removed as a type,
> but there are references for that in the solrconfig.xml -> workaround, it can
> be changed to {{lowercase}} from {{key_lower_case}} in
> logsearch-service_logs-solrconfig content, and restart Log Search (after
> that: restart solr)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24616) Disable Kerberos from Ambari UI didn't clean up keytab directories
[
https://issues.apache.org/jira/browse/AMBARI-24616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24616:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Disable Kerberos from Ambari UI didn't clean up keytab directories
> --
>
> Key: AMBARI-24616
> URL: https://issues.apache.org/jira/browse/AMBARI-24616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 5h 40m
> Remaining Estimate: 0h
>
> Disable Kerberos from Ambari UI didn't clean up keytab directories,
> stderr:
> {code:java}
> 2018-09-08 05:27:19,276 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,298 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,325 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,348 - Failed to remove identity for
> amsmon/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,465 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,491 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,515 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,539 - Failed to remove identity for
> dn/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,671 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,696 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,723 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,744 - Failed to remove identity for
> hbase/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,959 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:19,987 - Failed to remove identity for
> nm/ctr-e138-1518143905142-467151-01-06.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,049 - Failed to remove identity for
> nn/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,376 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-02.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,399 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-04.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,420 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,441 - Failed to remove identity for
> HTTP/ctr-e138-1518143905142-467151-01-05.hwx.s...@example.com from the
> Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,590 - Failed to remove identity for
> yarn-ats-hbase/ctr-e138-1518143905142-467151-01-03.hwx.s...@example.com
> from the Ambari database - Object: null is not a known Entity type.
> 2018-09-08 05:27:20,617 - Failed to remove identity
[jira] [Updated] (AMBARI-24548) Allow skipping Hive Metastore schema creation for sysprepped cluster
[
https://issues.apache.org/jira/browse/AMBARI-24548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24548:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Allow skipping Hive Metastore schema creation for sysprepped cluster
>
>
> Key: AMBARI-24548
> URL: https://issues.apache.org/jira/browse/AMBARI-24548
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Similar to AMBARI-24540, Hive Metastore DB schema may be manually pre-created
> to save time during initial service start. However, {{schematool}} could
> still take quite some time to confirm that the schema exists. The goal of
> this change is to allow users who pre-create Hive Metastore DB schema to make
> Ambari skip managing the DB (create or check existence).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24525) Accumulo does not startup in Federated Cluster
[
https://issues.apache.org/jira/browse/AMBARI-24525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24525:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Accumulo does not startup in Federated Cluster
> --
>
> Key: AMBARI-24525
> URL: https://issues.apache.org/jira/browse/AMBARI-24525
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In a manually setup federated cluster (not through deployNG) --
> Accumulo was installed and when trying to start, below error thrown --
> {noformat}
> 2018-08-16 07:33:31,748 [start.Main] ERROR: Thread
> 'org.apache.accumulo.master.state.SetGoalState' died.
> java.lang.IllegalArgumentException: Expected fully qualified URI for
> instance.volumes got ns2/apps/accumulo/data
> at
> org.apache.accumulo.core.volume.VolumeConfiguration.getVolumeUris(VolumeConfiguration.java:107)
> at
> org.apache.accumulo.server.fs.VolumeManagerImpl.get(VolumeManagerImpl.java:334)
> {noformat}
> Caused by incorrect config value:
> {{instance.volumes = hdfs://ns1,ns2/apps/accumulo/data}}
> where ns1 and ns2 are namespaces
> Expected is --
> {{instance.volumes =
> hdfs://ns1/apps/accumulo/data,hdfs://ns2/apps/accumulo/data}}
> according to --
> https://accumulo.apache.org/docs/2.0/administration/multivolume
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24622) Allow skipping package operations for LZO on sysprepped hosts
[ https://issues.apache.org/jira/browse/AMBARI-24622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24622: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Allow skipping package operations for LZO on sysprepped hosts > - > > Key: AMBARI-24622 > URL: https://issues.apache.org/jira/browse/AMBARI-24622 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > LZO packages may be pre-installed in sysprepped environments, but Ambari > still manages the repo and checks for existence of the packages, which takes > time. The goal of this change is to allow users who pre-install packages to > skip package manager operations for LZO packages, too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24647) [PERF] Host checks taking longer time than previous releases
[ https://issues.apache.org/jira/browse/AMBARI-24647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24647: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [PERF] Host checks taking longer time than previous releases > > > Key: AMBARI-24647 > URL: https://issues.apache.org/jira/browse/AMBARI-24647 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24647.patch > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24555) Nifi Registry install fails
[
https://issues.apache.org/jira/browse/AMBARI-24555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24555:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Nifi Registry install fails
> ---
>
> Key: AMBARI-24555
> URL: https://issues.apache.org/jira/browse/AMBARI-24555
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Facing issue installing Nifi Registry on HDP_HDF cluster. The create keytab
> step in Ambari is failing during installation. Below exception is seen in
> ambari logs.
>
> {code}
> 2018-08-21 13:11:03,401 ERROR [Server Action Executor Worker 1305]
> CreatePrincipalsServerAction:309 - Failed to create principal, - Failed to
> create new principal - no principal specified
> org.apache.ambari.server.serveraction.kerberos.KerberosOperationException:
> Failed to create new principal - no principal specified
> at
> org.apache.ambari.server.serveraction.kerberos.MITKerberosOperationHandler.createPrincipal(MITKerberosOperationHandler.java:159)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.createPrincipal(CreatePrincipalsServerAction.java:268)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.processIdentity(CreatePrincipalsServerAction.java:157)
> at
> org.apache.ambari.server.serveraction.kerberos.KerberosServerAction.processIdentities(KerberosServerAction.java:460)
> at
> org.apache.ambari.server.serveraction.kerberos.CreatePrincipalsServerAction.execute(CreatePrincipalsServerAction.java:92)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.execute(ServerActionExecutor.java:550)
> at
> org.apache.ambari.server.serveraction.ServerActionExecutor$Worker.run(ServerActionExecutor.java:466)
> at java.lang.Thread.run(Thread.java:748)
> 2018-08-21 13:11:03,401 INFO [Server Action Executor Worker 1305]
> KerberosServerAction:481 - Processing identities completed.
> 2018-08-21 13:11:04,191 ERROR [ambari-action-scheduler] ActionScheduler:482 -
> Operation completely failed, aborting request id: 117
> {code}
> The Ambari UI should not display any properties from Kerberos identity blocks
> that indicate they are referencing another Kerberos identity. There are 2
> ways we know this:
> - The new/preferred way: the identity block has a non-empty/non-null
> "reference" attribute
> - The old (backwards compatible way): the identity block has a "name"
> attribute the starts with a '/'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24663) 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
[
https://issues.apache.org/jira/browse/AMBARI-24663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24663:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> 'ambari-server setup' does not use AMBARI_SECURITY_MASTER_KEY env var
> -
>
> Key: AMBARI-24663
> URL: https://issues.apache.org/jira/browse/AMBARI-24663
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.1
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@h002 ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> ambari-server setup promts to enter current master key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24551) [Log Search UI] get rid of redundant requests after undoing or redoing several history steps
[ https://issues.apache.org/jira/browse/AMBARI-24551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24551: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [Log Search UI] get rid of redundant requests after undoing or redoing > several history steps > > > Key: AMBARI-24551 > URL: https://issues.apache.org/jira/browse/AMBARI-24551 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.1 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 4h > Time Spent: 2h 50m > Remaining Estimate: 1h 10m > > After undoing or redoing more than one history items several redundant API > requests are sent. This occurs because changes for several filter controls > are applied step-by-step, and each control change generates new request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24697) [Intermittent] Client installation failures when parallel_execution enabled
[
https://issues.apache.org/jira/browse/AMBARI-24697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24697:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> [Intermittent] Client installation failures when parallel_execution enabled
> ---
>
> Key: AMBARI-24697
> URL: https://issues.apache.org/jira/browse/AMBARI-24697
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.2
>Reporter: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.3
>
>
> Several client installation failing in a baked image setup due to timeout
> with Ambari-2.7.3.0-6
> {code:title=Infra Solr Client Install failed}
> stderr:
> Python script has been killed due to timeout after waiting 2400 secs
> stdout:
> 2018-09-26 04:30:05,749 - Stack Feature Version Info: Cluster Stack=3.0,
> Command Stack=None, Command Version=None -> 3.0
> 2018-09-26 04:30:05,769 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-09-26 04:30:05,773 - Group['cstm-users'] {}
> 2018-09-26 04:30:05,776 - Group['cstm-kms'] {}
> 2018-09-26 04:30:05,777 - Group['cstm-ranger'] {}
> 2018-09-26 04:30:05,777 - Group['cstm-zeppelin'] {}
> 2018-09-26 04:30:05,778 - Group['hdfs'] {}
> 2018-09-26 04:30:05,778 - Group['cstm-livy'] {}
> 2018-09-26 04:30:05,779 - Group['hadoop'] {}
> 2018-09-26 04:30:05,779 - Group['cstm-knox'] {}
> 2018-09-26 04:30:05,779 - Group['cstm-spark'] {}
> 2018-09-26 04:30:05,782 - User['yarn-ats'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,786 - User['superset'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,790 - User['cstm-hive'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,794 - User['cstm-sqoop'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,797 - User['cstm-yarn'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,801 - User['cstm-tez'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid':
> None}
> 2018-09-26 04:30:05,805 - User['cstm-storm'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,809 - User['cstm-kafka'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,840 - Adding user User['cstm-kafka']
> 2018-09-26 04:30:05,945 - User['cstm-logsearch'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:05,946 - Adding user User['cstm-logsearch']
> 2018-09-26 04:30:06,283 - User['cstm-infra-solr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:06,284 - Adding user User['cstm-infra-solr']
> 2018-09-26 04:30:06,491 - User['cstm-mr'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:06,492 - Adding user User['cstm-mr']
> 2018-09-26 04:30:06,732 - User['cstm-zeppelin'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['cstm-zeppelin', 'hadoop'], 'uid':
> None}
> 2018-09-26 04:30:06,733 - Adding user User['cstm-zeppelin']
> 2018-09-26 04:30:07,044 - User['cstm-oozie'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid':
> None}
> 2018-09-26 04:30:07,045 - Adding user User['cstm-oozie']
> 2018-09-26 04:30:07,404 - User['cstm-kms'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['cstm-kms', 'hadoop'], 'uid': None}
> 2018-09-26 04:30:07,405 - Adding user User['cstm-kms']
> 2018-09-26 04:30:07,660 - User['cstm-ranger'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['cstm-ranger', 'hadoop'], 'uid':
> None}
> 2018-09-26 04:30:07,665 - User['cstm-ams'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:07,666 - Adding user User['cstm-ams']
> 2018-09-26 04:30:07,920 - User['cstm-atlas'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:07,920 - Adding user User['cstm-atlas']
> 2018-09-26 04:30:08,060 - User['cstm-knox'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'cstm-knox'], 'uid': None}
> 2018-09-26 04:30:08,062 - Modifying user cstm-knox
> 2018-09-26 04:30:08,263 - User['cstm-hbase'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2018-09-26 04:30:08,273 - User['cstm-hdfs'] {'gid': 'hadoop',
> 'fetch_nonlocal_groups': True,
[jira] [Updated] (AMBARI-24638) Ambari-agent process memory leak
[ https://issues.apache.org/jira/browse/AMBARI-24638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24638: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Ambari-agent process memory leak > > > Key: AMBARI-24638 > URL: https://issues.apache.org/jira/browse/AMBARI-24638 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24638.patch, AMBARI-24638.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > There was one process which started using memory rapidly at certain point and > grew up to ~27GB of RSS used until eventually we restarted it. Which happened > after a month of running of 10 ambari-agent nodes. > [root@andrew2-1n01 ~]# ps aux | grep ambari_agent > root 39955 0.0 0.0 47580 6024 ?SAug17 0:00 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/AmbariAgent.py start > root 39959 20.4 10.2 31623096 27154348 ? Sl Aug17 7645:55 > /usr/bin/python /usr/lib/ambari-agent/lib/ambari_agent/main.py start > Just before the growth in memory usage is seen. This exception pops out: > ERROR 2018-09-11 10:56:59,716 websocket.py:552 - Websocket connection was > closed with an exception > Traceback (most recent call last): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 549, in run > if not self.once(): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 428, in > once > if not self.process(self.buf[:requested]): > File "/usr/lib/ambari-agent/lib/ambari_ws4py/websocket.py", line 483, in > process > self.reading_buffer_size = s.parser.send(bytes) or DEFAULT_READING_SIZE > ValueError: generator already executing > This exception is not seen on all other nodes or on this one at any other > period (during 1 month). So I suggest it can be the root cause. > Basically this error means that generator is being used by multiple threads. > So I will upload the fix to thread-lock this place. > This is just a guess solution which might work and might not. No way to test > really. But definitely we should try this. > > This is noticed in ambari-2.7.1.0-73 version as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24617) Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with LDAP Authentication
[ https://issues.apache.org/jira/browse/AMBARI-24617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24617: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Ambari 2.7 for HDP 3.0 has missing parameter while adding Hive service with > LDAP Authentication > --- > > Key: AMBARI-24617 > URL: https://issues.apache.org/jira/browse/AMBARI-24617 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Fix For: 2.7.3 > > > Hi, > When we want to add Hive service with LDAP authentication from Ambari, it is > asking for a parameter value but that parameter namely > hive.server2.authentication.ldap.url is missing in Ambari UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24640) Log Search: support to remove suffixes from field names
[
https://issues.apache.org/jira/browse/AMBARI-24640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24640:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Log Search: support to remove suffixes from field names
> ---
>
> Key: AMBARI-24640
> URL: https://issues.apache.org/jira/browse/AMBARI-24640
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> new available properties to remove suffixes:
> {{logsearch.web.labels.service_logs.field.fallback.suffixes=_l,_s,_b,_i}}
> {{logsearch.web.labels.audit_logs.field.fallback.suffixes=_l,_s,_b,_i}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24661) While registering agent can miss updates from server
[ https://issues.apache.org/jira/browse/AMBARI-24661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24661: --- Fix Version/s: (was: 2.7.2) 2.7.3 > While registering agent can miss updates from server > > > Key: AMBARI-24661 > URL: https://issues.apache.org/jira/browse/AMBARI-24661 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24661.patch > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24536) Ambari SPNEGO breaks SSO redirect
[ https://issues.apache.org/jira/browse/AMBARI-24536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24536: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Ambari SPNEGO breaks SSO redirect > - > > Key: AMBARI-24536 > URL: https://issues.apache.org/jira/browse/AMBARI-24536 > Project: Ambari > Issue Type: Bug > Components: ambari-server, security >Affects Versions: 2.6.0 >Reporter: Sean Roberts >Assignee: Robert Levas >Priority: Major > Labels: kerberos, pull-request-available, security, spnego, sso > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > When SPNEGO is enabled (`ambari-server setup-kerberos`), the SSO > (`ambari-server setup-sso`) redirect no longer works. > How to reproduce: > # Enable SSO `ambari-server setup-sso` > # `ambari-server restart` > # Visit Ambari and notice that you are redirected to the SSO system (i.e. > Knox) > # Enable SPNEGO `ambari-server setup-kerberos` > # `ambari-server restart` > # Visit Ambari and notice that you are *NOT redirected* to the SSO system > (i.e. Knox) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24639) Not able to turn off maintenance mode for a host.
[
https://issues.apache.org/jira/browse/AMBARI-24639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24639:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Not able to turn off maintenance mode for a host.
> -
>
> Key: AMBARI-24639
> URL: https://issues.apache.org/jira/browse/AMBARI-24639
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the cluster , while trying to turn off maintenance mode on host , nothing
> happens and below error is seen in the console.
> Initial analysis indicate that this could be because some host components are
> out of sync. But this may or may not be RC. Kindly check.
> {code:java}
> Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.onOffPassiveModeForHost (app.js:26825)
> at Class.doAction (app.js:26800)
> at handler (vendor.js:31554)
> at HTMLAnchorElement. (vendor.js:23346)
> at HTMLDivElement.dispatch (vendor.js:3178)
> at HTMLDivElement.elemData.handle (vendor.js:2854)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24653) YARN Timeline server v2 related system tests fail.
[ https://issues.apache.org/jira/browse/AMBARI-24653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24653: --- Fix Version/s: (was: 2.7.2) 2.7.3 > YARN Timeline server v2 related system tests fail. > -- > > Key: AMBARI-24653 > URL: https://issues.apache.org/jira/browse/AMBARI-24653 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.2 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24597) Popup shown when Ambari started on a different port other than 8080
[
https://issues.apache.org/jira/browse/AMBARI-24597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24597:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Popup shown when Ambari started on a different port other than 8080
> ---
>
> Key: AMBARI-24597
> URL: https://issues.apache.org/jira/browse/AMBARI-24597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Change the Ambari server port by setting the following
> {code:title=ambari.properties}
> client.api.port=8000
> {code}
> Ab error popup is observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24458) Start operation is disabled for HDFS after stopping components for one namespace
[ https://issues.apache.org/jira/browse/AMBARI-24458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24458: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Start operation is disabled for HDFS after stopping components for one > namespace > > > Key: AMBARI-24458 > URL: https://issues.apache.org/jira/browse/AMBARI-24458 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 > Environment: ambari-server version: ambari-server-2.7.1.0-70.x86_64 > ambari-server --hash: f6d369619dc259e6ade537d6cdb3396f9e01c3dd >Reporter: Vivek Rathod >Assignee: Dmytro Sen >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-08-10 at 10.16.46 AM.png, Screen Shot > 2018-08-10 at 10.17.01 AM.png > > Time Spent: 1h > Remaining Estimate: 0h > > Start operation is disabled for HDFS after stopping components for one > namespace > > STR: > 1) On hdfs service page, stop components for one namespace (ns1) > 2) Try to start them. Start button is disabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24582) Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
[
https://issues.apache.org/jira/browse/AMBARI-24582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24582:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Ambari Alert - HiveServer2 Process - False negative in Certain Scenarios
>
>
> Key: AMBARI-24582
> URL: https://issues.apache.org/jira/browse/AMBARI-24582
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Hive Alert & Hive Service Check both share the same logic from
> {{hive_check}} which attempts to execute something similar to:
> {code}
> beeline -u '%s' %s -e ';' 2>&1| awk '{print}' | grep -i -e 'Connection
> refused' -e 'Invalid URL'"
> {code}
> This type of negative condition checking misses a lot of failures, such as
> permission problems and SSL/JKS problems. Instead, we should change this to a
> positive check.
> - Add the {{-n}} option to specify the hive user since the hive warehouse
> inode is protected. This option is ignored for Kerberos
> - Change the grep to look for positive conditions
> -- {code}
> Connecting to jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> Connected to: Apache Hive (version 3.0.0.3.0.0.0-1553)
> Driver: Hive JDBC (version 3.0.0.3.0.0.0-1553)
> Transaction isolation: TRANSACTION_REPEATABLE_READ
> Beeline version 3.0.0.3.0.0.0-1553 by Apache Hive
> Closing: 0: jdbc:hive2://c7403.ambari.apache.org:1/;transportMode=binary
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24435) [Log Search UI] Remove underline text decoration from dropdowns on hover
[ https://issues.apache.org/jira/browse/AMBARI-24435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24435: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [Log Search UI] Remove underline text decoration from dropdowns on hover > > > Key: AMBARI-24435 > URL: https://issues.apache.org/jira/browse/AMBARI-24435 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch, logsearch >Affects Versions: 2.7.0 >Reporter: Istvan Tobias >Assignee: Istvan Tobias >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.3 > > Original Estimate: 2h > Time Spent: 3h > Remaining Estimate: 0h > > The dropdown buttons have underline text decoration on mouse hover, it should > be removed. -- 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 ] Jayush Luniya updated AMBARI-23876: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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.3 > > 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-24594) ams keystore password logged in clear text
[ https://issues.apache.org/jira/browse/AMBARI-24594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24594: --- Fix Version/s: (was: 2.7.2) 2.7.3 > ams keystore password logged in clear text > -- > > Key: AMBARI-24594 > URL: https://issues.apache.org/jira/browse/AMBARI-24594 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Fix For: 2.7.3 > > > We execute a command to convert truststore from JKS to PKCS12 before > starting up the AMS component. That command takes in the password as an > argument. The command output contains the password, need to replace it with a > placeholder. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24646) 'ambari-server setup-ldap' fails with AttributeError when master_key is not persisted
[
https://issues.apache.org/jira/browse/AMBARI-24646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24646:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> 'ambari-server setup-ldap' fails with AttributeError when master_key is not
> persisted
> -
>
> Key: AMBARI-24646
> URL: https://issues.apache.org/jira/browse/AMBARI-24646
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> *STR*
> Installed ambari-server and configured password encryption, but chose not to
> persist master key
> {code}
> [root@ctr ~]# ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Password encryption is enabled.
> Do you want to reset Master Key? [y/n] (n): y
> Master Key not persisted.
> Enter current Master Key:
> Enter new Master Key:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? n
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {code}
> Then export environment variable
> export AMBARI_SECURITY_MASTER_KEY=hadoop
> Thereafter ran the following:
> *Issue #1* - Gave AttributeError after accepting the 'Save settings' prompt,
> instead of asking for master key
> {code}
> [root@ctr ~]# ambari-server setup-ldap -v
> Using python /usr/bin/python
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: ps -p 5596
> INFO:
> process_pid=12677
> Please select the type of LDAP you want to use (AD, IPA, Generic
> LDAP):Generic LDAP
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389):
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (posixUser):
> User ID attribute (uid):
> Group object class (posixGroup):
> Group name attribute (cn):
> Group member attribute (memberUid):
> Distinguished name attribute (dn):
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (uid=ldapbind,cn=users,dc=ambari,dc=apache,dc=org):
> uid=hdfs,ou=people,ou=dev,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]:
> Results from LDAP are paginated when requested [true/false]:
>
> Review Settings
>
> Primary LDAP Host (ldap.ambari.apache.org): ctr
> Primary LDAP Port (389): 389
> Use SSL [true/false] (false): false
> User object class (posixUser): posixUser
> User ID attribute (uid): uid
> Group object class (posixGroup): posixGroup
> Group name attribute (cn): cn
> Group member attribute (memberUid): memberUid
> Distinguished name attribute (dn): dn
> Search Base (dc=ambari,dc=apache,dc=org): dc=apache,dc=org
> Referral method [follow/ignore] (follow): follow
> Bind anonymously [true/false] (false): false
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip): skip
> ambari.ldap.connectivity.bind_dn: uid=hdfs,ou=people,ou=dev,dc=apache,dc=org
> ambari.ldap.connectivity.bind_password: *
> Save settings [y/n] (y)? y
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 1060, in
> mainBody()
> File "/usr/sbin/ambari-server.py", line 1030, in mainBody
> main(options, args, parser)
> File "/usr/sbin/ambari-server.py", line 980, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 79, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/ambari-server/lib/ambari_server/setupSecurity.py", line 860,
> in setup_ldap
>
[jira] [Updated] (AMBARI-24604) Stack advisor error popup with "500 status code" thrown during customize service page of install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24604: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Stack advisor error popup with "500 status code" thrown during customize > service page of install wizard > --- > > Key: AMBARI-24604 > URL: https://issues.apache.org/jira/browse/AMBARI-24604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > ams-hbase hbase.rootdir property being set to "file://" leads to 500 server > error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24576) Ambari Metrics should handle a customized Zookeeper service principal name
[ https://issues.apache.org/jira/browse/AMBARI-24576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24576: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Ambari Metrics should handle a customized Zookeeper service principal name > -- > > Key: AMBARI-24576 > URL: https://issues.apache.org/jira/browse/AMBARI-24576 > Project: Ambari > Issue Type: Bug > Components: stacks >Affects Versions: 2.7.2 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > AMS should handle a customized Zookeeper service principal name. > Currently this is not supported due to hardcoded and implicit values > expecting the Zookeeper service principal name to be zookeeper/_HOST as > opposed to something like zookeeper-mycluster/_HOST. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24572: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24683) Cannot run HDFS service check without HDFS_CLIENT
[
https://issues.apache.org/jira/browse/AMBARI-24683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24683:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cannot run HDFS service check without HDFS_CLIENT
> -
>
> Key: AMBARI-24683
> URL: https://issues.apache.org/jira/browse/AMBARI-24683
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.3
>
>
> HDFS service check cannot be run if no host in the cluster has HDFS_CLIENT.
> The operation is not even created due to the following exception:
> {noformat}
> org.apache.ambari.server.controller.spi.SystemException: An internal system
> exception occurred: No hosts found for service: HDFS, component: HDFS_CLIENT
> in cluster: TEST
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:287)
> at
> org.apache.ambari.server.controller.internal.RequestResourceProvider.createResources(RequestResourceProvider.java:193)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:298)
> ...
> Caused by: org.apache.ambari.server.AmbariException: No hosts found for
> service: HDFS, component: HDFS_CLIENT in cluster: TEST
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.findHostAndAddServiceCheckAction(AmbariCustomCommandExecutionHelper.java:540)
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:1109)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:4252)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24636) Add Service wizard fails if a service without configs is installed
[ https://issues.apache.org/jira/browse/AMBARI-24636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24636: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Add Service wizard fails if a service without configs is installed > -- > > Key: AMBARI-24636 > URL: https://issues.apache.org/jira/browse/AMBARI-24636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 50m > Remaining Estimate: 0h > > Fails during the Customize services page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24635) Web Client Chooses Wrong Version When Reverting Configs
[
https://issues.apache.org/jira/browse/AMBARI-24635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24635:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Web Client Chooses Wrong Version When Reverting Configs
> ---
>
> Key: AMBARI-24635
> URL: https://issues.apache.org/jira/browse/AMBARI-24635
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> STR:
> - Setup a simple cluster with ZK, HDFS, YARN, Hive, Pig
> - Create at least 5 different configuration versions for Pig
> - Load the Pig configuration page and select v4
> - Now select V3 and then choose "Make Current"
> At this point, the web client will populate a dialog that says {{Created from
> service config version V4}} and indeed it restores v4, not v3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24587) HDI Livy2 fails to restart
[
https://issues.apache.org/jira/browse/AMBARI-24587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24587:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> HDI Livy2 fails to restart
> --
>
> Key: AMBARI-24587
> URL: https://issues.apache.org/jira/browse/AMBARI-24587
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: AMBARI-24587.patch
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Livy2 restart fails from Ambari due to Ambari could not fetch some Hadoop
> configs?
> StdErr:
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 148, in
> LivyServer().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 351, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 62, in start
> self.configure(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/livy2_server.py",
> line 52, in configure
> setup_livy(env, 'server', upgrade_type=upgrade_type, action =
> 'config')
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/setup_livy2.py",
> line 53, in setup_livy
> params.HdfsResource(None, action="execute")
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 681, in action_execute
> self.get_hdfs_resource_executor().action_execute(self)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/providers/hdfs_resource.py",
> line 164, in action_execute
> logoutput=logoutput,
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/environment.py", line
> 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py",
> line 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop
> --config /usr/hdp/3.0.1.0-175/hadoop/conf jar
> /var/lib/ambari-agent/lib/fast-hdfs-resource.jar
> /var/lib/ambari-agent/tmp/hdfs_resources_1535895647.58.json' returned 1.
> Initializing filesystem uri: hdfs://mycluster
> Creating: Resource [source=null,
> target=wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> type=directory, action=create, owner=livy, group=null, mode=700,
> recursiveChown=false, recursiveChmod=false, changePermissionforParents=false,
> manageIfExists=true] in hdfs://mycluster
> Exception occurred, Reason: Wrong FS:
> wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> expected: hdfs://mycluster
> java.lang.IllegalArgumentException: Wrong FS:
> wasb://spark2l-at30wu-livy2-121...@humbtesting5wua2.blob.core.windows.net/user/livy/recovery-69e01f25-3b7b-4af4-a787-37664ab45f0c,
> expected: hdfs://mycluster
> at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:781)
> at
[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 ] Jayush Luniya updated AMBARI-23327: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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 >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24569) Cannot deploy Hive Metastore with Kerberos without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24569:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cannot deploy Hive Metastore with Kerberos without HDFS
> ---
>
> Key: AMBARI-24569
> URL: https://issues.apache.org/jira/browse/AMBARI-24569
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In order to enable Kerberos for Hive MetaStore we need a property in
> {{core-site}}, which is ignored by Ambari if HDFS is not present. Hive
> Metastore start fails due to empty {{core-site}} with:
> {noformat}
> KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for
> /hive/cluster/delegationMETASTORE/keys
> {noformat}
--
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 ] Jayush Luniya updated AMBARI-24118: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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.3 > > 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-24633) Ambari strips leading space for valid YARN configs on the config compare screen
[
https://issues.apache.org/jira/browse/AMBARI-24633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24633:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Ambari strips leading space for valid YARN configs on the config compare
> screen
> ---
>
> Key: AMBARI-24633
> URL: https://issues.apache.org/jira/browse/AMBARI-24633
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 2 optional properties in yarn-site,
> {noformat}
> yarn.timeline-service.read.allowed.users
> .acl_application_max_priority
> {noformat}
> are of the form
> {noformat}
> ,..,..
> {noformat}
> Here the users are optional. Hence only groups could be specified with a
> leading space followed by ,..
> But after setting such a configuration, Ambari strips the leading space and
> shows them as
> {noformat}
> ,
> {noformat}
> instead of,
> {noformat}
> ,
> {noformat}
> when comparing 2 config versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
[ https://issues.apache.org/jira/browse/AMBARI-24523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24523: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Hive and Oozie JDBC url reset after set manually > > > Key: AMBARI-24523 > URL: https://issues.apache.org/jira/browse/AMBARI-24523 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > JDBC urls of Hive and Oozie are reset even after being set manually when > toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24681) Cannot deploy cluster without HDFS_CLIENT
[
https://issues.apache.org/jira/browse/AMBARI-24681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24681:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cannot deploy cluster without HDFS_CLIENT
> -
>
> Key: AMBARI-24681
> URL: https://issues.apache.org/jira/browse/AMBARI-24681
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: blueprint.json, bp-scale.json
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The attached blueprint cannot be deployed, because {{hadoop-env.sh}} is not
> saved by Ambari, because it requires {{HDFS_CLIENT}} component on at least
> one host:
> https://github.com/apache/ambari/blob/8d145e0c04917866fd76690688826cf44065370e/ambari-server/src/main/resources/stack-hooks/before-ANY/scripts/hook.py#L32-L33
> Datanode start fails with:
> {noformat}
> ExecutionFailed: Execution of 'ambari-sudo.sh su hdfs -l -s /bin/bash -c
> 'ulimit -c unlimited ; /usr/hdp/3.0.0.0-1634/hadoop/bin/hdfs --config
> /usr/hdp/3.0.0.0-1634/hadoop/conf --daemon start datanode'' returned 1.
> ERROR: JAVA_HOME is not set and could not be found.
> {noformat}
> This appears in output from {{after-INSTALL}} hook:
> {noformat}
> Parameter hadoop_conf_dir is missing or directory does not exist. This is
> expected if this host does not have any Hadoop components.
> {noformat}
> Additionally, host groups without {{HDFS_CLIENT}} cannot be scaled up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24620) Duplicate view of configurations in Add Service wizard
[ https://issues.apache.org/jira/browse/AMBARI-24620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24620: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Duplicate view of configurations in Add Service wizard > -- > > Key: AMBARI-24620 > URL: https://issues.apache.org/jira/browse/AMBARI-24620 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: duplicate-view.png > > Time Spent: 1h > Remaining Estimate: 0h > > See screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24553) Cannot start Hive Metastore without HDFS
[
https://issues.apache.org/jira/browse/AMBARI-24553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24553:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cannot start Hive Metastore without HDFS
>
>
> Key: AMBARI-24553
> URL: https://issues.apache.org/jira/browse/AMBARI-24553
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Starting Hive Metastore fails if HDFS is not present in the cluster with the
> error: {{JAVA_HOME is not set and could not be found.}}
> {noformat}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 211, in
> HiveMetastore().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive_metastore.py",
> line 61, in start
> create_metastore_schema() # execute without config lock
> File
> "/var/lib/ambari-agent/cache/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py",
> line 374, in create_metastore_schema
> user = params.hive_user
> File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line
> 166, in __init__
> self.env.run()
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py",
> line 263, in action_run
> returns=self.resource.returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 314, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of 'export
> HIVE_CONF_DIR=/usr/hdp/current/hive-metastore/conf/conf.server ;
> /usr/hdp/current/hive-server2-hive2/bin/schematool -initSchema -dbType mysql
> -userName hive -passWord [PROTECTED] -verbose' returned 1. Error: JAVA_HOME
> is not set and could not be found.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24546) Protect the Request resource so that only authorized users may have read-only access the data
[
https://issues.apache.org/jira/browse/AMBARI-24546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24546:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Protect the Request resource so that only authorized users may have read-only
> access the data
> -
>
> Key: AMBARI-24546
> URL: https://issues.apache.org/jira/browse/AMBARI-24546
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, rbac
> Fix For: 2.7.3
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> Protect the Request resource so that only authorized users may have read-only
> access the data.
> Users with the following roles should have read-only access:
> * {{AMBARI.ADMINISTRATOR}}
> * {{CLUSTER.ADMINISTRATOR}}
> * {{CLUSTER.OPERATOR}}
> * {{SERVICE.ADMINISTRATOR}}
> * {{SERVICE.OPERATOR}}
> * {{CLUSTER.USER}}
> Users with no role related to the cluster may not view the data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24716) Restrict user permissions for Atlas configuration file
[ https://issues.apache.org/jira/browse/AMBARI-24716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24716: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Restrict user permissions for Atlas configuration file > -- > > Key: AMBARI-24716 > URL: https://issues.apache.org/jira/browse/AMBARI-24716 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Need to restrict user permissions for Atlas configuration file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24583) Ambari agent status could be reported stale just after execution command thread has finished execution
[ https://issues.apache.org/jira/browse/AMBARI-24583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24583: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Ambari agent status could be reported stale just after execution command > thread has finished execution > -- > > Key: AMBARI-24583 > URL: https://issues.apache.org/jira/browse/AMBARI-24583 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24583.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24578) Quicklinks URL overflow outside the UI box
[ https://issues.apache.org/jira/browse/AMBARI-24578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24578: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Quicklinks URL overflow outside the UI box > -- > > Key: AMBARI-24578 > URL: https://issues.apache.org/jira/browse/AMBARI-24578 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: quicklinks.png > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Quicklinks in HDI environment are overflowing in UI. See attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24628) Fix possible "Phishing by Navigating Browser Tabs" vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24628:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Fix possible "Phishing by Navigating Browser Tabs" vulnerability
>
>
> Key: AMBARI-24628
> URL: https://issues.apache.org/jira/browse/AMBARI-24628
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: amarnath reddy pappu
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> According to details found at
> https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/phishing-by-navigating-browser-tabs/,
> it is possible to change the "window.opener.location" value in browser
> windows opened using normal anchor tags where the "target" attribute is
> specified as "_blank".
> This gives an attacker the ability to change the parent location and thus
> potentially allow for a phishing attack to invoked.
> To help this situation, it is suggested that the following attribute be set
> along with the "target" attribute:
> {noformat}
> rel="noopener noreferrer"
> {noformat}
> For example:
> {noformat}
> ...
> {noformat}
--
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 ] Jayush Luniya updated AMBARI-23817: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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 > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 1h 50m > 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-24641) Stackadvisor error while trying to add atlas service. Error - "if mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
[
https://issues.apache.org/jira/browse/AMBARI-24641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24641:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Stackadvisor error while trying to add atlas service. Error - "if
> mountPoints[mountPoint] < reqiuredDiskSpace: KeyError: None"
> --
>
> Key: AMBARI-24641
> URL: https://issues.apache.org/jira/browse/AMBARI-24641
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Stack advisor error:
> {code}
> Error details: None
> 2018-09-11 06:40:09,738 INFO [ambari-client-thread-24150]
> StackAdvisorRunner:167 - Advisor script stderr: Traceback (most recent
> call last):
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 184,
> in
> main(sys.argv)
> File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 138,
> in main
> result = stackAdvisor.validateConfigurations(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1079, in validateConfigurations
> validationItems = self.getConfigurationsValidationItems(services, hosts)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1468, in getConfigurationsValidationItems
>
> items.extend(self.getConfigurationsValidationItemsForService(configurations,
> recommendedDefaults, service, services, hosts))
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1521, in getConfigurationsValidationItemsForService
>
> items.extend(serviceAdvisor.getServiceConfigurationsValidationItems(configurations,
> recommendedDefaults, services, hosts))
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 218, in getServiceConfigurationsValidationItems
> return validator.validateListOfConfigUsingMethod(configurations,
> recommendedDefaults, services, hosts, validator.validators)
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 1491, in validateListOfConfigUsingMethod
> validationItems = method(siteProperties, siteRecommendations,
> configurations, services, hosts)
> File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/AMBARI_METRICS/service_advisor.py",
> line 556, in validateAmsHbaseSiteConfigurationsFromHDP206
> validationItems.extend([{"config-name": 'hbase.rootdir', "item":
> self.validatorEnoughDiskSpace(properties, 'hbase.rootdir', host["Hosts"],
> recommendedDiskSpace)}])
> File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py",
> line 2998, in validatorEnoughDiskSpace
> if mountPoints[mountPoint] < reqiuredDiskSpace:
> KeyError: None
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24593) Download client config fails if user running Ambari server has UID>2097151
[
https://issues.apache.org/jira/browse/AMBARI-24593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24593:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Download client config fails if user running Ambari server has UID>2097151
> ---
>
> Key: AMBARI-24593
> URL: https://issues.apache.org/jira/browse/AMBARI-24593
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When ambari is running with a user that has UID/GID >2097151 download client
> configs fails with the following error:
> {code}
> {
> "status" : 500,
> "message" : "org.apache.ambari.server.controller.spi.SystemException: group
> id '1966' is too big ( > 2097151 )"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24540) Allow skipping Oozie DB schema creation for sysprepped cluster
[
https://issues.apache.org/jira/browse/AMBARI-24540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24540:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Allow skipping Oozie DB schema creation for sysprepped cluster
> --
>
> Key: AMBARI-24540
> URL: https://issues.apache.org/jira/browse/AMBARI-24540
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Oozie DB schema may be manually pre-created to save time during initial
> service start. However, {{ooziedb.sh}} could still take quite some time to
> confirm that the schema exists. The goal of this change is to allow users
> who pre-create Oozie DB schema to make Ambari skip managing the DB (create or
> check existence).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24627) "Host is in Maintenance mode" text is not displayed in UI after maintenance mode is turned on
[ https://issues.apache.org/jira/browse/AMBARI-24627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24627: --- Fix Version/s: (was: 2.7.2) 2.7.3 > "Host is in Maintenance mode" text is not displayed in UI after maintenance > mode is turned on > - > > Key: AMBARI-24627 > URL: https://issues.apache.org/jira/browse/AMBARI-24627 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Behavior in ambari-2.7.0 > 1. login > 2. navigate host details page. > 3. click host action > 4. click "Turn On Maintenance Mode" > after the first confirm window. we can see the text which displays "Host is > in Maintenance mode" > > But in ambari-2.7.1 > The UI Tab which display "Turn On Maintenance Mode" > It is not getting displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24526) Status of components does not become RED if their deamon goes down immediately after successful start
[ https://issues.apache.org/jira/browse/AMBARI-24526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24526: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Status of components does not become RED if their deamon goes down > immediately after successful start > - > > Key: AMBARI-24526 > URL: https://issues.apache.org/jira/browse/AMBARI-24526 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24526.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24585) 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy' is not equal to the value of yarn_hierarchy in UI Deploy
[
https://issues.apache.org/jira/browse/AMBARI-24585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24585:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy' is not equal to
> the value of yarn_hierarchy in UI Deploy
> --
>
> Key: AMBARI-24585
> URL: https://issues.apache.org/jira/browse/AMBARI-24585
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: Screen Shot 2018-09-02 at 10.20.43 PM.png, Screen Shot
> 2018-09-02 at 10.22.33 PM.png, Screen Shot 2018-09-02 at 10.25.08 PM.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The property 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy'
> does not show up in the UI install wizard even when {{yarn_cgroups_enabled}}
> and {{gpu_module_enabled}} are enabled in YARN configs. But this property is
> available after deployment of the cluster.
> !Screen Shot 2018-09-02 at 10.20.43 PM.png|thumbnail!
> !Screen Shot 2018-09-02 at 10.22.33 PM.png|thumbnail!
> When trying to set a value for the config
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy', Stack advisor
> displays the following:
> {code}
> yarn.nodemanager.linux-container-executor.cgroups.hierarchy and
> yarn_hierarchy should always have same value
> yarn.nodemanager.linux-container-executor.cgroups.hierarchy and
> yarn_hierarchy should always have same value
> Name of the Cgroups hierarchy under which all YARN jobs will be launched
> {code}
> !Screen Shot 2018-09-02 at 10.25.08 PM.png|thumbnail!
> From the stack advisor description, looks like
> 'yarn.nodemanager.linux-container-executor.cgroups.hierarchy' property needs
> to be same as yarn_hierarchy. As part of UI Deploy, the property
> {{yarn_hierarchy}} is set to
> {{hadoop-yarn-tmp-ctr-e138-1518143905142-461959-01-02.hwx.site}}. But
> after deploy, the
> {{yarn.nodemanager.linux-container-executor.cgroups.hierarchy}} is set to
> {{/yarn}} and not the property set while UI Deploy. This is causing Deploy
> failures due to Nodemanagers not getting started. When this property is set
> correctly, Nodemanagers start successfully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24623) hdfsResource fails to using nameservices for filesystems which does not support that
[ https://issues.apache.org/jira/browse/AMBARI-24623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24623: --- Fix Version/s: (was: 2.7.2) 2.7.3 > hdfsResource fails to using nameservices for filesystems which does not > support that > > > Key: AMBARI-24623 > URL: https://issues.apache.org/jira/browse/AMBARI-24623 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24623.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Some filesystems does not support nameservices: > > > resource_management.core.exceptions.ExecutionFailed: Execution of 'hadoop > --config /usr/hdp/3.0.1.0-179/hadoop/conf jar > /var/lib/ambari-agent/lib/fast-hdfs-resource.jar > /var/lib/ambari-agent/tmp/hdfs_resources_1536226305.38.json' returned 1. > Exception occurred, Reason: abfs://mycluster has invalid authority. > abfs://mycluster has invalid authority. > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.initializeClient(AzureBlobFileSystemStore.java:732) > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.(AzureBlobFileSystemStore.java:129) > at > org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.initialize(AzureBlobFileSystem.java:97) > at > org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3354) > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:124) > at > org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3403) > at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3371) > at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:477) > at org.apache.ambari.fast_hdfs_resource.Runner.main(Runner.java:83) > 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 org.apache.hadoop.util.RunJar.run(RunJar.java:318) > at org.apache.hadoop.util.RunJar.main(RunJar.java:232) > -- 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 ] Jayush Luniya updated AMBARI-23476: --- Fix Version/s: (was: 2.7.2) 2.7.3 > 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.3 > > 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] [Updated] (AMBARI-24562) Protect the ClusterConfig resource so that only authorized users may have read-only access the data
[
https://issues.apache.org/jira/browse/AMBARI-24562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24562:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Protect the ClusterConfig resource so that only authorized users may have
> read-only access the data
> ---
>
> Key: AMBARI-24562
> URL: https://issues.apache.org/jira/browse/AMBARI-24562
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available, rbac
> Fix For: 2.7.3
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Protect the ClientConfig resource so that only authorized users may have
> read-only access the data.
> Users with the following permission should have read-only access:
> * {{CLUSTER.VIEW_CONFIGS}}
> * {{SERVICE.VIEW_CONFIGS}}
> * {{HOST.VIEW_CONFIGS}}
> These permissions should be allow for the following roles:
> * {{AMBARI.ADMINISTRATOR}}
> * {{CLUSTER.ADMINISTRATOR}}
> * {{CLUSTER.OPERATOR}}
> * {{SERVICE.ADMINISTRATOR}}
> * {{SERVICE.OPERATOR}}
> * {{CLUSTER.USER}}
> Users with no role related to the cluster may not view the data.
> Example REST API entry point:
> {noformat}
> GET
> /api/v1/clusters/cl1/services/HDFS/components/HDFS_CLIENT?format=client_config_tar
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24527) Unable to Add ZooKeeper-Only Host To Cluster With Hadoop
[ https://issues.apache.org/jira/browse/AMBARI-24527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24527: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Unable to Add ZooKeeper-Only Host To Cluster With Hadoop > > > Key: AMBARI-24527 > URL: https://issues.apache.org/jira/browse/AMBARI-24527 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: AMBARI-24527.patch, AMBARI-24527.patch, > AMBARI-24527.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24603: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 40m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- 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 ] Jayush Luniya updated AMBARI-23820: --- Fix Version/s: (was: 2.7.2) 2.7.3 > [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.3 > > Original Estimate: 48h > Time Spent: 48h > Remaining Estimate: 0h > > Provide a setting to show FQDN or short hostname: > FQDN: logsearch-demo-1.c.pramod-thangali.internal > Short Hostname: logsearch-demo-1 > If shortname is preferred then show: FQDN.split(“.”)[0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24556) Aggregation across clusters are not being done in AMS for even when multiple cluster support is enabled.
[ https://issues.apache.org/jira/browse/AMBARI-24556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24556: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Aggregation across clusters are not being done in AMS for even when multiple > cluster support is enabled. > > > Key: AMBARI-24556 > URL: https://issues.apache.org/jira/browse/AMBARI-24556 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.1 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24592) Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart
[ https://issues.apache.org/jira/browse/AMBARI-24592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24592: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Blueprint installation stuck (cannot resolve cluster-env), continues after > ambari-server restart > > > Key: AMBARI-24592 > URL: https://issues.apache.org/jira/browse/AMBARI-24592 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0, 2.7.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > The issue occurs with exported blueprints. These blueprints contain the stack > defaults. When a new cluster is installed from such blueprint the > *BlueprintConfigurationProcessor* falsely thinks it updates _cluster-env_ > when setting the stack defaults. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23217) Spark and Spark2 SSL credentials in Ambari UI are in plain text rather than being hidden
[ https://issues.apache.org/jira/browse/AMBARI-23217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-23217: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Spark and Spark2 SSL credentials in Ambari UI are in plain text rather than > being hidden > > > Key: AMBARI-23217 > URL: https://issues.apache.org/jira/browse/AMBARI-23217 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.6.2 >Reporter: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.3 > > > Below properties which are part of Spark and Spark2 are in plaintext rather > than being hidden in Ambari > livy.key-password > livy.keystore.password > livy.ssl.trustStorePassword > spark.ssl.keyPassword > spark.ssl.keyStorePassword > spark.ssl.trustStorePassword > spark.ssl.keyPassword > spark.ssl.keyStorePassword > spark.ssl.trustStorePassword -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24549) Move blueprint provisioning state property to host component level
[ https://issues.apache.org/jira/browse/AMBARI-24549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24549: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Move blueprint provisioning state property to host component level > -- > > Key: AMBARI-24549 > URL: https://issues.apache.org/jira/browse/AMBARI-24549 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Move blueprint provisioning state property from cluster level to host > component level. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24654) Tasks fail on ambari-agent intermittently under cpu load due to race condition in ambari-agent
[
https://issues.apache.org/jira/browse/AMBARI-24654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24654:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Tasks fail on ambari-agent intermittently under cpu load due to race
> condition in ambari-agent
> --
>
> Key: AMBARI-24654
> URL: https://issues.apache.org/jira/browse/AMBARI-24654
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Attachments: AMBARI-24654.patch, AMBARI-24654.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> INFO 2018-09-13 18:30:15,817 ClusterCache.py:125 - Rewriting cache
> ClusterTopologyCache for cluster 2
> ERROR 2018-09-13 18:30:16,386 CustomServiceOrchestrator.py:456 - Caught
> an exception while executing custom service command: 'exceptions.TypeError'>: 'NoneType' object has no attribute '__getitem__';
> 'NoneType' object has no attribute '__getitem__'
> Traceback (most recent call last):
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 324, in runCommand
> command = self.generate_command(command_header)
> File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 504, in generate_command
> command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp)
> File "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py",
> line 46, in get_configuration
> 'agentLevelParams': {'hostname':
> self.topology_cache.get_current_host_info(cluster_id)['hostName']},
> TypeError: 'NoneType' object has no attribute '__getitem__'
>
> This was found while perf testing.
> However can occur under any circumstances if ambari-agent node if slow enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24658) Cluster creation fails with KeyError in get_cluster_host_info method of ClusterTopologyCache.py
[
https://issues.apache.org/jira/browse/AMBARI-24658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24658:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Cluster creation fails with KeyError in get_cluster_host_info method of
> ClusterTopologyCache.py
> ---
>
> Key: AMBARI-24658
> URL: https://issues.apache.org/jira/browse/AMBARI-24658
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Siddharth Wagle
>Assignee: Andrew Onischuk
>Priority: Blocker
> Fix For: 2.7.3
>
>
> Cluster creation fails with KeyError in get_cluster_host_info method of
> ClusterTopologyCache.py'
> Here is the stacktrace:
> {code}
> ambari_agent - CustomServiceOrchestrator.py - [4840] - root - ERROR - Caught
> an exception while executing custom service command: 'exceptions.KeyError'>: 7; 7#012Traceback (most recent call last):#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py", line
> 324, in runCommand#012 command = self.generate_command(command_header)#012
> File "/usr/lib/ambari-agent/lib/ambari_agent/CustomServiceOrchestrator.py",
> line 504, in generate_command#012 command_dict =
> self.configuration_builder.get_configuration(cluster_id, service_name,
> component_name, required_config_timestamp)#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ConfigurationBuilder.py", line 43, in
> get_configuration#012 'clusterHostInfo':
> self.topology_cache.get_cluster_host_info(cluster_id),#012 File
> "/usr/lib/ambari-agent/lib/ambari_agent/ClusterTopologyCache.py", line 108,
> in get_cluster_host_info#012 hostnames =
> [self.hosts_to_id[cluster_id][host_id].hostName for host_id in
> component_dict.hostIds]#012KeyError: 7
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24552) Storm service-check fails due to missung StringUtils class definition
[
https://issues.apache.org/jira/browse/AMBARI-24552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24552:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> Storm service-check fails due to missung StringUtils class definition
> -
>
> Key: AMBARI-24552
> URL: https://issues.apache.org/jira/browse/AMBARI-24552
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: 2.6.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {code:java}
> 2018-08-21 21:46:35.810 o.a.s.util
> Thread-24-__metricsorg.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink-executor[4
> 4] [ERROR] Async loop died!
> java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils
> at
> org.apache.hadoop.metrics2.sink.storm.StormTimelineMetricsSink.prepare(StormTimelineMetricsSink.java:133)
> ~[ambari-metrics-storm-sink-with-common-2.6.1.0.144.jar:?]
> at
> org.apache.storm.metric.MetricsConsumerBolt.prepare(MetricsConsumerBolt.java:75)
> ~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at
> org.apache.storm.daemon.executor$fn__10252$fn__10265.invoke(executor.clj:800)
> ~[storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at org.apache.storm.util$async_loop$fn__553.invoke(util.clj:482)
> [storm-core-1.1.0.2.6.6.0-26.jar:1.1.0.2.6.6.0-26]
> at clojure.lang.AFn.run(AFn.java:22) [clojure-1.7.0.jar:?]
> at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.lang.StringUtils
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> ~[?:1.8.0_112]
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> ~[?:1.8.0_112]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ~[?:1.8.0_112]
> ... 6 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24645) Issues with tooltip containing custom time range for charts
[ https://issues.apache.org/jira/browse/AMBARI-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24645: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Issues with tooltip containing custom time range for charts > --- > > Key: AMBARI-24645 > URL: https://issues.apache.org/jira/browse/AMBARI-24645 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.2 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > - The tooltip content is not formatted > - Tooltip isn't displayed on some pages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24343) [LogSearch] Wrong (error) response format
[
https://issues.apache.org/jira/browse/AMBARI-24343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-24343:
---
Fix Version/s: (was: 2.7.2)
2.7.3
> [LogSearch] Wrong (error) response format
> -
>
> Key: AMBARI-24343
> URL: https://issues.apache.org/jira/browse/AMBARI-24343
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 2.7.1
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When I call the
> {noformat}
> /shipper/input/\{clusterName}/services/\{serviceName}
> {noformat}
> api endpoint with wrong json schema the backend responses with plain text
> body instead of json or empty body.
> For example:
> {code:json}
> {
> "input": [
> {
> "type": "zookeeper",
> "rowtype": "service",
> "path": "/var/log/zookeeper/zookeeper*.log"
> }
> ],
> "filter": [
> {
> "filter": "grok",
> "conditions": {
> "fieldss": {
> "type": [
> "zookeeper"
> ]
> }
> },
> "skipOnError": false,
> "deepExtract": false,
> "post_map_values": {
> "logtime": [
> {
> "map_date": {
> "target_date_pattern": "-MM-dd HH:mm:ss,SSS"
> }
> }
> ]
> },
> "log4j_format": "%d\{ISO8601} - %-5p [%t:%C\{1}@%L] - %m%n",
> "multiline_pattern": "^(%\{TIMESTAMP_ISO8601:logtime})",
> "message_pattern":
> "(?m)^%\{TIMESTAMP_ISO8601:logtime}%\{SPACE}-%\{SPACE}%\{LOGLEVEL:level}%\{SPACE}\\[%\{DATA:thread_name}\\@%\{INT:line_number}\\]%\{SPACE}-%\{SPACE}%\{GREEDYDATA:log_message}"
> }
> ]
> }
> {code}
> Where the `fieldss` is not a valid JSON key.
> The response plain text body:
> {code:javascript}
> Unrecognized field "fieldss" (class
> org.apache.ambari.logsearch.model.common.LSServerConditions), not marked as
> ignorable (one known property: "fields"])
> at [Source: UNKNOWN; line: -1, column: -1] (through reference chain:
> org.apache.ambari.logsearch.model.common.LSServerInputConfig["filter"]->org.apache.ambari.logsearch.model.common.LSServerFilterGrok["conditions"]->org.apache.ambari.logsearch.model.common.LSServerConditions["fieldss"])
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24605) ambari-server exception if any user with cluster operator role is trying to edit the widget.
[ https://issues.apache.org/jira/browse/AMBARI-24605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24605: --- Fix Version/s: (was: 2.7.2) 2.7.3 > ambari-server exception if any user with cluster operator role is trying to > edit the widget. > > > Key: AMBARI-24605 > URL: https://issues.apache.org/jira/browse/AMBARI-24605 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.1 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: RoleChart.png, > errorWhileEditingWidgetsAsClusterOperator.png > > Time Spent: 1h > Remaining Estimate: 0h > > *STR* > 1. login using widgetuser(username),widgetpass(password) the role is cluster > operator > 2. go to hdfs-> metrics tab > 3. EDIT shared the "Under Replicated Blocks" widgets. > 4. the error can be reproduced > *Actual Result:* > !errorWhileEditingWidgetsAsClusterOperator.png! > *Expected Result:* > According to our Role Chart a user with Cluster Operator role should be able > to create/edit widgets > !RoleChart.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24595) PrincipalKeyCredential.equals fails for subtypes
[ https://issues.apache.org/jira/browse/AMBARI-24595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24595: --- Fix Version/s: (was: 2.7.2) 2.7.3 > PrincipalKeyCredential.equals fails for subtypes > > > Key: AMBARI-24595 > URL: https://issues.apache.org/jira/browse/AMBARI-24595 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.2.0 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Fix > org.apache.ambari.server.security.credential.PrincipalKeyCredential#equals to > allow for subtypes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24772) Support cross-stack inheritance
Jayush Luniya created AMBARI-24772: -- Summary: Support cross-stack inheritance Key: AMBARI-24772 URL: https://issues.apache.org/jira/browse/AMBARI-24772 Project: Ambari Issue Type: Task Components: ambari-server, stacks Affects Versions: 2.8.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24773) Support cross-stack inheritance
Jayush Luniya created AMBARI-24773: -- Summary: Support cross-stack inheritance Key: AMBARI-24773 URL: https://issues.apache.org/jira/browse/AMBARI-24773 Project: Ambari Issue Type: Task Components: ambari-server, stacks Affects Versions: 2.8.0 Reporter: Jayush Luniya Assignee: Jayush Luniya Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
