Hi
I'm still having issues with Spacewalk 0.8 whereby a fresh client is
unable to run "yum update".
After hearing the issue was supposed to be fixed in Spacewalk 0.8, I
rebuilt my server, created a single channel with 3 python rpms and used
the UI to
"Alter channel Subscriptions"
On my client, I ran "yum clean all", "yum repolist" and then "yum update
python" .... wow it worked. At first I didn't understand how and I put
it down to someone
Having fixed/patched spacewalk 0.8.
Back in the office I rebuilt another Spacewalk and configured everything
(thinking spacewalk now works), after creating and syncing channels I
had the following setup:
[r...@spacewalk mail]# rhn-satellite-exporter --list-channels
Channel List:
B = Base Channel
C = Child Channel
B centos-5.3-x86_64-server
C centos-5.3-x86_64-centosplus
C centos-5.3-x86_64-extras
C centos-5.3-x86_64-updates
B centos-5.4-x86_64-server
C centos-5.4-x86_64-centosplus
C centos-5.4-x86_64-extras
C centos-5.4-x86_64-updates
B fedora-12-x86_64
C fedora-12-x86_64-updates
I then installed a client, registered it to spacewalk.....and "yum
update" fails
At first I couldn't understand what was going on because I had seen the
test one work, determined not to rebuild, I did the following on my
spacewalk server:
1. rhn-satellite stop
2. /etc/init.d/oracle-xe start
3. connect to Oracle, drop user spacewalk cascade
4. Create sspacewalk and other spacewalk steps
5. configure spacewalk
This time, before syncing my channels, I first created the test channel
(3x python rpms) confirmed my client could run "yum update python" and
then ran a channel import from
A previous export (to save sync/download time)
import_centos_5_3()
{
CHANNEL="centos-5.3-x86_64-server"
satellite-sync --mount-point=${IMPORT_DIR}/${CHANNEL} \
-c "centos-5.3-x86_64-server" \
-c "centos-5.3-x86_64-centosplus" \
-c "centos-5.3-x86_64-extras" \
-c "centos-5.3-x86_64-updates"
}
I then pointed my client to "centos-5.3-x86_64-server" and "yum update"
worked...........at last, after 2 months I had a WORKING spacewalk.
Then I tried to clone "centos-5.3-x86_64-server" together with updates,
resulting in:
B lgb-2.0.1
C lgb-2.0.1-updates
I then pointed my client to it....and to my horror it FAILS :(
In summary:
1. When deploying a fresh install of Spacewalk 0.8 on CentOS 5.4, you
need to create a tiny test channel before syncing/importing your other
channels
2. Even though point 1. gets things working, if you clone the channel
and start using the clone..."yum update" then fails
Where do we go from here? It takes many hours to setup these test
"instances" and I'm very surprised nobody else has deployed a fresh
install of Spacewalk and not encounterd these
Problems. I don't install from kickstart trees because the scripts to
create the trees didn't work when I was running Spacewalk on Fedora 12.
Is anybody else able to deploy a fresh install of Spacewalk 0.8 on
CentOS 5.4, sync channels and have their client run "yum update"
successfully?
Any ideas?
Regards
Bruce
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of John Hodrien
Sent: 10 March 2010 12:42
To: [email protected]
Subject: Re: [Spacewalk-list] Spec pc to run spacewalk
On Wed, 10 Mar 2010, Bushby, Bruce (London)(c) wrote:
> Hi John
>
> Thanks for getting back to me, I have posted my findings in two
> previous posts, I will include those posts in this email
Ah thanks, I don't remember reading them before.
So on the server, what does
/var/cache/rhn/repodata/<channel_name/primary.xml.gz look like?
You've only got one package in the repo, so it should be suitably short.
Do the provides look sensible? I'm guessing not.
If they do, is the same true on the copy the client has in
/var/cache/yum?
jh
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
**********************************************************************
Please consider the environment before printing this email or its attachments.
The contents of this email are for the named addressees only. It contains
information which may be confidential and privileged. If you are not the
intended recipient, please notify the sender immediately, destroy this email
and any attachments and do not otherwise disclose or use them. Email
transmission is not a secure method of communication and Man Investments cannot
accept responsibility for the completeness or accuracy of this email or any
attachments. Whilst Man Investments makes every effort to keep its network free
from viruses, it does not accept responsibility for any computer virus which
might be transferred by way of this email or any attachments. This email does
not constitute a request, offer, recommendation or solicitation of any kind to
buy, subscribe, sell or redeem any investment instruments or to perform other
such transactions of any kind. Man Investments reserves the right to monitor,
record and retain all electronic communications through its network !
to ensure the integrity of its systems, for record keeping and regulatory
purposes.
Visit us at: www.maninvestments.com
TG0908
**********************************************************************
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
