You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/12 09:45:00 UTC

[jira] [Updated] (AMBARI-22961) Blacklist by default /boot/efi path as mount point reported by Ambari Agent

     [ https://issues.apache.org/jira/browse/AMBARI-22961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated AMBARI-22961:
------------------------------------
    Labels: pull-request-available  (was: )

> Blacklist by default /boot/efi path as mount point reported by Ambari Agent
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-22961
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22961
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-agent
>    Affects Versions: trunk
>            Reporter: Dmytro Grinenko
>            Assignee: Dmytro Grinenko
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: trunk
>
>
> On EFI Based systems, efi partition mounting under /boot/efi path. It causing Agent to report this mount point as available partition location. On new cluster deploy, this partition could be proposed by stack_adviser as datanode storage location, which is wrong.
> Workaround for versions without this patch: add \{{/boot/efi}} to \{{ignore_mount_points}} property, \{{agent}} section in ambari-agent.ini configuration file.
> Problem source:
> - https://community.hortonworks.com/questions/118551/namenode-can-not-be-started-1.html 
> - ASF mailing list



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)