[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

[Nish Aravamudan]

https://github.com/systemd/systemd/issues/8686 seems related.

** Bug watch added: github.com/systemd/systemd/issues #8686
   https://github.com/systemd/systemd/issues/8686

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728181/+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 1773087] Re: Remove python3-apport as dependency of xserver-xorg

[Nish Aravamudan]

xserver-xorg now has an apport hook. So in order of ubuntu-bug to work,
it is necessary to have python3-apport installed, per LP: #1730035.
Definitely not a bug.

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

Title:
  Remove python3-apport as dependency of xserver-xorg

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Distro: Bionic
  Binary Package: xserver-xorg
  Version: 1:7.7+19ubuntu7

  Hello!
  The package xserver-xorg depends on python3-apport. I don't want to use 
apport on my systems.
  Can the dependency be removed?

  Also, it doesn't work anyway. That's how I noticed that the package is
  installed:

  root@00debac04ddf:~# foo
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in 
apport_excepthook
  os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/crash/_usr_bin_foo.0.crash'

  Original exception was:
  Traceback (most recent call last):
File "/usr/bin/foo", line 3, in 
  raise Exception
  Exception

  Thanks
  Jörn Heissler

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773087/+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 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

[Nish Aravamudan]

@cran: you can wait for your mirror, or download the debs from
archive.ubuntu.com.

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

I edited /etc/gdm3/custom.conf and put WaylandEnable=false back in (I
had it enabled before to test). Greeter came right up on reboot and my
external monitor works again.

What is curious is that my session choice in both cases was/is Gnome on
Xorg. So is it possible there's some change in the greeter's behavior?
As to using wayland or not.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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

Re: [Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

Hi Daniel,

On Mon, Mar 5, 2018 at 9:56 PM, Daniel van Vugt
 wrote:
> Nish,
>
> To figure the problem out you will need to be logged in already while
> it's happening(!), so..

Yeah, tricky when the machine physically seems to be hung (no
touchpad, no responsiveness to keyboard)

> 1. Log into a VT (Ctrl+Alt+F4) or install openssh-server and log in from a 
> separate machine.
> 2. Run 'top' to find the ID of the spinning process.
> 3. Run:
>kill -ABRT 
> 4. Wait a while for crash files to be written.
> 5. Look in /var/crash for crash files and run:
>ubuntu-bug /var/crash/YOURFILE.crash
> 6. Add a comment here telling us the ID of the new bug.

Thanks for the info!

I just was wondering, as the responsiveness of the desktop feels very
different, and it does seem like I'm now on an Xwayland session, even
though I didn't change anything. I wonder if it's Wayland that's
actually crashing?

gdm   2795  0.0  0.0 190684  5496 tty1 Ssl+ Mar05   0:00
/usr/lib/gdm3/gdm-wayland-session gnome-session --autostart
/usr/share/gdm/greeter/autostart
gdm   2878  0.0  0.3 563888 55076 tty1 Sl+  Mar05   0:00
/usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4
-listen 5 -displayfd 6
nacc  3428  0.0  0.0 190684  5408 tty2 Ssl+ Mar05   0:00
/usr/lib/gdm3/gdm-wayland-session gnome-session --session=gnome
nacc  3502  0.0  0.3 565704 56056 tty2 Sl+  Mar05   0:02
/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4
-listen 5 -displayfd 6

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  

[Touch-packages] [Bug 1753576] Re: GDM freeze

[Nish Aravamudan]

But if I plug in my usb-c dongle, it immediately freezes and the fans
start to spin. Unplugging the dongle has no effect. Suggestions for
debugging?

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze

[Nish Aravamudan]

I just rebooted again and without hitting any keys, it did come up to
the greeter without issue.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze

[Nish Aravamudan]

Hrm, I'm not entirely sure what just changed. I rebooted and unlike
before, I hit Escape at the splash screen, and the GDM greeter showed up
just fine (after hitting Escape again to go back to graphics mode). I'll
see if that's reproducible shortly.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze

[Nish Aravamudan]

Oh also the splash screen correctly displays on both monitors, so i
think it must be in X that the multiple displays fail.

I'll see if I can figure out how to get to a temrinal.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze

[Nish Aravamudan]

@vanvugt: no, as it's not crashed (afaict), it's just 100% cpu (based
upon fans). Numlock is still responsive as is sysrq, but i can't get to
any ttys (that is, ctrl+alt+f2, etc don't seem to work).

I even tried booting with 'text' and annoyingly gdm still started (I
might be misremembering how to do that, though).

Any suggestions on how to force a crash?

I might reboot now and just leave it to see if it eventually progresses.

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] [NEW] Xorg freeze

[Nish Aravamudan]

Public bug reported:

Here is what I know so far:

After rebooting this morning on Bionic (after receiving the gnome theme
updates, I think), upon reboot the CPU pegs and the greeter is never
displayed (there is a graphics system running, but I'm not sure what
it's doing). My num lock / caps lock keys work, but the touchpad on the
laptop does nothing to the mouse.

If I boot with nomodeset, greeter does not freeze.

Finally, in either case, I am now unable to use my external monitor,
which worked fine before (connected over a USB-C to HDMI dongle).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Mar  5 11:47:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: This is the first time
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
InstallationDate: Installed on 2015-12-17 (809 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 80MK
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C6CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K45914 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 900-13ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80MK
dmi.product.version: Lenovo YOGA 900-13ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Mar  5 11:17:58 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic freeze has-workaround regression reproducible 
single-occurrence ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: 

[Touch-packages] [Bug 1752656] [NEW] Please SRU archive keyrings to older releases

[Nish Aravamudan]

Public bug reported:

While not necessarily a critical issue for the Ubuntu keyrings, as
Debian uses newer keys periodically, it becomes impossible with the
default keyrings to verify the latest Debian archive files.

It seems reasonable to ensure the keyring contents in all releases are
the same, as the latest release is reflecting the latest archives.

** Affects: debian-archive-keyring (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-keyring (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: debian-archive-keyring (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Please SRU archive keyrings to older releases

Status in debian-archive-keyring package in Ubuntu:
  New
Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  While not necessarily a critical issue for the Ubuntu keyrings, as
  Debian uses newer keys periodically, it becomes impossible with the
  default keyrings to verify the latest Debian archive files.

  It seems reasonable to ensure the keyring contents in all releases are
  the same, as the latest release is reflecting the latest archives.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-archive-keyring/+bug/1752656/+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 1742243] Re: Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

** Changed in: openexr (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  Fix Committed

Bug description:
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1742243/+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 1742243] Re: Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

openexr (2.2.0-11.1ubuntu1) bionic; urgency=medium

  * Merge with Debian unstable (LP: #1742243). Remaining changes:
- Add ppc64el to the archs where to ignore test results.

 -- Nishanth Aravamudan <nish.aravamu...@canonical.com>  Tue, 09 Jan
2018 10:49:25 -0800


** Merge proposal linked:
   
https://code.launchpad.net/~nacc/ubuntu/+source/openexr/+git/openexr/+merge/335904

** Changed in: openexr (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: openexr (Ubuntu)
   Status: New => In Progress

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  In Progress

Bug description:
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1742243/+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 1742243] [NEW] Please merge with Debian unstable 2.2.0-11.1

[Nish Aravamudan]

Public bug reported:

TBD

** Affects: openexr (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please merge with Debian unstable 2.2.0-11.1

Status in openexr package in Ubuntu:
  New

Bug description:
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1742243/+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 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

[Nish Aravamudan]

** Summary changed:

- Please merge lvmlockd and sanlock support
+ Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

** Changed in: lvm2 (Ubuntu)
   Status: New => Confirmed

** Changed in: lvm2 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: lvm2 (Ubuntu)
Milestone: None => ubuntu-18.02

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

Title:
  Please merge lvm2 from Debian unstable for lvmlockd and sanlock
  support

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I am extremely interesting in utilizing the following stack to host
  disks for KVM virtual machines:

  * lvm2
  * lvmlockd
  * sanlock

  I believe in order to use lvmlockd, the lvm2 sources will need to be
  merged from Debian and the lvm2-lockd binary package will need to be
  built. Please could I request that this merge happen prior to the
  release of Beaver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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

Re: [Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Does the Ubuntu php build use the bundled tzdata? A lot of stuff comes from
the system not the source (e.g, pcre iirc)

On Dec 1, 2017 18:40, "Eric Desrochers" 
wrote:

> Same thing with new php pkg release in debian/unstable (php - 7.1.12-1).
> It still displays America/Sao_Paulo
>
> That exclude my theory about the tz bundle update. I'll do a proper
> bisect next week.
>
> - Eric
>
> --
> You received this bug notification because you are subscribed to php7.1
> in Ubuntu.
> Matching subscriptions: PHP7.0
> https://bugs.launchpad.net/bugs/1734967
>
> Title:
>   tzdata info for WGT/WGST broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions
>

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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

Re: [Touch-packages] [Bug 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Is this already fixed in proposed (MRE to latest upstream php 7.0 and
7.1)?

On Dec 1, 2017 03:48, "Bug Watch Updater" <1734...@bugs.launchpad.net>
wrote:

> ** Changed in: php7.0 (Debian)
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to php7.1
> in Ubuntu.
> Matching subscriptions: PHP7.0
> https://bugs.launchpad.net/bugs/1734967
>
> Title:
>   tzdata info for WGT/WGST broken
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions
>

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in php7.1 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid
Status in php7.0 package in Debian:
  New

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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 1734967] Re: tzdata info for WGT/WGST broken

[Nish Aravamudan]

Just to be clear, this isn't a bug based upon comment 1 but new tasks
were opened in comment 2?

If it's purely an SRU regression in tzdata that should be figured out.

Im guessing this is an upstream php issue. Has it been fixed there?

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

Title:
  tzdata info for WGT/WGST broken

Status in php5 package in Ubuntu:
  New
Status in php7.0 package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Invalid

Bug description:
  Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed
  from date command but instead just "-03". Problem is evident in PHP
  applications too, which now think we're in Sao Paolo.

  This appears to have changed with latest tzdata update or perhaps in
  combination with change from DST.

  Same problem on 16.04, 17.10 and Debian 9.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

I'm guessing this might be a quirk of the armhf runners:

test_tree_garbage (__main__.ChrootRunner)
copied source tree contains only expected files ... : Operation not permitted
cp: cannot create special file ‘/tmp/tmp36ee0r77/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmplo89rot6/chroot//dev/null’:
Operation not permitted
cp: cannot create special file ‘/tmp/tmpsd8_r783/chroot//dev/null’:
Operation not permitted
ERROR
test_tree_norestrictions_nobuild_fail_on_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with non-zero ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr ... ERROR
test_tree_norestrictions_nobuild_fail_on_stderr_and_exit (__main__.ChrootRunner)
source tree, no build, no restrictions, test fails with stderr+exit ... ERROR

I'll see if it might need some restrictions (or if the runner env
changed)?

-Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

If someone is interested in the proper upstream fixes, please file a new
bug and we will need to fix bionic and prepare a distinct SRU for the
existing releases.

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Released
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote:
> @arges
>
> Hi, would you need any more testing from us?

Nope, your part is done. All SRUs have to bake for 7 days in -proposed
to shake out regressions.

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  Fix Committed
Status in iproute2 source package in Xenial:
  Fix Committed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  In Progress

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote:
> On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> > I had a look at the two proposals and could not spot any obvious
> > mistakes:
> > 
> > - the correct upstream git commit has been cherry-picked
> > - I don't have any objections to attribution or log messages
> > 
> > Thanks again for shepherding this one through!
> 
> You're welcome, I'll upload them both today.
> 
> Thank you and Monique for filing the SRU template properly!

I have sponsored both packages. They will need to be approved by an SRU
team member (probably next week) before they appear in
{trusty,xenial}-proposed and then they will need testing as built in
proposed, with a minimum bake time of 7 days in proposed.

Thank you and Monique for your contribution to Ubuntu!

-Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [07:09:00 -], Jan Gutter wrote:
> I concur with option 2), unnecessary deviation will just cause
> confusion.

Thank you for confirming that!

> Regarding the other buffer sizes, the last time I looked they were
> mostly OK. The issue reared its head in this particular case because the
> netlink message that previously had a pretty constant per-netdev
> response size suddenly had the ability to balloon with "no warning". A
> number of workarounds exist (i.e. you have to explicitly ask for the VF
> info), but, in this case we actually want the VF info and iproute2 was
> just unprepared for the size of it.

Ok, that's good to hear.

> I guess the core issue is that it's entirely possible for the kernel to
> add extra netlink attributes to any query response, iproute2 makes the
> assumption that the queries it's making is not necessarily going to
> explode with gigabytes of new annotations and 16k will easily fit any
> current real-world system. A pragmatic approach would probably be to
> handle the "Message Truncated" path with a dynamically sized buffer as
> an exceptional case.

Yep, I can see how iproute2 itself has to move in lockstep with the
kernel, which also means older iproute2 that can run on newer kernels
needs periodic updates like this one.

> Any fix in iproute2 that "properly" addresses this issue has to be
> carefully vetted. Who knows how many inherent races will get exposed if
> the ip command doubles in execution time.

Yep :) I'm fine with eventually doubling the buffer again statically if
that is the conclusion upstream reaches. My guess is that is the
simplest solution.

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> I had a look at the two proposals and could not spot any obvious
> mistakes:
> 
> - the correct upstream git commit has been cherry-picked
> - I don't have any objections to attribution or log messages
> 
> Thanks again for shepherding this one through!

You're welcome, I'll upload them both today.

Thank you and Monique for filing the SRU template properly!

-Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

I have set up two MPs with the adjustments (it looks like Monique's
latest debdiffs followed path 2) from my previous comment already) to
the DEP3 headers that I think make the most sense. Please take a look at
them and if you approve the changes I will upload them.

I note also there are a number of statically sized buffers in the
iproute2 code -- is there any concern about other buffers overflowing?

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 19.10.2017 [09:35:19 -], Jan Gutter wrote:
> @nacc
> 
> Thanks so much for the explanation. I also found
> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Merge_Proposals_and_Reviewing
> that details a bit more of the internal processes. As relative outsiders
> to the Ubuntu process, I'd appreciate it very much if you could handle
> that part for Monique's patches. I can be on hand to answer technical
> questions if required.

And to be clear, the MP based workflow for the Git trees is brand new
and experimental :)

I'm happy to integrate the updated debdiffs (I'll reply to those
comments directly).

> Regarding the buffer size choice, it's very arbitrary as Phil said. I'm
> pretty sure we came to the same conclusion independently (libvirt and
> libnl had very similar issues) and the workaround is obvious. 32k seems
> to work for 64 VF's (our test case), but breaks with 128 VF's. Not a lot
> of machines can handle 128 concurrent VF's. I typed 64k "just because".
> libvirt+libnl allow message peeking. However, iproute2 uses netlink
> directly. So, implementing a similar idea would require an entirely new
> receive codepath with all the fun of finding out where new exception
> paths occur: something to be done on tip and not suitable for backport
> without thorough vetting.

Absolutely. My concern is the upstream code is at 32k as is Artful. I'm
hesitant to backport something different (64k) to X and T without also
ensuring Artful gets it (and BB when it opens), and presumably also
fixing it upstream.

So I see two routes forward:

1) File an upstream issue to request they bump to 64k, as you note 32k
is insufficient for 128 VFs. Link to that issue in this bug and we'll
fix AA, X and T with the suggested change (presuming upstream acks it).

2) Backport the upstream change as-is to X and T (AA already has the
necessary fix). This will be faster, of course, but does mean the 128 VF
case is broken. Given that it is less likely to be hit in the field,
perhaps that is ok -- and in the meanwhile, upstream can work on a
proper fix which, when available, we can backport accordingly (or decide
at that point, in any case).

