[Group.of.nepali.translators] [Bug 1757422] Re: Fix Runtime PM for r8169

2019-05-24 Thread Kai-Heng Feng 
** No longer affects: linux (Ubuntu)

** Changed in: linux-oem (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

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

Title:
  Fix Runtime PM for r8169

Status in HWE Next:
  New
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Triaged
Status in linux-oem source package in Bionic:
  New

Bug description:
  ===SRU Justification===
  [Impact]
  r8169 stays in D0 even when no ethernet cable is plugged in. This drains
  lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0,
  1.8W when r8169 is in D3. The power saved is substantial.

  [Fix]
  Improved rumtime PM logic to let the device gets suspended (D3) when the
  port is not in used and the link is down.

  [Test Case]
  The chip version is 8168h/8111h.
  Test when no ethernet gets plugged.

  Powertop shows power consumption is roughly 5.5W.
  lspci shows the device is in D0.

  With the patch,
  The power consumption is reduced to 1.8W.
  lspci shows the device is in D3, PME# is correctly enabled.
  Plug ethernet cable can corretly wake up the device.
  Unplug the cable, the device gets suspended to D3 correctly.

  [Regression Potential]
  Medium.
  - r8169 is so ubiquitous, with lots of different chip versions. It's
hard to test all of them.
  - PCI D3 needs system firmware (ACPI) support, this might hit some
plaform bugs.
  - the code is still in v4.16-rc*, so it's not well tested by end users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1689488] Re: vnc console accepts only 8 characters

2019-05-24 Thread Christian Ehrhardt  
novnc 1.1 is in disco and later at least.

** Also affects: novnc (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: novnc (Ubuntu Yakkety)

** Changed in: qemu (Ubuntu Xenial)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

** Changed in: qemu (Ubuntu Yakkety)
 Assignee: Christian Ehrhardt  (paelzer) => (unassigned)

** Also affects: qemu (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: novnc (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

Title:
  vnc console accepts only 8 characters

Status in novnc package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in novnc source package in Xenial:
  New
Status in qemu source package in Xenial:
  Incomplete
Status in qemu source package in Yakkety:
  Won't Fix
Status in novnc source package in Bionic:
  New
Status in qemu source package in Bionic:
  New

Bug description:
  We have an issue when send message via vnc console. The vnc accepts
  only the first 8 characters.

  The issue happens on ubuntu 15.05/15.10/16.04/16.10, but does not
  exist in ubuntu 14.04 and ubuntu 17.04.

  After investigation, I found the issue is caused by commit
  
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=2deb4acc7c7ee770a0e0e75fd321effd916ca7df

  and fixed by commit (it is already included in qemu v2.7.0, and ubuntu 
17.04/qemu-2.8)
  
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=c5ce83334465ee5acb6789a2f22d125273761c9e

  Can we include the fix in next minor release of qemu-2.5 for ubuntu
  16.04 ?

  Thanks.

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1830169] Re: lvm udev rule fails to call systemd-run

2019-05-24 Thread Launchpad Bug Tracker 
This bug was fixed in the package lvm2 - 2.03.02-2ubuntu2

---
lvm2 (2.03.02-2ubuntu2) eoan; urgency=medium

  * Fix patch of systemd-run in 69-lvm-metad.rules (LP: #1830169)

 -- Julian Andres Klode   Thu, 23 May 2019 16:24:43
+0200

** Changed in: lvm2 (Ubuntu Eoan)
   Status: New => Fix Released

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

Title:
  lvm udev rule fails to call systemd-run

Status in Ubuntu on IBM z Systems:
  Triaged
Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Xenial:
  New
Status in lvm2 source package in Bionic:
  New
Status in lvm2 source package in Cosmic:
  New
Status in lvm2 source package in Disco:
  New
Status in lvm2 source package in Eoan:
  Fix Released

Bug description:
  In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run 
command during removal ---  
 ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm 
pvscan --cache $major:$minor", GOTO="lvm_end"

  But /bin/systemd-run is not found,  in fact systemd-run is in /usr/bin
  /systemd-run.

  xx:~$ cat /etc/issue
  Ubuntu 18.04.2 LTS \n \l

  xx:~$ ls /bin/systemd-run
  ls: cannot access '/bin/systemd-run': No such file or directory

  xx:~$ ls /usr/bin/systemd-run
  /usr/bin/systemd-run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades

2019-05-24 Thread Launchpad Bug Tracker 
This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu8.8

---
qemu (1:2.12+dfsg-3ubuntu8.8) cosmic-security; urgency=medium

  * Add qemu-guest-agent Breaks: for unattended-upgrades versions not being
able to install it to avoid qemu-guest-agent blocking other security
updates. (LP: #1823872)

 -- Balint Reczey   Thu, 23 May 2019 15:09:48 +0200

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

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

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

Title:
  Fixing fsfreeze-hook can break unattended upgrades

Status in qemu package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * If an update has a new conffile at a path that in a former version was
     a directory like
  old: /a/b/c
  new: a/b
     Here b is the new file name and was a directory in the old version.
     Then unattended upgrades breaks on installing such a package.

   * a recent qemu update has such a case and due to that triggered the
     issue in >=Bionic

   * The fix is to harden unattended upgrades to be able to handle the case
     without aborting.

  [Test Case]

  Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12
  That can be done with:
    $ time uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic
    $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic 
label=daily

  Log in and apt update & upgrade all packages, then Install the release level 
qemu in there.
    $ uvt-kvm ssh bionic-testuu
    $ sudo apt update
    $ sudo apt dist-upgrade
    $ sudo apt install unattended-upgrades
    $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7

  All before was preparation, now force the unattended upgrade to trigger the 
bug.
    $ sudo unattended-upgrade -d

  With the bug you'll find some error like:
  found pkg: qemu-guest-agent
  conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191
  current md5: f61a64ac1e48993023018fd1cff85191
  conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 
15f6ff42cbc5550a07ee21c2a471d905
  /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles 
/etc/init.d/qemu-guest-agent
  /etc/qemu/fsfreeze-hook
  found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 2057, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1773, in main
  if conffile_prompt(item.destfile):
    File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt
  with open(prefix + conf_file, 'rb') as fp:
  IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'

  [Regression Potential]

   * The fix is trying to detect moved conffiles by looking for /etc/foo/foo 
when the new package ships /etc/foo and /etc/foo is not a known conffile and 
also checking the renames in the opposite direction.
  The potential regression is breaking the logic for detecting changed 
conffiles and either holding back a package for no reason or trying to install 
a package with a modified conffile on the system and aborting the upgrade in 
the middle due to the appearing conffile prompt. To avoid such regressions the 
test_conffile.py tests are extended to cover rename scenarios.

  [Other Info]

   * n/a

  ---

  As reported on 
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20
  We fixed an issue and we added workrounds since basic mv_conffile coudn't 
handle it and did all sort of upgrade tests.

  That all worked fine and moved the conffile.

  It was now reported that due to some pre-checks that unattended
  upgrades might do this might do some checks on its own.

  Next step:
  - check unattended upgrades through this change
  - check if it only affects cases were the former config was modified 
(minority) or the default file layout (majority)

  --- original report copied ---

  just wanted to add: This bug also crashes unattended-upgrade and thus
  prevents security updates on 18.04:

  root@mailin1:~# unattended-upgrade
  Traceback (most recent call last):
    File "/usr/bin/unattended-upgrade", line 1998, in 
  sys.exit(main(options))
    File "/usr/bin/unattended-upgrade", line 1714, in main
  if conffile_prompt(item.destfil

[Group.of.nepali.translators] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel

2019-05-24 Thread Po-Hsu Lin 
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux-kvm (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux-kvm (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-kvm source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-kvm source package in Cosmic:
  New

Bug description:
  The "enable disable fan test" will fail with Xenial KVM kernel

  Error message:
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 
0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanatic: unable to bring fan up, unable to configure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 10:22:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1763323/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker

2019-05-24 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Testing
  phase-changed: Thursday, 23. May 2019 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in 
expected channel(s):
- arch=arm64:channel=latest/candidate:rev=91'
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-snapdragon: 4.4.0-1114.119 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Testing
  phase-changed: Thursday, 23. May 2019 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker

2019-05-24 Thread Canonical Certification Team 
Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/TZR30TfI/1041-dragonboard-
kernel-440-1114119-91

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux-snapdragon: 4.4.0-1114.119 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Testing
  phase-changed: Thursday, 23. May 2019 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in 
expected channel(s):
  arch=arm64:channel=latest/candidate:rev=91'
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1830033] Re: Connection synchronization daemon fails at start due to a bug in launch script

2019-05-24 Thread Christian Ehrhardt  
I verified the proposed change (which is in the opposite diff direction
in the initial report) works in VMs and the PPA fixes the issue.

The fix seems easy enough, so I added MPs for Xenial and Bionic and a
PPA with the builds at [1]

[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830033-ipvsadm-
start

** Changed in: ipvsadm (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Connection synchronization daemon fails at start due to a bug in
  launch script

Status in ipvsadm package in Ubuntu:
  Fix Released
Status in ipvsadm source package in Xenial:
  Triaged
Status in ipvsadm source package in Bionic:
  Triaged
Status in ipvsadm source package in Cosmic:
  Fix Released
Status in ipvsadm package in Debian:
  Fix Released

Bug description:
  [Impact]

   * the init script has an argument twice, which makes the service fail to 
 start 

   * Without the fix the service is rather unusable as it can't be
  started

  [Test Case]

   * Needs a VM (no container)
 $ sudo apt install ipvsadm
 $ echo 'AUTO="true"' | sudo tee -a /etc/default/ipvsadm
 $ echo 'DAEMON="master"' | sudo tee -a /etc/default/ipvsadm
 $ sudo systemctl restart ipvsadm
 $ systemctl status ipvsadm

 With the bug this will show the sevrice failing
 [...]
 Try `/sbin/ipvsadm -h' or '/sbin/ipvsadm --help' for more information.
 ...fail!

  
  [Regression Potential] 

   * Even in the default config (just enabling it to run) this doesn't work.
 Hence the risk should be next to none.
 I can think of setups that "are meant to work" , but so far "didn't 
 start" now properly would start. For example if someone 
 configured the service but ignored that it failed to start.
 I hope and expect that this is a rather unimportant risk, it actually 
 is the fix we are intending to make.

  [Other Info]
   
   * TBH it is in main for a dependency from keepalive but I wonder how much 
 that could be a sugegsts instead. But that is for the future.

  ---

  
  The launch script for ipvsadm has a bug that prevents LVS from start in 
synchronization mode.

  How to reproduce.
  1. Install ipvsadm on ubuntu server 16.04 and modify /etc/default/ipvsadm to 
lauch LVS in master mode (or backup):
  AUTO="true"
  DAEMON="master"
  IFACE="eno1"
  SYNCID="0"

  2. Start "ipvsadm" service and check systemd unit log:
  # systemctl start ipvsadm
  # journalctl -u ipvsadm
  What you expected to happen
  The log output without error:
  May 22 12:41:46 xxx systemd[1]: Starting LSB: ipvsadm daemon...
  May 22 12:41:46 xxx ipvsadm[4619]:  * Clearing the current IPVS 
table...
  May 22 12:41:46 xxx ipvsadm[4619]:...done.
  May 22 12:41:46 xxx ipvsadm[4619]:  * Loading IPVS configuration...
  May 22 12:41:46 xxx ipvsadm[4619]:...done.
  May 22 12:41:46 xxx ipvsadm[4619]:  * Starting IPVS Connection 
Synchronization Daemon master
  May 22 12:41:46 xxx ipvsadm[4619]:...done.
  May 22 12:41:46 xxx systemd[1]: Started LSB: ipvsadm daemon.

  What happened instead:
  May 22 12:32:59 xxx systemd[1]: Starting LSB: ipvsadm daemon...
  May 22 12:32:59 xxx ipvsadm[15743]:  * Clearing the current IPVS table...
  May 22 12:32:59 xxx ipvsadm[15743]:...done.
  May 22 12:32:59 xxx ipvsadm[15743]:  * Loading IPVS configuration...
  May 22 12:32:59 xxx ipvsadm[15743]:...done.
  May 22 12:32:59 xxx ipvsadm[15743]:  * Starting IPVS Connection 
Synchronization Daemon master
  May 22 12:32:59 xxx ipvsadm[15743]: Try `/sbin/ipvsadm -h' or 
'/sbin/ipvsadm --help' for more information.
  May 22 12:32:59 xxx ipvsadm[15743]:...fail!
  May 22 12:32:59 xxx ipvsadm[15743]:...done.
  May 22 12:32:59 xxx systemd[1]: Started LSB: ipvsadm daemon.

  As you can see in log output, there is an message: "Try `/sbin/ipvsadm
  -h' or '/sbin/ipvsadm --help' for more information". This message
  relates to bug in script /etc/init.d/ipvsadm.

  Here a difference how script should be updated to get it work:
  --- /etc/init.d/ipvsadm   2019-05-22 12:41:34.429916226 +
  +++ /root/ipvsadm 2019-05-22 11:18:04.307344255 +
  @@ -29,16 +29,16 @@
   case $DAEMON in
    master|backup)
    log_daemon_msg "Starting IPVS Connection Synchronization Daemon" 
"$DAEMON"
  - $IPVSADM --start-daemon $DAEMON --mcast-interface \
  + $IPVSADM --syncid $SYNCID --start-daemon $DAEMON --mcast-interface \
   $IFACE --syncid $SYNCID || log_end_msg 1
    log_end_msg 0
    ;;
    both)
    log_daemon_msg "Starting IPVS Connection Synchronization Daemon" 
"master"
  - $IPVSADM --start-daemon master --mcast-interface \
  + $IPVSADM --syncid $SYNCID --star

[Group.of.nepali.translators] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker

2019-05-24 Thread Ubuntu Kernel Bot 
** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Testing
  phase-changed: Thursday, 23. May 2019 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   snap-release-to-beta: 'Pending -- snap dragonboard-kernel not in expected 
channel(s):
- arch=arm64:channel=latest/beta'
-   snap-release-to-edge: 'Pending -- snap dragonboard-kernel not in expected 
channel(s):
- arch=arm64:channel=latest/edge'
+   snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-snapdragon: 4.4.0-1114.119 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Testing
  phase-changed: Thursday, 23. May 2019 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
snap-certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp