The bug description says "dnsmasq on Ubuntu Jammy/Lunar crashes [...]",
but IIUC it's actually only the Jammy one that crashes (the lunar-on-
jammy one maybe has other issues, but doesn't exhibit the crash). Am I
right? In this case please update the bug description accordingly.
Thanks!
Edit: I
Hello, I verified that Sergio's PPA contains the candidate upstream
patch (upstream commit d290630d31f4517ab26392d00753d1397f9a4114). If the
crash is still happening that probably wasn't the issue after all.
I see two possible ways forward here. One is classic git based
debugging:
1. compile
@Sergio so i still see[1][2] those segfaults with those new packages:-
ii dnsmasq-base 2.86-1.1ubuntu0.4~ppa1
amd64Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-utils 2.86-1.1ubuntu0.4~ppa1
Thanks @Sergio, i missed those ppa links earlier, pushed test patch[1]
to validate it.
[1] https://review.opendev.org/c/openstack/ironic/+/897277
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
Hi,
I'm marking the status of this bug to Incomplete to reflect the fact
that we're waiting for information from the reporter.
@yatin, please let me know when you are able to give my PPA a try.
Thanks.
** Changed in: dnsmasq (Ubuntu Jammy)
Status: Confirmed => Incomplete
--
You
** Changed in: dnsmasq (Ubuntu Jammy)
Status: New => Confirmed
--
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:
dnsmasq on Ubuntu Jammy/Lunar crashes
@sergiodj hi
<< 1) Does the segfault happen with the dnsmasq package from Lunar/Mantic? I
see tasks for both systems added to this bug (and the Mantic one is set as
Confirmed), but it's not clear from the messages above whether the failure
really happens there.
I am not aware about any
Hello and thanks for taking the time to report this bug.
I read the discussion above and would like to clarify a few things:
1) Does the segfault happen with the dnsmasq package from Lunar/Mantic?
I see tasks for both systems added to this bug (and the Mantic one is
set as Confirmed), but it's
<< Will update and remove DNM from the test patch in ironic to use upstream
source 2.87.
Proposed https://review.opendev.org/c/openstack/ironic/+/888121
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
<< For neutron i will send a patch to add a sanity check to warn users running
2.86 version about this issue.
Pushed https://review.opendev.org/c/openstack/neutron/+/889015?usp=search
@Julia, thanks for checking those failures and reporting 2028279. Will
update and remove DNM from the test patch
@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
@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
** Also affects: dnsmasq (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: dnsmasq (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Also affects: dnsmasq (Ubuntu
So this also fails with version 2.89 that is in Lunar?
--
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:
dnsmasq on Ubuntu Jammy/Lunar crashes on
<<< 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
merged a patch
I'll bring it up in the next weekly Neutron meeting for visibility
purposes
** Changed in: neutron
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
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
I tried to setup dnsmasq-2.87 with
https://review.opendev.org/c/openstack/ironic/+/888121 by using source
install and avoiding newer package from lunar, still sometime some of
tests fails but i no longer see any segfault for dnsmasq with it. May be
someone from ironic Team could check and see if
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
19 matches
Mail list logo
