I tried to deploy greenwave into Openshit staging and the docker build[1] is failed. I can't troubleshoot the problem since I can't see any logs here[2]. Could anyone please take a look?
Thanks,
[1] https://os.stg.fedoraproject.org/console/project/greenwave/browse/builds/greenwave-docker-build/greenwave-docker-build-16?tab=details [2] https://os.stg.fedoraproject.org/console/project/greenwave/browse/rc/greenwave-web-20?tab=logs
I can see the log with this command oc logs build/greenwave-docker-build-16. Not sure why the UI shows nothing. It might be a bug in OpenShift.
oc logs build/greenwave-docker-build-16
This step is failed in the docker build:
Step 3 : RUN dnf -v -y install --setopt=tsflags=nodocs python-gunicorn python-requests PyYAML fedmsg-hub python2-flask ---> Running in 85abb69d7d25 DNF version: 2.5.1 cachedir: /var/cache/dnf Cannot download 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f26&arch=x86_64': Cannot prepare internal mirrorlist: Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=updates-released-f26&arch=x86_64 [Failed to connect to mirrors.fedoraproject.org port 443: No route to host]. Error: Failed to synchronize cache for repo 'updates' error: build error: The command '/bin/sh -c dnf -v -y install --setopt=tsflags=nodocs python-gunicorn python-requests PyYAML fedmsg-hub python2-flask' returned a non-zero code: 1
I can access the mirror from my local machine, so it seems like there is a networking problem in the container.
This was a remnant of the iptables mess we had before (the exclusion from standard infra rules didn't work as intended). This is now fixed, and a build is running now.
Metadata Update from @puiterwijk: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
greenwave-docker-build-23 Docker Dockerfile Complete 3 minutes ago 3m16s
Login to comment on this ticket.