Rudder

This bug lacks of informations about the context and it seems that we can't reproduce it. Unless we met again this bug, this is more appropriate to reject it.

I'd like to reopen this bug since it's still present: ZMD is broken but any request from rug use ZMD. This behavior leads to an accumulation of CFEngine processes and no report in the WebUI.

In fact, what I have heard from SuSE is that there is no way to detect if ZMD is broken. If ZMD is broken, we need to:
- kill all rug and ZMD process
- launch /etc/init.d/novell-zmd stop
- launch /etc/init.d/novell-zmd start
- wait for ZMD to synchronize rug DB with libzypp

What was suggested to me was to use zypper instead of rug, because it does not use ZMD but directly libzypp. This bug concerns only SLES 10 which is no more supported.

Nicolas PERRON wrote:

I wonder now if we should add to the management of Rug some promises to kill all mono processes and novell-zmd if too many mono processes are running.

That is rather easy to do, and seems like a quick win here.

The other solution seems to use zypper but it means to rework all package management. On SLES 10, it is possible to use the same configurations files for repositories than on SLES 11 but:
- it will require to use command line to add a repository: [...]
- the only way to know if a repository is already there is to add it from a file and expect to have a return code equal to 4

That sounds fine, we can get CFEngine to execute a command and set the result classes based on return codes. However, that will make the promises run slower, of course (each and every command run does). I'm not against it, but if it can be avoided by the above workaround, let's avoid it.

What do you think, Nicolas and Nicolas?

Jonathan CLARKE wrote:

Nicolas PERRON wrote:

I wonder now if we should add to the management of Rug some promises to kill all mono processes and novell-zmd if too many mono processes are running.

That is rather easy to do, and seems like a quick win here.

I prefered to do so, but I fear that it might definitively corrupt packages Databases if it is made too often. A Novell Guy advise me to use zypper instead.

The other solution seems to use zypper but it means to rework all package management. On SLES 10, it is possible to use the same configurations files for repositories than on SLES 11 but:
- it will require to use command line to add a repository: [...]
- the only way to know if a repository is already there is to add it from a file and expect to have a return code equal to 4

That sounds fine, we can get CFEngine to execute a command and set the result classes based on return codes. However, that will make the promises run slower, of course (each and every command run does). I'm not against it, but if it can be avoided by the above workaround, let's avoid it.

What do you think, Nicolas and Nicolas?

After a discussion with a Novell guy, it seems that zypper on SLES 10 SP3 is very limited and buggy and it is not possible to automatically accept choice. He recommended me to upgrade zypper like on this repository: http://download.opensuse.org/repositories/zypp:/zc10/SLE_10_SP3/ .
The problem is that upgrading to another version of zypper will not provide dependencies for ZMD then ZMD is removed and Rug is not more usable.

Retargeting to 2.6 since 2.4 is not maintained anymore

This is not supported anymore \o/ \o/ \o/