October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1049186] python-3.6 packages do not build reproducibly
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1049186 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:12711:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1050653] python3.6 should provide python3-typing (python-Sphinx concerned)
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1050653 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:12711:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 917607] package summary and description for python3 and python3-base are nearly the same
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=917607 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:12711:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1097748] devel:languages:nodejs/nodejs8: installing nodejs8 also installs nodejs9 and npm9 (instead of npm8)
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1097748 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:12711:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1145193] activating chrony-wait.service by default delays booting without network for 10 minutes
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c62 --- Comment #62 from ravas mi <ravas(a)tuta.io> --- It looks like NetworkManager does DNS related things _after_ chrony starts. I see that "Could not resolve address of initstepslew server <URL>." directly follows chrony starting, and then shortly after that I see > NetworkManager[1098]: <info> [1569905050.7145] dns-mgr[0x555d0a1ca210]: init: dns=default,systemd-resolved rc-manager=netconfig It seems like if we could ensure that DNS stuff happens prior to chrony starting, then "initstepslew" could replace chrony-wait, assuming "initstepslew" accepts a pool's URL (i.e. 3.opensuse.pool.ntp.org). That said, disabling chrony-wait and using "makestep 0.1 1" seems to work fine for my purposes, but then I don't know if I even benefit from the stepping. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1151291] [Build 13.30] openQA test fails in await_install: YaST breaks network during install
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1151291 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1145193] activating chrony-wait.service by default delays booting without network for 10 minutes
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c61 --- Comment #61 from ravas mi <ravas(a)tuta.io> --- >> "waitsync" has nothing to do with the question of stepping or slewing... > > "waitsync" seemingly only uses slewing. After looking at the journal I see that with chrony-wait enabled and "makestep 0.1 1" it takes around 14 seconds to select a source and then it steps. I misinterpreted the delay as slewing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1063638 http://bugzilla.suse.com/show_bug.cgi?id=1063638#c214 --- Comment #214 from Oliver Kurz <okurz(a)suse.com> --- It's hard for me to verify the solution as there are remaining parts in this bug cluster. I would appreciate if the bug assignees can look into https://bugzilla.suse.com/show_bug.cgi?id=1088010 for example to prevent concurrent balance+scrub which is hindering performance a lot as well, as it seems. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1145193] activating chrony-wait.service by default delays booting without network for 10 minutes
by bugzilla_noreply＠novell.com 01 Oct '19

01 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1145193 http://bugzilla.suse.com/show_bug.cgi?id=1145193#c60 --- Comment #60 from ravas mi <ravas(a)tuta.io> --- (In reply to Reinhard Max from comment #59) > (In reply to ravas mi from comment #57) > > I don't understand the point of "waitsync" on boot. Why do we need slewing > > at the first clock update? > > "waitsync" has nothing to do with the question of stepping or slewing, it > only makes chronyc block until either > > a) chronyd has synchronized the time > (regardless of the method it uses to get there) > > or > > b) the timeout has been reached. > "waitsync" seemingly only uses slewing. I meant that "makestep" seems like an alternative to chrony-wait/waitsync/slewing. > > Why not use "makestep" to immediately make the correction? > > We already have that in chrony.conf by default (as you already noticed > yourself in comment 51), but if there is no network during boot chronyd > cannot synchronize the time, even if you allow it to step. > > It might indeed be worthwile to think about moving from "makestep" to > "initstepslew", but that's irrelevant for the "no network at boot" issue > we're discussing here. It seems relevant. If either "makestep" or "initstepslew" fail to connect to an NTP server, then the boot continues. Why can't "makestep 0.1 1" replace the chrony-wait service? In testing, if I use "initstepslew" with a URL, then it always produces "Could not resolve address of initstepslew server <URL>." The documentation's example uses URLs, and if I use the IP of the server instead, it works -- implying the DNS isn't working at that point. If we could solve that, then "initstepslew" seems like it could also replace chrony-wait. -- You are receiving this mail because: You are on the CC list for the bug.

1 0