Description of problem: Unless you manually restart osad on the client system, osad is unable to detect the system in question was re-registered. Version-Release number of selected component (if applicable): osad-5.9.55-1 How reproducible: Always Steps to Reproduce: 1. Register a client system to Spacewalk, osad running and working 2. Re-register the machine in question 3. Schedule an event (ping for example) for the re-registered system Actual results: osad won't detect the system was re-registered, actions scheduled for the system won't be picked up. Expected results: osad is able to detect the system was re-registered. Additional info: https://bugzilla.redhat.com/show_bug.cgi?id=185476
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
spacewalk.git master: df8fd7dddba65f55305454d4b32a53ee2fe59813
Spacewalk 1.6 has been released.