Does spacewalk will be able to roll back to the old kernel?
For example I ugraded the CentOS from 6.8(kernel 3.0.0 for example) to 6.9
(kernel 3.1.0) Can I roll back to 6.8(kernel 3.0.0)?
Thanks
Francis Yakin | IT System Admin | direct: 510-749-2027
500 Wind River Way, Alameda, CA 94501
[ci
Sorry – one more issue I’m running into. Looks like anything that communicates
via XMLPRC can’t authenticate.
# spacewalk-channel --add -c microsoft_rhel7 -u mdiorio -p
Error validating data at server:
Error Message:
Invalid username/password combination
Error Class Code: 2
Error Class Info
I found that I was missing the pam_auth_service in rhn.conf, and that changed
the error:
rhn-plugin: Error communicating with server. The message was:
redstone.xmlrpc.XmlRpcFault: Either the password or username is incorrect.
Mar 14 17:09:56 la-1pspacewalk server: 2018-03-14 17:09:56,669
[ajp
Hi,
Thanks for your reply. It has been really helpful.
Below the process I've followed if it could help anybody else:
- apt-get update
- apt-get install apt-transport-spacewalk rhnsd
- add following lines in my sources.list
deb http://ftp.debian.org/debian jessie-backports main
de
Hi guys
i'm running spacewalk 2.7 with debian 8, debian 9 and ubuntu 16.04 channels.
one problem I am facing is that if apt uses
only /etc/apt/sources.list.d/spacewalk.list as lists when I run apt update
it shows that 400 packages are available for upgrade.
If I add the official sources in /etc/a
Hi Sebastien,
I've had the same issue and found out that the problem is with
python-openssl version
apt install python-openssl=16.0.0-1~bpo8+1 , fixed the issue for me.
Andrei
On Tue, Mar 13, 2018 at 5:54 PM, Sébastien Genesta <
genesta.sebast...@gmail.com> wrote:
> Hi,
>
> I'm encountering iss
Yes.
From: spacewalk-list-boun...@redhat.com on
behalf of Alexandru Raceanu
Sent: Tuesday, March 13, 2018 3:33 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
Is the certificate a wildcard ?
/Alex
Well... That part doesn't work at the moment as far as I can see and never
managed to get it working on SW 2.5/2.6/2.7.
I've already opened a bug report over 1 year ago (
https://bugzilla.redhat.com/show_bug.cgi?id=1382974 )
Feel free to add a +1 to that one.
If anyone else has any input on
As far as I know, the python ssl implementation is quite poor when it comes to
wildcard ssl certificates. Had similar issues.
I would strongly recommend to update the certificate as it's already expired
and try to avoid wildcards for now.
/Alex
From: "Daryl Rose"
To: spacewalk-list@redhat
You should still have the old kernel installed on the machine(s) and you will
be able to roll back the kernel by removing the kernel*- packages
using yum.
I think by default centos keeps the last 3 kernel versions.
In regards to spacewalk you can exclude all kernels and include only one
versi
Soham Chakraborty:
> Hi all,
>
> I am trying to figure out whether anyone has seen this problem. After I
> posted this thread, I had some discussion with Jan Hutar and although I
> tried all the steps he suggested (which are below), I am still stuck with
> this problem.
...
> The spacewalk-schema
Hi,
I've created a channel for CentOS 7 x86-x64.
This channel contains child channels:
-Base: http://mirror.centos.org/centos/7/os/x86_64/
-Extras: http://mirror.centos.org/centos/7/extras/x86_64/
-Updates: http://mirror.centos.org/centos/7/updates/x86_64/
-Zabbix: https://repo.zabbix.com/zabbix
Hey everyone,
I'm curious as to how many different distributions / versions of distributions
you guys are using in your spacewalk setup? How does this affect your
spacewalks performance overall? How many channels do you have and how often do
you sync channels?
Currently we're running 7 differe
Alex,
The wildcard cert is all I have to work with as we have multiple products that
use it. I don't remember my original reason for using it, but it seemed like
the thing to do at the time. Now I'm wishing that I just left it alone.
Thanks
Daryl
From: s
Alex,
You mean I should keep the old kernel on the clients it self.
In regards to spacewalk, yesterday we tried to create another repository with
old kernel and try to sync it with our servers., we tried to roll back, but it
failed.
Francis
From: spacewalk-list-boun...@redhat.com
[mailto:spa
Am 14. März 2018 16:25:30 MEZ schrieb Andrei Popenta :
>Hi guys
>
>i'm running spacewalk 2.7 with debian 8, debian 9 and ubuntu 16.04
>channels.
>
>one problem I am facing is that if apt uses
>only /etc/apt/sources.list.d/spacewalk.list as lists when I run apt
>update
>it shows that 400 packages ar
It seems like it would be trivial to add quick logic that if the user creation
is coming from PAM, to automatically “check the box” for Use PAM in the
database. Manually having to check the box every time a new user logs in in a
pain, and it resolves the issue of being able to use client side t
17 matches
Mail list logo
