bots: Drop docker resolv.conf hack #9040
Conversation
martinpitt
force-pushed
the
docker-cleanup
branch
from
c7ac63f to
034497f
Compare
|
Wow, that actually worked everywhere. Triggering continuous-atomic, fedora-26, and fedora-testing to have the full spectrum. |
https://bugzilla.redhat.com/show_bug.cgi?id=1448331 apparently got fixed a while ago, and the hack is not necessary on any of our images any more. Also, the resolv.conf creation hack was duplicated in a lot of places. Should this still happen in some special case, let's only do this in the tests, not on the images, as they are much harder to change and clean up. Remove the hack from the Atomic images for now. It is still present in {debian,fedora,openshift,rhel,selenium}.setup, these will be rebuilt and cleaned up in separate pull requests. Closes cockpit-project#9040
martinpitt
force-pushed
the
docker-cleanup
branch
from
034497f to
d828cb1
Compare
martinpitt
changed the title
|
image-refresh in progress on cockpit-tasks-sh8tm. |
cockpituous
changed the title
martinpitt
changed the title
|
I forgot, fedora-atomic is blocked by #9002. So let's only rebuild the other two atomics. |
|
image-refresh in progress on cockpit-tasks-mrr3b. |
cockpituous
changed the title
cockpituous
changed the title
|
image-refresh in progress on cockpit-tasks-fckv7. |
|
image-refresh fedora-atomic done: https://github.com/cockpituous/cockpit/commits/image-refresh-fedora-atomic-20180425-070202 |
cockpituous
changed the title
|
image-refresh in progress on cockpit-tasks-sh8tm. |
cockpituous
changed the title
|
image-refresh continuous-atomic done: https://github.com/cockpituous/cockpit/commits/image-refresh-continuous-atomic-20180425-070404 |
cockpituous
changed the title
|
image-refresh in progress on cockpit-tasks-npcrk. |
cockpituous
changed the title
cockpituous
changed the title
|
image-refresh in progress on cockpit-tasks-zj9p4. |
|
image-refresh continuous-atomic done: https://github.com/cockpituous/cockpit/commits/image-refresh-continuous-atomic-20180425-071818 |
cockpituous
changed the title
|
image-refresh in progress on cockpit-tasks-sh8tm. |
cockpituous
changed the title
|
image-refresh rhel-atomic done: https://github.com/cockpituous/cockpit/commits/image-refresh-rhel-atomic-20180425-072828 |
cockpituous
changed the title
|
image-refresh rhel-atomic done: https://github.com/cockpituous/cockpit/commits/image-refresh-rhel-atomic-20180425-074242 |
https://bugzilla.redhat.com/show_bug.cgi?id=1448331 apparently got fixed a while ago, and the hack is not necessary on any of our images any more. Also, the resolv.conf creation hack was duplicated in a lot of places. Should this still happen in some special case, let's only do this in the tests, not on the images, as they are much harder to change and clean up. Remove the hack from the Atomic images for now. It is still present in {debian,fedora,openshift,rhel,selenium}.setup, these will be rebuilt and cleaned up in separate pull requests. Closes cockpit-project#9040
https://bugzilla.redhat.com/show_bug.cgi?id=1448331 apparently got fixed a while ago, and the hack is not necessary on any of our images any more. Also, the resolv.conf creation hack was duplicated in a lot of places. Should this still happen in some special case, let's only do this in the tests, not on the images, as they are much harder to change and clean up. Remove the hack from the Atomic images for now. It is still present in {debian,fedora,openshift,rhel,selenium}.setup, these will be rebuilt and cleaned up in separate pull requests. Closes #9040
https://bugzilla.redhat.com/show_bug.cgi?id=1448331 apparently got fixed
a while ago, and the hack is not necessary on any of our images any
more. Also, the resolv.conf creation hack was duplicated in a lot of
places.
Should this still happen in some special case, let's only do this in the
tests, not on the images, as they are much harder to change and clean
up.
Remove the hack from the Atomic images for now. It is still present in
{debian,fedora,openshift,rhel,selenium}.setup, these will be rebuilt and
cleaned up in separate pull requests.