On Wed, 3 Feb 2010, James Hogarth wrote:
With 35 machines currently in my spacewalk install and an estimated 60
yet to come and all configuration managed centrally by spacewalk along
with local replicas of various yum repos in channels it would, quite
frankly, be infeasible to do a fresh install
> Hi Bruce,
>
> if your deployment consists of hundereds or thousands servers and use
> config channels then it's impossible to start over and over. And then you
> have to upgrade.
>
> Regards,
>
> --
> Michael Mráka
> Satellite Engineering, Red Hat
>
> _
Bushby, Bruce (London)(c) wrote:
%
% This is probably a stupid questionbut why "upgrade" spacewalk as apposed
to "re-deploying" a fresh install?
%
% I've always avoided upgrades finding they're more head ache then they're
worth. On the client side, my build is so automated it's quicker to "
Marcus Moeller wrote:
% > Of course we do support upgrades from one released version to another so
% > the main upgrade polishing comes regularly just before release :).
%
% I am aware of it. It is my testing env and this is more an informational note.
...
% > % CREATE TABLE rhnChecksumType
% > %
you would
export/import their configs.
-Original Message-
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Marcus Moeller
Sent: 02 February 2010 11:27
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] 0.7 upgrade to nigh
Dear Michael.
> nightly is latest development and experimental stuff and although we do
> our best regarding upgrades we frankly don't support them (to nightly),
> installation should always work.
>
> Of course we do support upgrades from one released version to another so
> the main upgrade polis
Marcus Moeller wrote:
% Hi all,
%
% I have upgrade my 0.7 to nightly and ran into problems during shema upgrade:
Hi Marcus,
nightly is latest development and experimental stuff and although we do
our best regarding upgrades we frankly don't support them (to nightly),
installation should always w
Hi all,
I have upgrade my 0.7 to nightly and ran into problems during shema upgrade:
CREATE TABLE rhnChecksumType
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
which leads to the following error during spacewalk-repo-sync:
SQLStatementPrepareError: ('ORA-
