New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minor documentation amendment #2645
Comments
@keichwa |
Thanks for the report! |
* Add info about refreshing software repositories uyuni-project/uyuni#2645 SUSE/spacewalk#12612 * default settings do not require 'zypper ref'. * Update modules/upgrade/pages/server-minor-upgrade-uyuni.adoc Co-authored-by: Lana Brindley <lbrindley@suse.de> * also add note about autorefresh and zypper ref
@keichwa it seems this was added to the docs, so closing the issue. |
yes, thanks for closing! |
@keichwa this is now reported at the list as missing: https://lists.opensuse.org/archives/list/users@lists.uyuni-project.org/message/6PACXIDHGBZZGUM32LTR6QUBG4YQPU6P/ Can you have a look? |
I guess it was removed because we have this note after the procedure:
I think it would be save if I'd add |
I think the problem that I (and, I guess, Heiner) encountered is that
autorefresh is disabled on OpenSuse by default - or at least, was when I
built our uyuni box some time ago.
Given that 'zypper ref' does no harm when autorefresh *is* enabled, and
allows the upgrade to not fail when it's *not *enabled, my suggestion is to
keep it in as a full step.
If there's resistance to this, then perhaps couch that step with "(This
step may be skipped if the system is automatically refreshing Zypper's
repositories at a frequent interval)" or similar?
…On Tue, 5 Oct 2021 at 09:44, Karl Eichwalder ***@***.***> wrote:
I guess it was removed because we have this note after the procedure:
[NOTE]
====
By default, zypper refreshes the repository every ten minutes (see ``repo.refresh.delay`` in [path]``/etc/zypp/zypp.conf``).
If ``autorefresh`` is disabled, run [command]``zypper ref`` to refresh all repositories.
====
I think it would be save if I'd add zypper ref as an OPTIONAL step, and
move the note to a place before the procedure. @juliogonzalez
<https://github.com/juliogonzalez> would this work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2645 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA65KM6NDXMF5M6JQLPE3YDUFK3IXANCNFSM4RX64ETQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Julio González Gil ***@***.***> writes:
@digdilem @keichwa I agree with just instructing the user to call
`zypper ref` as a "full step", meaning we will not really need a note.
@keichwa is there any particular reason you want to have it as
optional and keep the note?
The glorious details are here:
uyuni-project/uyuni-docs#584
Together with digdilem's background info I think that we should treat it
differently for Uyuni (add 'zypper ref' step) and SUMA (note is enough
because autorefresh is be default enabled).
…--
Karl Eichwalder
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer
HRB 36809, AG Nürnberg Maxfeldstr. 5, D-90409 Nürnberg
|
I see mlandres was pretty clear there:
But even if we specify |
uyuni-project/uyuni#2645 leaving out this step causes more trouble than good.
Yes, agreed. The step is back: uyuni-project/uyuni-docs#1213 |
uyuni-project/uyuni#2645 leaving out this step causes more trouble than good.
uyuni-project/uyuni#2645 leaving out this step causes more trouble than good.
* in upgrade guide, add "zypper ref" step (#1213) uyuni-project/uyuni#2645 leaving out this step causes more trouble than good.
merged |
Following "Server - Minor Upgrade" section of
https://www.uyuni-project.org/doc/2020.09/uyuni_upgrade_guide.pdf
This did not upgrade on my installation. The Uyuni repo was not automatically refreshed.
Suggestion:
Include an additional step between stage 1. and 2. of
The text was updated successfully, but these errors were encountered: