[Spacewalk-list] Problem registring Spacewalk client

[Bidault, Philippe]

Hello,

I have a problem after the kickstart of a CentOS 7 from a spacewalk server 2.2 (2.2.33-1.el6).

First of all, I do not understand the repos added by default on my fresh kickstarted client server :

[root at kickstarttest yum.repos.d]# ls -lrt
total 16
-rw-r--r--. 1 root root  156 Jul  4 13:00 CentOS-Vault.repo
-rw-r--r--. 1 root root 1331 Jul  4 13:00 CentOS-Sources.repo
-rw-r--r--. 1 root root  640 Jul  4 13:00 CentOS-Debuginfo.repo
-rw-r--r--. 1 root root 1612 Jul  4 13:00 CentOS-Base.repo

Knowing that I would only use the repos of my kickstart server. How can I change this behaviour ?
(I could remove the files from a post-script, but ....)

But the main problem I have is that I can't register on my server spacewalk. I can see my server on the http console, but
>From the client server, it shows me 0 package on the both channels added to this server :

[root at kickstarttest ~]# yum repolist
Loaded plugins: fastestmirror, langpacks, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
Loading mirror speeds from cached hostfile
repo id                                                     repo name                                                                                   status
centos7-base-x86_64                                         CentOS 7 Base - x86_64                                                                      0
epel7-x86_64                                                EPEL 7 - x86_64                                                                                 0
repolist: 0

And 'yum update' result :

[root at kickstarttest ~]# yum update
Loaded plugins: fastestmirror, langpacks, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Unknown),
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 <repoid>

     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=<repoid>.skip_if_unavailable=true

failed to retrieve repodata/repomd.xml from centos7-base-x86_64
error was [Errno 14] curl#51 - "Unable to communicate securely with peer: requested domain name does not match the server's certificate."

Anybody has an idea about the problem I have ?

Regards,
Philippe.

Philippe Bidault
Tel : +34 617 301 667
Tel bis : +34 93 550 1402
COLT ISU Managed Services
0811 653 653 / www.colt.net<http://www.colt.net/>
Colt Technology Services, 23-27 rue Pierre Valette, 92240 Malakoff, France


[Colt Disclaimer]
This email is from an entity of the Colt group of companies. Colt Group S.A.,
K2 Building, Forte 1, 2a rue Albert Borschette, L-1246 Luxembourg, R.C.S.
B115679.  Corporate and contact information for our entities can be found at
http://colt.net/uk/en/Colt-Group-of-Companies/index.htm. Internet
communications are not secure and Colt does not accept responsibility for the
accurate transmission of this message. Content of this email or its
attachments is not legally or contractually binding unless expressly
previously agreed in writing by Colt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141218/5837f6bd/attachment.htm>