[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

[Iain Lane]

It is not dbus which is asking for authentication here. That's not
really a thing that happens.

What does happen is that some services that own names on the bus will
check that a method's caller is authorised to make the call before
performing the action. This is usually achieved with PolicyKit - I think
that you're seeing a PolicyKit denial here.

A notable user is systemd - am I right in saying that this is a response
from a dbus call to a systemd method (StopUnit?)? If so, this behaviour
is certainly nothing new.

The relevant polkit action id is "org.freedesktop.systemd1.manage-
units". It is callable by admins (unix group admin or unix group sudo)
after they have authenticated with their password. If you call the
method as root, you won't get prompted and the action will be performed.

I would look at any changes to how you run the tests (which user?), then
any changes to the systemd stuff (is it new? is it now being called from
a non-root process whereas before it wasn't?). Note that policykit will
output to the journal when it authorises or denies acition requests,
which might be helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Incomplete
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
      http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller api-config-watcher disk-manager log-forwarder log-sender logging-config-updater machine-action-runner machiner migration-fortress migration-inactive-flag migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater state-config-watcher storage-provisioner termination-signal-handler unconverted-api-workers upgrade-check-flag upgrade-check-gate upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
      WaitMatch(c, matcher.Check, coretesting.LongWait, s.BackingState.StartSync)
  engine_test.go:234:
      c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

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