Hi List,
We use Content Lifecycle Management and have our systems in staged channels. To be informed about new patches for those systems we have to first sync the channels. How can we get this notification *before *syncing, so that we know when we have to sync? Or is it best to have one of each systems unstaged so we get to know about those updates? (i don't think so)
Thanks, BR Heiner
Hi List,
we still have not found a satisfying way to be informed about patches that need to be synced to our channels.
How do you achieve that? Do you sync your channels each time a CVE is released to find out if any system is affected? Or do you use another software?
BR Heiner
Hi
Seems you are looking for some kind of "diff" functionality between CLM Environments. Such a feature does not yet exist. You can check for patches not available in 1 Channel when you go to
Software => Manage => Channel => Patches => Add => "Add SUSE Patches"
When you now select the Vendor base channel of the selected channel and click on "View Associated Patches" you will get a list of the differences between the vendor channel and the CLM environment channel.
Similar functionality is available for packages.
This has of cause some downsides:
- you need to do this channel by channel to see the whole picture - you get also patches which are "filtered" for a reason.
With a combined view in the CLM project this would be much easier to handle. Please check if we have already an enhancement request in uyuni github project https://github.com/uyuni-project/uyuni/issues . If not, feel free to add one and describe what you would like to have.
Regards
Michael
Am Donnerstag, 12. August 2021, 08:36:39 CEST schrieb Heiner W.:
Hi List,
we still have not found a satisfying way to be informed about patches that need to be synced to our channels.
How do you achieve that? Do you sync your channels each time a CVE is released to find out if any system is affected? Or do you use another software?
BR Heiner
Hi Michael,
thanks for your feedback! I created https://github.com/uyuni-project/uyuni/issues/4117.
BR Heiner