[Touch-packages] [Bug 2026757] Change abandoned on ironic (stable/2023.2)

2024-03-01 Thread OpenStack Infra 
Change abandoned by "Julia Kreger " on branch: 
stable/2023.2
Review: https://review.opendev.org/c/openstack/ironic/+/910444
Reason: superceded by 2.85 version.

-- 
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 crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  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
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0

[Touch-packages] [Bug 2026757] Change abandoned on ironic (stable/2023.1)

2024-02-29 Thread OpenStack Infra 
Change abandoned by "Julia Kreger " on branch: 
stable/2023.1
Review: https://review.opendev.org/c/openstack/ironic/+/910518

-- 
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 crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  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
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0 error 5 in

[Touch-packages] [Bug 2026757] Related fix proposed to ironic (stable/2023.1)

2024-02-28 Thread OpenStack Infra 
Related fix proposed to branch: stable/2023.1
Review: https://review.opendev.org/c/openstack/ironic/+/910518

-- 
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 crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  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
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0 error 5 in libc.so.6[7f21dd302000+195000]

[Touch-packages] [Bug 2026757] Related fix merged to ironic (master)

2024-02-27 Thread OpenStack Infra 
Reviewed:  https://review.opendev.org/c/openstack/ironic/+/888121
Committed: 
https://opendev.org/openstack/ironic/commit/27f53debb6800d9552510d44957b4d7d6292eaf5
Submitter: "Zuul (22348)"
Branch:master

commit 27f53debb6800d9552510d44957b4d7d6292eaf5
Author: yatinkarel 
Date:   Tue Jul 11 14:44:06 2023 +0530

ci: Source install dnsmasq-2.87

dnsmasq-2.86 shipped in Ubuntu jammy has a
known issue[1] which is fixed in dnsmasq-2.87
but it's not yet released with Ubuntu jammy.

Until fixed version is available in Ubuntu
jammy let's use source install instead of
using a older version from Ubuntu focal.

[1] 
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016562.html

Update from Julia:

Pushing forward the source fix again as ubuntu removed the
prior path we were using as a focal package and replaced
it with a package which is demonstrating the same basic issue.

Related-Bug: #2026757
Change-Id: I7ffcd167fc1e3a8c1192d766743bb5620d85ef35

-- 
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 crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  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
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  **

[Touch-packages] [Bug 2026757] Related fix proposed to ironic (stable/2023.2)

2024-02-27 Thread OpenStack Infra 
Related fix proposed to branch: stable/2023.2
Review: https://review.opendev.org/c/openstack/ironic/+/910444

-- 
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 crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  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
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0 error 5 in libc.so.6[7f21dd302000+195000]

[Touch-packages] [Bug 1996958] Fix included in openstack/tripleo-heat-templates train-eol

2024-02-06 Thread OpenStack Infra 
This issue was fixed in the openstack/tripleo-heat-templates train-eol
release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1996958

Title:
  [Azure] 18.04 - non-unique ID_PATH for SCSI disks

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * The PATH_ID for SCSI disks on Azure/Hyper-V might not be unique
 with the systemd/udev version in Ubuntu 18.04 LTS (Bionic Beaver).

   * This cause issues on applications that require unique PATH_IDs;
 for example Veritas Dynamic Multi-Pathing (DMP).

   * The fix introduces changes to PATH_ID format/values for VMBUS,
 which would break stable names/links, so it must be an opt-in.

   * The kernel command line option 'udev.new_vmbus_path_id' (boolean)
 can be used to opt in to (different) unique PATH_IDs.

   * It's not used by default (i.e., no behavior change by default).

  [Test Plan]

   1. Launch an Ubuntu 18.04 VM on Azure
   2. Add extra disks to the VM
   3. Check the disks PATH_ID for (non-)unique values
   4. (Opt-in for the fix with kernel cmdline option; repeat 3.)

   * Before:

$ lsscsi | grep /dev/sd
[0:0:0:0]diskMsft Virtual Disk 1.0   /dev/sdc
[0:0:0:1]diskMsft Virtual Disk 1.0   /dev/sdd
[1:0:0:0]diskMsft Virtual Disk 1.0   /dev/sda
[1:0:0:1]diskMsft Virtual Disk 1.0   /dev/sdb

