Hi Steve. Are you talking about migrating a client? As far as I know we don't have an official procedure. But since Uyuni manages the repositories for the clients, and assuming your current Leap 42.3 are NOT traditional clients you could: 1. Adjust the channels assigned to the activation key to change them from Leap 42.3 to 15.0 2. Create an action change to: - Apply the highstate (so the Leap 15.0 repositories become available for the client(s) - Update all packages - Reboot. O course, this assumes the clients will not have any kind of dependency conflicts when switching from Leap 42.3 to Leap 15.0. On lunes, 11 de marzo de 2019 14:15:36 (CET) Steve Moring wrote:

Hi,

Having lab time is infrequent. I'm planning to spend some time playing this coming weekend. I'd like to test updating from os423 to os150 using uyuni. What are the proper highlevel steps to perform this upgrade?

Are there proper steps to clear a client bootstrapping? I'd like to test removing the channels defined for os423, updating to os150 using installation media, re-bootstrapping to os150 channels to compare the process.

Thanks,

-Steve

-- Julio González Gil <jgonzalez@suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)