The same issue:
https://openqa.suse.de/tests/2340493#step/zypper_migration/2

Another zypper migration failure:
https://openqa.suse.de/tests/2340494#step/zypper_migration/2

Output as: No migration available

leli wrote:

Verified on o.s.d.
https://openqa.suse.de/tests/2352766#step/zypper_migration/4

New failed: https://openqa.suse.de/tests/2360342#step/zypper_migration/2

From the console log, we can see there is no error output which is the reason why zypper_migration not return as failure.

#########################

wait_serial expected: [¶

qr/(?^{m:[num\/q])/,}
qr/(?^m:Disable obsolete repository)/,
qr/(?^m:Continue\? [y)/,
qr/(?^{m:Executing.*after} online migration|^{ZYPPER-DONE)/,}
qr/(?^m:Abort, retry, ignore\? [a)/,
qr/(?^m:Choose from above solutions by number[\s\S,]* [1)/,
qr/(?^ms:File conflicts .*^Continue\? [y)/,
qr/(?^m:View the notifications now\? [y)/,
qr/(?^m:Migration failed)/,
qr/(?^m:Do you agree with the terms of the license\? [y)/,
qr/(?^m:No migration available|^Can't get available migrations)/
]

Result:¶

Executing 'zypper patch-check --updatestack-only'

Refreshing service 'SMT-https_migration-smt_qa_suse_de'.
Loading repository data...
Reading installed packages...

0 patches needed (0 security patches)

Executing 'zypper refresh'

Repository 'SLE-Module-Basesystem15-Pool' is up to date.
Repository 'SLE-Module-Basesystem15-Updates' is up to date.
Repository 'SLE-Module-Desktop-Applications15-Pool' is up to date.
Repository 'SLE-Module-Desktop-Applications15-Updates' is up to date.
Repository 'SLE-Module-Packagehub-Subpackages15-Pool' is up to date.
Repository 'SLE-Module-Packagehub-Subpackages15-Updates' is up to date.
Repository 'SLE-Module-Server-Applications15-Pool' is up to date.
Repository 'SLE-Module-Server-Applications15-Updates' is up to date.
Repository 'SLE-Product-SLES15-Pool' is up to date.
Repository 'SLE-Product-SLES15-Updates' is up to date.
Repository 'SUSE-PackageHub-15-Pool' is up to date.
Repository 'SUSE-PackageHub-15-Standard-Pool' is up to date.
All repositories have been refreshed.

Welcome to SUSE Linux Enterprise Server 15 (ppc64le) - Kernel 4.12.14-25.25-default (hvc0).

br0: 10.0.2.15 fec0::317f:cdc4:d555:df30
eth0:

susetest login: Can't get available migrations from server: SUSE::Connect::ApiError: Could not determine productID for 'sle-module-packagehub-subpackages' with version '15', release '', and arch 'ppc64le'
ZYPPER-DONE
####################################

I tried to re-run this job, the console log contains the error info so zypper_migration returns failure as expected.https://openqa.suse.de/tests/2460347#step/zypper_migration/3
So maybe there is something need to be enhanced for function wait_serial or something wrong with the back_end.

@Oliver, WDYT?

leli wrote:

susetest login: Can't get available migrations from server: SUSE::Connect::ApiError: Could not determine productID for 'sle-module-packagehub-subpackages' with version '15', release '', and arch 'ppc64le'

Makes it pretty clear to me that the problem is about the new SCC channel "packagehub subpackages" as described in https://fate.suse.com/325963 . https://scc.suse.com/admin/products/1743 also lists that repository under "Attached Repositories". The same for ppc64le: https://scc.suse.com/admin/products/1741

I don't see anything wrong with wait_serial or the backend here. I wonder though why the value of "release" is empty. Maybe that is a symptom of the root cause? Did you compare to the x86_64 case?

Ah, I think I see now what your question is about. I missed the upper part of the comment because the "Can't" in "Can't get available migrations" is written in small letters. I suggest to wrap code and verbatim log output parts with the backticks so that redmine marks it as code sections appropriately.

But this can be exactly the problem. The ^ in the regex ^Can't might not match. So can you try to just match without the ^?

@Oliver, Thanks for reviewing this ticket. In fact, I think you haven't catch the keypoint of this ticket. This ticket is try to let zypper_migration return failed while not to return pass when failure happens.
I found in https://openqa.suse.de/tests/2447719#step/zypper_migration/2 zypper_migration hasn't catch the error message of 'Can't get available migrations' because the error message be added a unexpected header 'susetest login: ', since the condition is '^Can't get available migrations' then can't catch the non begin with the expected string.
I think we can workaround this by modify the expected condition to remove '^' then just 'Can't get available migrations' then report failure.

@Oliver, yes, just as you said, I will fix this issue by removing '^' in the condition. Thanks.

Your comments are really hard to read as it does not show the ^ character. Please use back ticks to mark the verbatim sections

@Oliver, already updated the comments with back ticks for '\v', thanks.

yes, that looks good +1