$ for sd in /dev/sd?; do \
  udevadm test-builtin path_id /block/${sd#/dev} \
2>/dev/null | grep ID_PATH=; \
  done | sort | uniq -c
2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:0
2 ID_PATH=acpi-VMBUS:00-scsi-0:0:0:1

   * After:

Opt-in mechanism:

$ cat

[Touch-packages] [Bug 1841072] Related fix merged to oslo.utils (master)

2023-11-16 Thread OpenStack Infra 
Reviewed:  https://review.opendev.org/c/openstack/oslo.utils/+/850099
Committed: 
https://opendev.org/openstack/oslo.utils/commit/2319e6d32812ac8244b8dcacee6d1fadfab1c656
Submitter: "Zuul (22348)"
Branch:master

commit 2319e6d32812ac8244b8dcacee6d1fadfab1c656
Author: Takashi Kajinami 
Date:   Mon Jul 18 22:18:27 2022 +0900

Remove strict from is_same_callback()

The strict argument has been deprecated since 4.6.0 because it has no
effect in Python >=3.8 [1].

Because now this library supports only Python >=3.8, the logic for old
python versions can be removed.

[1] https://review.opendev.org/c/openstack/oslo.utils/+/750216

Related-Bug: #1841072
Change-Id: I5873c0df347a4e9a8a1fbfcf9f1212af14f7aef2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1841072

Title:
  test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  fails on Python 3.8

Status in oslo.utils:
  Fix Released
Status in python-oslo.utils package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  When running the unit test on Python 3.8, it fails with the following
  traceback:

  
oslo_utils.tests.test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  
---

  Captured traceback:
  ~~~
  b'Traceback (most recent call last):'
  b'  File "/tmp/oslo.utils/oslo_utils/tests/test_reflection.py", line 156, 
in test_different_instance_callbacks'
  b'self.assertTrue(reflection.is_same_callback(b.b, c.b, 
strict=False))'
  b'  File 
"/tmp/oslo.utils/.tox/py38/lib/python3.8/site-packages/unittest2/case.py", line 
702, in assertTrue'
  b'raise self.failureException(msg)'
  b'AssertionError: False is not true'
  b''

  This is apparently caused by a behavior change in Python 3.8 due to
  [1]. I have confirmed the different behavior by running tests manually
  on 3.6, 3.7 (both return True) and 3.8.

  According to [2], only taskflow seems to be using that method now, and
  it is not changing the default value for the "strict" parameter.

  [1] - https://bugs.python.org/issue1617161
  [2] - http://codesearch.openstack.org/?q=is_same_callback=nope==

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.utils/+bug/1841072/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1841072] Re: test_reflection.CallbackEqualityTest.test_different_instance_callbacks fails on Python 3.8

2020-09-08 Thread OpenStack Infra 
Reviewed:  https://review.opendev.org/750216
Committed: 
https://git.openstack.org/cgit/openstack/oslo.utils/commit/?id=632f15515fb224863c1027c658858c595ad5d11b
Submitter: Zuul
Branch:master

commit 632f15515fb224863c1027c658858c595ad5d11b
Author: Ghanshyam Mann 
Date:   Mon Sep 7 16:15:20 2020 -0500

Fix is_same_callback() testing for python3.8

Python3.8 onwards, comparision of bound methods is
changed. It no longer decide the bound method's equality based
on their bounded objects equality instead it checks the identity
of their '__self__'.

Details about this behavior change in python 3.8
- https://bugs.python.org/issue1617161
- python-dev discussion: 
https://mail.python.org/pipermail/python-dev/2018-June/153959.html

So python3.8 onwards, 'strict' arg has no meaning. For backward 
compatibility
for python <3.8, we can keep the 'strict' arg but with deprecation warning.

Also modify the is_same_callback() unit tests to verify the 'strict'
arg based on python version.

Change-Id: I3e6d9bbceccacddd0e1a514bbe5d0722a3408ecb
Closes-Bug: #1841072


** Changed in: oslo.utils
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1841072

Title:
  test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  fails on Python 3.8

Status in oslo.utils:
  Fix Released
Status in python-oslo.utils package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  When running the unit test on Python 3.8, it fails with the following
  traceback:

  
