Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker: curl: (22) The requested URL returned error: 404 Not Found for certain plugins #707

Closed
jcrben opened this issue Jul 11, 2018 · 6 comments

Comments

@jcrben
Copy link
Contributor

jcrben commented Jul 11, 2018

UPDATE: this is no longer happening for now, but still interested in learning more

I noticed today that my build of the docker container stopped working due to plugins not being accessible

Looks like the same issue as #470 and maybe a couple others? Don't see anything open tho. dc61939 says "They retry will likely get another mirror" but maybe there's a way to guarantee that?

If I remove pipeline-model-definition:1.3.1 and configuration-as-code:experimental it works. Is downtime on the plugins download site tracked anywhere? Not sure about the best place for these types of issues to be tracked. Also it's not entirely clear which URL precisely is failing.

I poked around at https://updates.jenkins.io/download/plugins/ to see if I could find a missing plugin, but both workflow-steps-api (https://updates.jenkins.io/download/plugins/workflow-step-api/) and structs seem to be available.

Docker commands that you execute

Reproduction available at https://gitlab.com/jcrben-repro/jenkins-jcasc-docker - run ./builder_jenkins.sh as mentioned in the readme

Note: the repro repo uses 2.128 but I also tried the latest tag.

Actual result

Stalls out with docker: curl: (22) The requested URL returned error: 404 Not Found for certain plugins

Expected outcome

Docker container built successfully

Have you tried a non-dockerized Jenkins and get the expected outcome?

No - specifically want to use the docker version.

Output of docker version

Client:
 Version:      18.03.1-ce
 API version:  1.37
 Go version:   go1.9.5
 Git commit:   9ee9f40
 Built:        Thu Apr 26 07:13:02 2018
 OS/Arch:      darwin/amd64
 Experimental: false
 Orchestrator: swarm

Server:
 Engine:
  Version:      18.03.1-ce
  API version:  1.37 (minimum version 1.12)
  Go version:   go1.9.5
  Git commit:   9ee9f40
  Built:        Thu Apr 26 07:22:38 2018
  OS/Arch:      linux/amd64
  Experimental: true

Other relevant information

image

@carlossg
Copy link
Contributor

There are some temporary issues, something for the Jenkins INFRA team to look at

@jcrben
Copy link
Contributor Author

jcrben commented Jul 18, 2018

NOTE: working again now

Encountering this again now with jenkins/jenkins:2.133:
image

Seems like there's a bug here where it's not trying a different mirror...? When I download these plugins manually from the browser, they work OK.

@rhuanbarreto
Copy link

This is still ocurring. I have an automated build to create a jenkins blueocean image from the following Dockerfile:

FROM jenkins/jenkins:alpine

USER root

ARG user=root
ARG group=root

RUN echo http://dl-cdn.alpinelinux.org/alpine/edge/community >> /etc/apk/repositories && \
    apk -U add docker py-pip

RUN pip install docker-compose

RUN /usr/local/bin/install-plugins.sh blueocean

RUN rm -rf /var/lib/apt/lists/* \
    /var/cache/apk/* \
    /usr/share/man \
    /tmp/*

VOLUME /var/run/docker.sock

On the build I get lot's of 404 not found on plugins lke sse-gateway workflow-step-api that are internal dependencies of blueocean.

@batmat
Copy link
Member

batmat commented Sep 10, 2018

Hello, though this issue can occur from time to time, this is AFAICT not an issue that is specific to this repository. This looks like something related to the mirroring infrastructure.
As Carlos was saying above, please file an issue in the INFRA project on the Jenkins issue tracker if you want to dig more. https://issues.jenkins-ci.org/

@batmat batmat closed this as completed Sep 10, 2018
@jcrben
Copy link
Contributor Author

jcrben commented Sep 12, 2018

So I guess this isn't tracked anywhere? Do you mind if I open an INFRA issue, or would that just be a distraction or a duplicate?

@josephaxisa
Copy link

josephaxisa commented Nov 29, 2018

I am having this exact same issue. Setting ATTEMPTS=3 as per the suggestion in #767 seems to solve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants