Uyuni proxy upgrade keichwa #388

keichwa · 2020-07-21T17:59:55Z

Description

upgrade uyuni proxy to 2020.07 with OS update

Target branches

To what product version this document applies?

Manager-3.2
Manager-4.0
Manager-4.1
Uyuni

Links

Fixes #<insert issue or PR link, if any>

juliogonzalez

Are you sure this is the correct procedure? I never tried to upgrade a proxy, but it doesn't make any sense to me. Specially because you are installing server repositories.

AFAIK the proxies are always clients, so that would mean either updating the clients from the Uyuni Server, either just replacing them.

Please check with @mantel

juliogonzalez · 2020-07-21T18:04:57Z

modules/upgrade/pages/proxy-uyuni.adoc

+. Replace and refresh software repositories:
+
+----
+mv /etc/zypp/repos.d /etc/zypp/repos.d.old


Huh? what's this :-?

It's creating a backup of the old repos directory but this is wrong. What if the user has some other repositories enabled?

On a proxy, it should not. This is not what worries me most. The whole script is what worries me. I think it's the wrong way to do the uprade.

Funny enough it seems we tell people to install the Uyuni Proxy not as a client: https://www.uyuni-project.org/uyuni-docs/uyuni/installation/install-proxy-uyuni.html

I don't know why this is this way. To me it seems strange and wrong, but OK. For now it is how it is. So the script seems to make sense.

Ah now I understand it. You tell them to it that way, but then you say this: https://www.uyuni-project.org/uyuni-docs/uyuni/installation/uyuni-proxy-registration.html (BTW the channel name for spacewalk-common-channels is not uyuni-proxy-stable-leap-151 bot uyuni-proxy-stable-leap)

So in the end this migration script is still wrong, as the proxies will be clients. If you run this script, yeah, the migration will work, but then the Server will still think the proxy is a Leap 15.1, so I guess it will crate a mess.

This what I suspect that needs to be done if you want to migrate:

Add the Leap 15.2 channels with spacewalk-common-channels opensuse_leap15_2 opensuse_leap15_2-non-oss opensuse_leap15_2-non-oss-updates opensuse_leap15_2-updates opensuse_leap15_2-uyuni-client uyuni-proxy-stable-leap-152

Sync them: spacewalk-repo-sync -p opensuse_leap15_2-x86_64 (this will sync the parent and all children).

Adjust the proxies using SSM or one by one to use the Leap 15.2 channels you just added and synced. Remember to apply the changes.

Perform the migration (this is the "gray" area for me, maybe this where they need to run spacewalk-proxy stop; zypper ref; zypper -n dup --allow-vendor-change; shutdown -r now directly on the proxies).

And that should be all.

As for the procedure to add the proxy, itself, I'd say its wrong. What should be required is: Clean openSUSE Leap 15.2 installed and 100% updated (now that we are switching), and then Proxy Registration and finally Uyuni Proxy Setup (BTW the requirements still say Leap 15.1)

BTW I just noticed we don't have uyuni-proxy-stable-leap-152, so time to create it.

OK, I thought a little about all this mess. Let's do the following:

I will tag Uyuni tomorrow, and will no accept more submissions to the master branch (meanwhile I will prepare a MU as well)

@keichwa and @mantel can test the migration of the proxy tomorrow and Thursday and have the doc ready by end of Thursday

@jcayouette prepares the package and the PR for the website on Thursday by the end of the day, or Friday, early in the morning.

I start the release on Friday morning, as soon as the PR and the package for the doc are ready.

We create an issue for the Uyuni Proxy Installation, so we can remove that instruction about adding the repositories manually, but to be fixed on a future Uyuni release.

Sounds fair enough? That gives some more time to test the migration without that much pressure.

Please ACK tomorrow morning if we have an agreement.

I answered too quickly yesterday. While this script probably would (sort of) work, the clean way to upgrade the proxy would be to initiate an autoyast upgrade from the server. This way all the information regarding the proxy would stay consistent. We even had this documented some time ago; biggest issue is providing a working autoyast file which is a bit tricky.

So in the end this migration script is still wrong, as the proxies will be clients. If you run this script, yeah, the migration will work, but then the Server will still think the proxy is a Leap 15.1, so I guess it will crate a mess.

Maybe this could even be fixed up by refreshing the information from the proxy, but yes, the only really clean way is to perform the upgrade via autoyast so the server is aware of any modifications done to the proxy.

I think that providing manual instructions should be fine as well (if it is easier) as long as they are accurate. Something like what I described above.

I think that providing manual instructions should be fine as well (if it is easier) as long as they are accurate. Something like what I described above.

Yes, especially as it is much easier than to fiddle around with autoyast files. We just need to confirm that the changes in the proxy's system can be updated to the new state afterwards.

juliogonzalez

I approved, but I obviously was requesting changes :-)

paususe · 2020-07-21T18:19:08Z

modules/upgrade/pages/proxy-uyuni.adoc

+. Replace and refresh software repositories:
+
+----
+mv /etc/zypp/repos.d /etc/zypp/repos.d.old


It's creating a backup of the old repos directory but this is wrong. What if the user has some other repositories enabled?

modules/upgrade/pages/proxy-uyuni.adoc

Thanks, Pau! Co-authored-by: Pau Garcia Quiles <[email protected]>

keichwa · 2020-07-22T04:40:40Z

Julio González Gil <[email protected]> writes:

Sounds fair enough? That gives some more time to test the migration without that much pressure. Please ACK tomorrow morning if we have an agreement.

ACK, I think this is a good proposal.

…

-- Karl Eichwalder

keichwa · 2020-07-22T12:57:05Z

can you please check whether I'm on the right track. I mostly reused what we have for upgrading/migrating SUMA Proxy, and I tried to adjust it as needed.

juliogonzalez

Not approving, but not declining either.

If both procedures are tested to work, then I am happy with merging the PR.

If not, please test at least the non-autoyast approach, and if you can't test autoyast just don't document it for now.

juliogonzalez · 2020-07-22T12:57:38Z

modules/upgrade/pages/proxy-uyuni.adoc

+. In the {productname} Server {webui}, navigate to menu:Systems[Proxy] and click the name of the proxy.
+. Click menu:Software[Software Channels], and select the openSUSE Leap {opensuse-version} channel.
+. Click menu:Software[Packages], and select all the packages to be updated on the proxy, and then apply the selection.
+. On the {productname} Proxy, start the proxy service:


Does it work? If so, fine with me.

juliogonzalez · 2020-07-22T12:57:57Z

modules/upgrade/pages/proxy-autoyast-uyuni.adoc

+. On the {productname} Server {webui}, navigate to the [guimenu]``System List``, select the proxy, and navigate to the menu:Software[Software Channels] subtab.
+. Clear the old channels.
+. In the [guimenu]``Base Channel`` field, select `openSUSE Leap 15.1 (x86_64)``.
+. In the [guimenu]``Child Channels`` field, select all the recommended channels.


Does this procedure work? Otherwise I'd not document it.

juliogonzalez · 2020-07-22T13:23:52Z

can you please check whether I'm on the right track. I mostly reused what we have for upgrading/migrating SUMA Proxy, and I tried to adjust it as needed.

Please test at least the manual procedure, ask help from @mantel if needed, and feel free to remove autoyast for now if you can't verify it.

juliogonzalez

To me it looks good. Was autoyast procedure tested as well? If so: great! If not, I'd avoid publishing it for now.

modules/upgrade/pages/proxy-autoyast-uyuni.adoc

modules/upgrade/pages/proxy-uyuni.adoc

keichwa · 2020-07-24T10:09:43Z

To me it looks good. Was autoyast procedure tested as well? If so: great! If not, I'd avoid publishing it for now.

the ay procedure is currently not included in the generated docs. I commented the include statement in the nav.

keichwa added 3 commits July 21, 2020 15:17

start with proxy

9911d6b

proxy upgrade procedure

a41c132

eadd uyuni proxy entry

5242c65

keichwa requested review from mantel, Loquacity and juliogonzalez July 21, 2020 17:59

juliogonzalez approved these changes Jul 21, 2020

View reviewed changes

juliogonzalez self-requested a review July 21, 2020 18:08

juliogonzalez requested changes Jul 21, 2020

View reviewed changes

paususe suggested changes Jul 21, 2020

View reviewed changes

paususe reviewed Jul 21, 2020

View reviewed changes

modules/upgrade/pages/proxy-uyuni.adoc Outdated Show resolved Hide resolved

Update modules/upgrade/pages/proxy-uyuni.adoc

20769cf

Thanks, Pau! Co-authored-by: Pau Garcia Quiles <[email protected]>

keichwa marked this pull request as draft July 21, 2020 18:56

juliogonzalez mentioned this pull request Jul 21, 2020

Channels for Uyuni Proxy and Server for openSUSE Leap 15.2 uyuni-project/uyuni#2432

Merged

14 tasks

upgrade uyuni server: webui and autoyast

038615d

keichwa requested review from juliogonzalez and paususe July 22, 2020 12:54

keichwa marked this pull request as ready for review July 22, 2020 12:55

juliogonzalez reviewed Jul 22, 2020

View reviewed changes

Loquacity approved these changes Jul 22, 2020

View reviewed changes

keichwa added 2 commits July 24, 2020 05:57

rework according to feedback

653fbad

disable proxy-autoyast-uyuni.adoc which is currently untested

7a4bec1

juliogonzalez approved these changes Jul 24, 2020

View reviewed changes

keichwa commented Jul 24, 2020

View reviewed changes

modules/upgrade/pages/proxy-autoyast-uyuni.adoc Outdated Show resolved Hide resolved

modules/upgrade/pages/proxy-uyuni.adoc Outdated Show resolved Hide resolved

keichwa added 2 commits July 24, 2020 12:07

Update modules/upgrade/pages/proxy-autoyast-uyuni.adoc

0448b58

Update modules/upgrade/pages/proxy-uyuni.adoc

f26fe26

keichwa merged commit 7f66b2a into master Jul 24, 2020

keichwa deleted the uyuni-proxy-upgrade-keichwa branch July 24, 2020 10:18

Uyuni proxy upgrade keichwa #388

Uyuni proxy upgrade keichwa #388

Uh oh!

Conversation

keichwa commented Jul 21, 2020

Description

Target branches

Links

Uh oh!

juliogonzalez left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliogonzalez Jul 21, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliogonzalez Jul 21, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliogonzalez Jul 21, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliogonzalez left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

keichwa commented Jul 22, 2020 via email

Uh oh!

keichwa commented Jul 22, 2020

Uh oh!

juliogonzalez left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

juliogonzalez commented Jul 22, 2020

Uh oh!

juliogonzalez left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

keichwa commented Jul 24, 2020

Uh oh!

Uh oh!

juliogonzalez Jul 21, 2020 •

edited

Loading

juliogonzalez Jul 21, 2020 •

edited

Loading

juliogonzalez Jul 21, 2020 •

edited

Loading