Description of problem:
SELinux is preventing snapd from 'read' accesses on the directory /lost+found.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that snapd should be allowed read access on the lost+found directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'snapd' --raw | audit2allow -M my-snapd
# semodule -X 300 -i my-snapd.pp

Additional Information:
Source Context                system_u:system_r:snappy_t:s0
Target Context                system_u:object_r:lost_found_t:s0
Target Objects                /lost+found [ dir ]
Source                        snapd
Source Path                   snapd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    <Unknown>
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.13.12-300.fc27.x86_64 #1 SMP Wed
                              Nov 8 16:38:01 UTC 2017 x86_64 x86_64
Alert Count                   1
First Seen                    2017-11-16 21:51:29 CET
Last Seen                     2017-11-16 21:51:29 CET
Local ID                      d6131151-2c20-4f19-a622-8aa2089d5850

Raw Audit Messages
type=AVC msg=audit(1510865489.438:3181): avc:  denied  { read } for  pid=2316 comm="snapd" name="lost+found" dev="dm-3" ino=11 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:lost_found_t:s0 tclass=dir permissive=1


Hash: snapd,snappy_t,lost_found_t,dir,read


Additional info:
component:      selinux-policy
reporter:       libreport-2.9.3
hashmarkername: setroubleshoot
kernel:         4.13.12-300.fc27.x86_64
type:           libreport