You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the documentation lists ~50 GB of storage per SUSE product as requirement. This might be realistic for the base repositories - but it is not sufficient for the Package Hub repository.
What does the documentation say now?
50 GB per SUSE product.
What change is required?
It would be a nice addition to have the hint, that Package Hub requires additional ~20 GB of storage. From my point of view, the most customers/users also sync this repository (like most EL users also sync the EPEL repository).
What content needs to be added?
A small notice could be added.
Subject Matter Expert (SME)
?
Version
It is applicable to SUSE Manager 4.x / Uyuni 2022.xx or newer. It can be backported, if you want.
The text was updated successfully, but these errors were encountered:
Thanks for the report. I hope we now can fix it together with #2446 . Maybe, you now can watch that one, and add comments and concerns if changes are not clear enough. YaST now warns if less than 100 GB is available.
PR is here: #2448 --maybe, we should mention Package Hub explicitly.
Documentation Update Required
Currently, the documentation lists ~50 GB of storage per SUSE product as requirement. This might be realistic for the base repositories - but it is not sufficient for the Package Hub repository.
What does the documentation say now?
50 GB per SUSE product.
What change is required?
It would be a nice addition to have the hint, that Package Hub requires additional ~20 GB of storage. From my point of view, the most customers/users also sync this repository (like most EL users also sync the EPEL repository).
What content needs to be added?
A small notice could be added.
Subject Matter Expert (SME)
?
Version
It is applicable to SUSE Manager 4.x / Uyuni 2022.xx or newer. It can be backported, if you want.
The text was updated successfully, but these errors were encountered: