SuSe SLES: error when refreshing puppet yum repository

Torsten Kleiber

unread,

Jun 12, 2014, 7:12:47 AM6/12/14

to puppet...@googlegroups.com

Hi!

I try to activate the yum repository for SUSE Linux Enterprise Server 11:

myserver:~ # zypper --non-interactive addrepo -t YUM http://yum.puppetlabs.com puppet
Adding repository 'puppet' [done]
Repository 'puppet' successfully added
Enabled: Yes
Autorefresh: No
URI: http://yum.puppetlabs.com/

myserver:~ # zypper --non-interactive refresh
Repository 'SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152' is up to date.
Retrieving repository 'puppet' metadata [\]
File '/repodata/repomd.xml' not found on medium 'http://yum.puppetlabs.com/'

Abort, retry, ignore? [a/r/i/?] (a): a
Retrieving repository 'puppet' metadata [error]
Repository 'puppet' is invalid.
Can't provide /repodata/repomd.xml : Media Exception
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'puppet' because of the above error.
Repository 'sle-11-x86_64' is up to date.
Some of the repositories have not been refreshed because of an error.

myserver:~ # cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
myserver:~ #

Any hints why this happens?

Kind regards

Torsten

Throwe, Jesse

unread,

Jun 12, 2014, 8:38:43 AM6/12/14

to puppet...@googlegroups.com

Torsten,

The puppetlabs yum repository is for EL releases only. Because SLES
is 'special' you need to use a repo with RPMS (and metadata) tailored
for zypper and its ilk.

https://build.opensuse.org/project/show/systemsmanagement:puppet

- Jesse

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/df44c6e6-8b9c-4415-8833-9f8d1254631a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Torsten Kleiber

unread,

Jun 12, 2014, 9:15:50 AM6/12/14

to puppet...@googlegroups.com

Thank you!

But now I get another error:

vdu10272:~ # zypper --non-interactive refresh
Retrieving repository 'puppet' metadata [/]
Download (curl) error for 'https://build.opensuse.org/project/show/systemsmanagement:puppet/repodata/repomd.xml':
Error code: Unrecognized error
Error message: SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Retrieving repository 'puppet' metadata [error]
Repository 'puppet' is invalid.
Can't provide /repodata/repomd.xml : Media Exception
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'puppet' because of the above error.

Some of the repositories have not been refreshed because of an error.

Darin Perusich

unread,

Jun 12, 2014, 12:09:14 PM6/12/14

to puppet...@googlegroups.com

build.opensuse.org is the OBS project location where the packages are
managed/built. Successfully built packages are published at
download.opensuse.org, so for SLES use the below repo URL.

http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/

--
Later,
Darin

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/puppet-users/d882a8e3-f688-4f61-b733-551b7aba4a90%40googlegroups.com.

Torsten Kleiber

unread,

Jun 13, 2014, 6:03:37 AM6/13/14

to puppet...@googlegroups.com

Thanks for this!

zypper refresh with this repo is now successful.

But now I get another error:

myserver:~ # zypper --non-interactive install --repo puppet puppet
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: nothing provides rubygems needed by rubygem-ruby-shadow-2.3.4-21.1.x86_64
Solution 1: do not ask to install a solvable providing puppet
Solution 2: break rubygem-ruby-shadow by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c] (c): c

Darin Perusich

unread,

Jun 13, 2014, 8:47:19 AM6/13/14

to puppet...@googlegroups.com

rubygem-ruby-shadow is available in the repo so I don't know what
could be causing that.

I just added that repo to a SLES box, installed puppet and it pulled
down the dependencies without issue, the the output below.

What the output you get from "zypper info rubygem-ruby-shadow" and
"zypper lr -d "?

slestest:~ # zypper ar
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3

puppet
Adding repository 'puppet' [done]
Repository 'puppet' successfully added
Enabled: Yes
Autorefresh: No

GPG check: Yes
URI: http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3

slestest:~ # zypper in puppet

Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW packages are going to be installed:
facter puppet ruby rubygem-hiera rubygem-json_pure
rubygem-ruby-shadow rubygems

7 new packages to install.
Overall download size: 4.9 MiB. After the operation, additional 17.8
MiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package ruby-1.8.7.p357-0.9.15.1.x86_64 (1/7), 1.8 MiB (6.4
MiB unpacked)
Retrieving: ruby-1.8.7.p357-0.9.15.1.x86_64.rpm [done]
Retrieving package facter-2.0.1-2.1.x86_64 (2/7), 80.0 KiB (222.0 KiB unpacked)
Retrieving: facter-2.0.1-2.1.x86_64.rpm [done]
Retrieving package rubygems-1.8.15-0.14.1.x86_64 (3/7), 181.0 KiB
(558.0 KiB unpacked)
Retrieving: rubygems-1.8.15-0.14.1.x86_64.rpm [done]
Retrieving package rubygem-ruby-shadow-2.3.4-21.1.x86_64 (4/7), 23.0
KiB (89.0 KiB unpacked)
Retrieving: rubygem-ruby-shadow-2.3.4-21.1.x86_64.rpm [done]
Retrieving package rubygem-json_pure-1.8.1-28.12.x86_64 (5/7), 276.0
KiB (759.0 KiB unpacked)
Retrieving: rubygem-json_pure-1.8.1-28.12.x86_64.rpm [done]
Retrieving package rubygem-hiera-1.2.1-11.11.x86_64 (6/7), 46.0 KiB
(115.0 KiB unpacked)
Retrieving: rubygem-hiera-1.2.1-11.11.x86_64.rpm [done]
Retrieving package puppet-3.6.2-2.1.x86_64 (7/7), 2.6 MiB (9.6 MiB unpacked)
Retrieving: puppet-3.6.2-2.1.x86_64.rpm [done (1.0 MiB/s)]
Installing: ruby-1.8.7.p357-0.9.15.1 [done]
Installing: facter-2.0.1-2.1 [done]
Installing: rubygems-1.8.15-0.14.1 [done]
Installing: rubygem-ruby-shadow-2.3.4-21.1 [done]
Installing: rubygem-json_pure-1.8.1-28.12 [done]
Installing: rubygem-hiera-1.2.1-11.11 [done]
Installing: puppet-3.6.2-2.1 [done]
Additional rpm output:
%{1} puppet.service
warning: /etc/puppet/puppet.conf saved as /etc/puppet/puppet.conf.rpmorig
%{1} puppet.service
--
Later,
Darin

> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/puppet-users/18f47009-68f3-4eb3-9ff4-375da38d7d94%40googlegroups.com.

Torsten Kleiber

unread,

Jun 13, 2014, 2:11:50 PM6/13/14

to puppet...@googlegroups.com

Could it be related to the fact, that I'm on patchset 1 or that old puppet 2.6 seems to exist in one of the other repositories?

Here is the outpput:

myserver:~ # zypper info rubygem-ruby-shadow

Loading repository data...
Reading installed packages...

Information for package rubygem-ruby-shadow:

Kind regards

Torsten

Torsten Kleiber

unread,

Jun 13, 2014, 2:16:29 PM6/13/14

to puppet...@googlegroups.com

BTW: I try to install via following command, because of the double puppet in another repository:

Torsten Kleiber

unread,

Jun 16, 2014, 6:33:25 AM6/16/14

to puppet...@googlegroups.com

The problem is rubygem itself, which was missing. This has to be installed from the SDK which was not available as repository on th system.

Am Freitag, 13. Juni 2014 14:47:19 UTC+2 schrieb Darin Perusich:

Reply all

Reply to author

Forward