February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 423007] zypper: wrapping usage texts
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=423007 http://bugzilla.suse.com/show_bug.cgi?id=423007#c11 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ma(a)suse.com) | --- Comment #11 from Michael Andres <ma(a)suse.com> --- I think c#10 explains it. In the past we had monolithic command help texts which were in fact fix formated by the translators. We slowly migrated them and menawhile all command help texts are dynamically formated according to the terminal width (but at most 100 columns). So you can red it even with 40 columns: > Command options: > > -t, --type <TYPE> Type of package > (package, patch, > pattern, product). > -n, --name Select packages by > plain name, not by > capability. Default: > false > -C, --capability Select packages > solely by > capability. Default: > false -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 916587] zypper does not update package when used with -C
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=916587 http://bugzilla.suse.com/show_bug.cgi?id=916587#c3 --- Comment #3 from Michael Andres <ma(a)suse.com> --- The issue will vanish once zypper is completely solver-job based. In the current code stream zypper would need pick the candidate, what we don't want. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124088] /bin/dracut-emergency refers to /dev/consoles (with an s)
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124088 http://bugzilla.suse.com/show_bug.cgi?id=1124088#c4 Daniel Molkentin <daniel.molkentin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfasheh(a)suse.com --- Comment #4 from Daniel Molkentin <daniel.molkentin(a)suse.com> --- *** Bug 1124394 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124451] New: Calamares: Boost.Python error in job "machineid"
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124451 Bug ID: 1124451 Summary: Calamares: Boost.Python error in job "machineid" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 796101 --> http://bugzilla.opensuse.org/attachment.cgi?id=796101&action=edit log After fixing https://bugzilla.opensuse.org/show_bug.cgi?id=1124423 new bug found: 12:37:37 [0]: Installation failed: 12:37:37 [0]: - message: "Boost.Python error in job \"machineid\"." 12:37:37 [0]: - details: "<div><strong><class 'subprocess.CalledProcessError'></strong></div><div>Command 'systemd-machine-id-setup' returned non-zero exit status 127.</div><div>Traceback:</div><div><pre> File "/usr/lib64/calamares/modules/machineid/main.py", line 57, in run\n check_target_env_call("systemd-machine-id-setup")\n\n File "<string>", line 2, in <module>\n</pre></div>" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1116675] sendmail system service wrongly Aliased to .target unit
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1116675 http://bugzilla.suse.com/show_bug.cgi?id=1116675#c6 --- Comment #6 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Ednilson Miura from comment #4) > While testing S:M:10026:18227 (sendmail update). The issue still exists > after the update: > IMHO it is fixed. The previous link was done by the old package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 916587] zypper does not update package when used with -C
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=916587 http://bugzilla.suse.com/show_bug.cgi?id=916587#c2 Michael Schröder <mls(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls(a)suse.com --- Comment #2 from Michael Schröder <mls(a)suse.com> --- Why would that be a problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123982] New: multipathd fails to create multipaths on iscsi
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123982 Bug ID: 1123982 Summary: multipathd fails to create multipaths on iscsi Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After a recent tumbleweed update, multipathd fails to setup multipaths on iscsi devices. The logs show the following error: Jan 30 17:02:18 santana multipathd[553]: --------start up-------- Jan 30 17:02:18 santana multipathd[553]: read /etc/multipath.conf Jan 30 17:02:18 santana multipathd[553]: path checkers start up Jan 30 17:02:18 santana multipathd[553]: ST3160021A_5JS2B44K: ignoring map Jan 30 17:02:23 santana multipathd[553]: 3600a098000aad1e300001f9f5c4e9add: failed in domap for addition of new path sdc Jan 30 17:02:23 santana multipathd[553]: uevent trigger error Jan 30 17:02:24 santana multipathd[553]: 3600a098000aad73f00002f965c4e9bf0: failed in domap for addition of new path sdb Jan 30 17:02:24 santana multipathd[553]: uevent trigger error Jan 30 17:02:24 santana multipathd[553]: 3600c0ff000daac373699135601000000: failed in domap for addition of new path sde Jan 30 17:02:24 santana multipathd[553]: uevent trigger error Jan 30 17:02:24 santana multipathd[553]: 3600c0ff000daac37f7199a5b01000000: failed in domap for addition of new path sdd Jan 30 17:02:24 santana multipathd[553]: uevent trigger error --< multipath -v3 shows: --> Feb 01 12:21:59 | sdc: udev property ID_WWN whitelisted Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: user_friendly_names = no (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: alias = 3600a098000aad1e300001f9f5c4e9add (setting: default to WWID) Feb 01 12:21:59 | sdc: ownership set to 3600a098000aad1e300001f9f5c4e9add Feb 01 12:21:59 | sdc: rdac state = up Feb 01 12:21:59 | sdc: reported target port group is 0 Feb 01 12:21:59 | sdc: aas = 00 [active/optimized] Feb 01 12:21:59 | sdg: ownership set to 3600a098000aad1e300001f9f5c4e9add Feb 01 12:21:59 | sdg: rdac state = up Feb 01 12:21:59 | sdg: reported target port group is 1 Feb 01 12:21:59 | sdg: aas = 01 [active/non-optimized] Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: failback = "immediate" (setting: storage device configuration) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: path_grouping_policy = group_by_prio (setting: storage device configuration) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: path_selector = "service-time 0" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: no_path_retry = 30 (setting: storage device configuration) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: retain_attached_hw_handler = yes (setting: implied in kernel >= 4.3.0) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: skip_kpartx = no (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: features = "2 pg_init_retries 50" (setting: storage device configuration) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: hardware_handler = "1 alua" (setting: retained by kernel driver) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: rr_weight = "uniform" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: minio = 1 (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: fast_io_fail_tmo = 5 (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: deferred_remove = no (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: delay_watch_checks = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: delay_wait_checks = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: marginal_path_err_sample_time = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: marginal_path_err_rate_threshold = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: marginal_path_err_recheck_gap_time = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: marginal_path_double_failed_time = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: san_path_err_threshold = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: san_path_err_forget_rate = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: san_path_err_recovery_time = "no" (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: skip_kpartx = no (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: ghost_delay = "no" (setting: multipath.conf defaults/devices section) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: flush_on_last_del = no (setting: multipath internal) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: update dev_loss_tmo to 150 Feb 01 12:21:59 | sdc: ignoring dev_loss_tmo on iSCSI Feb 01 12:21:59 | sdg: ignoring dev_loss_tmo on iSCSI Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: set ACT_CREATE (map does not exist) Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: failed to load map, error 22 Feb 01 12:21:59 | Initialized new file [/dev/shm/multipath/failed_wwids/.lock] Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: domap (0) failure for create/reload map Feb 01 12:21:59 | 3600a098000aad1e300001f9f5c4e9add: ignoring map Feb 01 12:21:59 | sdc: orphan path, map removed internally Feb 01 12:21:59 | sdg: orphan path, map removed internally --< -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 940538] %posttrans script execution lacks progress indicator
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=940538 http://bugzilla.novell.com/show_bug.cgi?id=940538#c3 Benjamin Zeller <bzeller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |bzeller(a)suse.com Resolution|--- |FIXED --- Comment #3 from Benjamin Zeller <bzeller(a)suse.com> --- This was already implemented in libzypp and zypper -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123245] New: After zypper dup from Leap:15.0 to Tumbleweed boot fails intermittently failed to find grub_efi_allocate_fixed
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1123245 Bug ID: 1123245 Summary: After zypper dup from Leap:15.0 to Tumbleweed boot fails intermittently failed to find grub_efi_allocate_fixed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: davejplater(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I used zypper dup from Leap:15.0 to update to the same Tumbleweed snapshot on an HP pavilion laptop born mid 2018. I resized the windows partition and installed Leap:15.0 on it. I set it up to boot from grub, which I use to boot windows 10 (mainly for netflix download and play later) the boot system has survived monthly windows updates without a problem. The first reboot after zypper dup to Tumbleweed failed with "failed to find grub_efi_allocate_fixed" I fixed this by booting installed system from an installation usb stick and running yast2 bootloader but firstly after running yast bootloader and changing the boot menu timeout fro 9 to 8 it went wrong again, fixed it with boot installed system then running yast bootloader again. After a Windows 10 driver update - same problem again. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1124423] New: Calamares installer fails with "Sudoers dir is not writable"
by bugzilla_noreply＠novell.com 06 Feb '19

06 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124423 Bug ID: 1124423 Summary: Calamares installer fails with "Sudoers dir is not writable" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 796084 --> http://bugzilla.opensuse.org/attachment.cgi?id=796084&action=edit screenshot calamares-3.1.10 for openSUSE Leap 15.0 and calamares-3.1.11 for openSUSE Tumbleweed fails at copying LiveCD content to new system. Error: "Sudoers dir is not writable" calamares RPM source contains 3.1.4-unpackfs.conf.patch that suggest copying from source: "/read-only". In latest medium (generated by KIWI-ng) there is no such directory anymore. Seems that KIWI-ng generate LiveCD ISO images differently than KIWI. -- You are receiving this mail because: You are on the CC list for the bug.

1 9