Daniel -- I've not noticed that particular problem, but I've similarly noticed some issues with SSM in spacewalk 2.0.
MY issue is that I will define systems for SSM, go to the package update function, schedule ALL systems (in the SSM subset) to do all available updates. They get scheduled and executed, with spacewalk reporting that "all succeeded". When I navigate back to the SSM, though, I find that there are systems that still have outdated packages! Near as I can tell, it seems to be based upon different OS versions, meaning that, for instance, all the CentOS *6* hosts will be fully updated, but the CentOS *5* servers within the SSM subset don't actually get their updates. Solution is to simply schedule and execute the bulk update again, but I don't recall this hiccup previous to version 2.0 Andy On 3/19/14 5:37 AM, "Daniel Souvignier" <[email protected]> wrote: Hello, I've got a problem with the System Set Manager. Neither package installs nor package removals will work, only updates and script commands. If I install or remove from a single system via spacewalk web interface, it works just fine. I'm using stable spacewalk 2.0. What can be causing this? If I try to remove a package, the message is always "package xy could not be found", but why? Does it matter if I select systems which already have the package removed alongside with systems which need to have this package removed? Thanks!the SS Regards, Daniel -- ---------------------------------------------------------------- Daniel Souvignier Fachinformatiker Systemintegration in Ausbildung Lehrstuhl für integrierte Analogschaltungen RWTH Aachen Sommerfeldstraße 24 (Walther-Schottky-Haus) 52074 Aachen Raum 24C 313 Tel.:0241/80-27771 www.ias.rwth-aachen.de _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