oslo_utils.tests.test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  
---

  Captured traceback:
  ~~~
  b'Traceback (most recent call last):'
  b'  File "/tmp/oslo.utils/oslo_utils/tests/test_reflection.py", line 156, 
in test_different_instance_callbacks'
  b'self.assertTrue(reflection.is_same_callback(b.b, c.b, 
strict=False))'
  b'  File 
"/tmp/oslo.utils/.tox/py38/lib/python3.8/site-packages/unittest2/case.py", line 
702, in assertTrue'
  b'raise self.failureException(msg)'
  b'AssertionError: False is not true'
  b''

  This is apparently caused by a behavior change in Python 3.8 due to
  [1]. I have confirmed the different behavior by running tests manually
  on 3.6, 3.7 (both return True) and 3.8.

  According to [2], only taskflow seems to be using that method now, and
  it is not changing the default value for the "strict" parameter.

  [1] - https://bugs.python.org/issue1617161
  [2] - http://codesearch.openstack.org/?q=is_same_callback=nope==

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.utils/+bug/1841072/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1841072] Re: test_reflection.CallbackEqualityTest.test_different_instance_callbacks fails on Python 3.8

2020-09-07 Thread OpenStack Infra 
Fix proposed to branch: master
Review: https://review.opendev.org/750216

** Changed in: oslo.utils
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1841072

Title:
  test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  fails on Python 3.8

Status in oslo.utils:
  In Progress
Status in python-oslo.utils package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  When running the unit test on Python 3.8, it fails with the following
  traceback:

  
oslo_utils.tests.test_reflection.CallbackEqualityTest.test_different_instance_callbacks
  
---

  Captured traceback:
  ~~~
  b'Traceback (most recent call last):'
  b'  File "/tmp/oslo.utils/oslo_utils/tests/test_reflection.py", line 156, 
in test_different_instance_callbacks'
  b'self.assertTrue(reflection.is_same_callback(b.b, c.b, 
strict=False))'
  b'  File 
"/tmp/oslo.utils/.tox/py38/lib/python3.8/site-packages/unittest2/case.py", line 
702, in assertTrue'
  b'raise self.failureException(msg)'
  b'AssertionError: False is not true'
  b''

  This is apparently caused by a behavior change in Python 3.8 due to
  [1]. I have confirmed the different behavior by running tests manually
  on 3.6, 3.7 (both return True) and 3.8.

  According to [2], only taskflow seems to be using that method now, and
  it is not changing the default value for the "strict" parameter.

  [1] - https://bugs.python.org/issue1617161
  [2] - http://codesearch.openstack.org/?q=is_same_callback=nope==

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.utils/+bug/1841072/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1878752] Related fix merged to charm-ceph-osd (master)

2020-05-18 Thread OpenStack Infra 
Reviewed:  https://review.opendev.org/728488
Committed: 
https://git.openstack.org/cgit/openstack/charm-ceph-osd/commit/?id=b1aab5d0e12e433b714e39f78945baf16e508a41
Submitter: Zuul
Branch:master

commit b1aab5d0e12e433b714e39f78945baf16e508a41
Author: James Page 
Date:   Fri May 15 17:00:25 2020 +0100

Trigger udev rescan if pv_dev disappears

Workaround for kernel by in Ubuntu 20.04 LTS.

When using by-dname device paths with MAAS and bcache, the pvcreate
operation results in the by-dname entry for the block device being
deleted.  The subsequent vgcreate then fails as the path cannot
be found.

Trigger a rescan of block devices if the pv_dev path does not
exists after the pvcreate operation.

Change-Id: If7e11f6bd1effd2d5fc2dc5abbaba6865104006f
Depends-On: Ifb16c47ae5ff316cbcfc3798de3446a3774fa012
Related-Bug: 1878752

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1878752] Related fix proposed to charm-ceph-osd (master)

2020-05-15 Thread OpenStack Infra 
Related fix proposed to branch: master
Review: https://review.opendev.org/728488

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878752

Title:
  vgcreate fails on /dev/disk/by-dname block devices

Status in OpenStack ceph-osd charm:
  New
Status in curtin package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

