Skip to content

Commit

Permalink
backport 4.3: Ccg migrate el 2 sll #23428 (#2737) (#2753)
Browse files Browse the repository at this point in the history
* Ccg migrate el 2 sll #23428 (#2737)

* basic info taken from the initial issue
SUSE/spacewalk#23428
* reference migration section from clients' register section
Co-authored-by: Ornela Marić <[email protected]>
Co-authored-by: Ricardo Mateus <[email protected]>
  • Loading branch information
keichwa authored Feb 1, 2024
1 parent aa5622f commit 5187648
Show file tree
Hide file tree
Showing 7 changed files with 56 additions and 5 deletions.
2 changes: 2 additions & 0 deletions .changelog
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
# - Fixed error in Bat section of Upgrade Guide (bsc#1234567)
# For guidelines: https://en.opensuse.org/openSUSE:Creating_a_changes_file_(RPM)#Changelog_section_.28.25changelog.29

- Added section about migrating Enterprise Linux (EL) clients to SUSE Liberty
Linux to Client Configuration Guide
- Added detailed information about the messages produced by subscription matcher
- Added Pay-as-you-go as supported service on Azure to the Public Cloud Guide
- Added and fixed configuration details in Troubleshooting Renaming
Expand Down
39 changes: 39 additions & 0 deletions modules/client-configuration/pages/clients-sleses.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -289,3 +289,42 @@ This gives you a backup of the original synchronization data.

include::snippets/create_bootstrap_repo_register.adoc[]



[[clients-sleses-el-migration]]
== Migrate Enterprise Linux (EL) clients to {sll}

If an Enterprise Linux (EL) client such as RHEL and all clones (like {centos}, {almalinux}, {rocky}, and {oracle}) is already registered as a minion on {productname} and users wanted to migrate it to {sll} they can use a re-activation key to apply the activation key that drives the migration.

For more information about re-activation keys, see xref:client-configuration:activation-keys.adoc#reactivation[].

The re-activation key is per minion, and can be generated with the {webui} or using the API.
For more information, see https://documentation.suse.com/suma/4.3/api/suse-manager/api/system.html#apidoc-system-obtainReactivationKey-loggedInUser-sid.

To re-activate a client, the user can run the bootstrap script on the client and pass the re-activation key as an environment variable. Example:

----
REACTIVATION_KEY=<KEY> ./bootstrap_liberate9.sh
----

Another method is to add some special flags to the {salt} client configuration file located at [path]``/etc/venv-salt-minon/minion.d/susemanager.conf`` (or [path]``/etc/salt-minon/minion.d/susemanager.conf``) the following content (join this content with the already existing one):

----
grains:
susemanager:
activation_key: "<KEY_ID>"
management_key: "MINION_REACTIVATION_KEY"
----

After changing the [path]``susemanager.conf`` file, the [systemitem]``salt-minion`` service needs to be restarted on the {salt} server. By default with:

----
systemctl restart venv-salt-minon
----

Or for legacy {salt} with:

----
systemctl restart salt-minon
----

Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@ The method and details vary depending on the operating system of the client.
Before you start, ensure that the client has the date and time synchronized correctly with the {productname} Server.

You must also have created an activation key.
For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].

* For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
* For more information about migrating {almalinux} to {sll}, see xref:client-configuration:clients-sleses.adoc#clients-sleses-el-migration[].
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@ The method and details varies depending on the operating system of the client.
Before you start, ensure that the client has the date and time synchronized correctly with the {productname} Server.

You must also have created an activation key.
For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].

* For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
* For more information about migrating {centos} to {sll}, see xref:client-configuration:clients-sleses.adoc#clients-sleses-el-migration[].
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@ The method and details varies depending on the operating system of the client.
Before you start, ensure that the client has the date and time synchronized correctly with the {productname} Server.

You must also have created an activation key.
For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].

* For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
* For more information about migrating {oracle} to {sll}, see xref:client-configuration:clients-sleses.adoc#clients-sleses-el-migration[].
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@ The method and details varies depending on the operating system of the client.
Before you start, ensure that the client has the date and time synchronized correctly with the {productname} Server.

You must also have created an activation key.
For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].

* For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
* For more information about migrating {rhel} to {sll}, see xref:client-configuration:clients-sleses.adoc#clients-sleses-el-migration[].
Original file line number Diff line number Diff line change
Expand Up @@ -7,4 +7,6 @@ The method and details vary depending on the operating system of the client.
Before you start, ensure that the client has the date and time synchronized correctly with the {productname} Server.

You must also have created an activation key.
For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].

* For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
* For more information about migrating {rocky} to {sll}, see xref:client-configuration:clients-sleses.adoc#clients-sleses-el-migration[].

0 comments on commit 5187648

Please sign in to comment.