[Spacewalk-list] spacecmd not update sid of server

[Parsons, Aron]

Hi Issam,
spacecmd keeps a local cache of server->sid mappings as to not have to hit the server constantly for lookups.  If you delete a system outside of spacecmd, it does not know to update the cache.  You must manually clear the caches (clear_caches command) or wait for it to expire (3600 seconds, hardcoded in misc.py).

Enhancements to this behavior could to be look for that specific exception and update the cache automatically or to make the TTLs on the caches configurable.

/aron

-----Original Message-----
Date: Mon, 29 Apr 2013 16:20:35 +0200
From: Issam Harrathi <issamneo at gmail.com>
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] spacecmd not update sid of server
Message-ID:
	<CAL941vuBKZZYHb0utNd4Hy2ZCa-d0uyZ53=L==NDYD5oDtCivw at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,
I have a strange problem on spacewalk 1.7:
i Install my server(apache1.local.org) with spacewalk, then using a script I add the custom.system.info myserver=="search:hostname:apache1"
spacecmd -u login -p pwd -- systemaddcustomvalue $1 $2 $3 $4 $myserver

everything works OK
BUT when i delete the system( system==> click on apache1==>delete system) then i re-install apache1 and rerun myscript the script tell me : ERROR: redstone.xmlrpc.XmlRpcFault: No such system - sid = 1000010035 this is the old sid now the sid is 1000010036.
Why spacewalk still refer to the old value of sid? and how to tell it that the new value is 1000010036

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.redhat.com/archives/spacewalk-list/attachments/20130429/6dacc4e6/attachment.html>