Bug description:
  Ubuntu Focal, OpenStack Charmers Next Charms.

  juju run-action --wait ceph-osd/0 add-disk osd-devices=/dev/disk/by-
  dname/bcache2

  unit-ceph-osd-0:
    UnitId: ceph-osd/0
    id: "5"
    message: exit status 1
    results:
  ReturnCode: 1
  Stderr: |
    partx: /dev/disk/by-dname/bcache2: failed to read partition table
  Failed to find physical volume "/dev/bcache1".
  Failed to find physical volume "/dev/bcache1".
  Device /dev/disk/by-dname/bcache2 not found.
    Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 79, in 
    request = add_device(request=request,
  File "/var/lib/juju/agents/unit-ceph-osd-0/charm/actions/add-disk", 
line 34, in add_device
    charms_ceph.utils.osdize(device_path, hookenv.config('osd-format'),
  File "lib/charms_ceph/utils.py", line 1497, in osdize
    osdize_dev(dev, osd_format, osd_journal,
  File "lib/charms_ceph/utils.py", line 1570, in osdize_dev
    cmd = _ceph_volume(dev,
  File "lib/charms_ceph/utils.py", line 1705, in _ceph_volume
    cmd.append(_allocate_logical_volume(dev=dev,
  File "lib/charms_ceph/utils.py", line 1965, in 
_allocate_logical_volume
    lvm.create_lvm_volume_group(vg_name, pv_dev)
  File "hooks/charmhelpers/contrib/storage/linux/lvm.py", line 104, in 
create_lvm_volume_group
    check_call(['vgcreate', volume_group, block_device])
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['vgcreate', 
'ceph-911bc34b-4634-4ebd-a055-876b978d0b0a', '/dev/disk/by-dname/bcache2']' 
returned non-zero exit status 5.
  Stdout: |2
  Physical volume "/dev/disk/by-dname/bcache2" successfully created.
    status: failed
    timing:
  completed: 2020-05-15 06:04:41 + UTC
  enqueued: 2020-05-15 06:04:30 + UTC
  started: 2020-05-15 06:04:39 + UTC

  The same action on the /dev/bcacheX device succeeds - looks like some
  sort of behaviour break in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1878752/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1807262] Fix included in openstack/sqlalchemy-migrate 0.12.0

2019-01-23 Thread OpenStack Infra 
This issue was fixed in the openstack/sqlalchemy-migrate 0.12.0 release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807262

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in sqlalchemy-migrate:
  Fix Released
Status in cinder package in Ubuntu:
  Fix Released
Status in migrate package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp

2019-01-21 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/623564
Committed: 
https://git.openstack.org/cgit/openstack/sqlalchemy-migrate/commit/?id=231a4d2ae9f8496cfc8eea2e6bb8186a0dd602f9
Submitter: Zuul
Branch:master

commit 231a4d2ae9f8496cfc8eea2e6bb8186a0dd602f9
Author: Corey Bryant 
Date:   Fri Dec 7 13:49:20 2018 -0500

Use legacy_alter_table ON in sqlite recreate_table

Use "PRAGMA legacy_alter_table = ON" with sqlite >= 3.26 when
using "ALTER TABLE RENAME TO migration_tmp" to maintain legacy
behavior.

As of sqlite version 3.26, when a table is renamed using
"ALTER TABLE RENAME TO", REFERENCES clauses that refer to the
table will be updated. To maintain legacy (3.24 and earlier)
behavior, "PRAGMA legacy_alter_table" can be set to true and
"PRAGMA foreign_keys" can be set to false. [1]

[1] https://www.sqlite.org/src/info/ae9638e9c0ad0c36

Thanks to "László Böszörményi (GCS)"  for
providing the code for this patch, which has since been
slightly modified.

Change-Id: I539988ab2ad6df6c8f423ecec15364ad8fcc7267
Closes-Bug: 1807262


** Changed in: sqlalchemy-migrate
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/1807262

Title:
  stein unit tests fail with sqlalchemy.exc.NoSuchTableError:
  migration_tmp

Status in sqlalchemy-migrate:
  Fix Released
Status in cinder package in Ubuntu:
  Fix Released
Status in migrate package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid

Bug description:
  Several tests that use sqlite fail with:
  "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently
  hitting this with nova and cinder packages in disco.

  Note this started sometime after 11/19 when nova
  2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built
  successfully at the time).

  After doing some digging this appears to occur with libsqlite3-0
  3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some
  more details on that, shown by running a failing unit test from the
  cinder package: https://paste.ubuntu.com/p/hsnQFQD572/

  Update: The test in the paste above also works successfully with
  libsqlite3-0 3.25.3-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1759796] Re: Ubuntu images fail to build due to broken dh-python package

2018-04-03 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/557906
Committed: 
https://git.openstack.org/cgit/openstack/kolla/commit/?id=3a26647c789ebd17064bcf63a88e673bcb0ecca0
Submitter: Zuul
Branch:stable/queens

commit 3a26647c789ebd17064bcf63a88e673bcb0ecca0
Author: Martin André 
Date:   Thu Mar 29 11:01:43 2018 +0200

Pin dh-python to earlier version to fix ubuntu gate

Let's pin the package until the dh-python from ubuntu-cloud-archive is
fixed.

Change-Id: I59f827bc7eb27a30f5d5f06628b3be535fcfabcc
Related-Bug: #1759796
(cherry picked from commit 739c51392f4244d68c023b061ce0300932db285b)


** Tags added: in-stable-queens

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1759796

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1759796/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1759796] Related fix proposed to kolla (stable/queens)

2018-03-30 Thread OpenStack Infra 
Related fix proposed to branch: stable/queens
Review: https://review.openstack.org/557906

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1759796

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1759796/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1759796] Related fix merged to kolla (master)

2018-03-29 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/557655
Committed: 
https://git.openstack.org/cgit/openstack/kolla/commit/?id=739c51392f4244d68c023b061ce0300932db285b
Submitter: Zuul
Branch:master

commit 739c51392f4244d68c023b061ce0300932db285b
Author: Martin André 
Date:   Thu Mar 29 11:01:43 2018 +0200

Pin dh-python to earlier version to fix ubuntu gate

Let's pin the package until the dh-python from ubuntu-cloud-archive is
fixed.

Change-Id: I59f827bc7eb27a30f5d5f06628b3be535fcfabcc
Related-Bug: #1759796

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1759796

Title:
  Ubuntu images fail to build due to broken dh-python package

Status in kolla:
  New
Status in dh-python package in Ubuntu:
  New

Bug description:
  Some ubuntu images fails to build and block the gate.

  2018-03-28 15:07:13.498244 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-controller' to succeed!
  2018-03-28 15:07:13.498650 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-northd' to succeed!
  2018-03-28 15:07:13.498957 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'bifrost-base' to succeed!
  2018-03-28 15:07:13.499241 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovsdpdk' to succeed!
  2018-03-28 15:07:13.499559 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-sb-db-server' to succeed!
  2018-03-28 15:07:13.499867 | primary | CRITICAL:tests.test_build:>>> Expected 
image 'ovn-nb-db-server' to succeed!

  http://logs.openstack.org/33/555733/1/check/kolla-build-ubuntu-
  source/72f9085/job-output.txt.gz#_2018-03-28_15_07_13_498244

  Looking more closely, it appears they fail to install lsb-release that
  depends on python3. Going up the dependency chain, the issue seems to
  be in dh-python that added a dependency on python3-distuils. However
  python3-distuils doesn't exist and should probably be
  python3-distutils.

  ()[root@f8bc5d1d504e bifrost-5.0.1.dev43]# apt-cache show dh-python
  Package: dh-python
  Priority: optional
  Section: python
  Installed-Size: 429
  Maintainer: Piotr Ożarowski 
  Architecture: all
  Version: 3.20180325ubuntu1~cloud0
  Replaces: python3 (<< 3.3.2-4~)
  Suggests: libdpkg-perl, dpkg-dev
  Depends: python3:any (>= 3.3.2-2~), python3-distuils
  Breaks: python3 (<< 3.3.2-4~)
  Supported: 60m
  Filename: pool/main/d/dh-python/dh-python_3.20180325ubuntu1~cloud0_all.deb
  Size: 89382
  SHA256: 5d31a348f141d7ca366eeb21b58633bed96a0b27417ce8759e1cb785cb1db8bc
  SHA1: a817acac0042ab6e22dd686376717a20e449ae03
  MD5sum: d89b5e505bbb93b57efe4bfb85fc353d
  Description: Debian helper tools for packaging Python libraries and 
applications
  Description-md5: b21cd6f99d6093fdc7e0ba30c8dd949f
  Multi-Arch: foreign
  Original-Maintainer: Piotr Ożarowski 

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla/+bug/1759796/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Fix included in openstack/neutron 10.0.0.0b1

2016-11-16 Thread OpenStack Infra 
This issue was fixed in the openstack/neutron 10.0.0.0b1 development
milestone.

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1235337] Fix included in openstack/python-tripleoclient 0.0.10

