subject:"\[Touch\-packages\] \[Bug 1590838\] Re\: scheduled shutdown \-r does not work without dbus in xenial LXC container"

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2018-02-27 Thread Launchpad Bug Tracker

This bug was fixed in the package landscape-client - 18.01-0ubuntu1

---
landscape-client (18.01-0ubuntu1) bionic; urgency=medium

  * New upstream release 18.01:
- Ported to python3 (LP: #1577850)
- move Replaces/Breaks landscape-client-ui rules to landscape-common
  (LP: #1560424)
- Add a libpam-systemd Depends if built for xenial (LP: #1590838)
- Some units not reporting swift usage (LP: #1588404)
- Fix missing install directories for landscape-common and drop
  usr/share/landscape as its only used and created by landscape-client.
  (LP: #1680842)
- Fix VM detection for Xen, by returning "xen" only for paravirtualized and
  HVM hosts, not for dom0. (LP: #1601818)
- Add an indication of truncation to process output that has been truncated
  prior to delivery to the server. (LP: #1629000)
- add /snap/bin to the PATH when executing scripts. (LP: #1635634)
- Save the original sources.list file when a repository profile is
  associated with a computer and restore it when the profile is removed.
  (LP: #1607529)
- Drop the legacy HAService plugin, which is no longer used.
- Avoid double-decoding package descriptions in build_skeleton_apt, which
  causes an error with Xenial python-apt. (LP: #1655395)
- Remove dead dbus code and textmessage (confirmed not supported in server
  for ~2 years). (LP: #1657372)
- Move bzr-builddeb conf file from deprecated location to debian/
  (LP: #1658796)
- Support for new server error message about there being too many pending
  computers already (LP: #1662530)
- Add a timestamp to the package reporter result (LP: #1674252)
- Check if ubuntu-release-upgrader is running before apt-update (LP: 
#1699179)
- Implicitly trust file-local sources managed by landscape. On upgrades,
  add the trusted flag to the landscape file-local apt source file if it's
  not there. (LP: #1736576)
- Use local system tools to change the user's password (LP: #1743558)
  * clean up packaging and getting in sync with the new landscape version:
- d/rules: drop extra:suggests which is unused since 13.07.1-0ubuntu2
- Remove antique postinst code. No supported landscape-client version
  installs cronjobs anymore (since a long time).
- d/landscape-client.docs: the README file is now a markdown file, so
  install that instead.
- d/landscape-common.postinst: no need to single out
  /var/lib/landscape/.gnupg when fixing ownerships, just do it over
  the entire parent directory.
- guard user and group removal via an empty .cleanup.* file in post, so we
  only remove the user/group if we were the ones who created them at
  install time.
- lintian: remove absolute path from update-motd calls in maintainer
  scripts
- d/rules: drop special handling for dapper, hardy and lucid, which are no
  longer supported.
- d/rules: make sure we have an "extra:Depends=" in substvars even if it's
  empty
- d/rules: drop dh_pycentral handling, it's obsolete
  * Dropped (already included in this version):
- d/p/set-vm-info-to-kvm-for-aws-C5-instances.patch:
  Sets vm_info to kvm for new AWS EC2 C5 instances. (LP #1742531)
- d/p/set-vm-info-to-kvm-for-digitalocean-instances.patch:
  Sets vm_info to kvm for digitalocean instances. (LP #1743232)
- Add proxy handling to package reporter. (LP #1531150)
- Fix regression in configuration hook under install-cd chroot (LP #1699789)
- Report autoremovable packages (LP #1208393)
- Do not re-register client by default (LP #1618483)
- Don't report packages that are coming from backports, so that Landscape
  doesn't try to upgrade to versions of packages that are in backports.
  (LP #1668583)
- Cope with an api change in python-swift that broke swift storage
  reporting in Autopilot. (LP #1563565)

 -- Andreas Hasenack   Wed, 21 Feb 2018 18:04:05
-0300

** Changed in: landscape-client (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2018-02-22 Thread Andreas Hasenack

** Changed in: landscape-client (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Changed in: landscape-client (Ubuntu)
   Status: New => In Progress

** Changed in: landscape-client (Ubuntu Yakkety)
   Status: New => Won't Fix

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  Won't Fix
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-07-06 Thread Landscape Builder

** Changed in: landscape-client
   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/1590838

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  Fix Committed
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-07-05 Thread Martin Pitt

** Also affects: landscape-client (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: landscape-client (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: Won't Fix

** Changed in: systemd (Ubuntu Yakkety)
   Status: Won't Fix => Fix Released

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  In Progress
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Xenial:
  New
Status in systemd source package in Xenial:
  Won't Fix
Status in landscape-client source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debian

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-07-05 Thread Andreas Hasenack

** Changed in: landscape-client
   Status: New => In Progress

** Changed in: landscape-client
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

** Branch linked: lp:~ahasenack/landscape-client/libpam-systemd-depends-
xenial-onwards

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  In Progress
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-07-05 Thread Andreas Hasenack

** Also affects: landscape-client
   Importance: Undecided
   Status: New

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in Landscape Client:
  New
Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default 20160609_11:40
  oracle6   i386default 20160609_11:40
  oracle7   amd64   default 20160609_11:40
  plamo 5.x amd64   default 20160608_21:36
  plamo 5.x

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-06-20 Thread Martin Pitt

Adding a landscape-client task. I suggest to add a libpam-systemd
dependency to landscape-client to ensure that scheduled shutdown works.

** Also affects: landscape-client (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in landscape-client package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default 20160609_11:40
  oracle6   i386default 20160609_11:40

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-06-17 Thread Martin Pitt

Ah, I just noticed that immediate shutdowns work fine. Scheduled
shutdowns however are handled by logind, and that requires dbus. I'm
afraid this won't change.

This has been "fixed" in yakkety by pulling libpam-systemd and
consequently dbus into the container images, as we were able to make
init/systemd-sysv/systemd non-essential. This is quite an intrusive
change though, and not suitable for backporting.

So for now I'm afraid you need to install libpam-systemd if you need
scheduled shutdowns.

** Changed in: systemd (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

2016-06-17 Thread Martin Pitt

** Summary changed:

- shutdown -r  does not work without dbus in xenial LXC container
+ scheduled shutdown -r  does not work without dbus in xenial LXC container

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

Title:
  scheduled shutdown -r  does not work without dbus in xenial LXC
  container

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  The command "shutdown -r +5" doesn't work in a xenial lxc container. I
  found this out by trying to use Landscape to restart a xenial lxc
  container and the operation failed. I was told by the Landscape team
  that the restart button simply does a "shutdown -r +5".

  The problem seems to be that the dbus package is missing in the xenial
  lxc image.

  This is what happens:

  root@xenialtest:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  And if I install dbus:

  root@xenialtest:/# shutdown -r +5
  Shutdown scheduled for Wed 2016-06-08 19:28:44 UTC, use 'shutdown -c' to 
cancel.

  The issue happens whether I use the download template or the ubuntu
  template when creating the LXC container:

  root@davecorelaptop:/var/cache/lxc# lxc-create -t ubuntu -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-start -d -n test2
  root@davecorelaptop:/var/cache/lxc# lxc-attach -n test2

  root@test2:/# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  Codename: xenial

  root@test2:/# shutdown -r +5
  Failed to connect to bus: No such file or directory
  Failed to connect to bus: No such file or directory

  
  or

  
  root@davecorelaptop:~# lxc-create -t download -n test
  Setting up the GPG keyring
  Downloading the image index

  ---
  DIST  RELEASE ARCHVARIANT BUILD
  ---
  alpine3.0 amd64   default 20160608_18:03
  alpine3.0 i386default 20160608_17:50
  alpine3.1 amd64   default 20160608_17:50
  alpine3.1 i386default 20160608_18:03
  alpine3.2 amd64   default 20160608_17:50
  alpine3.2 i386default 20160608_17:50
  alpine3.3 amd64   default 20160608_17:50
  alpine3.3 i386default 20160608_17:50
  alpineedgeamd64   default 20160608_17:50
  alpineedgei386default 20160608_17:50
  centos6   amd64   default 20160609_02:16
  centos6   i386default 20160609_02:16
  centos7   amd64   default 20160609_02:16
  debianjessie  amd64   default 20160608_22:42
  debianjessie  arm64   default 20160609_02:38
  debianjessie  armel   default 20160608_22:42
  debianjessie  armhf   default 20160608_22:42
  debianjessie  i386default 20160608_22:42
  debianjessie  powerpc default 20160608_22:42
  debianjessie  ppc64el default 20160608_22:42
  debianjessie  s390x   default 20160608_22:42
  debiansid amd64   default 20160608_22:42
  debiansid arm64   default 20160608_22:42
  debiansid armel   default 20160608_22:42
  debiansid armhf   default 20160608_22:42
  debiansid i386default 20160608_22:42
  debiansid powerpc default 20160608_22:42
  debiansid ppc64el default 20160608_22:42
  debiansid s390x   default 20160608_22:42
  debianstretch amd64   default 20160608_22:42
  debianstretch arm64   default 20160608_22:42
  debianstretch armel   default 20160608_22:42
  debianstretch armhf   default 20160608_22:42
  debianstretch i386default 20160608_22:42
  debianstretch powerpc default 20160608_22:42
  debianstretch ppc64el default 20160608_22:42
  debianstretch s390x   default 20160608_22:42
  debianwheezy  amd64   default 20160608_22:42
  debianwheezy  armel   default 20160608_22:42
  debianwheezy  armhf   default 20160608_22:42
  debianwheezy  i386default 20160608_22:42
  debianwheezy  powerpc default 20160609_02:38
  debianwheezy  s390x   default 20160608_22:42
  fedora22  amd64   default 20160609_01:27
  fedora22  armhf   default 20160112_01:27
  fedora22  i386default 20160609_01:27
  fedora23  amd64   default 20160609_01:27
  fedora23  i386default 20160609_01:27
  gentoocurrent amd64   default 20160608_14:12
  gentoocurrent i386default 20160608_14:12
  opensuse  13.2amd64   default 20160609_00:53
  oracle6   amd64   default 20160609_11:40
  oracle6   i386default 20160609_11:40
  oracle7   amd64   default 20160609_11:40
  plamo 5.x amd64   default 20160608_21:36
  plamo 5.x

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

[Touch-packages] [Bug 1590838] Re: scheduled shutdown -r does not work without dbus in xenial LXC container

9 matches

Site Navigation

Mail list logo

Footer information