Re: [Spacewalk-list] spacewalk upgrade for client

[Robert Paschedag]

Just re-register to new server with

rhnreg_ks --force --activationkey= 
--serverUrl=https://

Regards
Robert
Am 02.02.2016 23:09 schrieb Benjamin Fernandis :
>
> Hi,
>
> In previous we are using spacewalk version 2.3. Now we created new server 
> which has latest version 2.4 . What would be best way to upgrade clients to 
> connect with new spacewalk server which has 2.4 version.
>
> I am thinking to remove client packages from client machine and setup 2.4 
> repo and install accordingly. Please suggest me if is there any better way 
> for this.
>
> what is best way to use spacewalk for update systems. we thinking to pull 
> updates from spacewalk by running yum update at client end.
>
> do we require to move existing base repo which comes with centos after 
> installation to use spacewalk repo in yum update ?
>
> Thanks
> Ben

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

[Spacewalk-list] spacewalk upgrade for client

[Benjamin Fernandis]

Hi,

In previous we are using spacewalk version 2.3. Now we created new server
which has latest version 2.4 . What would be best way to upgrade clients to
connect with new spacewalk server which has 2.4 version.

I am thinking to remove client packages from client machine and setup 2.4
repo and install accordingly. Please suggest me if is there any better way
for this.

what is best way to use spacewalk for update systems. we thinking to pull
updates from spacewalk by running yum update at client end.

do we require to move existing base repo which comes with centos after
installation to use spacewalk repo in yum update ?

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

Re: [Spacewalk-list] Package collision questions

[Kalchik, Jeffery]

Unless I’ve done something wrong (not the first time, & won’t be the last, I’m 
sure,) the fix listed in the first bug doesn’t appear to work in my environment.

Jeff

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Kalchik, Jeffery
Sent: Monday, January 25, 2016 7:13 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Package collision questions

I haven’t.  Might be able to get to test it this week.

Jeff

From: 
spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of jeff macfarland
Sent: Friday, January 22, 2016 4:36 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Package collision questions

It is "interesting", yes. I would like to fold in to something that depends 
less on having a specfic minor version. Can be time consuming to keep things in 
line with new releases.

But did you use the suggested fix from the first bug? Sounds more appropriate 
that my (apparently) corner case of having empty base channels.

On Fri, Jan 22, 2016 at 1:35 PM, Kalchik, Jeffery 
mailto:jdkalc...@landolakes.com>> wrote:
I can show a couple of dozen collisions in every distribution tree.  
Fortunately, the majority of those don’t affect my kickstarts.  When it does, I 
figure out which package I want to use, & remove the conflicting package[s].

Historically, I’ve depended on digging through the kickstart logs.  I still 
will probably have to do that, but the Perl script will help tremendously in 
figuring out what other channels & packages are also affected.  I’ll also have 
to update the channel cloning configuration files to blacklist the problem 
packages.

Looking at your Bugzilla submission, you run a little different than we do, you 
have to maintain multiple minor releases, we only maintain the major versions.  
I.e. only CentOS 7.2, not CentOS 7.2 and 7.0.  That’s an interesting method of 
controlling minor versions, though.

Thanks for the input.

Jeff

From: 
spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com]
 On Behalf Of jeff macfarland
Sent: Friday, January 22, 2016 1:04 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Package collision questions

I've run into this more than a couple times. Two fixes I am aware of

https://bugzilla.redhat.com/show_bug.cgi?id=1076490
https://bugzilla.redhat.com/show_bug.cgi?id=1287829
I submitted the latter but haven't tried out a nightly build so I am just 
waiting for the next release to see if it fixed my particular issue. In the 
meantime, I am resigned to removing an offending package manually and filtering 
out from the sync (typically on an updates channel). This works for me because 
I don't care which package is used. For the conflicting packages I've seen (all 
from centos.org), all are the same minus a different signing 
date.


On Fri, Jan 22, 2016 at 11:25 AM, Kalchik, Jeffery 
mailto:jdkalc...@landolakes.com>> wrote:
Good morning, all.

I have a long standing situation that isn’t showing any signs of improvement.  
In short, I have a number of situations where a particular package name exists 
with multiple checksums & backend .rpm files.

Some background:

I have 5 major release trees (base channel and child channels) in Spacewalk 
(2.4,)  CentOS6, CentOS7, Oracle Linux 5, Oracle Linux 6, and Oracle Linux 7.  
The release channels have all been created through spacewalk-common-channels.  
I also have some extra child channels in each tree for things like a local 
utilities channel and application channels.  Each release tree is cloned into 
development, QA, & production trees.  All client systems are registered to a 
dev, QA or production tree, never to a release tree/channel.

A package may exist in multiple channels in a tree, downloaded from separate 
repositories.  This can cause problems during a kickstart, when a package with 
a different checksum gets sent down to anaconda.  To make things worse, the 
kickstart problem does not always occur.   I also suspect that it could be an 
issue in spacecmd, as commands like ‘package_remove PKG’ don’t allow me to 
specify which package to remove.  Yes, ‘softwarechannel_removepackage PKG’ 
helps, I do limit each channel to a single repository, there shouldn’t be any 
collisions within a given channel.

Here’s an example.  I’ve written a Perl script to spin through the base 
channels, generate the channel list for that tree, & find all packages with 
multiple IDs and checksum.

librepo-1.7.16-1.el7.x86_64
128863  centos7-x86_64,dev-centos7-x86_64,prod-centos7-x86_64,qa-centos7-x86_64
136116  
dev-epel7-centos7-x86_64,dev-epel7-oraclelinux7-x86_64,epel7-centos7-x86_64,epel7-oraclelinux7-x86_64,prod-epel7-centos7-x86_64,prod-epel7-oraclelinux7-x86_64,qa-epel7

[Spacewalk-list] Create KS Distribution Error

[Philipp Wehling]

Hello, 

I want to create an KS-Distribution for OracleLinux, but I get this error: 

Exception: 
javax.servlet.ServletException: java.lang.RuntimeException: 
redstone.xmlrpc.XmlRpcFault: :[Errno 13] Permission 
denied: '/var/lib/tftpboot/aarch64/grub.cfg' 



Here are the permissions of this file: 



# ll /var/lib/tftpboot/aarch64/grub.cfg 
-rw-r--r--. 1 root root 17 Jan 15 11:07 /var/lib/tftpboot/aarch64/grub.cfg 

# ls -Z /var/lib/tftpboot/aarch64/grub.cfg 
-rw-r--r--. root root system_u:object_r:public_content_t:s0 
/var/lib/tftpboot/aarch64/grub.cfg 










I think it is related to SELinux, but I dont want to turn it off. Can anyone 
help me? 







kind regards, 

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