<html>
<head>
<base href="https://bugzilla.suse.com/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Increase in failures "Migration failed with {0}'.format(issue)" across all CSP's when upgrading DMS"
href="https://bugzilla.suse.com/show_bug.cgi?id=1203115">1203115</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Increase in failures "Migration failed with {0}'.format(issue)" across all CSP's when upgrading DMS
</td>
</tr>
<tr>
<th>Classification</th>
<td>SUSE Linux Enterprise Server
</td>
</tr>
<tr>
<th>Product</th>
<td>SUSE Linux Enterprise Server 12 SP5 in Public Clouds
</td>
</tr>
<tr>
<th>Version</th>
<td>On-Demand
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5 - None
</td>
</tr>
<tr>
<th>Component</th>
<td>DMS
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dms-bugs@lists.suse.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>rich.paredes@suse.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>public-cloud-maintainers@suse.de
</td>
</tr>
<tr>
<th>Group</th>
<td>SUSE Public Cloud
</td>
</tr>
<tr>
<th>Found By</th>
<td>---
</td>
</tr>
<tr>
<th>Blocker</th>
<td>---
</td>
</tr></table>
<p>
<div>
<pre>We're receiving an increase in support cases across both Amazon and Google with
customers performing upgrades via DMS.
A workaround that seemed to work in the past was to run:
zypper in --oldpackage suse-migration-sle15-activation-2.0.32-6.27.1 and
overwrite the newer version.
But this no longer works.
Sep 02 18:58:09 localhost suse-migration[1353]: Traceback (most recent call
last):
Sep 02 18:58:09 localhost suse-migration[1353]: File
"/usr/bin/suse-migration", line 11, in <module>
Sep 02 18:58:09 localhost suse-migration[1353]:
load_entry_point('suse-migration-services==2.0.33', 'console_scripts',
'suse-migration')()
Sep 02 18:58:09 localhost suse-migration[1353]: File
"/usr/lib/python3.6/site-packages/suse_migration_services/units/migrate.py",
line 117, in main
Sep 02 18:58:09 localhost suse-migration[1353]: 'Migration failed with
{0}'.format(issue)
Sep 02 18:58:09 localhost suse-migration[1353]:
suse_migration_services.exceptions.DistMigrationZypperException: Migration
failed with bash: stderr: (no output on stderr), stdout: (no output on stdout)
Sep 02 18:58:09 localhost systemd[1]: suse-migration.service: Main process
exited, code=exited, status=1/FAILURE
Sep 02 18:58:09 localhost systemd[1]: Failed to start Run Zypper Migration.
Sep 02 18:58:09 localhost systemd[1]: suse-migration.service: Unit entered
failed state.
Sep 02 18:58:09 localhost systemd[1]: suse-migration.service: Failed with
result 'exit-code'.
I'll upload the logs also.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>