2016-11-09 Thread OpenStack Infra 
This issue was fixed in the openstack/python-tripleoclient 0.0.10
release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1235337

Title:
  signon-ui ships files in a wrong directory

Status in Online Accounts: Sign-on UI:
  Fix Committed
Status in signon-ui package in Ubuntu:
  Fix Committed

Bug description:
  The signon-ui package ships a binary, /usr/libexec/signon-ui/browser-
  process, in a location that is disallowed by the FHS.  This needs to
  be moved to /usr/lib/signon-ui/browser-process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: signon-ui 0.15+13.10.20131003.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  4 08:57:30 2013
  InstallationDate: Installed on 2010-09-24 (1106 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MarkForUpload: True
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to saucy on 2013-05-06 (150 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/signon-ui/+bug/1235337/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1241668] Fix included in openstack/python-tripleoclient 0.0.10

2016-11-09 Thread OpenStack Infra 
This issue was fixed in the openstack/python-tripleoclient 0.0.10
release.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1241668

Title:
  gdb embeds python3.3, but support scripts are not compatible

Status in Python:
  Fix Released
Status in gdb package in Ubuntu:
  Invalid
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3.3 package in Ubuntu:
  Fix Released
Status in gdb source package in Saucy:
  Invalid
Status in python2.7 source package in Saucy:
  Won't Fix
Status in python3.3 source package in Saucy:
  Won't Fix

Bug description:
  The saucy gdb appears to be linked against libpython3.3.

  This results in a conflict when trying to debug python2.7 programs,
  which use the python2.7-dbg.py scripts from python2.7-dbg.  This makes
  debugging Python programs difficult.

  
File "/usr/lib/debug/usr/bin/python2.7-gdb.py", line 54
  Py_TPFLAGS_HEAPTYPE = (1L << 9)
  ^
  SyntaxError: invalid syntax
File "/usr/lib/debug/usr/bin/python2.7-gdb.py", line 54
  Py_TPFLAGS_HEAPTYPE = (1L << 9)

  There are also invalid print statements that show up as well.

  If these are updated, then the file parses, but `py-bt` fails with:

  Error occurred in Python command: global name 'long' is not defined

  Updating all of the long() references to int() doesn't work:

  Error occurred in Python command: 'gdb.Value' object cannot be
  interpreted as an integer

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1241668/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Fix included in openstack/neutron 9.0.0.0rc2

2016-09-27 Thread OpenStack Infra 
This issue was fixed in the openstack/neutron 9.0.0.0rc2 release
candidate.

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-24 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/375645
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f74a6c047f02e077e4fd943e2eb256df82e05509
Submitter: Jenkins
Branch:stable/newton

commit f74a6c047f02e077e4fd943e2eb256df82e05509
Author: Brian Haley 
Date:   Tue Sep 6 14:44:41 2016 -0400

Fix dhcp_release6 error when not supported

If the system does not have a version of dnsmasq that supports
dhcp_release6, warn about but otherwise handle it gracefully, and also
don't even try to execute it the next time.

Closes-Bug: #1622002
Related-Bug: #1624079

(cherry picked from commit d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e)
Change-Id: I6bb9547f9d9a9fcfb2357521f3f5bd1dc1dd5136


** Tags added: in-stable-newton

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-23 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/366291
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e
Submitter: Jenkins
Branch:master

commit d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e
Author: Brian Haley 
Date:   Tue Sep 6 14:44:41 2016 -0400

Fix dhcp_release6 error when not supported

If the system does not have a version of dnsmasq that supports
dhcp_release6, warn about but otherwise handle it gracefully, and also
don't even try to execute it the next time.

Closes-Bug: #1622002
Related-Bug: #1624079
Change-Id: I6bb9547f9d9a9fcfb2357521f3f5bd1dc1dd5136


** Changed in: neutron
   Status: In Progress => Fix Released

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  Fix Released
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Fix proposed to neutron (stable/newton)

2016-09-23 Thread OpenStack Infra 
Fix proposed to branch: stable/newton
Review: https://review.openstack.org/375645

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  In Progress
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1622002] Re: dhcp_release6 can be called when it is not present

