[Bug 1158478] New: Transaction server debuginfo install fails without useful diagnostic.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 Bug ID: 1158478 Summary: Transaction server debuginfo install fails without useful diagnostic. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening@forge.provo.novell.com Reporter: william.brown@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Doing a pkg install of debuginfo to resolve an issue, the commands fails but does not describe why it fails. And because it's in a transactional environment, I can't access the logs or details? This seems like a situation where dropping into a shell may be a good solution to help resolve and diagnose once an error occurs. transactional-update pkg install cyrus-sasl-crammd5-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-digestmd5-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-gssapi-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-plain-debuginfo-2.1.27-1.6.x86_64 glibc-debuginfo-2.30-1.3.x86_64 krb5-debuginfo-1.17-4.2.x86_64 libaudit1-debuginfo-2.8.4-2.3.x86_64 libcom_err2-debuginfo-1.45.4-1.2.x86_64 libcrack2-debuginfo-2.9.6-2.14.x86_64 libcrypt1-debuginfo-4.4.3-2.3.x86_64 libdb-4_8-debuginfo-4.8.30-38.2.x86_64 libeconf0-debuginfo-0.3.3+git20191028.3ac14ce-1.1.x86_64 libfreebl3-debuginfo-3.47.1-1.1.x86_64 libgcrypt20-debuginfo-1.8.5-1.3.x86_64 libgpg-error0-debuginfo-1.36-2.2.x86_64 libicu-suse65_1-debuginfo-65.1-1.1.x86_64 libkeyutils1-debuginfo-1.6-1.3.x86_64 libldap-2_4-2-debuginfo-2.4.48-48.4.x86_64 liblz4-1-debuginfo-1.9.2-1.2.x86_64 liblzma5-debuginfo-5.2.4-4.3.x86_64 libopenssl1_1-debuginfo-1.1.1d-1.1.x86_64 libpcre1-debuginfo-8.42-3.1.x86_64 libsasl2-3-debuginfo-2.1.27-1.6.x86_64 libselinux1-debuginfo-2.9-6.1.x86_64 libsqlite3-0-debuginfo-3.29.0-2.2.x86_64 libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64 libsystemd0-debuginfo-243-4.1.x86_64 mozilla-nspr-debuginfo-4.23-1.1.x86_64 mozilla-nss-debuginfo-3.47.1-1.1.x86_64 pam-debuginfo-1.3.1+git20190923.ea78d67-1.3.x86_64 Checking for newer version. transactional-update 2.17 started Options: pkg install cyrus-sasl-crammd5-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-digestmd5-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-gssapi-debuginfo-2.1.27-1.6.x86_64 cyrus-sasl-plain-debuginfo-2.1.27-1.6.x86_64 glibc-debuginfo-2.30-1.3.x86_64 krb5-debuginfo-1.17-4.2.x86_64 libaudit1-debuginfo-2.8.4-2.3.x86_64 libcom_err2-debuginfo-1.45.4-1.2.x86_64 libcrack2-debuginfo-2.9.6-2.14.x86_64 libcrypt1-debuginfo-4.4.3-2.3.x86_64 libdb-4_8-debuginfo-4.8.30-38.2.x86_64 libeconf0-debuginfo-0.3.3+git20191028.3ac14ce-1.1.x86_64 libfreebl3-debuginfo-3.47.1-1.1.x86_64 libgcrypt20-debuginfo-1.8.5-1.3.x86_64 libgpg-error0-debuginfo-1.36-2.2.x86_64 libicu-suse65_1-debuginfo-65.1-1.1.x86_64 libkeyutils1-debuginfo-1.6-1.3.x86_64 libldap-2_4-2-debuginfo-2.4.48-48.4.x86_64 liblz4-1-debuginfo-1.9.2-1.2.x86_64 liblzma5-debuginfo-5.2.4-4.3.x86_64 libopenssl1_1-debuginfo-1.1.1d-1.1.x86_64 libpcre1-debuginfo-8.42-3.1.x86_64 libsasl2-3-debuginfo-2.1.27-1.6.x86_64 libselinux1-debuginfo-2.9-6.1.x86_64 libsqlite3-0-debuginfo-3.29.0-2.2.x86_64 libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64 libsystemd0-debuginfo-243-4.1.x86_64 mozilla-nspr-debuginfo-4.23-1.1.x86_64 mozilla-nss-debuginfo-3.47.1-1.1.x86_64 pam-debuginfo-1.3.1+git20190923.ea78d67-1.3.x86_64 Separate /var detected. /etc on overlayfs detected. Calling zypper install Loading repository data... Reading installed packages... Package 'libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64' not found. Resolving package dependencies... The following 54 NEW packages are going to be installed: audit-debugsource cracklib-debugsource cyrus-sasl-crammd5-debuginfo cyrus-sasl-debuginfo cyrus-sasl-debugsource cyrus-sasl-digestmd5-debuginfo cyrus-sasl-gssapi-debuginfo cyrus-sasl-plain-debuginfo e2fsprogs-debugsource glibc-debuginfo glibc-debugsource icu-debugsource keyutils-debugsource krb5-debuginfo krb5-debugsource libaudit1-debuginfo libcom_err2-debuginfo libcrack2-debuginfo libcrypt1-debuginfo libdb-4_8-debuginfo libdb-4_8-debugsource libeconf-debugsource libeconf0-debuginfo libfreebl3-debuginfo libgcrypt-debugsource libgcrypt20-debuginfo libgpg-error-debugsource libgpg-error0-debuginfo libicu-suse65_1-debuginfo libkeyutils1-debuginfo libldap-2_4-2-debuginfo liblz4-1-debuginfo liblzma5-debuginfo libopenssl1_1-debuginfo libpcre1-debuginfo libsasl2-3-debuginfo libselinux-debugsource libselinux1-debuginfo libsqlite3-0-debuginfo libsystemd0-debuginfo libxcrypt-debugsource lz4-debugsource mozilla-nspr-debuginfo mozilla-nspr-debugsource mozilla-nss-debuginfo mozilla-nss-debugsource openldap2-debugsource openssl-1_1-debugsource pam-debuginfo pam-debugsource pcre-debugsource sqlite3-debugsource systemd-debugsource xz-debugsource The following 24 recommended packages were automatically selected: audit-debugsource cracklib-debugsource cyrus-sasl-debugsource e2fsprogs-debugsource glibc-debugsource icu-debugsource keyutils-debugsource krb5-debugsource libdb-4_8-debugsource libeconf-debugsource libgcrypt-debugsource libgpg-error-debugsource libselinux-debugsource libxcrypt-debugsource lz4-debugsource mozilla-nspr-debugsource mozilla-nss-debugsource openldap2-debugsource openssl-1_1-debugsource pam-debugsource pcre-debugsource sqlite3-debugsource systemd-debugsource xz-debugsource 54 new packages to install. Overall download size: 53.1 MiB. Already cached: 0 B. After the operation, additional 298.5 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Checking for file conflicts: [.......done] Warning: 54 packages had to be excluded from file conflicts check because they are not yet downloaded. Note: Checking for file conflicts requires not installed packages to be downloaded in advance in order to access their file lists. See option '--download-in-advance / --dry-run --download-only' in the zypper manual page for details. Retrieving package audit-debugsource-2.8.4-2.3.x86_64 (1/54), 123.4 KiB (506.8 KiB unpacked) Retrieving: audit-debugsource-2.8.4-2.3.x86_64.rpm [..done (13.2 KiB/s)] ( 1/54) Installing: audit-debugsource-2.8.4-2.3.x86_64 [...........done] Retrieving package cracklib-debugsource-2.9.6-2.14.x86_64 (2/54), 20.8 KiB ( 53.5 KiB unpacked) Retrieving: cracklib-debugsource-2.9.6-2.14.x86_64.rpm [.done (1007 B/s)] ( 2/54) Installing: cracklib-debugsource-2.9.6-2.14.x86_64 [......done] Retrieving package cyrus-sasl-debugsource-2.1.27-1.6.x86_64 (3/54), 186.2 KiB ( 1.0 MiB unpacked) Retrieving: cyrus-sasl-debugsource-2.1.27-1.6.x86_64.rpm [..done (144.5 KiB/s)] ( 3/54) Installing: cyrus-sasl-debugsource-2.1.27-1.6.x86_64 [...........done] Retrieving package e2fsprogs-debugsource-1.45.4-1.2.x86_64 (4/54), 622.5 KiB ( 3.3 MiB unpacked) Retrieving: e2fsprogs-debugsource-1.45.4-1.2.x86_64.rpm [....done (218.4 KiB/s)] ( 4/54) Installing: e2fsprogs-debugsource-1.45.4-1.2.x86_64 [............done] Retrieving package glibc-debugsource-2.30-1.3.x86_64 (5/54), 4.3 MiB ( 33.9 MiB unpacked) Retrieving: glibc-debugsource-2.30-1.3.x86_64.rpm [...........done (419.0 KiB/s)] ( 5/54) Installing: glibc-debugsource-2.30-1.3.x86_64 [............done] Retrieving package icu-debugsource-65.1-1.1.x86_64 (6/54), 2.8 MiB ( 18.3 MiB unpacked) Retrieving: icu-debugsource-65.1-1.1.x86_64.rpm [.........done (352.6 KiB/s)] ( 6/54) Installing: icu-debugsource-65.1-1.1.x86_64 [............done] Retrieving package keyutils-debugsource-1.6-1.3.x86_64 (7/54), 33.3 KiB (120.5 KiB unpacked) Retrieving: keyutils-debugsource-1.6-1.3.x86_64.rpm [.done (1010 B/s)] ( 7/54) Installing: keyutils-debugsource-1.6-1.3.x86_64 [.........done] Retrieving package krb5-debugsource-1.17-4.2.x86_64 (8/54), 1.5 MiB ( 9.7 MiB unpacked) Retrieving: krb5-debugsource-1.17-4.2.x86_64.rpm [.....done (366.2 KiB/s)] ( 8/54) Installing: krb5-debugsource-1.17-4.2.x86_64 [............done] Retrieving package libdb-4_8-debugsource-4.8.30-38.2.x86_64 (9/54), 989.5 KiB ( 5.4 MiB unpacked) Retrieving: libdb-4_8-debugsource-4.8.30-38.2.x86_64.rpm [...done (395.5 KiB/s)] ( 9/54) Installing: libdb-4_8-debugsource-4.8.30-38.2.x86_64 [............done] Retrieving package libeconf-debugsource-0.3.3+git20191028.3ac14ce-1.1.x86_64 (10/54), 27.3 KiB ( 54.5 KiB unpacked) Retrieving: libeconf-debugsource-0.3.3+git20191028.3ac14ce-1.1.x86_64.rpm [.done (988 B/s)] (10/54) Installing: libeconf-debugsource-0.3.3+git20191028.3ac14ce-1.1.x86_64 [..........done] Retrieving package libgcrypt-debugsource-1.8.5-1.3.x86_64 (11/54), 567.6 KiB ( 3.4 MiB unpacked) Retrieving: libgcrypt-debugsource-1.8.5-1.3.x86_64.rpm [..done (212.9 KiB/s)] (11/54) Installing: libgcrypt-debugsource-1.8.5-1.3.x86_64 [............done] Retrieving package libgpg-error-debugsource-1.36-2.2.x86_64 (12/54), 126.9 KiB (602.6 KiB unpacked) Retrieving: libgpg-error-debugsource-1.36-2.2.x86_64.rpm [..done (315.9 KiB/s)] (12/54) Installing: libgpg-error-debugsource-1.36-2.2.x86_64 [............done] Retrieving package libselinux-debugsource-2.9-6.1.x86_64 (13/54), 108.7 KiB (440.0 KiB unpacked) Retrieving: libselinux-debugsource-2.9-6.1.x86_64.rpm [.done] (13/54) Installing: libselinux-debugsource-2.9-6.1.x86_64 [...........done] Retrieving package libxcrypt-debugsource-4.4.3-2.3.x86_64 (14/54), 136.1 KiB (729.4 KiB unpacked) Retrieving: libxcrypt-debugsource-4.4.3-2.3.x86_64.rpm [.done (1007 B/s)] (14/54) Installing: libxcrypt-debugsource-4.4.3-2.3.x86_64 [...........done] Retrieving package lz4-debugsource-1.9.2-1.2.x86_64 (15/54), 107.0 KiB (520.8 KiB unpacked) Retrieving: lz4-debugsource-1.9.2-1.2.x86_64.rpm [..done (107.6 KiB/s)] (15/54) Installing: lz4-debugsource-1.9.2-1.2.x86_64 [...........done] Retrieving package mozilla-nspr-debugsource-4.23-1.1.x86_64 (16/54), 293.8 KiB ( 1.6 MiB unpacked) Retrieving: mozilla-nspr-debugsource-4.23-1.1.x86_64.rpm [..done (187.4 KiB/s)] (16/54) Installing: mozilla-nspr-debugsource-4.23-1.1.x86_64 [............done] Retrieving package mozilla-nss-debugsource-3.47.1-1.1.x86_64 (17/54), 2.3 MiB ( 16.5 MiB unpacked) Retrieving: mozilla-nss-debugsource-3.47.1-1.1.x86_64.rpm [.......done (366.1 KiB/s)] (17/54) Installing: mozilla-nss-debugsource-3.47.1-1.1.x86_64 [............done] Retrieving package openldap2-debugsource-2.4.48-48.4.x86_64 (18/54), 1.2 MiB ( 8.0 MiB unpacked) Retrieving: openldap2-debugsource-2.4.48-48.4.x86_64.rpm [....done (359.5 KiB/s)] (18/54) Installing: openldap2-debugsource-2.4.48-48.4.x86_64 [............done] Retrieving package openssl-1_1-debugsource-1.1.1d-1.1.x86_64 (19/54), 2.0 MiB ( 12.5 MiB unpacked) Retrieving: openssl-1_1-debugsource-1.1.1d-1.1.x86_64.rpm [.....done (391.6 KiB/s)] (19/54) Installing: openssl-1_1-debugsource-1.1.1d-1.1.x86_64 [............done] Retrieving package pam-debugsource-1.3.1+git20190923.ea78d67-1.3.x86_64 (20/54), 211.3 KiB (966.1 KiB unpacked) Retrieving: pam-debugsource-1.3.1+git20190923.ea78d67-1.3.x86_64.rpm [.done (190.0 KiB/s)] (20/54) Installing: pam-debugsource-1.3.1+git20190923.ea78d67-1.3.x86_64 [............done] Retrieving package pcre-debugsource-8.42-3.1.x86_64 (21/54), 347.8 KiB ( 2.2 MiB unpacked) Retrieving: pcre-debugsource-8.42-3.1.x86_64.rpm [..done (262.3 KiB/s)] (21/54) Installing: pcre-debugsource-8.42-3.1.x86_64 [............done] Retrieving package sqlite3-debugsource-3.29.0-2.2.x86_64 (22/54), 1.6 MiB ( 8.6 MiB unpacked) Retrieving: sqlite3-debugsource-3.29.0-2.2.x86_64.rpm [....done (441.4 KiB/s)] (22/54) Installing: sqlite3-debugsource-3.29.0-2.2.x86_64 [............done] Retrieving package systemd-debugsource-243-4.1.x86_64 (23/54), 2.2 MiB ( 15.5 MiB unpacked) Retrieving: systemd-debugsource-243-4.1.x86_64.rpm [......done (457.5 KiB/s)] (23/54) Installing: systemd-debugsource-243-4.1.x86_64 [............done] Retrieving package xz-debugsource-5.2.4-4.3.x86_64 (24/54), 212.6 KiB (983.2 KiB unpacked) Retrieving: xz-debugsource-5.2.4-4.3.x86_64.rpm [..done (236.0 KiB/s)] (24/54) Installing: xz-debugsource-5.2.4-4.3.x86_64 [............done] Retrieving package libaudit1-debuginfo-2.8.4-2.3.x86_64 (25/54), 66.5 KiB (189.7 KiB unpacked) Retrieving: libaudit1-debuginfo-2.8.4-2.3.x86_64.rpm [.done (1009 B/s)] (25/54) Installing: libaudit1-debuginfo-2.8.4-2.3.x86_64 [.........done] Retrieving package libcrack2-debuginfo-2.9.6-2.14.x86_64 (26/54), 31.4 KiB ( 70.6 KiB unpacked) Retrieving: libcrack2-debuginfo-2.9.6-2.14.x86_64.rpm [.done (1008 B/s)] (26/54) Installing: libcrack2-debuginfo-2.9.6-2.14.x86_64 [......done] Retrieving package libsasl2-3-debuginfo-2.1.27-1.6.x86_64 (27/54), 136.4 KiB (456.6 KiB unpacked) Retrieving: libsasl2-3-debuginfo-2.1.27-1.6.x86_64.rpm [..done (41.7 KiB/s)] (27/54) Installing: libsasl2-3-debuginfo-2.1.27-1.6.x86_64 [..........done] Retrieving package cyrus-sasl-plain-debuginfo-2.1.27-1.6.x86_64 (28/54), 34.3 KiB ( 79.3 KiB unpacked) Retrieving: cyrus-sasl-plain-debuginfo-2.1.27-1.6.x86_64.rpm [.done (1001 B/s)] (28/54) Installing: cyrus-sasl-plain-debuginfo-2.1.27-1.6.x86_64 [.......done] Retrieving package cyrus-sasl-gssapi-debuginfo-2.1.27-1.6.x86_64 (29/54), 48.0 KiB (126.8 KiB unpacked) Retrieving: cyrus-sasl-gssapi-debuginfo-2.1.27-1.6.x86_64.rpm [.done] (29/54) Installing: cyrus-sasl-gssapi-debuginfo-2.1.27-1.6.x86_64 [........done] Retrieving package cyrus-sasl-digestmd5-debuginfo-2.1.27-1.6.x86_64 (30/54), 71.3 KiB (218.8 KiB unpacked) Retrieving: cyrus-sasl-digestmd5-debuginfo-2.1.27-1.6.x86_64.rpm [.done (997 B/s)] (30/54) Installing: cyrus-sasl-digestmd5-debuginfo-2.1.27-1.6.x86_64 [..........done] Retrieving package cyrus-sasl-debuginfo-2.1.27-1.6.x86_64 (31/54), 126.6 KiB (549.4 KiB unpacked) Retrieving: cyrus-sasl-debuginfo-2.1.27-1.6.x86_64.rpm [.done (1007 B/s)] (31/54) Installing: cyrus-sasl-debuginfo-2.1.27-1.6.x86_64 [...........done] Retrieving package cyrus-sasl-crammd5-debuginfo-2.1.27-1.6.x86_64 (32/54), 36.9 KiB ( 86.8 KiB unpacked) Retrieving: cyrus-sasl-crammd5-debuginfo-2.1.27-1.6.x86_64.rpm [.done (999 B/s)] (32/54) Installing: cyrus-sasl-crammd5-debuginfo-2.1.27-1.6.x86_64 [.......done] Retrieving package libcom_err2-debuginfo-1.45.4-1.2.x86_64 (33/54), 47.3 KiB (137.7 KiB unpacked) Retrieving: libcom_err2-debuginfo-1.45.4-1.2.x86_64.rpm [..done (1.5 KiB/s)] (33/54) Installing: libcom_err2-debuginfo-1.45.4-1.2.x86_64 [........done] Retrieving package glibc-debuginfo-2.30-1.3.x86_64 (34/54), 6.0 MiB ( 35.6 MiB unpacked) Retrieving: glibc-debuginfo-2.30-1.3.x86_64.rpm [................done (417.9 KiB/s)] (34/54) Installing: glibc-debuginfo-2.30-1.3.x86_64 [............done] Retrieving package libicu-suse65_1-debuginfo-65.1-1.1.x86_64 (35/54), 7.7 MiB ( 32.8 MiB unpacked) Retrieving: libicu-suse65_1-debuginfo-65.1-1.1.x86_64.rpm [..................done (446.9 KiB/s)] (35/54) Installing: libicu-suse65_1-debuginfo-65.1-1.1.x86_64 [............done] Retrieving package libkeyutils1-debuginfo-1.6-1.3.x86_64 (36/54), 21.5 KiB ( 41.0 KiB unpacked) Retrieving: libkeyutils1-debuginfo-1.6-1.3.x86_64.rpm [..done (21.1 KiB/s)] (36/54) Installing: libkeyutils1-debuginfo-1.6-1.3.x86_64 [......done] Retrieving package krb5-debuginfo-1.17-4.2.x86_64 (37/54), 1.9 MiB ( 9.0 MiB unpacked) Retrieving: krb5-debuginfo-1.17-4.2.x86_64.rpm [......done (386.0 KiB/s)] (37/54) Installing: krb5-debuginfo-1.17-4.2.x86_64 [............done] Retrieving package libdb-4_8-debuginfo-4.8.30-38.2.x86_64 (38/54), 3.6 MiB ( 24.4 MiB unpacked) Retrieving: libdb-4_8-debuginfo-4.8.30-38.2.x86_64.rpm [.........done (465.3 KiB/s)] (38/54) Installing: libdb-4_8-debuginfo-4.8.30-38.2.x86_64 [............done] Retrieving package libeconf0-debuginfo-0.3.3+git20191028.3ac14ce-1.1.x86_64 (39/54), 44.1 KiB (114.4 KiB unpacked) Retrieving: libeconf0-debuginfo-0.3.3+git20191028.3ac14ce-1.1.x86_64.rpm [..done (59.6 KiB/s)] (39/54) Installing: libeconf0-debuginfo-0.3.3+git20191028.3ac14ce-1.1.x86_64 [.......done] Retrieving package libgcrypt20-debuginfo-1.8.5-1.3.x86_64 (40/54), 877.4 KiB ( 4.5 MiB unpacked) Retrieving: libgcrypt20-debuginfo-1.8.5-1.3.x86_64.rpm [...done (334.7 KiB/s)] (40/54) Installing: libgcrypt20-debuginfo-1.8.5-1.3.x86_64 [............done] Retrieving package libgpg-error0-debuginfo-1.36-2.2.x86_64 (41/54), 161.8 KiB (555.6 KiB unpacked) Retrieving: libgpg-error0-debuginfo-1.36-2.2.x86_64.rpm [..done (182.4 KiB/s)] (41/54) Installing: libgpg-error0-debuginfo-1.36-2.2.x86_64 [............done] Retrieving package libselinux1-debuginfo-2.9-6.1.x86_64 (42/54), 190.7 KiB (706.6 KiB unpacked) Retrieving: libselinux1-debuginfo-2.9-6.1.x86_64.rpm [.done (80.6 KiB/s)] (42/54) Installing: libselinux1-debuginfo-2.9-6.1.x86_64 [...........done] Retrieving package libcrypt1-debuginfo-4.4.3-2.3.x86_64 (43/54), 158.9 KiB (689.8 KiB unpacked) Retrieving: libcrypt1-debuginfo-4.4.3-2.3.x86_64.rpm [.done (71.4 KiB/s)] (43/54) Installing: libcrypt1-debuginfo-4.4.3-2.3.x86_64 [...........done] Retrieving package liblz4-1-debuginfo-1.9.2-1.2.x86_64 (44/54), 234.6 KiB ( 1.3 MiB unpacked) Retrieving: liblz4-1-debuginfo-1.9.2-1.2.x86_64.rpm [..done (229.4 KiB/s)] (44/54) Installing: liblz4-1-debuginfo-1.9.2-1.2.x86_64 [...........done] Retrieving package mozilla-nspr-debuginfo-4.23-1.1.x86_64 (45/54), 330.6 KiB ( 1.3 MiB unpacked) Retrieving: mozilla-nspr-debuginfo-4.23-1.1.x86_64.rpm [..done (218.7 KiB/s)] (45/54) Installing: mozilla-nspr-debuginfo-4.23-1.1.x86_64 [............done] Retrieving package mozilla-nss-debuginfo-3.47.1-1.1.x86_64 (46/54), 2.0 MiB ( 9.8 MiB unpacked) Retrieving: mozilla-nss-debuginfo-3.47.1-1.1.x86_64.rpm [......done (403.3 KiB/s)] (46/54) Installing: mozilla-nss-debuginfo-3.47.1-1.1.x86_64 [............done] Retrieving package libfreebl3-debuginfo-3.47.1-1.1.x86_64 (47/54), 515.0 KiB ( 2.3 MiB unpacked) Retrieving: libfreebl3-debuginfo-3.47.1-1.1.x86_64.rpm [...done (331.4 KiB/s)] (47/54) Installing: libfreebl3-debuginfo-3.47.1-1.1.x86_64 [............done] Retrieving package libldap-2_4-2-debuginfo-2.4.48-48.4.x86_64 (48/54), 375.3 KiB ( 1.7 MiB unpacked) Retrieving: libldap-2_4-2-debuginfo-2.4.48-48.4.x86_64.rpm [..done (265.8 KiB/s)] (48/54) Installing: libldap-2_4-2-debuginfo-2.4.48-48.4.x86_64 [............done] Retrieving package libopenssl1_1-debuginfo-1.1.1d-1.1.x86_64 (49/54), 2.7 MiB ( 12.7 MiB unpacked) Retrieving: libopenssl1_1-debuginfo-1.1.1d-1.1.x86_64.rpm [.......done (449.1 KiB/s)] (49/54) Installing: libopenssl1_1-debuginfo-1.1.1d-1.1.x86_64 [............done] Retrieving package pam-debuginfo-1.3.1+git20190923.ea78d67-1.3.x86_64 (50/54), 530.4 KiB ( 2.0 MiB unpacked) Retrieving: pam-debuginfo-1.3.1+git20190923.ea78d67-1.3.x86_64.rpm [...done (322.1 KiB/s)] (50/54) Installing: pam-debuginfo-1.3.1+git20190923.ea78d67-1.3.x86_64 [............done] Retrieving package libpcre1-debuginfo-8.42-3.1.x86_64 (51/54), 461.6 KiB ( 2.0 MiB unpacked) Retrieving: libpcre1-debuginfo-8.42-3.1.x86_64.rpm [..done (321.1 KiB/s)] (51/54) Installing: libpcre1-debuginfo-8.42-3.1.x86_64 [............done] Retrieving package libsqlite3-0-debuginfo-3.29.0-2.2.x86_64 (52/54), 1.6 MiB ( 5.6 MiB unpacked) Retrieving: libsqlite3-0-debuginfo-3.29.0-2.2.x86_64.rpm [......done (320.8 KiB/s)] (52/54) Installing: libsqlite3-0-debuginfo-3.29.0-2.2.x86_64 [............done] Retrieving package libsystemd0-debuginfo-243-4.1.x86_64 (53/54), 937.9 KiB ( 3.4 MiB unpacked) Retrieving: libsystemd0-debuginfo-243-4.1.x86_64.rpm [...done (371.9 KiB/s)] (53/54) Installing: libsystemd0-debuginfo-243-4.1.x86_64 [............done] Retrieving package liblzma5-debuginfo-5.2.4-4.3.x86_64 (54/54), 383.7 KiB ( 1.3 MiB unpacked) Retrieving: liblzma5-debuginfo-5.2.4-4.3.x86_64.rpm [...done (267.1 KiB/s)] (54/54) Installing: liblzma5-debuginfo-5.2.4-4.3.x86_64 [............done] Installation has completed with error. ERROR: zypper install on /tmp/tmp.XXVSzekuha failed with exit code 104! Removing snapshot #8... Removing overlay directory /var/lib/overlay/8... transactional-update finished -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c1 Alynx Zhou <alynx.zhou@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com Component|Upgrade Problems |libzypp Assignee|bnc-team-screening@forge.pr |zypp-maintainers@suse.de |ovo.novell.com | QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #1 from Alynx Zhou <alynx.zhou@suse.com> --- Hi, it looks zypper failed, please take a look at this, thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c2 --- Comment #2 from William Brown <william.brown@suse.com> --- If zypper fails when in a transaction, how am I meant to investigate after the environment is rolled back? I'm suggesting that when zypper DOES fail like this that you are prompted to access a shell in the transaction before it's rolled back so that you can investigate what the error was? Thanks, -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c3 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |kukuk@suse.com Resolution|--- |INVALID --- Comment #3 from Thorsten Kukuk <kukuk@suse.com> --- 1. of course the log files do exist and are available in the system, they are not deleted. And if you want to have a shell, use the option to start a shell for debugging. Your claims in this regard are wrong. 2. zypper is giving you all informations to solve the problem. Instead of pasting the long output, you should have read it. man zypper -> you try to install a package which does not exist, and zypper is even telling you that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c4 --- Comment #4 from William Brown <william.brown@suse.com> --- (In reply to Thorsten Kukuk from comment #3)
1. of course the log files do exist and are available in the system, they are not deleted. And if you want to have a shell, use the option to start a shell for debugging. Your claims in this regard are wrong.
But the shell won't be in the environment where the "error" happened, it will be a new snapshot yes?
2. zypper is giving you all informations to solve the problem. Instead of pasting the long output, you should have read it.
man zypper -> you try to install a package which does not exist, and zypper is even telling you that.
gdb suggested this command to install the debug info, so there is something gdb knows about these packages that doesn't line up when zypper attempts the download then. I'm just doing what the system is telling me here. For the record, I actually totally missed that error on multiple reads because there is so much information overload, and the error condition is listed *early* in the process, rather than being declared at the end. The error condition also doesn't include the important word "error" in it, making it further able to be overlooked. A better structure would be to move the relevant errors to the end of the output, near "Installation has completed with error." to help make the errors easier and accessible to spot - generally without "command" output I would expect anything "before" this point to be working for a package manager. IE: (54/54) Installing: liblzma5-debuginfo-5.2.4-4.3.x86_64 [............done] Installation has completed with error. ERROR: Package 'libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64' not found. ERROR: zypper install on /tmp/tmp.XXVSzekuha failed with exit code 104! Removing snapshot #8... Removing overlay directory /var/lib/overlay/8... transactional-update finished This output would have been much more helpful than the cryptic "script failed with error" code. So I think there are some genuine improvements to be made here for this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c5 --- Comment #5 from William Brown <william.brown@suse.com> --- Worth also highlighting that in this case gdb has given me a set of debuginfo from metadata that clearly isn't able to be satisfied, so that seems like an issue as well ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c6 --- Comment #6 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to William Brown from comment #4)
(In reply to Thorsten Kukuk from comment #3)
1. of course the log files do exist and are available in the system, they are not deleted. And if you want to have a shell, use the option to start a shell for debugging. Your claims in this regard are wrong.
But the shell won't be in the environment where the "error" happened, it will be a new snapshot yes?
If you call the same command again with the shell option, it will be the same snapshot.
2. zypper is giving you all informations to solve the problem. Instead of pasting the long output, you should have read it.
man zypper -> you try to install a package which does not exist, and zypper is even telling you that.
gdb suggested this command to install the debug info, so there is something gdb knows about these packages that doesn't line up when zypper attempts the download then. I'm just doing what the system is telling me here.
And zypper is telling you, that a package you want to install does not exist and quits with an error code.
For the record, I actually totally missed that error on multiple reads because there is so much information overload, and the error condition is listed *early* in the process, rather than being declared at the end.
The end contains a clear statement: zypper exits with an error code and the error code is mentioned. Exactly what you did request is printed at the end.
So I think there are some genuine improvements to be made here for this.
If you read the the error code and what it means, you know for what you have to search in the output. The experience is: overlading the end with too much informatons does not help, there will be exact the same bug reports as yours, as people don't read as they claims it's too much informations. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158478 http://bugzilla.suse.com/show_bug.cgi?id=1158478#c7 --- Comment #7 from William Brown <william.brown@suse.com> --- (In reply to Thorsten Kukuk from comment #6)
(In reply to William Brown from comment #4)
(In reply to Thorsten Kukuk from comment #3)
1. of course the log files do exist and are available in the system, they are not deleted. And if you want to have a shell, use the option to start a shell for debugging. Your claims in this regard are wrong.
But the shell won't be in the environment where the "error" happened, it will be a new snapshot yes?
If you call the same command again with the shell option, it will be the same snapshot.
That's not clear as a 'user experience', and should be indicated that this behaviour does exist. An important aspect of human psychology and interaction is discoverability, making things in a UI able to be found. So I would suggest: HINT: To access the environment where the error occured, run 'transactional-update shell' This makes it clear and known to people that this feature exists - I certainly had no idea until you just told me then, which likely means no one else knows either. In other words, if people don't know it exists, does the feature exist at all?
2. zypper is giving you all informations to solve the problem. Instead of pasting the long output, you should have read it.
man zypper -> you try to install a package which does not exist, and zypper is even telling you that.
gdb suggested this command to install the debug info, so there is something gdb knows about these packages that doesn't line up when zypper attempts the download then. I'm just doing what the system is telling me here.
And zypper is telling you, that a package you want to install does not exist and quits with an error code.
For the record, I actually totally missed that error on multiple reads because there is so much information overload, and the error condition is listed *early* in the process, rather than being declared at the end.
The end contains a clear statement: zypper exits with an error code and the error code is mentioned. Exactly what you did request is printed at the end.
Error codes don't communicate what happened, because I'm not a computer :(
So I think there are some genuine improvements to be made here for this.
If you read the the error code and what it means, you know for what you have to search in the output. The experience is: overlading the end with too much informatons does not help, there will be exact the same bug reports as yours, as people don't read as they claims it's too much informations.
I'm not suggesting that you "overload" as much as "refine" *where* the error information is to improve visibility and locality of that. Because the error message was in the first 10% of the output, people will not be looking there (and even if they are, the error lacks distinguishing markers to prompt that it's there). These bug reports come from people like me because the user interaction of the experience could be improved - rather than looking at the symptom (the existence of the error, the bug report), you should be asking why someone with a lot of experience was able to (rather easily) overlook this error and raise a false bug - this implies to me that a communication and user interaction problem exists between the tool and the user which is causing them to overlook things. Which is why I will suggest again that the error messages are: * defined as "error" rather than just a "not found" with no identification that it's the cause of the error. * That "errors" are collected to a single, localised location at the end of the output to aid isolation of the issue * Communication about investigative steps and features that exist should also be communicated I believe as already mentioned, the output below already greatly would improve the "experience" ... Lots of output goes here ... (54/54) Installing: liblzma5-debuginfo-5.2.4-4.3.x86_64 [............done] Installation has completed with error. ERROR: Package 'libsvrcore0-debuginfo-1.4.2.4~git0.c881f6ec0-82.1.x86_64' not found. ERROR: zypper install on /tmp/tmp.XXVSzekuha failed with exit code 104! HINT: To access the environment where the error occured, run 'transactional-update shell' Removing snapshot #8... Removing overlay directory /var/lib/overlay/8... transactional-update finished If the output looked like that, I would never have reported this bug at all because I would have been given the information needed and the agency and tools to know how to investigate. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com