Project

General

Profile

Actions

action #38750

closed

[QAM] test fails in zypper_lifecycle_toolchain

Added by osukup almost 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2018-07-23
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

# Test died: 'zypper -n in cpp6 cpp7 cross-nvptx-gcc7 \
… libstdc++6-devel-gcc7-32bit | nvptx-tools sle-module-toolchain-release-cd' failed with code 105 at /var/lib/openqa/cache/tests/sle/lib/utils.pm line 370.

looks pretty wrong .. see PIPE in zypper command

openQA test in scenario sle-12-SP3-Server-DVD-Incidents-x86_64-qam-allpatterns+addons@64bit fails in
zypper_lifecycle_toolchain

Reproducible

Fails since (at least) Build :7829:util-linux.1529909269

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by osukup almost 6 years ago

I hate redmine ...

# Test died: 'zypper -n in cpp6 cpp7 cross-nvptx-gcc7 cross-nvptx-newlib7-devel gcc5-32bit gcc5-ada gcc5-ada-32bit gcc5-c++-32bit gcc5-fortran-32bit gcc5-info gcc6 gcc6-32bit gcc6-c++ gcc6-c++-32bit gcc6-fortran gcc6-fortran-32bit gcc6-info gcc6-locale gcc7 gcc7-32bit gcc7-ada gcc7-ada-32bit gcc7-c++ gcc7-c++-32bit gcc7-fortran gcc7-fortran-32bit gcc7-info gcc7-locale libada5 libada5-32bit libada7 libada7-32bit libffi-devel-gcc5-32bit libstdc++6-devel-gcc5-32bit libstdc++6-devel-gcc6 libstdc++6-devel-gcc6-32bit libstdc++6-devel-gcc7 libstdc++6-devel-gcc7-32bit | nvptx-tools sle-module-toolchain-release-cd' failed with code 105 at /var/lib/openqa/cache/tests/sle/lib/utils.pm line 370.
Actions #2

Updated by okurz almost 6 years ago

  • Description updated (diff)

I guess every markdown parser would do the same ;)

Actions #3

Updated by okurz almost 6 years ago

I think I could reproduce the problem with

docker run -it --rm registry.suse.de/suse/sle-12-sp3/docker/update/cr/images/suse/sles12sp3:2.0.2 sh -c 'echo "nameserver 10.160.0.1" > /etc/resolv.conf; zypper ar -f http://download.suse.de/ibs/SUSE:/Maintenance:/8033/SUSE_Updates_SLE-Module-Toolchain_12_x86_64/ incident8033 && zypper ref && zypper se -u -r 1 -t package | awk "{print \$2}"'

-->

Retrieving repository 'incident8033' metadata ...........................................................................................................[done]
Building repository 'incident8033' cache ................................................................................................................[done]
All repositories have been refreshed.
service
Problem retrieving the repository index file for service 'container-suseconnect':
[container-suseconnect|file:/usr/lib/zypp/plugins/services/container-suseconnect] 
Skipping
repository
installed

|

lifecycle-data-sle-module-toolchain

Problem is that the awk '{ print $2}' is not safe to use when the first column either has an entry or not. Maybe we can find a better way to parse the output of zypper se

Actions #4

Updated by riafarov almost 6 years ago

I was able to reproduce issue on my box too, checking how to avoid parsing problem

Actions #5

Updated by okurz almost 6 years ago

How about

zypper se -ur SLE-Module-Toolchain12-Updates -t package | sed -n 's/^[ ^|]*| \([^|]*\).*$/\1/p' | grep -vE '(gcc6-ada|libada6)

This gives just the output

lifecycle-data-sle-module-toolchain

Probably the safest way is to use xml output of zypper and just show the matches with grep

zypper --xmlout se -ur SLE-Module-Toolchain12-Updates -t package | grep -oP '(?<=name=")[^"]*'
Actions #6

Updated by riafarov almost 6 years ago

I would go for this one: zypper -q se -urq SLE-Module-Toolchain12-Updates -t package | awk -F '|' '{print \$2}' | grep -vE '(gcc6-ada|libada6)'

Actions

Also available in: Atom PDF