Red Hat Bugzilla – Bug 1271334
Test failures on latest fedora-1.9 branch
Last modified: 2016-07-19 14:12:25 EDT
Created attachment 1082502 [details]
Description of problem:
The current git HEAD of the fedora-1.9 branch of projectatomic/docker has a bunch of FAILures. I've attached a full log of "make test" to assist.
Version-Release number of selected component (if applicable):
git HEAD of fedora-1.9 branch, at commit 49b2a65633375ed1f5cf0de6f7147510f3836ff3
Steps to Reproduce:
1. Clone the projectatomic/docker repo and checkout the fedora-1.9 branch
2. Run "sudo make test"
FAILures as seen in attached file.
No FAILures, like when run against upstream docker.
A few of these failures seem to be due to the secrets getting mounted at /tmp/secrets rather than under /run. One of the affected tests is TestDiffEnsureOnlyKmsgAndPtmx, which essentially does a `docker run -d busybox sleep 0` and then `docker diff`.
The reason it fails is that it finds /tmp and /tmp/secrets in the output of `docker diff`, which it did not expect. The strange thing is that this only seems to occur when running the test. If I make an RPM at the same commit and run the same docker run & diff, I get /run and /run/secrets as expected. So it looks like there's something going on in the way the docker testing environment is set up.
Thanks to Jonathan for fixing these issues. The latest fedora-1.9 should not have the /run != /tmp problems.
Putting this ON_QA as docker 1.9 is already in stable and 1.10.1 is in testing.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.