group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1571209@xxxxxxxxxxxxxxxxxx>]

This bug was dead for quite some time, but the issue still exists for Trusty (were we could take the supposed change) and we have to check the systemd cases in >=Xenial.
Adapting tasks and will come back once I tested on >=Xenial.

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

** Also affects: libvirt (Ubuntu Artful)
   Importance: High
     Assignee: Serge Hallyn (serge-hallyn)
       Status: Fix Released

** Changed in: libvirt (Ubuntu Artful)
       Status: Fix Released => Incomplete

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

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

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

** Changed in: libvirt (Ubuntu Precise)
       Status: New => Won't Fix

** Changed in: libvirt (Ubuntu Artful)
     Assignee: Serge Hallyn (serge-hallyn) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1571209

Title:
  Sockfile check retries too short for a busy system boot

Status in libvirt package in Ubuntu:
  Incomplete
Status in libvirt source package in Precise:
  Won't Fix
Status in libvirt source package in Trusty:
  Triaged
Status in libvirt source package in Wily:
  Won't Fix
Status in libvirt source package in Xenial:
  Incomplete
Status in libvirt source package in Zesty:
  Incomplete
Status in libvirt source package in Artful:
  Incomplete

Bug description:
  [ problem description ]

  sockfile_check_retries is first introduced by #1455608, for preventing
  the failure case of sockfile not ready, but it was default to a hard-
  coded value "5", it might be too short for a busy system boot.

  #1455608 -
  https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1455608

  
  [ step to reproduce ]

  setup a clean install system (Ubuntu Server 14.04.4 LTS), and assemble
  os disk as RAID-1, boot up some guest instances (count > 10, start-at-
  boot), force shutdown host by pressing power-button for 3s ~ 5s, or
  via IPMI command, then power-on afterward. it may sometimes failed to
  get sockfile ready after in "post-start" script, with an line of error
  in /var/log/syslog,

  ==> kernel: [ 313.059830] init: libvirt-bin post-start process (2430)
  terminated with status 1 <==

  since there's multiple VMs Read/Write before a non-graceful shutdown,
  RAID devices need to re-sync after boot, and lead to a slow response,
  but start-up script for libvirt-bin can only wait 5 cycles, 2 seconds
  wait for each cycle, so it will timed-out after 10s, and exit with
  "1".

  
  [ possible solution ]

  extend the retry times for sockfile waiting, and make it possible to
  change via editing `/etc/default/libvirt-bin` file.

  <please see the patch file as attachment>

  
  [ sysinfo ]

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 14.04.4 LTS
  Release: 14.04
  Codename: trusty

  $ uname -a
  Linux host2 4.2.0-35-generic #40~14.04.1-Ubuntu SMP Fri Mar 18 16:37:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  
  [ related issue ]

  #1386465 -
  https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465

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