In reference to issue #3183

[hostedvideorn]

In reference to issue #3183

For some reason when trying to synchronize the Jenkins repository lately I am getting the following error

Errors:
404, message='Not Found', url=URL('https://ftp-nyc.osuosl.org/pub/jenkins/redhat/jenkins-2.233-1.1.noarch.rpm')

[hostedvideorn]

@dduportal

[hostedvideorn]

Packages are being downloaded from https://pkg.jenkins.io/redhat/ - maybe the metadata has old info

[hostedvideorn]

Hi @dduportal - any comments / updates on this issue? thanks

[MarkEWaite]

https://ftp-nyc.osuosl.org/pub/jenkins/redhat/jenkins-2.333-1.1.noarch.rpm downloads correctly for me.

https://get.jenkins.io/redhat/jenkins-2.333-1.1.noarch.rpm?mirrorlist shows the expected set of mirrors that have the file available.

https://get.jenkins.io/redhat/jenkins-2.333-1.1.noarch.rpm downloads the file from my nearest mirror site as well

I don't think that we should spend any further effort attempting to make the Red Hat proprietary tool "Red Hat Satellite" work. We don't have access to that tool. We don't have a compelling use case for that tool, since our mirrors already provide global distribution. If someone from Red Hat wants to contribute a pull request to the Jenkins project to resolve it, we're willing to consider that pull request.

[hostedvideorn]

Hi @MarkEWaite, I never asked for the tool to be fixed because the tool works fine.
The file is jenkins-2.233-1.1.noarch.rpm and not jenkins-2.333-1.1.noarch.rpm

When trying to download https://ftp-nyc.osuosl.org/pub/jenkins/redhat/jenkins-2.233-1.1.noarch.rpm I got a 404 which means not found. I tried it manually as well with the same results.

[MarkEWaite]

Jenkins mirrors do not commit to retain all historical releases. The mirror you're trying to access (ftp-nyc.osuosl.org) does not have that file. It likely had that file at one time, but the file has been removed from the mirror.

Jenkins 2.233 is a weekly that was released 33 months ago. The Jenkins project stopped delivering security fixes for that release over 32 months ago. The Jenkins update center does not support versions older than 2.324 for weekly releases and 2.319.1 for LTS releases (see "Choosing a Jenkins version to build against").

If you must have that rpm file, it is available from https://archives.jenkins.io/redhat/jenkins-2.233-1.1.noarch.rpm.

I'm closing this ticket. No further work is planned on it.

[hostedvideorn]

@dduportal - right. I don't want to download that file. I was just pointing that the metadata still had that file and when trying to download from the mirror it was giving a 404 and throwing the error shown. I was pointing it out so maybe the metadata could be refreshed or something. That's all.

[hostedvideorn]

Jenkins mirrors do not commit to retain all historical releases. The mirror you're trying to access (ftp-nyc.osuosl.org) does not have that file. It likely had that file at one time, but the file has been removed from the mirror.

Jenkins 2.233 is a weekly that was released 33 months ago. The Jenkins project stopped delivering security fixes for that release over 32 months ago. The Jenkins update center does not support versions older than 2.324 for weekly releases and 2.319.1 for LTS releases (see "Choosing a Jenkins version to build against").

If you must have that rpm file, it is available from https://archives.jenkins.io/redhat/jenkins-2.233-1.1.noarch.rpm.

I'm closing this ticket. No further work is planned on it.

Hi @MarkEWaite - please see comments above. I don't plan to download this file but just pointing that the metadata still had it and because of that it was throwing the error shown.

[timja]

Re-opening in case there's something that can be done about the metadata not containing releases forever when mirrors won't have them

[hostedvideorn]

Thanks @timja - much appreciated

[hostedvideorn]

Re-opening in case there's something that can be done about the metadata not containing releases forever when mirrors won't have them

I'm following up to know if the team has been able to make any more progress on this.

[dduportal]

@hostedvideorn We'll let you know when we'll have time to prioritize this issue.

Alas we have other major tasks to work that will take us until mid-February before we can properly focus here. Sorry for that.

[dduportal]

Update: we are working on solutions. Some of our fellow Jenkins users in China faces the same kind of problem due to the network. We might have a solution as explained in #3636 (comment).

Please note that we do not provide any ETA: it's our top priority but we don't know obstacle on the road of this change.

[dduportal]

Hi @hostedvideorn , we recently defined archives.jenkins.io as the fallback for mirror downloads (as part of #3828), instead of the OSUOSL. It ensures we always have the file in the fallback.

You can see this behavior with https://get.jenkins.io/redhat/jenkins-2.233-1.1.noarch.rpm?mirrorlist: the mirror redirector system is now able to serve the file.

I've set up a local pulp mirror with and it worked without errors: the metadata keeps being served by pkg.jenkins.io and are specifying get.jenkins.io for binaries to download.

As such, I am closing this issue as solved: can you comment and reopen if it is not the case please (with error message up to date)?