2016-09-23 Thread OpenStack Infra 
** Changed in: neutron
 Assignee: Brian Haley (brian-haley) => Ihar Hrachyshka (ihar-hrachyshka)

-- 
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/1622002

Title:
  dhcp_release6 can be called when it is not present

Status in neutron:
  In Progress
Status in dnsmasq package in Ubuntu:
  New

Bug description:
  If someone enables dhcpv6-stateful addressing on a subnet, but they
  are running an old version of dnsmasq (<2.76), then the dhcp agent
  could try and run dhcp_release6 even though it isn't present.  An
  example:

  http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron-
  multinode-full-ubuntu-
  xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272

  Checking it's present first would fix this problem.

  Since the change to call dhcp_release6 was just added in
  https://review.openstack.org/#/c/301747/ we should fix this before
  Newton ships and people complain.

  There is also an effort to get Cirros to support DHCPv6 so that we can test 
this in the gate,
  https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so 
we can add a functional test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1622002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name

2014-10-20 Thread OpenStack Infra 
Fix proposed to branch: master
Review: https://review.openstack.org/129642

** Changed in: openstack-manuals
   Status: Confirmed = In Progress

** Changed in: openstack-manuals
 Assignee: (unassigned) = Matt Kassawara (ionosphere80)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1362521

