[ https://issues.apache.org/jira/browse/AMBARI-22961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361369#comment-16361369 ]
Hudson commented on AMBARI-22961: --------------------------------- SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8711 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8711/]) AMBARI-22961 Blacklist by default /boot/efi path as mount point reported (hapy.lestat: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e2ddcbbec50ba07b585a532a92dde0ac18f87e50]) * (edit) ambari-agent/src/main/python/ambari_agent/Hardware.py > 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 > > Time Spent: 3h > Remaining Estimate: 0h > > 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)