I prefer 2), because I do not like diverging from upstream (or at least
not without an upstream bug report). If you and Monique are ok with 2),
I can update the debdiffs before sponsoring them.

> I'm sure it'll save a lot of time once the kinks have been worked out of
> the automation, backports are quite the double-edged sword.

Definitely :)

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# 

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

@mvandenberg,

Couple of nits in your debdiffs.

1) changelogs are targetting UNRELEASED, please update to xenial and
trusty respectively.

2) Is there a reason your fix is different than the fix upstream/Debian?
Does Debian need your version instead?

3) Please use appropriate DEP3 headers (dpkg-source --commit creates a
template patch with them): http://dep.debian.net/deps/dep3/, especially
Origin (not Origin/Author).

4) The actual author appears to be Phil Sutter, not Jan Gutter, although
Jan authored the patch in this bug. Consider using dep3changelog once
you have a quilt patch to generate the changelog in the standard format
(with an attribution to Phil or Jan as you decide).

5) The trusty version number seems off, it should be 3.12.0-2ubuntu1.1.
Please take a look at
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging.

Can you fix these up and reupload the debdiffs?

Thanks,
Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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

Re: [Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

On 17.10.2017 [08:56:17 -], Jan Gutter wrote:
> @nacc I built from source to verify that the one-liner is directly
> responsible for fixing and breaking the issue (inherent paranoia). I did
> test with the binaries and they worked.

Ah ok, yeah -- I guess that's reasonable, and is a good preemptive test,
but given that it needs to be backported to a different release, feels a
bit like busywork (the same time could have been spent building it for
xenial :)

> Apologies, I'm unfamiliar with the Ubuntu SRU process as you can
> probably see. What exactly is an "MP" and how would one go about to
> propose one?

MP = Merge Proposal. Roughly like GitHub's Pull Requests (PR), except
less formal with Git (bzr I think is somewhat more first-class in
Launchpad).

> I'm aware of the need of testing bugfixes like these, I'm not familiar
> with your release pipeline, however.

http://www.justgohome.co.uk/blog/2017/07/developing-ubuntu-using-
git.html

may help a bit. Roughly:

$ sudo snap install --classic git-ubuntu
$ git ubuntu clone iproute2
$ cd iproute2
$ ... make and commit changes
$ git ubuntu submit

Now, the issue is that middle bit, where you have to know a bit about
source packaging. That is, simply cherry-picking the upstream/Debian fix
is not quite right, as you need to change it into a Quilt patch and then
insert a changelog entry.

We are currently developing a fix for that so you can just do a

$ git ubuntu remote add debian
$ git cherry-pick 72b365e83
$ git ubuntu build-source

And it should spit out a commit that has the quiltify'd and
changelogify'd result that you can use as a base or to submit.

Feel free to find me on IRC if you want some more pointers.

In the meanwhile, I'll try and look at Monique's debdiffs this week.

-Nish

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+subscriptions

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

[Touch-packages] [Bug 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

@jangutter: I'm not sure why you built from source? I assume you
actually tested the version in 17.04 and it worked.

The proper solution is to backport the Debian change to xenial and
trusty, most likely. A git repository that can be used with `git-ubuntu`
(sudo snap install --classic git-ubuntu`) is available here:
https://code.launchpad.net/~usd-import-
team/ubuntu/+source/iproute2/+git/iproute2

Feel free to propose MPs against ubuntu/xenial-devel and ubuntu/trusty-
devel, or I can do it if you'd prefer.

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1720126] Re: [ip link] Message truncated error for large number of passthrough VFs

[Nish Aravamudan]

** Also affects: iproute2 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: iproute2 (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: iproute2 (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: iproute2 (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: iproute2 (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: iproute2 (Ubuntu)
   Importance: High => Undecided

** Also affects: iproute2 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  [ip link] Message truncated error for large number of passthrough VFs

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Trusty:
  New
Status in iproute2 source package in Xenial:
  Confirmed
Status in iproute2 source package in Zesty:
  Fix Released
Status in iproute2 package in CentOS:
  Unknown

Bug description:
  [Impact]

  When querying a Physical Function netdev with a large amount of VF's
  (more than 30), the resulting return message can overflow the 16K
  netlink message buffer.

  This can be fixed by enabling message peeking on the socket and
  resizing the buffer on receive, or by simply enlarging the receive
  buffer.

  Since there's an upper limit to the number of VF's per PF, it's
  relatively sane to just enlarge the receive buffer. Please see the
  attached patch.

  [Test Case]

  # Set up 60 VF's on an SR-IOV device
  ip link show > /dev/null

  Observe the following:
  Message truncated
  Message truncated
  Message truncated

  [Regression Potential]

  1) Applications relying on the broken behaviour will need to be updated, but 
it would be a really dubious use case.
  2) Increasing the rx buffer size increases the memory footprint (but 
realistically, this is tiny).
  3) Extra processing time is now needed to parse the larger buffer, in the 
case that a call to "ip link" is on the critical time path of an application, 
(called multiple times in a tight loop, for example), it would affect load.

  [Other Info]

  Observed on Ubuntu kernel 4.4.0-93-generic on both 14.04 and 16.04

  
=
  Ubuntu16 system

  stack@cluster04:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  stack@cluster04:~$ uname -r
  4.4.0-93-generic

  stack@cluster04:~$ apt-cache policy iproute2
  iproute2:
    Installed: 4.3.0-1ubuntu3.16.04.1
  Version table:
  *** 4.3.0-1ubuntu3.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  
=

  Ubuntu14 system:
  root@boomslang:~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  Codename: trusty

  root@boomslang:~# uname -r
  4.4.0-96-generic

  root@boomslang:~# apt-cache policy iproute2
  iproute2:
    Installed: 3.12.0-2ubuntu1
    Version table:
   *** 3.12.0-2ubuntu1 0
  500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1650666] Re: GVim crashes when opening new tab

[Nish Aravamudan]

** Description changed:

+ [Impact]
+ 
+ A severe regression has been found in the GTK 3 variant of Gvim.
+ Upon start-up, it crashes immediately with multiple failed
+ assertions.
+ 
+ A second related, but less severe problem may occur when opening
+ new tabs within the GTK 3 variant of Gvim.
+ 
+ [Test Case]
+ 
+ Please note that in the following test cases, a given machine may
+ experience either of the test cases, while being unable to
+ experience the other test case. Please do /not/ discount
+ the merits of this SRU on being able to only confirm a single
+ test case, but not both.
+ 
+ This patch equally corrects both test cases listed below, to
+ produce a working GTK 3 Gvim variant.
+ 
+ IMPORTANT: Both test cases below require the package "vim-gtk3"
+ to be installed, prior to testing for either test case's
+ impact to one's machine.
+ 
+ [[TEST CASE #1]]
+ 
+ 1. From a terminal window, launch the GTK 3 variant of Gvim:
+ 
+   $ vim.gtk3
+ 
+ 2. Immediately upon launch (whereby the window may or may
+not briefly display); the terminal window will show error
+messages relating to `unity_gtk_menu_*` critical
+assertions.
+ 
+A full example of the experienced error output shown is:
+ 
+ ```
+ (gvim:13519): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <= 
(gint)rarray->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_child_shell: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_shell_get_item: assertion '0 <= 
index && index < items->len' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_label: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ** (gvim:13519): CRITICAL **: unity_gtk_menu_item_get_icon: assertion 
'UNITY_GTK_IS_MENU_ITEM (item)' failed
+ ```
+ 
+ [[TEST CASE #2]]
+ 
+ 1. From a terminal window, launch the GTK 3 variant of Gvim:
+ 
+   $ vim.gtk3
+ 
+ 2. Upon the window opening, attempt to open a new tab by entering
+the key sequences ":tabnew" and pressing . The
+program should now SEGV and abort.
+ 
+ [Regression Potential]
+ 
+ * The bug is possibly applicable to all later Ubuntu releases,
+   which combine Unity and GTK 3.
+ 
+ * The upstream Vim project has not incorporated the fix, and
+   most likely will not. The specifics behind the fix might
+   be construed as too specific to the combination of Ubuntu,
+   Unity, and GTK 3; and not general enough to patch for all
+   downstream distributions.
+ 
+ [Other Info]
+ 
+ * Further information about this bug is available at the URLs:
+   https://github.com/vim/vim/issues/851
+   https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1650666
+ 
+ ---
+ 
  When I open new tab using :tabnew command, GVim crashes in
  unity_gtk_menu_section_get_item_attributes function of libunity-
  gtk3-parser0 package.
- 
  
  Steps to reproduce:
  1. Run gvim from vim-gtk3 package
  2. Type `:tabnew`
  3. GVim exits, the window closes
- 
  
  Stack trace obtained via gdb:
  
  mymedia@comp2:~$ gdb -silent --args gvim -f -u /dev/null -U /dev/null 
--noplugin
  Reading symbols from gvim...(no debugging symbols found)...done.
  gdb$ run
  Starting program: /usr/bin/gvim -f -u /dev/null -U /dev/null --noplugin
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffe986d700 (LWP 11042)]
  [New Thread 0x7fffe906c700 (LWP 11043)]
  [New Thread 0x7fffe886b700 (LWP 11044)]
  
  (gvim:11038): GLib-CRITICAL **: g_ptr_array_insert: assertion 'index_ <=
  (gint)rarray->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_child_shell:
  assertion 'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_shell_get_item: assertion
  '0 <= index && index < items->len' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_label: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  ** (gvim:11038): CRITICAL **: unity_gtk_menu_item_get_icon: assertion
  'UNITY_GTK_IS_MENU_ITEM (item)' failed
  
  Thread 1 "gvim" received signal SIGSEGV, Segmentation fault.
- unity_gtk_menu_section_get_item_attributes (model=, 
item_index=, 
- attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
+ unity_gtk_menu_section_get_item_attributes (model=, 
item_index=,
+ attributes=0x7fff8b90) at ../../../lib/unity-gtk-menu-section.c:130
  130   ../../../lib/unity-gtk-menu-section.c: Нет такого файла или каталога.
- gdb$ backtrace 
+ gdb$ backtrace
  #0  0x7fffe9a82083 in unity_gtk_menu_section_get_item_attributes 
(model=, item_index=, attributes=0x7fff8b90) 
at ../../../lib/unity-gtk-menu-section.c:130
  #1  0x7653f23c in 

[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

With a fully updated daily image (lxc launch ubuntu-daily:artful; lxc
exec  apt update; lxc exec  apt full-upgrade; lxc
exec  reboot; lxc exec  systemctl status):

State: running
 Jobs: 0 queued
   Failed: 0 units

Nice work everyone!

Now, ideally, any package that shows up in the container image by
default is checked that this doesn't regress going forward :)

** Changed in: lvm2 (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

** Changed in: open-iscsi (Ubuntu)
 Assignee: Nish Aravamudan (nacc) => (unassigned)

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in nfs-utils package in Ubuntu:
  New
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1709670] Re: logrotate never recovers if the statefile is corrupted

[Nish Aravamudan]

Sponsored to artful.

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

Title:
  logrotate never recovers if the statefile is corrupted

Status in logrotate package in Ubuntu:
  In Progress
Status in logrotate source package in Trusty:
  Confirmed
Status in logrotate source package in Xenial:
  Confirmed
Status in logrotate source package in Zesty:
  Confirmed
Status in logrotate source package in Artful:
  In Progress
Status in logrotate package in Debian:
  Unknown

Bug description:
  [Impact]

  logrotate never recovers if the statefile is corrupted unless you remove it 
or fix the corruption by hand.
  System will eventually run out of disk space on /var/log for instance.

  [Test Case]

  - Install logrotate
  - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate 
the statefile "var/lib/logrotate/status"
  - Modify "/var/lib/logrotate/status" by removing the first line in order to 
corrupt the file
  - Re-run "/etc/cron.daily/logrotate" and one will get the following error : 
"error: bad top line in state file /var/lib/logrotate/status" every time you 
run logrotate

  Unless you remove the statefile and start again or fix the corruption
  by hand.

  [Regression Potential]

   * Risk of potential regression is low, and IMHO couldn't be worst than the 
actual situation where logrotate simply doesn't recover from a corrupt 
statefile.
   
   * The current patch does recover (after verification) and has been through 
some upstream CI validation, community feedbacks, et al.

  [Other Info]

  * Upstream commit:
  
https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a

  * Upstream bug:
  https://github.com/logrotate/logrotate/issues/45

  * Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1671951] Re: networkd should allow configuring IPV6 MTU

[Nish Aravamudan]

Unsubscribing sponsors based upon IRC discussion with rharper:

10:57 < nacc> rharper: is LP: #1671951 actually ready to sponsor?
10:57 < ubottu> Launchpad bug 1671951 in systemd (Ubuntu) "networkd should 
allow configuring IPV6 MTU" [Medium,New] 
https://launchpad.net/bugs/1671951
11:07 < rharper> nacc: it was, but not sure of the status now;  the debdiff 
 likely needs refreshed against systemd in artful;  I'm not 
 sure of xnox or anyone else attempted to re-work the issue 
 upstream;
11:08 < nacc> rharper: ok, can i unsub sponsors for now?
11:08 < rharper> sure

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd package in Ubuntu:
  New

Bug description:
  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  
  Some context from those discussions

  
  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+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 1700826] Re: please include numactl on the ubuntu-server iso

[Nish Aravamudan]

1), 2) and 3) done and approved/merged.

Now the AAs need to do the actual pocket copy & promotion for the older
releases.

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+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 1700826] Re: please include numactl on the ubuntu-server iso

[Nish Aravamudan]

** Changed in: ubuntu-meta (Ubuntu Zesty)
   Status: In Progress => Fix Committed

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+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 1700826] Re: please include numactl on the ubuntu-server iso

[Nish Aravamudan]

** Changed in: ubuntu-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Zesty:
  Fix Committed

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+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 1700826] Re: please include numactl on the ubuntu-server iso

[Nish Aravamudan]

Here is my understanding of next steps:

1) A MP should be submitted against the Artful seeds to update the 17.10 
image(s) (which have not been release-published yet). On the next run, that 
will lead to numactl showing up in main in 17.10.
2) A MP should be submitted against the Zesty seeds to update the 17.04 
publishing.
3) A MP should be submitted against the Xenial seeds to update the 16.04 
publishing.
4) A request needs to be made to the AAs to actually move the binary package in 
the released series. They will need to do a pocket copy from $series/universe 
to $series-updates/main of the same version, since the $series release pocket 
is frozen. This will lead to numactl showing up in main in 17.04 and 16.04.
5) When the 16.04.3 ISOs are built, presuming 4) is complete for 16.04, then 
numactl should show up on the ISO.

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

Title:
  please include numactl on the ubuntu-server iso

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-meta source package in Zesty:
  New

Bug description:
  I've submitted an MIR for the numactl binary package at: LP: #1700824.
  Assuming that is approved, please also include this on the server seed, which 
I believe is necessary for it to appear on the ubuntu-server ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+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 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Nish Aravamudan]

This is bit of a funky SRU (IMO). It seems like we want version 2 (from
the linked repository) in all releases > 12.04. However, given that is
not yet present in any release != 12.04, I'm not sure we need to worry
about the exact version (that is, they can all be 2?).

My immediate feedback is the debian/changelog from the linked repo
should be for artful, not precise. Then that can be backported (I think)
to all releases != 12.04. If this already existed, it seems like it
would say "trusty" and then have been copied forward.

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  New
Status in ubuntu-meta source package in Trusty:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-meta source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Yakkety:
  New
Status in ubuntu-meta source package in Yakkety:
  New
Status in ubuntu-advantage-tools source package in Zesty:
  New
Status in ubuntu-meta source package in Zesty:
  New
Status in ubuntu-advantage-tools source package in Artful:
  New
Status in ubuntu-meta source package in Artful:
  New

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Nish Aravamudan]

@zwets, to be clear, file the bug at: https://bugs.launchpad.net
/~ubuntu-motd

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Nish Aravamudan]

@zwets, would you be willing to file a new bug? It's basically a clarity
issue on the messsage itself. It isn't actually saying you are running
16.10 or 17.04 or anything else. It's just letting you know that 16.10
goes EOL soon. So update your machines. But not necessarily that this
particular machine needs updating. It's confusing and I think deserves a
bit of rewriting to be clearer (maybe using the lsb user_agent to change
the exact text of the message).

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Nish Aravamudan]

@zwets: agreed, I see that as well. I assume the server side of
motd.ubuntu.com is not using the USER_AGENT lsb value correctly?

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

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+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 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just

[Nish Aravamudan]

Sponsored the upload to Trusty.

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

Title:
  ntpdate startup routine prevents ntp service from launching up on
  Ubuntu 16.04 server on system boot; manually starting ntp service
  works: [FIX in DESCRIPTION], just need to apply it and release a new
  version

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Trusty:
  In Progress
Status in ntp source package in Xenial:
  In Progress
Status in ntp source package in Yakkety:
  In Progress
Status in ntp source package in Zesty:
  In Progress

Bug description:
  [Impact]

   * Fixes several broken cases, those are:
   * Case 1 - ntp configured to drift time slowly, but time jumping
   - ntp is running and drifts time towards a target being way off
   - an interface comes up
   - stop ntpd
   - warp time via ntpdate-debian (static interfaces will even set -b)
   - (re-)start ntpd
   - if users relied on non-time warp they are now in trouble

   * Case 2 - ntp start/stop storms
   - ntpd comes up normally
   - the admin brings interfaces up/down rather often
   - ntp is restarted very very often due to this for no reason
   => reason for bugs like debian 823533

   * Case 3 - unintentional enablement of ntp
   - ntpd is installed but disabled (for whatever reason)
   - all is fine on any ifup/down
   - one installs ntpdate, maybe even without realizing due to a depends
   - now on the next ifup ntpd (or openntpd) will be started

   * Solution, drop the broken Delta

  [Test Case]

   * Testing Case 2/3 as it is the easiest, case 1 needs a more complex 
 setup to cause the time drift but otherwise works the same way.
 - install ntp and ntpdate
 - stop ntp
 - ifup/ifdown an interface multiple times; as simplification you can 
   also call /etc/network/if-up.d/ntpdate directly (not that this 
   spawns the change asnchronous and locks concurrency, so do that a 
   few times over the time of a minute or so)
 - the service of ntp should still be stopped and not report plenty of 
   restarts

  
  [Regression Potential] 

   * It improves a lot of cases (otherwise we wouldn't SRU), but there is 
 one regression potential I can see:

 - users that relied on starting NTP later on after other interfaces 
   got up due to that code in ntpdate which did that as a side effect. 
   But that is outweigh by Case2/3 for the majority of users. And even 
   Case1 only hits this potential regression on e.g. late network 
   intialization, but in that case please remind that the default 
   (systemd timedatectl) would handle that.

 - Since most users of ntp do not install ntpdate (which doesn't work 
   when ntp is active) we should be rather safe to assume that almost 
   no one should rely on that side effect.

 - Furthermore this is a Ubuntu Delta for very long, cause issues (see 
   the references on the git commit) but never made it into Debian - 
   in that sense another indicator it isn't an important delta to 
   have.

  [Other Info]
   
   * The original intention "what if net is available too late" fixed 
 correctly would not be part of ntpdate, but ntp and additionally 
 check if it is actually meant to be enabled - but I never seen/heard 
 of any of it since systemd is around - maybe new ordering mostly 
 avoids the original issue.


  ---

  
  I've installed ntp service on the clean ubuntu 16.04 server system. 
Configured it. Checked that it works, but, after reboot, it doesn't start 
automatically.
  When I check: 'systemctl is-enabled ntp', it shows enabled.
  If I manually start it 'systemctl start ntp' it starts just fine and woks 
correctly,
  but until I manually start it, 'systemctl status ntp' shows:

  Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
  Active: inactive (deadi)

  Installed 1.29ubuntu2 version of init-systems-helper, but it didn't
  fix the problem.

  Found a bugreport on ntpd package:

  https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596

  led to solution that involves a change to be made in file:

  /etc/network/if-up.d/ntpdate

  of ntpdate package

  After changing from:
  __CODE_START__

  invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s $OPTS 2>/dev/null 
|| :

  invoke-rc.d --quiet $service start >/dev/null 2>&1 || true

  __CODE_END__

  to:
  __CODE_START__

  systemctl --quiet stop $service.service >/dev/null 2>&1 || true

   # Avoid running more than one at a time
   flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s 

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@kai-holthaus: after editing the service file, did you issue a `sudo
systemctl daemon-reload` ?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@Kai: Hrm, that is odd -- was your 16.04 system the fresh install or an
upgraded one?

The lines I pasted in #49 are supposed to be present in 16.04 (afaict).

If they don't, can you provide `apt policy open-iscsi` in a pastebin?
And can you test if changing those lines to match fixes the issue there?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@Kai: In xenial, open-iscsi.service should have the following lines
alreadY

Wants=network-online.target remote-fs-pre.target iscsid.service
After=network-online.target iscsid.service

Can you confirm that is the case on your system?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 962616] Re: mii-tool assumes NIC names of the form eth* when given no interface(s) as argument

[Nish Aravamudan]

** Also affects: net-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: net-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  mii-tool assumes NIC names of the form eth* when given no interface(s)
  as argument

Status in net-tools package in Ubuntu:
  Fix Released
Status in net-tools source package in Trusty:
  Won't Fix
Status in net-tools source package in Xenial:
  Won't Fix

Bug description:
  On a system with biosdevname enabled, which names NICs in the forms
  em* and p*p*, mii-tool will return the message "no MII interfaces
  found" if mii-tool is called without specifying an interface. The
  correct behavior would be to iterate through em* and p*p*. (More
  information on biosdevname can be found at
  
http://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/962616/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@kai-holthause or @gimpeystrada: would either of you be able to test
with the daily artful (17.10) ISO?

@kai-holthause: I think you did find a real ordering issue, nicely done
:)

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  New

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@kai-holthaus: also, afaict, that might mean you are hitting a
*different* bug (yay for so many bugs) in open-iscsi relative to
@gimpeystrada, as @gimpeystrada and others in this channel have said
they experience this issue with a fresh install of 16.04 (16.10 and
17.04 as well). That's ok, we can look at the journal and figure it out
first, but the end result might be opening another bug.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@kai-holthaus: Thank you for the excellent data point, again, and for
your willingness to provide the data!

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@kai-holthaus: thank you for responding so quickly. Can you set up a
persistent journal as described in c#8 and provide the journal as
mentioned in that comment for the failed shutdown?

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@gimpeystrada: Thank you for providing your journal logs (in the future,
providing the raw journal file is better, as then we can run
`journalctl` on it locally). From the logs:

Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: iscsiadm: initiator reported 
error (8 - connection timed out)
Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: iscsiadm: Could not log into all 
portals
Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: :0113,3260] successful.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Child 3234 
belongs to open-iscsi.service
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Main process 
exited, code=exited, status=8/n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Changed start -> 
failed
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=936 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd-logind[2801]: Got message type=signal 
sender=:1.2 destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=936 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Job 
open-iscsi.service/start finished, result=failed
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Failed to start Login to default 
iSCSI targets.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=937 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Unit entered 
failed state.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Failed with 
result 'exit-code'.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: cgroup is empty

I *think* the issue in this case is that open-iscsi.service is actually
in a failed state before shutdown, which I think means it does not run
the ExecStop commands? Can you verify that is the case (boot your
system, `systemctl is-system-running` should indicate "degraded",
`systemctl status open-iscsi.service` should indicate Failed). The
problem is that the open-iscsi.service has:

ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
ExecStart=/sbin/iscsiadm -m node --loginall=automatic
ExecStart=/lib/open-iscsi/activate-storage.sh
ExecStop=/lib/open-iscsi/umountiscsi.sh
ExecStop=/bin/sync
ExecStop=/lib/open-iscsi/logout-all.sh

This indicates it, on 'start' of the service, it will try to login to
and active all configured iSCSI targets (the two ExecStart lines).
However, if either of those fail (as they did in the journal in this
case), the ExecStop lines *do not* run. From `man systemd.service`:

   Note that if any of the commands specified in ExecStartPre=,
   ExecStart=, or ExecStartPost= fail (and are not prefixed with "-",
   see above) or time out before the service is fully up, execution
   continues with commands specified in ExecStopPost=, the commands in
   ExecStop= are skipped.

So, I think that we should be using ExecStopPost instead.

@gimpeystrada, can you test locally if your system works correctly by
editing /lib/systemd/system/open-iscsi.service to use ExecStopPost
rather than ExecStop? You will need to run `systemctl daemon-reload`
after editing the service file, I believe.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 

[Touch-packages] [Bug 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions

[Nish Aravamudan]

** Changed in: openssh (Ubuntu Trusty)
   Status: Confirmed => Triaged

** Tags added: server-next

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

Title:
  sshd-ConsoleKit integration patch causes abrupt termination of
  multichannel sessions

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged

Bug description:
  Attached to this report is a small app the reproduces the issue by creating 
multiple channels within one sessions. (I fist hit this issue using JSCH 
library)
  Following information is printed to stdout if sshd is launched with -d flags 
(I've modified the sshd code to print PIDs next to debug level):
  debug3(7526): monitor_read: checking request 156
  debug3(7526): mm_answer_consolekit_register entering
  debug1(7526): session_by_tty: session 0 tty /dev/pts/1
  debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1
  debug1(7573): session_by_channel: session 2 channel 2
  debug1(7573): session_input_channel_req: session 2 req pty-req
  debug1(7573): Allocating pty.
  debug3(7573): mm_request_send entering: type 28
  debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY
  debug3(7573): mm_request_receive_expect entering: type 29
  debug3(7573): mm_request_receive entering
  debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was 
not provided by any .service files
  debug3(7526): mm_request_send entering: type 157
  debug3(7526): mm_request_receive entering
  debug3(7526): monitor_read: checking request 28
  debug3(7526): mm_answer_pty entering
  debug2(7526): session_new: allocate (allocated 2 max 10)
  debug3(7526): session_unused: session id 2 unused
  debug1(7526): session_new: session 2
  mm_request_receive_expect: read: rtype 157 != type 29

  From the log, it looks as if two processes use the same set of pipes
  to communicate to the monitor, one of them is sending
  MONITOR_REQ_CONSOLEKIT_REGISTER, while another  MONITOR_REQ_PTY, and
  because they use same set of pipes, and because both processes use
  same pipe FDs, monitor reply is sometimes delivered to the wrong
  process.

  I can reproduce the failure 90% of time using attached app, which expects 
first argument to be host name, second - login and the third - password, that 
are defaulted to ubuntu:ubuntu@localhost:
  $ ./ssh-multisession 
  Connecting to localhost...Done!
  Authenticating as ubuntu...Done.
  Starting channel 0
  Starting channel 1
  ssh_channel_request_pty()=-1: Socket error: disconnected
  Starting channel 2
  ssh_channel_open_session()=-1: Writing packet: error on socket (or connection 
closed): Operation now in progress
  Starting channel 3

  The same script works fine if sshd is compiled without consolekit.patch:
  ./ssh-multisession debian-host debian debian
  Connecting to 172.17.162.237...Done!
  Authenticating as debian...Done.
  Starting channel 0
  Starting channel 1
  Starting channel 2
  Starting channel 3
  Starting channel 4
  Starting channel 5
  Starting channel 6
  Starting channel 7
  Starting channel 8
  Starting channel 9

  P.S. To compile a test app one needs to have libssh-dev package
  installed on your system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+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 1334916] Re: sshd-ConsoleKit integration patch causes abrupt termination of multichannel sessions

[Nish Aravamudan]

** Also affects: openssh (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  sshd-ConsoleKit integration patch causes abrupt termination of
  multichannel sessions

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Triaged

Bug description:
  Attached to this report is a small app the reproduces the issue by creating 
multiple channels within one sessions. (I fist hit this issue using JSCH 
library)
  Following information is printed to stdout if sshd is launched with -d flags 
(I've modified the sshd code to print PIDs next to debug level):
  debug3(7526): monitor_read: checking request 156
  debug3(7526): mm_answer_consolekit_register entering
  debug1(7526): session_by_tty: session 0 tty /dev/pts/1
  debug1(7573): server_input_channel_req: channel 2 request pty-req reply 1
  debug1(7573): session_by_channel: session 2 channel 2
  debug1(7573): session_input_channel_req: session 2 req pty-req
  debug1(7573): Allocating pty.
  debug3(7573): mm_request_send entering: type 28
  debug3(7573): mm_pty_allocate: waiting for MONITOR_ANS_PTY
  debug3(7573): mm_request_receive_expect entering: type 29
  debug3(7573): mm_request_receive entering
  debug1(7526): Unable to open session: The name org.freedesktop.ConsoleKit was 
not provided by any .service files
  debug3(7526): mm_request_send entering: type 157
  debug3(7526): mm_request_receive entering
  debug3(7526): monitor_read: checking request 28
  debug3(7526): mm_answer_pty entering
  debug2(7526): session_new: allocate (allocated 2 max 10)
  debug3(7526): session_unused: session id 2 unused
  debug1(7526): session_new: session 2
  mm_request_receive_expect: read: rtype 157 != type 29

  From the log, it looks as if two processes use the same set of pipes
  to communicate to the monitor, one of them is sending
  MONITOR_REQ_CONSOLEKIT_REGISTER, while another  MONITOR_REQ_PTY, and
  because they use same set of pipes, and because both processes use
  same pipe FDs, monitor reply is sometimes delivered to the wrong
  process.

  I can reproduce the failure 90% of time using attached app, which expects 
first argument to be host name, second - login and the third - password, that 
are defaulted to ubuntu:ubuntu@localhost:
  $ ./ssh-multisession 
  Connecting to localhost...Done!
  Authenticating as ubuntu...Done.
  Starting channel 0
  Starting channel 1
  ssh_channel_request_pty()=-1: Socket error: disconnected
  Starting channel 2
  ssh_channel_open_session()=-1: Writing packet: error on socket (or connection 
closed): Operation now in progress
  Starting channel 3

  The same script works fine if sshd is compiled without consolekit.patch:
  ./ssh-multisession debian-host debian debian
  Connecting to 172.17.162.237...Done!
  Authenticating as debian...Done.
  Starting channel 0
  Starting channel 1
  Starting channel 2
  Starting channel 3
  Starting channel 4
  Starting channel 5
  Starting channel 6
  Starting channel 7
  Starting channel 8
  Starting channel 9

  P.S. To compile a test app one needs to have libssh-dev package
  installed on your system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916/+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 1662520] Re: openssh-server abruptly terminates multichannel sessions

[Nish Aravamudan]

*** This bug is a duplicate of bug 1334916 ***
https://bugs.launchpad.net/bugs/1334916

Hello and thank you for filing this bug report. I've opened a task in
the other bug for Trusty and that is the best place to follow up on it.

** This bug has been marked a duplicate of bug 1334916
   sshd-ConsoleKit integration patch causes abrupt termination of multichannel 
sessions

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

Title:
  openssh-server abruptly terminates multichannel sessions

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  The bug fixed in
  https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1334916
  (1:6.9p1-3) was never released for Ubuntu 14.04. The symptoms in
  openssh-server 1:6.6p1-2ubuntu2.8 are exactly the same as reported in
  that bug.

  Unfortunately, moving from 14.04 to a more recent release like 16.04
  isn't an option for us. Neither is reverting to the previous release
  for 14.04, due to the security vulns that were fixed in the latest
  release.

  I'm happy to supply more information if required.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-server 1:6.6p1-2ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Feb  7 13:35:30 2017
  InstallationDate: Installed on 2015-03-13 (696 days ago)
  InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014)
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1662520/+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 1694659] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nish Aravamudan]

Hello and thank you for filing this bug report.

It appears you have a local configuration error, as indicated by sshd:

 Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 66: Bad configuration option: X11UseForwarding
 /etc/ssh/sshd_config: terminating, 1 bad configuration options

Per `man sshd_config`, you want either:

X11Forwarding
or
X11UseLocalhost

But I don't know which you intended. "X11UseForwarding" is not a valid
option, though.

** Changed in: openssh (Ubuntu)
   Status: New => Invalid

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  Can't upgrade my ubuntu because of this

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed May 31 11:55:36 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-27 (92 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 66: Bad configuration option: X11UseForwarding
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1694659/+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 1693944] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Nish Aravamudan]

** Changed in: openssh (Ubuntu)
   Status: New => Invalid

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I was doing a normal update and got this error message at the end.

  I'm new to Ubuntu and I honestly don't know what the problem could be.
  I've not had problems with OpenSSH before

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri May 26 18:39:19 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-06 (232 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693944/+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 1682136] Re: dnsmasq bad hex constant with 2 mac addresses but not true

[Nish Aravamudan]

** Changed in: dnsmasq (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  dnsmasq bad hex constant with 2 mac addresses but not true

Status in dnsmasq package in Ubuntu:
  Invalid

Bug description:
  Following line of dnsmasq.conf will not allow dnsmasq to start giving
  error "bad hex constant at line x in /etc/dnsmasq.conf" and this
  despite the fact that there is no error in mac addresses.

  dhcp-
  
host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

  With only one of those two mac addresses, all is good, so there is no
  error in mac addresses. In the dnsmasq.conf they are other dhcp-host
  with multiple mac addresses like

  dhcp-
  
host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

  and they are not rejected.

  When copying the default configuration line in a dnsmasq-2.72-3 of
  Debian 8.7, no problem.

  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  dnsmasq:
Installé : 2.59-4ubuntu0.2
Candidat : 2.59-4ubuntu0.2
   Table de version :
   *** 2.59-4ubuntu0.2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   2.59-4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
  ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  Date: Wed Apr 12 15:25:20 2017
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682136/+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

Re: [Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

On Wed, May 24, 2017 at 1:45 PM, Scott <1569...@bugs.launchpad.net> wrote:
> Fresh install 16.04 download ISO from ubuntu
> Can confirm this issue as well.
> If I manually log out of the iscsi session reboot no issue

Interesting data point.

> If I am logged into iscsi session reboot hangs. Need to physically
power cycle server

I think the open-iscsi or iscsid services have a killall sessions
portion when the service shuts down. I wonder if that's either a) not
running or b) somehow incorrect. I could imagine for iSCSI root it'd
be an issue, but for non-root, I'm not sure why that's not working.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+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 1689833] Re: OpenVPN server does not start properly on boot

[Nish Aravamudan]

Thank you for reporting this bug. I will add it to the server team
backlog, as it does appear to be a real issue.

** Changed in: openvpn (Ubuntu)
   Status: New => Triaged

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

Title:
  OpenVPN server does not start properly on boot

Status in openvpn package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  OpenVPN intermittently fails to bind to local address during boot on
  Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does
  not.

  /var/log/openvpn.log
  Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:02 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address 
[AF_INET]192.168.4.254:1194: Cannot assign requested address
  Wed May 10 15:42:02 2017 Exiting due to fatal error

  In case it does not start, running 'sudo service openvpn start' fixes
  that problem.

  /var/log/openvpn.log
  Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:43 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 
HWADDR=52:54:00:f0:26:0c
  Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened
  Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100
  Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, 
tt->did_ifconfig_ipv6_setup=0
  Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500
  Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 
172.16.1.2
  Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2
  Wed May 10 15:42:43 2017 GID set to nogroup
  Wed May 10 15:42:43 2017 UID set to nobody
  Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194
  Wed May 10 15:42:43 2017 UDPv4 link remote: [undef]
  Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256
  Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0
  Wed May 10 15:42:43 2017 IFCONFIG POOL LIST
  Wed May 10 15:42:43 2017 Initialization Sequence Completed

  My guess is that systemd starts OpenVPN too early before the network
  is brought up sufficiently. Running 'sudo systemctl edit --full
  openvpn' and adding 'Wants=network-online.target' does not change that
  behaviour.

  user@server:~$ sudo systemd-analyze critical-chain
  graphical.target @2.160s
  └─multi-user.target @2.159s
    └─ntp.service @2.054s +104ms
  └─remote-fs.target @2.052s
    └─remote-fs-pre.target @2.052s
  └─open-iscsi.service @1.993s +57ms
    └─iscsid.service @1.942s +47ms
  └─network-online.target @1.941s
    └─network.target @1.929s
  └─networking.service @1.793s +134ms
    └─apparmor.service @1.140s +395ms
  └─local-fs.target @1.140s
    └─local-fs-pre.target @1.139s
  └─lvm2-monitor.service @602ms +536ms
    └─lvm2-lvmetad.service @773ms
  └─systemd-journald.socket @574ms
    └─-.slice @500ms

  The boot time is quite short. Clean install with the additional
  packages ntp and openssh-server. This happens both on bare metal and
  as a Virtual Machine (KVM) as well.

  /etc/openvpn/server.conf
  local 192.168.4.254
  port 1194
  proto udp
  dev tun
  ca ./easy-rsa/keys/ca.crt
  cert ./easy-rsa/keys/crt.crt
  key ./easy-rsa/keys/key.key
  dh ./easy-rsa/keys/dh2048.pem
  tls-auth ./easy-rsa/keys/ta.key 0
  server 172.16.1.0 255.255.255.0

[Touch-packages] [Bug 1689144] Re: package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Nish Aravamudan]

Translated from DpkgTerminalLog:

Preparing to unpack ... / libnss3_2% 3a3.28.4-0ubuntu0.17.04.1_amd64.deb ...
Unpacking libnss3: amd64 (2: 3.28.4-0ubuntu0.17.04.1) about (2: 
3.26.2-1ubuntu1) ...
Preparing to unpack ... / libxslt1.1_1.1.29-2ubuntu0.1_amd64.deb ...
Unpacking libxslt1.1: amd64 (1.1.29-2ubuntu0.1) on (1.1.29-2) ...
Dpkg: error processing package libnspr4: amd64 (--configure):
 The package is in a bad state of inconsistency; Should
 Reinstall it before attempting to configure it.
Configuring libxslt1.1: amd64 (1.1.29-2ubuntu0.1) ...
Processing 'triggers' for libc-bin (2.24-9ubuntu2) ...
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplc4.so is not a symbolic link

/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libnspr4.so is not a
symbolic link

/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/libplds4.so is not a
symbolic link

Dpkg: problems with dependencies prevent the configuration of libnss3: amd64:
 Libnss3: amd64 depends on libnspr4 (> = 2: 4.12); However:
  Package libnspr4: amd64 is not configured yet.

Dpkg: error processing package libnss3: amd64 (--configure):
 Dependency problems - leaving unconfigured

I believe your system is in a very inconsistent state and am unable to
reproduce this. As far as I can tell, there is no bug in nss, but when
libnspr4 is installed, issues are seen. Please manually try and
reinstall libnspr4 and see if the issues go away.

** Changed in: nss (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to
  install/upgrade: problemas de dependência - deixando desconfigurado

Status in nss package in Ubuntu:
  Incomplete

Bug description:
  Não sei muito bem somente que o sistema pediu para relatar para os
  desenvolvedores

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering:
   libnss3:amd64: Install
   libxslt1.1:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun May  7 12:49:50 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-05-06 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: nss
  Title: package libnss3:amd64 2:3.28.4-0ubuntu0.17.04.1 failed to 
install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1689144/+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 1689204] Re: dpkg: error processing archive /var/cache/apt/archives/init-system-helpers_1.29ubuntu4_all.deb (--unpack): trying to overwrite '/usr/sbin/invoke-rc.d', which is also

[Nish Aravamudan]

I am unable to reproduce this issue. Per the changelog, sysv-rc (from
src:sysvinit) dropped the invoke.rc bits in 2.88dsf-59.3ubuntu1:

sysvinit (2.88dsf-59.3ubuntu1) xenial; urgency=low

  * Dropped various changes for invoke.rc which has moved to
init-system-helpers.


# apt install --reinstall sysv-rc init-system-helpers
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 2 reinstalled, 0 to remove and 15 not upgraded.
Need to get 50.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 sysv-rc all 
2.88dsf-59.3ubuntu2 [18.2 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
init-system-helpers all 1.29ubuntu4 [32.3 kB]
Fetched 50.5 kB in 0s (61.0 kB/s)   
Preconfiguring packages ...
(Reading database ... 25504 files and directories currently installed.)
Preparing to unpack .../init-system-helpers_1.29ubuntu4_all.deb ...
Unpacking init-system-helpers (1.29ubuntu4) over (1.29ubuntu4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up init-system-helpers (1.29ubuntu4) ...
(Reading database ... 25504 files and directories currently installed.)
Preparing to unpack .../sysv-rc_2.88dsf-59.3ubuntu2_all.deb ...
Unpacking sysv-rc (2.88dsf-59.3ubuntu2) over (2.88dsf-59.3ubuntu2) ...
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up sysv-rc (2.88dsf-59.3ubuntu2) ...

and dpkg agrees that sysv-rc no longer contains any invoke-rc
references:

# dpkg -L sysv-rc
/.
/etc
/etc/rc0.d
/etc/rc0.d/README
/etc/init.d
/etc/init.d/rcS
/etc/init.d/README
/etc/init.d/rc
/etc/rc3.d
/etc/rc3.d/README
/etc/rc1.d
/etc/rc1.d/README
/etc/rcS.d
/etc/rcS.d/README
/etc/rc2.d
/etc/rc2.d/README
/etc/rc6.d
/etc/rc6.d/README
/etc/rc5.d
/etc/rc5.d/README
/etc/rc4.d
/etc/rc4.d/README
/var
/var/lib
/var/lib/insserv
/usr
/usr/share
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/sysv-rc
/usr/share/doc
/usr/share/doc/sysv-rc
/usr/share/doc/sysv-rc/copyright
/usr/share/doc/sysv-rc/README.Debian
/usr/share/doc/sysv-rc/NEWS.Debian.gz
/usr/share/doc/sysv-rc/README.runlevels.gz
/usr/share/sysv-rc
/usr/share/sysv-rc/saveconfig
/usr/share/doc/sysv-rc/changelog.Debian.gz

Can you provide any more details, and perhaps the output for `apt policy
sysv-rc`?

** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

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

Title:
  dpkg: error processing archive /var/cache/apt/archives/init-system-
  helpers_1.29ubuntu4_all.deb (--unpack):  trying to overwrite
  '/usr/sbin/invoke-rc.d', which is also in package sysv-rc
  2.88dsf-59.3ubuntu2

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  I was trying to do a normal apt-get upgrade when I started to run into
  issues. I am not sure how to fix this since it is a system package.
  This system was upgraded from 14.04 to 16.04, but it was working fine
  for awhile.

  I started in this thread, but I could not get it working.
  https://ubuntuforums.org/showthread.php?t=2359412

  This machine is now a Proxmox VM, so I have the option to do some
  testing with it.

  
  #: apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
bsdutils linux-generic linux-headers-generic linux-image-generic
  The following packages will be upgraded:
apparmor apt apt-transport-https apt-utils bind9-host console-setup 
console-setup-linux dbus dbus-x11 desktop-file-utils distro-info-data dnsutils 
docker-engine
dpkg-dev eject graphviz grub-common grub-pc grub-pc-bin grub2-common init 
init-system-helpers initramfs-tools initramfs-tools-bin initramfs-tools-core
keyboard-configuration klibc-utils krb5-locales krb5-multidev 
libapparmor-perl libapparmor1 libapt-inst2.0 libapt-pkg5.0 libarchive13 
libbind9-140 libblkid1
libc-bin libc-dev-bin libc6 libc6-dev libcdt5 libcgraph6 libdbus-1-3 
libdns-export162 libdns162 libdpkg-perl libdrm-amdgpu1 libdrm-intel1 
libdrm-nouveau2
libdrm-radeon1 libdrm2 libevent-2.0-5 libevent-core-2.0-5 libfdisk1 
libfreetype6 libfreetype6-dev libgc1c2 libgd-dev libgd3 libgl1-mesa-dri 
libgl1-mesa-glx
libglapi-mesa libglib2.0-0 libglib2.0-data libgnutls-openssl27 libgnutls30 
libgssapi-krb5-2 libgssrpc4 libgvc6 libgvpr2 libhogweed4 libicu55 
libisc-export160
libisc160 libisccc140 libisccfg140 libk5crypto3 libkadm5clnt-mit9 
libkadm5srv-mit9 libkdb5-8 libklibc libkrb5-3 libkrb5support0 liblwres141 
libmount1
libmysqlclient-dev libmysqlclient20 libnettle6 libpam-systemd libpathplan4 
libpci-dev libpci3 libpq-dev 

[Touch-packages] [Bug 1683095] Re: rsync has -C / --cvs-exclude enabled permanently

[Nish Aravamudan]

Hello and thank you for filing this bug report.

Can you provide (perhaps as attachments if needed) an example command
and output that show the exact issue?

Please mark it as New once you have done so.

** Changed in: rsync (Ubuntu)
   Status: New => Incomplete

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

Title:
  rsync has -C / --cvs-exclude enabled permanently

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I've noticed that every rsync command
  has the -C option added and I can see no way to disable this very
  unwanted behavior. I've been running the same set of rsync commands
  for years and the -C option was never tacked on like it is now (as far
  as I can tell). I've read the man pages, checked the various config
  files, tried adding --no-C to all of my scripts (as annoying as that
  is) and still see no functioning way to disable this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1683095/+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 1682227] Re: dnsmasq, network manager *still* not able to relay DNS queries or respond to DNS requests after VPN connection failure / die off

[Nish Aravamudan]

Thank you very much for filing this bug report. It seems like it is a
real issue and I will place it on the Server Team's backlog for now.

** Changed in: dnsmasq (Ubuntu)
   Status: New => Triaged

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

Title:
  dnsmasq, network manager *still* not able to relay DNS queries or
  respond to DNS requests after VPN connection failure / die off

Status in dnsmasq package in Ubuntu:
  Triaged

Bug description:
  This remains an issue.  Supposedly fixed, it's still an issue in
  16.04.

  When an OpenVPN connection enables, or dies off, dnsmasq ceases to
  respond.  The upstream DNS servers set are two bind9 instances that
  both reply to direct queries, so the core issue is that `dnsmasq` is
  broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 12 15:58:28 2017
  InstallationDate: Installed on 2016-12-20 (112 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682227/+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 1682136] Re: dnsmasq bad hex constant with 2 mac addresses but not true

[Nish Aravamudan]

Hello and thank you for filing this bug report. 12.04 has gone EOL in
the meanwhile, though. Does this issue occur with Trusty or later?

** Changed in: dnsmasq (Ubuntu)
   Status: New => Incomplete

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

Title:
  dnsmasq bad hex constant with 2 mac addresses but not true

Status in dnsmasq package in Ubuntu:
  Incomplete

Bug description:
  Following line of dnsmasq.conf will not allow dnsmasq to start giving
  error "bad hex constant at line x in /etc/dnsmasq.conf" and this
  despite the fact that there is no error in mac addresses.

  dhcp-
  
host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi

  With only one of those two mac addresses, all is good, so there is no
  error in mac addresses. In the dnsmasq.conf they are other dhcp-host
  with multiple mac addresses like

  dhcp-
  
host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi

  and they are not rejected.

  When copying the default configuration line in a dnsmasq-2.72-3 of
  Debian 8.7, no problem.

  Description:Ubuntu 12.04.5 LTS
  Release:12.04

  dnsmasq:
Installé : 2.59-4ubuntu0.2
Candidat : 2.59-4ubuntu0.2
   Table de version :
   *** 2.59-4ubuntu0.2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   2.59-4 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf]
  ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-116-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  Date: Wed Apr 12 15:25:20 2017
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682136/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

In Artful, we have (running with -proposed for open-iscsi and lvm2):

● snapd.service loaded failed failed Snappy daemon 
● snapd.socket  loaded failed failed Socket activation for snapp
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

snapd team probably need to fix the first two.

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

lvm2 fix is in 2.02.168-2ubuntu1 in artful.

** Changed in: lvm2 (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: open-iscsi (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

** Changed in: lvm2 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Fix Committed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1427807] Re: usermod's man refers to --*-sub-uids but accepts only --*-subuids

[Nish Aravamudan]

@sdeziel, afaict, that is an upstream fix committed,but not the ubuntu
package in artful.

** Changed in: shadow (Ubuntu)
   Status: Fix Committed => Triaged

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

Title:
  usermod's man refers to --*-sub-uids but accepts only --*-subuids

Status in shadow package in Ubuntu:
  Triaged

Bug description:
  The man page refers to sub-uids and sub-gids but those don't take any
  "-" between sub and [ug]ids. The help message conforms to what the
  command accepts though.

  $ man usermod | grep -F -- -sub
 -v, --add-sub-uids FIRST-LAST
 -V, --del-sub-uids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-uids and --add-sub-uids are 
specified remove of all subordinate uid ranges happens before any
 -w, --add-sub-gids FIRST-LAST
 -W, --del-sub-gids FIRST-LAST
 This option may be specified multiple times to remove multiple 
ranges to a users account. When both --del-sub-gids and --add-sub-gids are 
specified remove of all subordinate gid ranges happens before any

  $ usermod --help | grep -F -- -sub
-v, --add-subuids FIRST-LAST  add range of subordinate uids
-V, --del-subuids FIRST-LAST  remvoe range of subordinate uids
-w, --add-subgids FIRST-LAST  add range of subordinate gids
-W, --del-subgids FIRST-LAST  remvoe range of subordinate gids

  
  More info on the environment:

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ apt-cache policy passwd
  passwd:
Installed: 1:4.1.5.1-1ubuntu9
Candidate: 1:4.1.5.1-1ubuntu9
Version table:
   *** 1:4.1.5.1-1ubuntu9 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 13:37:50 2015
  InstallationDate: Installed on 2014-01-26 (400 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1427807/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

I'm going to upload rbalint's fixes in the merges for open-iscsi and
lvm2 I plan on doing this week.

** Changed in: open-iscsi (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: open-iscsi (Ubuntu)
   Status: Triaged => In Progress

** Changed in: open-iscsi (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: lvm2 (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  In Progress
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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

Re: [Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 08.05.2017 [11:25:03 -], Balint Reczey wrote:
> >> 1.b i'd like another way to do that, but not sure what a better way would
> >> be.
> > 
> > Yeah, I spent some time looking at the CPC generater and it seems like
> > this is pretty hard-coded:
> > 
> > 999-cpc-fixes.chroot:
> > ## --
> > # for maverick and newer, use LABEL= for the '/' entry in fstab
> > if [ -n "${root_fs_label}" ]; then
> >bl="[:blank:]"
> >lstr="LABEL=${root_fs_label}"
> >sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," 
> > "${rootd}/etc/fstab"
> > fi
> > cat > /etc/fstab << EOM
> > LABEL=cloudimg-rootfs / ext4 defaults 0 0
> > EOM
> 
> I think the cleanest solution would be providing images for containers
> without this invalid fstab entry.

I *think* containers and VMs use the same cloud image, so I don't think
bifurcating for this one change is reasonable.

> The second cleanest seems to be not starting
> systemd-remount-fs.service in containers, or at least not in lxc.

Except it's possible that a user might have other entries that should be
remounted, possibly? When, say, passing real disks into the container?

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1669133] Re: Drop unnecessary rename of dlm -> dlm-controld (binary package)

[Nish Aravamudan]

** Changed in: dlm (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: lvm2 (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: ocfs2-tools (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  Drop unnecessary rename of dlm -> dlm-controld (binary package)

Status in dlm package in Ubuntu:
  Triaged
Status in lvm2 package in Ubuntu:
  Triaged
Status in ocfs2-tools package in Ubuntu:
  Triaged

Bug description:
  dlm -> dlm-controld transition (will need to be kept through 18.04 for LTS 
upgraders)
- Add transitional dummy binary package to rename back
- Drop delta in lvm2 and ocfs2-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1669133/+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 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.

[Nish Aravamudan]

Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.

** Also affects: accountsservice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libpam-ldap (Ubuntu)
   Status: New => Invalid

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

Title:
  Login prompt never presented with ldap login and ldapi set with a
  name.

Status in accountsservice package in Ubuntu:
  New
Status in libpam-ldap package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  I have a ldap login configuration that has worked with several Ubuntu
  versions.

  Unfortunately it doesn't work with 16.10.

  If I left my ldapi setting using a name as I used to, the login prompt
  never appears. If I change the ldapi setting to the IP of the
  authentication server, the login works perfectly.

  The authentication server name resolution works fine on 16.10 (after
  login) and on previous version even during login.

  It seems to me my problem is related to some ordering issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libpam-ldap 184-8.7ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17
  Uname: Linux 4.8.0-44-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue Mar 28 14:33:27 2017
  InstallationDate: Installed on 2017-03-27 (1 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: libpam-ldap
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+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

Re: [Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Nish Aravamudan]

Lukas, thank you for the detailed information. However

On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko  wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while connection is active.

You seemed to have ignored Paul's message and instead provided context
which should go in a different bug.

This bug was for name resolution failing after suspend/resume. It had
nothing directly to do with VPNs. Please file a new bug.

On Mon, Apr 24, 2017 at 9:33 AM, Lukas Dzunko  wrote:
> Hello Paul. DNS leak mean that DNS queries still hit local DNS server
> while VPN connection is active. DNS resolver should query only DNS
> servers defined by VPN while connection is active.
>
> I did following test:
>
> - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
> (dnsmasq-base=2.75-1ubuntu0.16.04.2)
> - restated my laptop to ensure clean start
> - connected to VPN using openconnect / network-manager-openconnect-gnome
>
> Observed results -> DNS queries are forwarded only to DNS servers
> defined by LAN connection (this is wrong / connection not working at
> all)
>
> - "killall dnsmasq"
> - dnsmasq get automatically restarted by system
>
> Observed results -> most of the the queries are forwarded to DNS servers
> defined by VPN, but lot of queries get forwarded to DNS servers defined
> by LAN connection (this is still wrong / DNS leaks, attacker can hijack
> connection even if VPN is enabled)
>
> - I downgraded back to network-manager to 1.2.2-0ubuntu0.16.04.4 
> (dnsmasq-base stay same)
> - restated my laptop to ensure clean test
> - connected to same VPN using openconnect
>
> Observed results -> DNS queries are forwarded only to DNS servers
> defined by VPN connection. There are no leaks to LAN DNS server (this is
> correct behavior).
>
> ==
>
> DNS leaks are bad for several reasons. Most important ones are that it
> provide visibility of host names to possibly un-trusted network and give
> ability to hijack connection. When I connect to VPN server I expect that
> all traffic hit only particular vpn server / gateway. If there is query
> to "secure-company-server.example.com" and this hit DNS on LAN then we
> are instantly leaking secured names. If LAN DNS server respond to this
> (or response is spoofed) then connection will be made outside of VPN
> environment. This effectively kill security of VPN connection ...
>
> ==
>
> FYI: I am currently in environment where DHCP set DNS servers but policy
> deny connection to them (don't ask why). Therefore is much more visible
> if queries get forwarded to LAN DNS server just because they never get
> responded ... this may be reason why some of folks here claim that fix
> is working. If LAN DNS server respond with something then there is no
> visibility of problem ...
>
> ==
>
> FYI2: all tests for this update was monitored by wireshark. ... just to
> not confuse with previous "fyi" comment
>
> ==
>
> Lukas
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1639776
>
> Title:
>   name resolution (dnsmasq) fails to send queries out after
>   suspend/resume reconnects the interface
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Released
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  

[Touch-packages] [Bug 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Nish Aravamudan]

https://anonscm.debian.org/cgit/resolvconf/resolvconf.git/commit/?id=05a25d1d831ebe3955fb9641a3ba708bca68d35a

1.80 isn't out yet, so we should probably just backport the fix to the
affected releases.

** Also affects: resolvconf (Ubuntu Zesty)
   Importance: High
   Status: Confirmed

** Also affects: resolvconf (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: resolvconf (Ubuntu Aa-series)
   Importance: Undecided
   Status: New

** Also affects: resolvconf (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  New
Status in resolvconf source package in Yakkety:
  New
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in aa-series:
  New

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1593489/+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

Re: [Touch-packages] [Bug 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface

[Nish Aravamudan]

Hi Paul,

https://wiki.ubuntu.com/StableReleaseUpdates is the standard reference.

It takes at least 7 days in -proposed before the SRU team will release
it.

Thanks,
Nish

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

Title:
  name resolution (dnsmasq) fails to send queries out after
  suspend/resume reconnects the interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in network-manager source package in Xenial:
  Invalid
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in network-manager source package in Yakkety:
  Invalid
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager

[Nish Aravamudan]

@Alberto,

why did you mark the samba task critical? As far as I can tell, there is
no bug in samba itself, all of these bugs are in update-manager and just
have been seen with various binary packages which we're marking this bug
and then indicating they are invalid.

** Changed in: samba (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  "Use of uninitialized value" in debconf via update-manager

Status in debconf package in Ubuntu:
  Invalid
Status in php7.0 package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Confirmed

Bug description:
  During a software upgrade, process was stuck on php7.0-xml
  configuration for 20 minutes, after that I killed the process. I am
  not sure what additional info are required, will be happy to provide
  any.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  Date: Fri Dec  2 09:52:06 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-03-11 (265 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: php7.0
  Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Nish Aravamudan]

** Tags removed: verification-needed yakkety
** Tags added: verification-done-yakkety verification-needed-xenial

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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

Re: [Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

On 29.03.2017 [03:19:16 -], Serge Hallyn wrote:
> Thanks, Nish.  My thoughts:
> 
> 1.a sounds good

Ack.
 
> 1.b i'd like another way to do that, but not sure what a better way would
> be.

Yeah, I spent some time looking at the CPC generater and it seems like
this is pretty hard-coded:

999-cpc-fixes.chroot:
## --
# for maverick and newer, use LABEL= for the '/' entry in fstab
if [ -n "${root_fs_label}" ]; then
   bl="[:blank:]"
   lstr="LABEL=${root_fs_label}"
   sed -i "s,^[^#${bl}]*\([${bl}]*/[${bl}].*\),${lstr}\1," "${rootd}/etc/fstab"
fi
cat > /etc/fstab << EOM
LABEL=cloudimg-rootfs   /   ext4 defaults 0 0
EOM

> 1.c does lvm also fail in privileged containers?  I can see no use to
> running it (for now) in an unprivileged container, so the same solution
> as 1.a seems reasonable.

It also fails in privileged containers in the same way (see 2.b in
comment 20). Note that it works if I manually start the socket after
boot.

> 1.d
> CAP_ADMIN_READ is not a real capability.  So if 1.d is fixed by that,
> then something else is wrong.

Right, follow-on comments indicated it was a thinko on my part. I think
it make sense, based upon the context in the audit bug that perhaps we
just don't do auditing in unprivileged containers (similar to the 1.a
change)?

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1640320] Re: FTBFS in zesty

[Nish Aravamudan]

Based upon c#6 unsubscribing ubuntu-sponsors.

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  In Progress

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+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 1672941] Re: FTBFS with older versions of OpenSSL

[Nish Aravamudan]

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  FTBFS with older versions of OpenSSL

Status in cyrus-sasl2 package in Ubuntu:
  Fix Committed

Bug description:
  cyrus-sasl2 currently FTBFS in Zesty because we have an older version
  of OpenSSL than in Debian (1.0.2 vs 1.1.0). There was a patch upstream
  to fix this: https://github.com/cyrusimap/cyrus-
  sasl/commit/ccb394dc857c0f1ef03a6be5011b5aedc1dbf042

  debdiff attached. Tested building with pbuilder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1672941/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Nish Aravamudan]

I uploaded the fix today to 16.04 and 16.10, will need to go through the
SRU process.

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  In Progress
Status in dnsmasq source package in Yakkety:
  In Progress
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Nish Aravamudan]

** Description changed:

+ [Impact]
+ 
+  * suspend/resume (which involves disconnection of network devices)
+ leads to dnsmasq failures.
+ 
+ [Test Case]
+ 
+  * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures
+ upon resume.
+ 
+ [Regression Potential]
+ 
+  * The fix was NMU'd in Debian in the version immediately after 16.10's.
+ I believe the regression potential is very low as this is a clear bug-
+ fix from upstream.
+ 
+ ---
+ 
  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
- 
  
  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772
  
  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
  
  I didn't yet test if applying that patch to ubuntu package works. I will
  try the patch in a few hours.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  In Progress
Status in dnsmasq source package in Yakkety:
  In Progress
Status in dnsmasq package in Debian:
  Unknown

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1675683] Re: Computer sluggish/irresponsive for several minutes after hibernation

[Nish Aravamudan]

This is probably going to be tricky to debug as it's probably hardware
dependent.

Can you first run `sudo dmesg -C`, then suspend and resume and then
attach the output of `dmesg` ?

** Changed in: pm-utils (Ubuntu)
   Status: New => Incomplete

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

Title:
  Computer sluggish/irresponsive for several minutes after hibernation

Status in pm-utils package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  my computer is very sluggish for a good five minutes after thawing from 
hibernation.

  Booting the system and the thawing process in itself seems to run fine
  : the console displays the progress of reloading contents into RAM at
  a satisfying pace, then the lightdm unlock interface displays.

  From this point on, things become strange : the computer has an
  constant and intense hard drive activity and applications do not
  respond to input in a swift manner (moving the mouse cursor works in
  "real time" though, and the clock, which displays seconds, also works
  almost normally).

  This reminds me of what happens when you set focus back to an
  application that had been paged to swap : it is irresponsive until it
  is back in RAM. Except this happens for all applications at once.

  This stops after several minutes (more than five) and the computer
  becomes usable again.

  I experienced the problem today again. The current RAM usage is 7.2
  Gio / 15.6 Gio and swap usage is 4.2 Gio / 31.3 Gio.

  Main memory usage is :
  firefox 3.4 Gio
  firefox (other instance) 1.7 Gio
  thunderbird 624 Mio
  xfwm4 213 Mio

  Hibernation with TuxOnIce did not induce this problem (I am not using
  it currently due to mismanagement of video drivers).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 09:20:15 2017
  InstallationDate: Installed on 2016-09-07 (197 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1675683/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Nish Aravamudan]

It would appear that Debian fixed this in 2.76-4.1, which should be in
17.04. I will provide SRUs for 16.04 and 17.04 this week.

** Also affects: dnsmasq (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: dnsmasq (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: dnsmasq (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: dnsmasq (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: dnsmasq (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: dnsmasq (Ubuntu Xenial)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Changed in: dnsmasq (Ubuntu Yakkety)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

** Also affects: dnsmasq (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722
   Importance: Unknown
   Status: Unknown

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  In Progress
Status in dnsmasq source package in Yakkety:
  In Progress
Status in dnsmasq package in Debian:
  Unknown

Bug description:
  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  
  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 678440] Re: "apt-get changelog" doesn't take source package names

[Nish Aravamudan]

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  "apt-get changelog" doesn't take source package names

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apt

  Hi

  Currently, "apt-get changelog" doesn't accept source package names
  (e.g. eglibc) nor does it honor -o APT::Get::Only-Source / --only-
  source (e.g. "apt-get --only-source changelog linux"  doesn't use the
  linux source package in Ubuntu but the linux binary package in linux-
  meta).

  at least in the Ubuntu and Debian cases, binary packages are mapped to
  source packages to construct the changelog URLs, so it would seem
  sensible to support source packages as input?

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/678440/+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 1186924] Re: "apt-get install taskname^" is not documented

[Nish Aravamudan]

** Changed in: apt (Ubuntu)
   Importance: Undecided => Low

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

Title:
  "apt-get install taskname^" is not documented

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  % GET https://patches.ubuntu.com/a/apt/apt_0.9.7.7ubuntu4.patch | fgrep 
'taskname^'
  +  * merged "install-task" branch (use with "apt-get install taskname^")
  -  * merged "install-task" branch (use with "apt-get install taskname^")
  +with "apt-get install taskname^"

  (I had to use the online version as the changelog installed by the
  package is unfortunately truncated.)

  This feature is not documented in apt-get(8)despite it seems patched
  into apt since Edgy. Checked the man-pages of Precise and Raring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1186924/+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 1672555] Re: If srcpkg is in main but a binary package is in universe, `apt changelog` fails

[Nish Aravamudan]

This was fixed on c.u.c by using Julian's suggested mod_rewrite changes.
No changes are needed to extract-changelogs or apt.

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

Title:
  If srcpkg is in main but a binary package is in universe, `apt
  changelog` fails

Status in extract-changelogs:
  Invalid
Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ apt changelog qemu
  Err:1 http://changelogs.ubuntu.com qemu 1:2.8+dfsg-3ubuntu2 Changelog
Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)
  E: Failed to fetch 
http://changelogs.ubuntu.com/changelogs/pool/universe/q/qemu/qemu_2.8+dfsg-3ubuntu2/changelog
  Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)

  This is because the binary package's component is used to generate the
  URI, but the source is in main and changelogs are organized by source.

  Based upon IRC conversation with slangasek and juliank, it possibly
  makes sense to flatten the pool/ changelogs to drop the component
  subdirectory (with symlinks for BC) and then change apt to not use the
  component in the URI generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/extract-changelogs/+bug/1672555/+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 1672555] Re: If srcpkg is in main but a binary package is in universe, `apt changelog` fails

[Nish Aravamudan]

** Changed in: extract-changelogs
   Status: In Progress => Invalid

** Changed in: apt (Ubuntu)
   Status: New => Invalid

** Changed in: extract-changelogs
 Assignee: Nish Aravamudan (nacc) => (unassigned)

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

Title:
  If srcpkg is in main but a binary package is in universe, `apt
  changelog` fails

Status in extract-changelogs:
  Invalid
Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ apt changelog qemu
  Err:1 http://changelogs.ubuntu.com qemu 1:2.8+dfsg-3ubuntu2 Changelog
Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)
  E: Failed to fetch 
http://changelogs.ubuntu.com/changelogs/pool/universe/q/qemu/qemu_2.8+dfsg-3ubuntu2/changelog
  Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)

  This is because the binary package's component is used to generate the
  URI, but the source is in main and changelogs are organized by source.

  Based upon IRC conversation with slangasek and juliank, it possibly
  makes sense to flatten the pool/ changelogs to drop the component
  subdirectory (with symlinks for BC) and then change apt to not use the
  component in the URI generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/extract-changelogs/+bug/1672555/+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 1672555] Re: If srcpkg is in main but a binary package is in universe, `apt changelog` fails

[Nish Aravamudan]

Thanks to juliank on IRC: https://gist.github.com/julian-
klode/600237d0b61cf92b01748b25cf5921d7 A potential configuration-only
change for old clients backwards-compatiblity.

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

Title:
  If srcpkg is in main but a binary package is in universe, `apt
  changelog` fails

Status in extract-changelogs:
  In Progress
Status in apt package in Ubuntu:
  New

Bug description:
  $ apt changelog qemu
  Err:1 http://changelogs.ubuntu.com qemu 1:2.8+dfsg-3ubuntu2 Changelog
Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)
  E: Failed to fetch 
http://changelogs.ubuntu.com/changelogs/pool/universe/q/qemu/qemu_2.8+dfsg-3ubuntu2/changelog
  Changelog unavailable for qemu=1:2.8+dfsg-3ubuntu2 (404  Not Found)

  This is because the binary package's component is used to generate the
  URI, but the source is in main and changelogs are organized by source.

  Based upon IRC conversation with slangasek and juliank, it possibly
  makes sense to flatten the pool/ changelogs to drop the component
  subdirectory (with symlinks for BC) and then change apt to not use the
  component in the URI generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/extract-changelogs/+bug/1672555/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

Ok, the audit stuff was 'resolved' in LP: #1457054, where I think
everyone decided to agree that unprivileged containers didn't matter...

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

heh, after a few more sips of coffee and actually reading the manpage,
my 1.d.1 is obviously incorrect because CAP_ADMIN_READ is not a
capability. So in effect it's masking out the audit socket :)

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

Wanted to level-set (and subscribing pitti and hallyn for their advice):

1) LXD unprivileged containers:

4 services in the Zesty daily are failed at start:

1.a) iscsid.service

  This is because iscsid needs CAP_IPC_LOCK to run mlockall().
Unprivileged containers end up failing in the host kernel.

  I believe the right way about this is to make the change hallyn did to
open-iscsi.service in iscsid.service and make open-iscsi.service
properly depend on iscsid.service. But I also think the change made by
hallyn is too broad and means even privileged containers cannot use
iscsi, which does not seem to be strictly true.

1.a.1) Proposed solution: http://paste.ubuntu.com/24196051/

  Effectively, only run iscsid if not in a user namespace (which is
where the capabilities get dropped, aiui). And open-iscsi service adds
conditions (adapter from Fedora's service file) to check that nodes are
defined (which would imply some configuration has been done) and a
session exists (which I think means that /etc/iscsi/iscsid.conf contains
node.startup=automatic and iscsid has started up a session therefore).

  If we are worried about the potential breakage (I need to of course
test all this in the various iSCSI configurations), we might consider
just making the first change (ConditionVirtualization=!private-users) to
both .service files, but I feel like that is mostly a workaround for not
being able to express cleanly the dependency between the two services:
open-iscsi.service can only run if iscsid.service is running; but if
iscsid.service is not running because of a Condition, then open-
iscsi.service should not be in a failed state.

1.b) systemd-remount-fs.service

  z2 systemd-remount-fs[50]: mount: can't find LABEL=cloudimg-rootfs

  /etc/fstab:
LABEL=cloudimg-rootfs   /ext4   defaults0 0

  This doesn't really make sense in the context of LXD containers
afaict, because they don't have a /dev/disk/by-label necessarily? Also,
the / is all configured by LXD in practice, not by how the cloud-image
is configured?

1.b.1) Proposed solution, comment out the entry in /etc/fstab in the LXD
images.

1.c) lvm2-lvmetad.socket

  lvm[61]:   Daemon lvmetad returned error 104
  lvm[61]:   WARNING: Failed to connect to lvmetad. Falling back to device 
scanning.
  ...
  lvm2-lvmetad.socket: Trigger limit hit, refusing further activation.

  But manually running `systemctl start lvm2-lvmetad.socket` at `lxc
exec z1 bash`, works. That seems confusing and implies some sort of
ordering issue? (Note that confusingly `systemctl restart
lvm2-lvmetad.socket` does *not* work.)

1.c.1) I don't have a proposed solution for this.

1.d) systemd-journal-audit.socket

  I found this older thread: https://lists.freedesktop.org/archives
/systemd-devel/2015-May/032113.html on this topic. Specifically,
https://lists.freedesktop.org/archives/systemd-
devel/2015-May/032126.html.

  Looking at the socket file, though, I see:

  ConditionCapability=CAP_AUDIT_READ

  which I do not believe is the same as CAP_ADMIN_READ. I don't know if
the ML post or the change are incorrect, but I did verify that using
CAP_ADMIN_READ in the container instead of CAP_AUDIT_READ did correctly
conditionalize the socket start, while CAP_AUDIT_READ does not.

1.d.1) Proposed solution: changing the ConditionCapability to
CAP_ADMIN_READ.

2) Privileged containers

2.a) systemd-remount-fs.service

  Same as 1.b) above.

2.b) lvm2-lvmetad.socket

  Same as 1.c) above.

With the changes in 1.a.1, 1.b.1 and 1.d.1:

3) Unpriviled container

3.a) Only 1.c) remains, and after issuing `systemctl start
lvm2-lvmetad.socket`, `systemctl status` reports 'running'.

4) Privileged container

4.a) same as 3.a)

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket  

[Touch-packages] [Bug 1673491] Re: [Zesty] libvirtd Segmentation fault after running virt-manager

[Nish Aravamudan]

** Also affects: libnl3 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Zesty] libvirtd  Segmentation fault after running virt-manager

Status in libnl3 package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  in Ubuntu 17.04 we can't open a virt-manager, we see sefault

  This issue happen when we update from kernel 4.10.0-9-generic to
  4.10.0-11-generic

  root@:~# /usr/sbin/libvirtd
  Segmentation fault (core dumped)   

  root@:~# gdb /usr/sbin/libvirtd ./core 
  GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git
  Copyright (C) 2017 Free Software Foundation, Inc.  
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.   
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"   
  and "show warranty" for details. 
  This GDB was configured as "x86_64-linux-gnu".   
  Type "show configuration" for configuration details. 
  For bug reporting instructions, please see:  
  . 
  Find the GDB manual and other documentation resources online at: 
  .
  For help, type "help".   
  Type "apropos word" to search for commands related to "word"...  
  Reading symbols from /usr/sbin/libvirtd...(no debugging symbols found)...done.
  [New LWP 4232]
  [New LWP 4216]
  [New LWP 4219]
  [New LWP 4218]
  [New LWP 4231]
  [New LWP 4215]
  [New LWP 4220]
  [New LWP 4224]
  [New LWP 4221]
  [New LWP 4223]
  [New LWP 4222]
  [New LWP 4217]
  [New LWP 4225]
  [New LWP 4227]
  [New LWP 4230]
  [New LWP 4229]
  [New LWP 4228]
  [Thread debugging using libthread_db enabled] 
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/sbin/libvirtd'.   
  Program terminated with signal SIGSEGV, Segmentation fault.   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  [Current thread is 1 (Thread 0x7f97dff94700 (LWP 4232))]  
   
  (gdb) where   
   
  #0  0x7f97fa93367f in rtnl_link_sriov_parse_vflist () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200
  #1  0x7f97fa927fad in ?? () from 
/usr/lib/x86_64-linux-gnu/libnl-route-3.so.200  
  #2  0x7f980bfb76c3 in nl_cache_parse () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #3  0x7f980bfb770b in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #4  0x7f980bfbdc1c in nl_recvmsgs_report () from 
/lib/x86_64-linux-gnu/libnl-3.so.200
  #5  0x7f980bfbe049 in nl_recvmsgs () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #6  0x7f980bfb6aab in ?? () from /lib/x86_64-linux-gnu/libnl-3.so.200 
   
  #7  0x7f980bfb763d in nl_cache_pickup () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #8  0x7f980bfb7871 in nl_cache_refill () from 
/lib/x86_64-linux-gnu/libnl-3.so.200   
  #9  0x7f97fa926975 in 

[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

** Summary changed:

- fails in lxd container
+ systemd in degraded state on startup in LXD containers

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

Title:
  systemd in degraded state on startup in LXD containers

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1576341] Re: fails in lxd container

[Nish Aravamudan]

16.04:

$ lxc launch xenial x1
$ lxc file pull x1/etc/cloud/build.info -
build_name: server
serial: 20160211-034510
$ lxc exec x1 systemctl is-system-running
degraded
$ lxc exec x1 -- systemctl --state=failed
  UNIT LOAD   ACTIVE SUBDESCRIPTION
● dev-hugepages.mount  loaded failed failed Huge Pages File System
● iscsid.service   loaded failed failed iSCSI initiator daemon (iscs
● systemd-remount-fs.service   loaded failed failed Remount Root and Kernel File
● systemd-sysctl.service   loaded failed failed Apply Kernel Variables
● lvm2-lvmetad.socket  loaded failed failed LVM2 metadata daemon socket
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

16.10:

$ lxc launch ubuntu:yakkety y1
$ lxc file pull y1/etc/cloud/build.info -
build_name: server
serial: 20170307
$ lxc exec y1 systemctl is-system-running
degraded
$ lxc exec y1 -- systemctl --state=failed
  UNIT LOAD   ACTIVE SUBDESCRIPTION
● dev-hugepages.mount  loaded failed failed Huge Pages File System
● iscsid.service   loaded failed failed iSCSI initiator daemon (iscs
● open-iscsi.service   loaded failed failed Login to default iSCSI targe
● systemd-remount-fs.service   loaded failed failed Remount Root and Kernel File
● systemd-sysctl.service   loaded failed failed Apply Kernel Variables
● lvm2-lvmetad.socket  loaded failed failed LVM2 metadata daemon socket
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

17.04:

$ lxc launch ubuntu-daily:zesty z1
$ lxc file pull z1/etc/cloud/build.info -
build_name: server
serial: 20170315.1
$ lxc exec z1 systemctl is-system-running
degraded
$ lxc exec enormous-quetzal -- systemctl --state=failed
  UNIT  LOAD   ACTIVE SUBDESCRIPTION
 
● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid) 
● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket 
● systemd-journald-audit.socket loaded failed failed Journal Audit Socket   
 

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB= The low-level unit activation state, values depend on unit type.

4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

$ lxc exec enormous-quetzal apt policy open-iscsi
open-iscsi:
  Installed: 2.0.873+git0.3b4b4500-14ubuntu17

So things are better generally. I'm not sure if this is high enough
priority where we might want to consider SRUing some of the changes back
to 16.04?

--

Also, Serge, I was looking at your change from c#17 -- does that mean
even privileged containers would no longer get their iSCSI devices to
start? (iscsiadm mentions that iscsid is often needed) And shouldn't we
do the same (to be consistent) for iscsid.service? Actually, it seems
like if we had done it in iscsid.service, the following:

ExecStartPre=/bin/systemctl --quiet is-active iscsid.service

from open-iscsi.service would have avoided needing to change open-
iscsi.service at all?

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

Title:
  fails in lxd container

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass 

[Touch-packages] [Bug 1576341] Re: fails in lxd container

[Nish Aravamudan]

Did some digging on the mlockall failure:

/* we don't want our active sessions to be paged out... */
if (mlockall(MCL_CURRENT | MCL_FUTURE)) {
log_error("failed to mlockall, exiting...");
log_close(log_pid);
exit(ISCSI_ERR);
}

so I think it's a real issue for iscsid (and I'm not sure we want to
debug random failures in the code if it can't ensure it's 'active
sessions') don't stay in memory.


That change, fwiw, was originally introduced in 2005:

https://github.com/open-iscsi/open-
iscsi/commit/6f37c861162157f4a6e28c2fa3cf50e61726c8f3

so it's unlikely to have been tested anytime recently without it :)

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

Title:
  fails in lxd container

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Invalid
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The ubuntu:xenial image shows 'degraded' state in lxd on initial boot.

  $ lxc launch xenial x1
  $ sleep 10
  $ lxc file pull x1/etc/cloud/build.info -
  build_name: server
  serial: 20160420-145324

  $ lxc exec x1 systemctl is-system-running
  degraded

  $ lxc exec x1 -- systemctl --state=failed
    UNIT  LOAD   ACTIVE SUBDESCRIPTION
  ● dev-hugepages.mount   loaded failed failed Huge Pages File System
  ● iscsid.serviceloaded failed failed iSCSI initiator daemon 
(iscsid)
  ● open-iscsi.serviceloaded failed failed Login to default iSCSI 
targets
  ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel 
File Systems
  ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables
  ● lvm2-lvmetad.socket   loaded failed failed LVM2 metadata daemon 
socket
  ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  7 loaded units listed. Pass --all to see loaded but inactive units, too.
  To show all installed unit files use 'systemctl list-unit-files'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 17:28:04 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: open-iscsi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Nish Aravamudan]

Any chance you've been able to reproduce this with 16.04 or later? the
upstart -> systemd differences are rather significant.

I wonder if upstart is not opening /dev/console for input early enough
or so.

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1547193/+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 1547193] Re: Impossible to answer "disk drive not ready" question on serial console

[Nish Aravamudan]

Hello,

Does your serial console work normally? e.g., if you run a getty on it,
can you login over it?

Thanks,
Nish

** Changed in: mountall (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Impossible to answer "disk drive not ready" question on serial console

Status in mountall package in Ubuntu:
  Incomplete

Bug description:
  When booting a server that is suffering from a (probably unrelated)
  bug in multipath-tools, I get the following questions posed on the
  serial console during bootup:

  The disk drive for /opt/vnx is not ready yet or not present.
  Continue to wait, or Press S to skip mounting or M for manual recovery

  Problem is, pressing "S" or "M" (even if followed by a newline) does
  absolutely nothing on the serial console. It does work on the KVM
  console, but that might not be available. You might very well need to
  send someone to a physical data centre somewhere in the middle of
  nowhere. (I ended up with powercycling the server, temporarily network
  booting it into a ramdisk, mounting the rootfs and commenting out the
  problematic entry from /etc/fstab, and rebooting again - which went
  fine, allowing me to later mount the missing filesystem manually via
  ssh.)

  I found no way to make the boot finish or break out to a debug shell,
  and it happens before sshd starts, so you're basically stuck with no
  apparent way to recover.  For this reason I feel the bug is quite
  severe.

  For what it's worth I'm running 14.04.4 LTS, mountall package version
  is 2.53. The kernel command line is
  «BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-77-generic
  root=UUID=2a141a43-97b0-4084-8816-ed1c41ac43e0 ro rootflags=subvol=@
  console=tty1 console=ttyS0,115200n8».

  Tore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1547193/+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