Title:
  juno: not a valid cloud-archive name

Status in Ubuntu Cloud Archive:
  Confirmed
Status in OpenStack Manuals:
  In Progress
Status in “software-properties” package in Ubuntu:
  Confirmed

Bug description:
  While installing Openstack  on Ubuntu 14.04 (LTS) getting the below
  error. I am following  the instructions as per the document @
  http://docs.openstack.org/trunk/install-guide/install/apt/openstack-
  install-guide-apt-trunk.pdf

  
  # add-apt-repository cloud-archive:juno
  'juno': not a valid cloud-archive name.
  Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 
'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 
'tools-proposed']

  
  Is the document still in development? let me know what does this error mean 
and how to proceed further.

  Page 22 : URL :  http://docs.openstack.org/trunk/install-
  guide/install/apt/openstack-install-guide-apt-trunk.pdf

  Regards,
  Satish

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1362521] Re: juno: not a valid cloud-archive name

2014-10-20 Thread OpenStack Infra 
Reviewed:  https://review.openstack.org/129642
Committed: 
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=9a50e10b3737368776f72ccd3788d30862b85cc6
Submitter: Jenkins
Branch:master

commit 9a50e10b3737368776f72ccd3788d30862b85cc6
Author: Matthew Kassawara mkassaw...@gmail.com
Date:   Mon Oct 20 10:07:24 2014 -0500

Add workaround for Ubuntu Cloud archive

I added a workaround for the Ubuntu Cloud archive repository
because the 'add-apt-repository' method does not contain
information about Juno packages.

Change-Id: Ib222dc1a1919e3e3f55e694426d25fbefb9e3cbe
Closes-Bug: #1362521


** Changed in: openstack-manuals
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1362521

Title:
  juno: not a valid cloud-archive name

Status in Ubuntu Cloud Archive:
  Confirmed
Status in OpenStack Manuals:
  Fix Released
Status in “software-properties” package in Ubuntu:
  Confirmed

Bug description:
  While installing Openstack  on Ubuntu 14.04 (LTS) getting the below
  error. I am following  the instructions as per the document @
  http://docs.openstack.org/trunk/install-guide/install/apt/openstack-
  install-guide-apt-trunk.pdf

  
  # add-apt-repository cloud-archive:juno
  'juno': not a valid cloud-archive name.
  Must be one of ['folsom', 'folsom-proposed', 'grizzly', 'grizzly-proposed', 
'havana', 'havana-proposed', 'icehouse', 'icehouse-proposed', 'tools', 
'tools-proposed']

  
  Is the document still in development? let me know what does this error mean 
and how to proceed further.

  Page 22 : URL :  http://docs.openstack.org/trunk/install-
  guide/install/apt/openstack-install-guide-apt-trunk.pdf

  Regards,
  Satish

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1362521/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp