[sle-beta] FW: [Beta-programs] - SLES12-SP3 Beta migration
Waite, Dick (External)
Dick.Waite at softwareag.com
Thu May 11 08:51:55 MDT 2017
Grand Day,
I found the message at the bottom from Vincent to “lists.suse.com” on Tuesday. He feels it should not need the “test repo” any more. He asked if I’d try it out and post my output for comments on this list.
I used a VMware Workstation machine. I had SP-3 Beta1 running on the machine. I took a check point and the did an update with Yast2 and the Beta2 .iso file. That ran grand and I took another check point.
I’m not too familiar with the good “zipper” but it does what I want, so if I should have given it more options or used other command, please speak up. The machine is running with a Beta SCC code. So here we are at the Beta2 check point, my simple IVP ran Okay (not shown).
# We are at a running SP-3 Beta2 migrated system
rjw02-12-1-2:~ # cat /etc/issue
Welcome to SUSE Linux Enterprise Server 12 SP3 Beta2 (x86_64) - Kernel \r (\l).
rjw02-12-1-2:~ # zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
---+----------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+--------
1 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ----
2 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ----
3 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No
4 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ----
5 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes
6 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | No | ---- | ----
7 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ----
8 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ----
9 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No
10 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ----
11 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes
12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ----
13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ----
14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No
15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ----
16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes
17 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ----
18 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ----
19 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No
20 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ----
21 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes
rjw02-12-1-2:~ #
###################################### So going back to the "Before Beta2 check point" ........
rjw02-12-1-2:~ # cat /etc/issue
Welcome to SUSE Linux Enterprise Server 12 SP3 Beta1 (x86_64) - Kernel \r (\l). The Beta1 check point…..
rjw02-12-1-2:~ # # we are now back at Beta1
rjw02-12-1-2:~ #
rjw02-12-1-2:~ #
rjw02-12-1-2:~ # zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
---+----------------------------------------------------------------------------------------------+----------------------------------------------+---------+-----------+--------
1 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Pool | SLE-Module-Legacy12-Debuginfo-Pool | No | ---- | ----
2 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Debuginfo-Updates | SLE-Module-Legacy12-Debuginfo-Updates | No | ---- | ----
3 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Pool | SLE-Module-Legacy12-Pool | Yes | (r ) Yes | No
4 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Source-Pool | SLE-Module-Legacy12-Source-Pool | No | ---- | ----
5 | Legacy_Module_12_x86_64:SLE-Module-Legacy12-Updates | SLE-Module-Legacy12-Updates | Yes | (r ) Yes | Yes
6 | SLES12-SP3-12.3-0 | SLES12-SP3-12.3-0 | Yes | (r ) Yes | No
7 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Pool | SLES12-SP3-Debuginfo-Pool | No | ---- | ----
8 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Debuginfo-Updates | SLES12-SP3-Debuginfo-Updates | No | ---- | ----
9 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Pool | SLES12-SP3-Pool | Yes | (r ) Yes | No
10 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Source-Pool | SLES12-SP3-Source-Pool | No | ---- | ----
11 | SUSE_Linux_Enterprise_Server_12_SP3_x86_64:SLES12-SP3-Updates | SLES12-SP3-Updates | Yes | (r ) Yes | Yes
12 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Pool | SLE-SDK12-SP3-Debuginfo-Pool | No | ---- | ----
13 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Debuginfo-Updates | SLE-SDK12-SP3-Debuginfo-Updates | No | ---- | ----
14 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Pool | SLE-SDK12-SP3-Pool | Yes | (r ) Yes | No
15 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Source-Pool | SLE-SDK12-SP3-Source-Pool | No | ---- | ----
16 | SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64:SLE-SDK12-SP3-Updates | SLE-SDK12-SP3-Updates | Yes | (r ) Yes | Yes
17 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Pool | SLE-Module-Web-Scripting12-Debuginfo-Pool | No | ---- | ----
18 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Debuginfo-Updates | SLE-Module-Web-Scripting12-Debuginfo-Updates | No | ---- | ----
19 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Pool | SLE-Module-Web-Scripting12-Pool | Yes | (r ) Yes | No
20 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Source-Pool | SLE-Module-Web-Scripting12-Source-Pool | No | ---- | ----
21 | Web_and_Scripting_Module_12_x86_64:SLE-Module-Web-Scripting12-Updates | SLE-Module-Web-Scripting12-Updates | Yes | (r ) Yes | Yes
rjw02-12-1-2:~ # # These are the repositories I can see
rjw02-12-1-2:~ #
rjw02-12-1-2:~ # zypper info zypper-migration-plugin
Refreshing service 'Legacy_Module_12_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_12_SP3_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Software_Development_Kit_12_SP3_x86_64'.
Refreshing service 'Web_and_Scripting_Module_12_x86_64'.
Loading repository data...
Reading installed packages...
Information for package zypper-migration-plugin:
------------------------------------------------
Repository : SLES12-SP3-Pool
Name : zypper-migration-plugin
Version : 0.10-12.4
Arch : noarch
Vendor : SUSE LLC <https://www.suse.com/>
Support Level : Level 3
Installed Size : 16.7 KiB
Installed : Yes
Status : up-to-date
Source package : zypper-migration-plugin-0.10-12.4.src
Summary : Zypper subcommand for online migration
Description :
Zypper subcommand for online migration to new service pack.
rjw02-12-1-2:~ # # we do have a zypper-migration-plugin and it's up-2-date ?????
rjw02-12-1-2:~ #
rjw02-12-1-2:~ # # so lets try a migration from SP-3 Beta1 to Beta2
rjw02-12-1-2:~ #
rjw02-12-1-2:~ # zypper migration --help
Usage: zypper migration [options]
--[no-]allow-vendor-change Allow vendor change
-v, --[no-]verbose Increase verbosity
-q, --[no-]quiet Suppress normal output, print only error messages
-n, --non-interactive Do not ask anything, use default answers automatically
--query Query available migration options and exit
--disable-repos Disable obsolete repositories without asking
--migration N Select migration option N
--from REPO Restrict upgrade to specified repository
-r, --repo REPO Load only the specified repository
-l, --auto-agree-with-licenses Automatically say 'yes' to third party license confirmation prompt
--debug-solver Create solver test case for debugging
--recommends Install also recommended packages
--no-recommends Do not install recommended packages
--replacefiles Install the packages even if they replace files from other packages
--details Show the detailed installation summary
--download MODE Set the download-install mode
--download-only Replace repositories and download the packages, do not install. WARNING: Upgrade with 'zypper dist-upgrade' as soon as possible.
rjw02-12-1-2:~ # # just cheking what "help" will show us...
rjw02-12-1-2:~ # zypper migration --query
Executing 'zypper refresh'
Repository 'SLE-Module-Legacy12-Pool' is up to date.
Repository 'SLE-Module-Legacy12-Updates' is up to date.
Repository 'SLES12-SP3-12.3-0' is up to date.
Retrieving repository 'SLES12-SP3-Pool' metadata ............................................................................................................................[done]
Building repository 'SLES12-SP3-Pool' cache .................................................................................................................................[done]
Repository 'SLES12-SP3-Updates' is up to date.
Retrieving repository 'SLE-SDK12-SP3-Pool' metadata .........................................................................................................................[done]
Building repository 'SLE-SDK12-SP3-Pool' cache ..............................................................................................................................[done]
Repository 'SLE-SDK12-SP3-Updates' is up to date.
Repository 'SLE-Module-Web-Scripting12-Pool' is up to date.
Repository 'SLE-Module-Web-Scripting12-Updates' is up to date.
All repositories have been refreshed.
Executing 'zypper --no-refresh patch-check --updatestack-only'
Loading repository data...
Reading installed packages...
Considering 0 out of 1 applicable patches:
0 patches needed (0 security patches)
No migration available.
rjw02-12-1-2:~ # # It's saying "No migration available."
rjw02-12-1-2:~ # # do we push on.... This is running on a VMware Workstation and I do have a check point at a good Beta2 level...
rjw02-12-1-2:~ # zypper migration
Executing 'zypper refresh'
Repository 'SLE-Module-Legacy12-Pool' is up to date.
Repository 'SLE-Module-Legacy12-Updates' is up to date.
Repository 'SLES12-SP3-12.3-0' is up to date.
Repository 'SLES12-SP3-Pool' is up to date.
Repository 'SLES12-SP3-Updates' is up to date.
Repository 'SLE-SDK12-SP3-Pool' is up to date.
Repository 'SLE-SDK12-SP3-Updates' is up to date.
Repository 'SLE-Module-Web-Scripting12-Pool' is up to date.
Repository 'SLE-Module-Web-Scripting12-Updates' is up to date.
All repositories have been refreshed.
Executing 'zypper --no-refresh patch-check --updatestack-only'
Loading repository data...
Reading installed packages...
Considering 0 out of 1 applicable patches:
0 patches needed (0 security patches)
No migration available. Not a surprising result ;o)
rjw02-12-1-2:~ # # Ummmm the same message....
So it seems to run the command Okay but does not “migrate from Beta1 to beta2” Should I have given it more commands or options to commands ????
Your input very welcome….
__R
############################################################# original post ######################################################
[sles-beta] [ANNOUNCE] Online Migration from SLES12 to SLES12-SP1 Beta
Vincent Moutoussamy vmoutoussamy at suse.com <mailto:sles-beta%40lists.suse.com?Subject=Re%3A%20%5Bsles-beta%5D%20%5BANNOUNCE%5D%20Online%20Migration%20from%20SLES12%20to%20SLES12-SP1%0A%09Beta&In-Reply-To=%3CF5BA5312-CCD2-4ECC-8FA5-2BD3D629B4FF%40suse.com%3E>
Thu Sep 17 08:21:18 MDT 2015
Good news everyone,
The tools for the Service Pack Online Migration between SLES 12 GA and SLES 12 SP1 Beta is now available for beta testing.
The online migration between service packs allows to migrate a system to a new service pack while the system is still running.
It is not necessary to download a new DVD and boot from that for an upgrade.
== Requirements ==
In order to do an online update, the following requirements must be met :
- SLES 12 as base system,
- SLES 12 subscribed to :
- SCC :
Please use the registration key sent to you for the SLES 12 SP1 Beta Program.
For more information please check our last communication about these keys: [ANNOUNCE] Beta test Subscription key for SLE 12 SP1 Beta.
For any issue about the subscription, please contact us at beta-programs at lists.suse.com.<http://lists.suse.com/mailman/listinfo/sles-beta>
- SMT :
SMT needs to be the one from the update channel of SLES12 SP1 Beta3.
== Run an Online Migration ==
1) Add the repository with the beta migration tools :
# zypper ar -f http://beta.suse.com/private/SLE12/SP1-BETA/SUSE:SLE-12:MigrationTest.repo
You should now see something like that :
# zypper lr
# | Alias | Name | Enabled | GPG Check | Refresh
--+-----------------------------------------------------------------+------------------------------------------------------------------------+---------+-----------+--------
1 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Debuginfo-Pool | SLES12-Debuginfo-Pool | No | ---- | No
2 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Debuginfo-Updates | SLES12-Debuginfo-Updates | No | ---- | Yes
3 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Pool | SLES12-Pool | Yes | (r ) Yes | No
4 | SUSE_Linux_Enterprise_Server_12_x86_64:SLES12-Updates | SLES12-Updates | Yes | (r ) Yes | Yes
5 | SUSE_SLE-12_MigrationTest | testing project for backporting online migration to SLE 12 GA (SLE_12) | Yes | ( p) Yes | Yes
2) Update everything from the new added repository
# zypper dup --from SUSE_SLE-12_MigrationTest
3) Install the migration tools (only one of them is necessary, based on your preference)
# zypper in yast2-migration zypper-migration-plugin
4) Perform the migration itself
In SLE11, the migration tool was known as wagon (or YaST wagon module), it’s now call simply “migration"
a) via YaST: run 'yast2 migration' and follow the work-flow
b) via zypper: run 'zypper migration' and follow the instructions you get via your terminal. To see all options, run 'zypper migration --help'
If the migration is aborted, the system needs to be (manually) re-registered with the old products via SUSEConnect; in future versions,
this will be handled automatically.
Thank you for your feedback,
Your SUSE Linux Enterprise Team
--
Vincent Moutoussamy
SUSE Beta Program and SDK Project Manager
Software AG – Sitz/Registered office: Uhlandstraße 12, 64297 Darmstadt, Germany – Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Karl-Heinz Streibich (Vorsitzender/Chairman), Eric Duffaut, Dr. Wolfram Jost, Arnd Zinnhardt, Dr. Stefan Sigg; - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Dr. Andreas Bereczky - http://www.softwareag.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/sle-beta/attachments/20170511/9e6a7306/attachment.htm>
More information about the sle-beta
mailing list