Rudder

This VM is based on AMI Version: Amazon Linux AMI 2017.03.1.20170812

Can you try the RHEL 6 Rudder package?

Hi Alexis,

I get the same error :(

[root@HOST ~]# cat /etc/yum.repos.d/rudder.repo
[Rudder_4.3]
name=Rudder 4.3 EL repository
baseurl=http://www.rudder-project.org/rpm-4.3/RHEL_6/
gpgcheck=1
gpgkey=https://www.rudder-project.org/rpm-repos/rudder_rpm_key.pub

[root@HOST ~]# yum install rudder-agent
Loaded plugins: priorities, update-motd, upgrade-helper
Resolving Dependencies
--> Running transaction check
---> Package rudder-agent.x86_64 1398866025:4.3.4.release-1.EL.7 will be installed
--> Processing Dependency: dmidecode for package: 1398866025:rudder-agent-4.3.4.release-1.EL.7.x86_64
--> Processing Dependency: libpcre.so.1()(64bit) for package: 1398866025:rudder-agent-4.3.4.release-1.EL.7.x86_64
--> Running transaction check
---> Package dmidecode.x86_64 1:2.12-5.8.amzn1 will be installed
---> Package rudder-agent.x86_64 1398866025:4.3.4.release-1.EL.7 will be installed
--> Processing Dependency: libpcre.so.1()(64bit) for package: 1398866025:rudder-agent-4.3.4.release-1.EL.7.x86_64
--> Finished Dependency Resolution
Error: Package: 1398866025:rudder-agent-4.3.4.release-1.EL.7.x86_64 (Rudder_4.3)
           Requires: libpcre.so.1()(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

It seems yum is still trying to install RHEL7 version, did your remove the RHEL7 repo and refresh package lists?

Alexis MOUSSET wrote:

It seems yum is still trying to install RHEL7 version, did your remove the RHEL7 repo and refresh package lists?

I thought i did i am using "yum check-update" which I thought is the RHEL version of "apt-get update".

But i get the same error prehaps im using wrong command?

Matthew Frost wrote:

Alexis MOUSSET wrote:

It seems yum is still trying to install RHEL7 version, did your remove the RHEL7 repo and refresh package lists?

I thought i did i am using "yum check-update" which I thought is the RHEL version of "apt-get update".

But i get the same error prehaps im using wrong command?

and if i use "yum makecache"
One of the configured repositories failed (Rudder 4.3 EL repository),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

yum-config-manager --disable Rudder_4.3

4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

yum-config-manager --save --setopt=Rudder_4.3.skip_if_unavailable=true

failure: repodata/1af8a55855a4a249085fa015675d9e8f9a90b9b9b8be436cd4e39c99b1582b53-filelists.xml.gz from Rudder_4.3: [Errno 256] No more mirrors to try.
http://www.rudder-project.org/rpm-4.3/RHEL_6/repodata/1af8a55855a4a249085fa015675d9e8f9a90b9b9b8be436cd4e39c99b1582b53-filelists.xml.gz: [Errno 14] HTTP Error 404 - Not Found

Does that mean that agent version it not avaiable for RHEL_6 ?

The 1af8a55855a4a249085fa015675d9e8f9a90b9b9b8be436cd4e39c99b1582b53-filelists.xml.gz file is part of the RHEL7 repo (and not RHEL6), this is strange.

Maybe my yum cache is not cleared will try to clear it again.

Matthew Frost wrote:

Maybe my yum cache is not cleared will try to clear it again.

Fixed With

yum clean all

I can confirm the RHEL 6 repo works!!

Thanks! sorry for the bug report!

Thanks for the report. No need to be sorry, this is actually a documentation bug!