Project

General

Profile

Actions
Copy link

Bug #6783

closed

Bug with 1.5 repo?

Added by jean berghof almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
1.5.1
Red Hat JIRA:

Description

Hi all,
I encountered some problems with the repo today, so i can't download some packages when i try to install foreman-installer.


"Downloading Packages:
(1/2): rubygem-little-plugger-1.1.3-17.el6.noarch.rpm                                                                                 |  12 kB     00:00
http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-little-plugger-1.1.3-17.el6.noarch.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=foreman clean metadata
Trying other mirror.
(2/2): rubygem-powerbar-1.0.11-7.el6.noarch.rpm                                                                                       |  12 kB     00:00
http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-powerbar-1.0.11-7.el6.noarch.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=foreman clean metadata
Trying other mirror.
"

I tried to install it on a new server and i still encountered the problem.
I tried usual things with yum problems (yum --enablerepo=foreman clean metadata, yum clean all) but problem still present.

I encountered this problem on a fresh red hat 6.5 install. For foreman's installation, i just follow the quickstart guide instructions. You will find more information about my configuration on the join file, i don't know if all information required are there but i will be glad to give you what you need.

Regards, Jean.

Files

Log Report Bug Foreman.txt Log Report Bug Foreman.txt 14.5 KB System Info jean berghof, 07/25/2014 11:37 AM
Actions
Copy link
 #1

Updated by Dominic Cleal almost 10 years ago

  • Status changed from New to Feedback

Do you have a proxy server between you and our repository? Earlier in July we had a security incident and re-signed all of our RPMs (https://groups.google.com/forum/#!topic/foreman-announce/BiIT784Mb7Q), so I'm wondering if something has cached the old version of the RPM.

Actions
Copy link
 #2

Updated by jean berghof almost 10 years ago

Hi Dominic >
I solved this by importing manually the GPG Key this morning, exactly the action explain in your related-post.
So yes probably somehting cached by our proxy server.

Sorry for the inconvenience, Ticket solved.

PS :
Step for me to fix it :
rpm --import http://yum.theforeman.org/RPM-GPG-KEY-foreman
yum clean all
And download the 2 packages creating problem directly from repo :
yum install http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-powerbar-1.0.11-7.el6.noarch.rpm
yum install http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-little-plugger-1.1.3-17.el6.noarch.rpm
And reste was OK.

Actions
Copy link
 #3

Updated by jean berghof almost 10 years ago

Hi Dominic >
I solved this by importing manually the GPG Key this morning, exactly the action explain in your related-post.
So yes probably somehting cached by our proxy server.

Sorry for the inconvenience, Ticket solved.

PS :
Step for me to fix it :
rpm --import http://yum.theforeman.org/RPM-GPG-KEY-foreman
yum clean all
And download the 2 packages creating problem directly from repo :
yum install http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-powerbar-1.0.11-7.el6.noarch.rpm
yum install http://yum.theforeman.org/releases/1.5/el6/x86_64/rubygem-little-plugger-1.1.3-17.el6.noarch.rpm
And now i'm fighting with the foreman-installer but i think it will be ok :).

Actions
Copy link
 #4

Updated by Dominic Cleal almost 10 years ago

  • Status changed from Feedback to Resolved

Glad you got it sorted, thanks for letting us know.

Actions
Copy link

Also available in: Atom PDF