I believe this was an eventlet issue. Given age, I'm going to move this
to invalid. If it is observed again, please file detailed new bug, or
reopen this one.
** Changed in: ironic
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch se
Indeed, and unfortunately it seems like I've been able to identify the
root cause which is still present in 2.90. What changed, we're no longer
seeing a segfault which was the tell-tale sign we were looking for, but
instead we just see it quietly exit with no trace. This led me to
getting a setup w
https://lists.thekelleys.org.uk/pipermail/dnsmasq-
discuss/2023q2/017134.html and original post relates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2026757
Title:
dnsm
Took some effort, but I've managed to capture a core dump
root@np0036907443:/opt/stack/dnsmasq# coredumpctl info 328293
PID: 328293 (dnsmasq)
UID: 65534 (nobody)
GID: 30 (dip)
Signal: 6 (ABRT)
Timestamp: Fri 2024-03-01 16:19:37 UTC (2min 34s ago)
Com
** Attachment added: "coredumpctl info output for 2.90 from Ubuntu Jammy"
https://bugs.launchpad.net/ironic/+bug/2026757/+attachment/5751229/+files/dnsmasq-jammy-2.90-package-coredumpctl_info
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Attachment added: "core dump file from 2.90 on Ubuntu Jammy"
https://bugs.launchpad.net/ironic/+bug/2026757/+attachment/5751255/+files/dnsmasq-jammy-2.90-package-coredumpctl_dump.core
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Listing... Done
dnsmasq-base-lua/unknown,unknown 2.90-0ubuntu0.22.04.1 amd64
dnsmasq-base/unknown,unknown,now 2.90-0ubuntu0.22.04.1 amd64
[installed,automatic]
dnsmasq-utils/unknown,unknown,now 2.90-0ubuntu0.22.04.1 amd64 [installed]
dnsmasq/unknown,unknown,now 2.90-0ubuntu0.22.04.1 all [installed
** Attachment added: "core dump file from 2.90 on Ubuntu Jammy"
https://bugs.launchpad.net/ironic/+bug/2026757/+attachment/5751256/+files/dnsmasq-jammy-2.90-package-coredumpctl_dump.core
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
So, trying to at least get symbols for the dnsmasq binary has been
largely unsucessful, so i build v2.90 from dnsmasq git, and here is what
I got:
Found module linux-vdso.so.1 with build-id:
975d8292a19f8c241322ae7eb151b63f4f01d8e2
Found module ld-linux-x86-64.so.2
This is from v2.90 from the ubuntu packaging:
Stack trace of thread 34:
#0 0x7f21c90499fc pthread_kill (libc.so.6 + 0x969fc)
#1 0x7f21c8ff5476 raise (libc.so.6 + 0x42476)
#2 0x7f21c8fdb7f3 abort (libc.so.6 + 0x287f3
Petr messaged me and suggested maybe we try using rr to capture the
execution and failure to aid in debugging, unfortunately the cpu
performance events are unavailable on the machine I'm attempting
reproduction on.
I did manage to spend a little time the last two days adding some
additional debug
So, I tossed the change because I wanted to try and produce the failure.
I tried to re-create it, but didn't have the best of luck which makes me
think I masked the issue a bit too well. Playing with valgrind has me
questioning reality:
==1119241== ERROR SUMMARY: 9 errors from 6 contexts (suppress
Yes, still happens with 2.90-0ubuntu0.22.04.1.
It is a problem with the upstream code as far as I can tell from
dnsmasq, not the ubuntu package build itself.
Message: Process 1671294 (dnsmasq) of user 65534 dumped core.
Found module linux-vdso.so.1 with bui
Public bug reported:
The Ironic project's CI has been having major blocking issues moving to
utilizing Ubuntu Jammy and with some investigation we were able to
isolate the issues down to the dhcp updates causing dnsmasq to crash on
Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds sim
Greetings Yatin!
So, the failure appears to be rooted in ipxe failing to get the complete
set of data from the server. My guess is that is something to do with
spanning tree as iPXE for ubuntu has also changed it's behavior. My
feeling is this is rooted with some spanning tree behavior, which we
m
@yatin, It appears, with your newest patch to our CI jobs in Ironic, in
order to just use pure upsteam source (Thanks by the way!), that the CI
job failed in a specific scenario where we're attempting to validate we
can boot an ISO via iPXE. That being said, the logs indicate we made it
far past dh
@yatin, Also, on the prior change, the most recent run failed somewhere
rooted with libvirt or uefi firmware booting. The same exact scenario
test worked in your version revision. That specific test is not doing
network booting, but it got the DHCP addresses as I would expect. What
seemingly failed
17 matches
Mail list logo
