[Spacewalk-list] FW: package install fail

2019-01-15 Thread Zhou, Rui A. (NSB - CN/Shanghai)


From: Zhou, Rui A. (NSB - CN/Shanghai)
Sent: 2019年1月16日 10:28
To: 'spacewalk-list@redhat.com' 
Cc: Zhu, Ting (NSB - CN/Shanghai) 
Subject: package install fail

Hi: dears
   I had install the spacewalk2.8,  it all works fine, client can register to 
server and spacewalk can send cmd etc…
But when I use the spacewalk to install os, it always appears the following 
tips, of course the five packages wrote in the KS.
I understand it will find the configured tree path(/var/ftp/pub/CentOS7) to 
install needed packages, but it not work.
So I try to config cobbler repo(rndmirrors), It doesn't seem to work either.  
It's been bothering me for a long time.
Am I missing any configuration? Hope to be helped! Thank you!


[root@splunk-server repo_mirror]# ls -la /var/www/cobbler/repo_mirror/rndmirrors
total 368
drwxr-xr-x  4 root   root   54 Jan 15 23:35 .
drwxr-xr-x  3 apache apache 24 Jan 15 19:12 ..
-rw-r--r--  1 root   root   373476 Jan 15 23:35 comps.xml
drwxr-xr-x  2 root   root   29 Jan 15 19:12 .origin
drwxr-xr-x 33 root   root  285 Jan 15 23:35 Packages


[cid:image001.png@01D4AD84.66591730]


CentOS7--1.cfg
Description: CentOS7--1.cfg
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Spacewalk - Patching Log Files

2019-01-15 Thread p.cook...@bham.ac.uk
Thanks for your feedback Matt, that’s helpful.

Phil

From: spacewalk-list-boun...@redhat.com  On 
Behalf Of mattma...@gmail.com
Sent: 11 January 2019 21:18
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Spacewalk - Patching Log Files

Logging on the client isn't enabled by default, but I believe you can get that 
information by enabling it in the /etc/sysconfig/rhn/up2date config file.

writeChangesToLog[comment]=Log to /var/log/up2date which packages has been 
added and removed
writeChangesToLog=1

Otherwise you can query the API to get all the events for a particular system.

On Wed, Jan 9, 2019 at 5:24 AM 
p.cook...@bham.ac.uk 
mailto:p.cook...@bham.ac.uk>> wrote:
Good morning all

I’ve found that /var/log/yum.log, on client systems, isn’t updated when 
patching RHEL 6/7 systems from a Spacewalk server (v2.8). I know details of 
patching activities can be found in the Schedule > Completed Actions or yum 
history, after the event, but is there any log on client or server that can be 
monitored from the command line actually during patching? It’s just to monitor 
the patching activity, really, rather than a need to trace a problem or 
similar. If not, I presume that’s because the details you see in Schedule > 
Actions are actually being directly written to the embedded PostgreSQL database?

Regards

Philip Cookson
Linux Administrator
IT Services
ERI Building
Edgbaston
Birmingham
B15 2TT

Tel: 0121 414 4731
Email: p.cook...@bham.ac.uk

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[Spacewalk-list] Managing Channels/Repositories - Patching Workflow

2019-01-15 Thread p.cook...@bham.ac.uk
Hi all

I've recently built a SW 2.8 environment, added Channels/Repositories for 
RHEL/Oracle Linux 6/7 and successfully patched relevant client systems. I now 
want to know how people are managing their patching workflow - at this point in 
time I just want to ensure the same group of patches are applied to Dev, Test 
and Production after sufficient testing has been performed. If I never re-sync 
these repositories obviously they'll remain static and could be used for the 
whole workflow. However, other service areas may want their environments 
patched at different times with additional patches. I guess I could just create 
similar Channels/Repositories, at a later time, but that would be time 
consuming and need more disk space. I've seen references to cloning using 
WebUI, spacecmd -- softwarechannel_clone, spacewalk-clone-by-date or 
spacewalk-manage-channel-lifecycle and can research these further but just 
wondering what people have found to be the easiest and most reliable solution 
really?

Regards
Phil

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list