Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Using the overlay2 driver, a file which is deleted still shows up in calls to 'ls' and also in file globs. This causes problems for any command where a glob is consumed and tries to act on a file which doesn't actually exist.
Version-Release number of selected component (if applicable):
This is seen on a current up-to-date centos-7 host and containers
# uname -a
Linux uc-ovb-master.localdomain 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12 15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# docker --version
Docker version 1.12.6, build 3a094bd/1.12.6
How reproducible:
This is seen always on an up-to-date centos-7 host and containers.
Steps to Reproduce:
# docker run --user root -ti --rm centos:7 /bin/bash -c "rm -f /etc/init.d/README ; ls /etc/init.d ; echo /etc/init.d/* ; cat /etc/init.d/README"
Actual results:
The following output occurs
README
/etc/init.d/README
cat: /etc/init.d/README: No such file or directory
Expected results:
/etc/init.d/*
cat: /etc/init.d/README: No such file or directory
Additional info:
In OpenStack TripleO we've switched to using the overlay2 driver, but this bug is causing errors with files not existing when running "cp -a /etc/* ...". See the attached launchpad bug.
What's the underlying fs type? `docker info` ?
I think this is likely to be a dup of: https://bugzilla.redhat.com/show_bug.cgi?id=1288162#c81
Basically, your /var/lib/docker needs to be on a newer XFS. You can make it its own LV, or reinstall with 7.3.
I tried again with a newer centos cloud image (CentOS-7-x86_64-GenericCloud-1704) and cannot reproduce.
# xfs_info / |grep ftype
naming =version 2 bsize=4096 ascii-ci=0 ftype=1