[Bug 1093033] New: [Build 20180511] openQA test fails in consoletest_setup, curl failed with Could not connect to Server
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 Bug ID: 1093033 Summary: [Build 20180511] openQA test fails in consoletest_setup, curl failed with Could not connect to Server Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC URL: https://openqa.opensuse.org/tests/675265/modules/conso letest_setup/steps/29 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: normand@linux.vnet.ibm.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- The consoletest_setup script is failing because curl is not able to access the ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64-lvm@ppc64 fails in [consoletest_setup](https://openqa.opensuse.org/tests/675265/modules/consoletest_setup/steps/29) ## Reproducible Fails since (at least) Build [20180427](https://openqa.opensuse.org/tests/665973) ## Expected result Last good: [20180425](https://openqa.opensuse.org/tests/663532) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?machine=ppc64&arch=ppc64&test=lvm&flavor=DVD&distri=opensuse&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c1 --- Comment #1 from Michel Normand <normand@linux.vnet.ibm.com> --- Seems to be specific to ppc64 (BE) as no such failure for ppc64le: https://openqa.opensuse.org/tests/675245#step/consoletest_setup/29 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c2 --- Comment #2 from Michel Normand <normand@linux.vnet.ibm.com> --- May be related to "systemd[1]: Failed to start Authorisation Manager" as per https://openqa.opensuse.org/tests/675265#step/consoletest_setup/53 How to continue investigation ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c3 --- Comment #3 from Michel Normand <normand@linux.vnet.ibm.com> --- Created attachment 769987 --> http://bugzilla.opensuse.org/attachment.cgi?id=769987&action=edit polkit_service_segv.png in attached png file, I captured the output of systemctl status polkit.service; that reports a SEGV error cause. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c6 Michel Normand <normand@linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjorn.lie@gmail.com Flags| |needinfo?(bjorn.lie@gmail.c | |om) --- Comment #6 from Michel Normand <normand@linux.vnet.ibm.com> --- Bjorn as owner of the last change 0.114, Do you have a suggestion to capture more data to investigate why polkit.service failed to start: === [michel@twppc64be:~] $sudo systemctl status polkit.service polkit.service - Authorization Manager Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: disabled) Active: failed (Result: signal) since Tue 2018-05-29 18:21:23 CEST; 2min 50s ago Docs: man:polkit(8) Process: 1863 ExecStart=/usr/lib/polkit-1/polkitd --no-debug (code=killed, signal=SEGV) Main PID: 1863 (code=killed, signal=SEGV) mai 29 18:21:23 twppc64be systemd[1]: Starting Authorization Manager... mai 29 18:21:23 twppc64be polkitd[1863]: Started polkitd version 0.114 mai 29 18:21:23 twppc64be systemd[1]: polkit.service: Main process exited, code=killed, status=11/SEGV mai 29 18:21:23 twppc64be systemd[1]: polkit.service: Failed with result 'signal'. mai 29 18:21:23 twppc64be systemd[1]: Failed to start Authorization Manager. [michel@twppc64be:~] $sudo systemctl restart polkit Job for polkit.service failed because a fatal signal was delivered to the control process. See "systemctl status polkit.service" and "journalctl -xe" for details. === -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c7 --- Comment #7 from Michel Normand <normand@linux.vnet.ibm.com> --- Created attachment 771804 --> http://bugzilla.opensuse.org/attachment.cgi?id=771804&action=edit mozjs52-spec_ppc64.patch Able to retrieve backtrace with gdb, as detailed below. This is pointing to a SEGV in libmozjs52. I did a trial with a mozjs52.spec change; after build and install I was able to start with no error the polkitd. === gdb /usr/lib/polkit-1/polkitd ... Thread 1 "polkitd" received signal SIGSEGV, Segmentation fault. js::detail::MutexImpl::lock (this=0x188) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/threading/posix/MutexImpl.cpp:70 70 TRY_CALL_PTHREADS(pthread_mutex_lock(&platformData()->ptMutex), (gdb) bt #0 js::detail::MutexImpl::lock (this=0x188) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/threading/posix/MutexImpl.cpp:70 #1 0x00007ffff66c719c in js::LockGuard<js::Mutex>::LockGuard (aLock=..., this=<synthetic pointer>) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/threading/LockGuard.h:25 #2 js::AutoLockHelperThreadState::AutoLockHelperThreadState (this=<synthetic pointer>) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/vm/HelperThreads.h:511 #3 js::GlobalHelperThreadState::ensureInitialized (this=0x0) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/vm/HelperThreads.cpp:704 #4 0x00007ffff6722774 in JSRuntime::init (this=0x1000c9ec0, maxbytes=<optimized out>, maxNurseryBytes=<optimized out>) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/vm/Runtime.cpp:292 #5 0x00007ffff65339c0 in JSContext::init (maxNurseryBytes=16777216, maxBytes=8388608, this=0x1000c9cc0) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/jscntxt.cpp:96 #6 js::NewContext (parentRuntime=0x0, maxNurseryBytes=16777216, maxBytes=8388608) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/jscntxt.cpp:112 #7 JS_NewContext (maxbytes=<optimized out>, maxNurseryBytes=<optimized out>, parentContext=<optimized out>) at /usr/src/debug/mozjs52-52.6.0-3.1.ppc64/js/src/jsapi.cpp:476 #8 0x0000000100012ebc in polkit_backend_js_authority_constructed (object=0x100087900) at polkitbackendjsauthority.cpp:453 #9 0x00007ffff7c06b10 in ?? () from /usr/lib64/libgobject-2.0.so.0 #10 0x00007ffff7c08a10 in .g_object_new_with_properties () from /usr/lib64/libgobject-2.0.so.0 #11 0x00007ffff7c0952c in .g_object_new () from /usr/lib64/libgobject-2.0.so.0 #12 0x0000000100010348 in polkit_backend_authority_get () at polkitbackendauthority.c:1434 #13 0x000000010000e0b8 in main (argc=<optimized out>, argv=<optimized out>) at polkitd.c:219 === -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c9 --- Comment #9 from Michel Normand <normand@linux.vnet.ibm.com> --- (In reply to Marcus Meissner from comment #8)
Wolfgang, can you add this patch to mozjs52?
I just create an osc sr#613045 with mimimal patch not yet build complete in OBS, but validated locally by successfull start of polkitd. https://build.opensuse.org/request/show/613045 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c10 Wolfgang Rosenauer <wolfgang@rosenauer.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #10 from Wolfgang Rosenauer <wolfgang@rosenauer.org> --- thanks, waiting for Factory acceptance -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c12 --- Comment #12 from Michel Normand <normand@linux.vnet.ibm.com> --- FYIO, need a _constraints change to avoid transient OBS build failure, tracked by another PR https://build.opensuse.org/request/show/617547 before to be able to confirm correction of this bug. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c13 --- Comment #13 from Michel Normand <normand@linux.vnet.ibm.com> --- still waiting for the _constraint change to reach TW, as today still in Staging:E with PR https://build.opensuse.org/request/show/617548 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093033 http://bugzilla.opensuse.org/show_bug.cgi?id=1093033#c14 --- Comment #14 from Michel Normand <normand@linux.vnet.ibm.com> --- (In reply to Michel Normand from comment #13)
still waiting for the _constraint change to reach TW, as today still in Staging:E with PR https://build.opensuse.org/request/show/617548
moved from Staging: to Staging:F and still waiting :( https://build.opensuse.org/project/show/openSUSE:Factory:Staging:F -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com