This failure has not been due to Juju but rather the setup of the CI
environment. We have not seen any consecutive failures of this nature,
so the issue has been resolved.
I am closing this report.
** Changed in: juju
Status: Incomplete => Fix Released
** Changed in: dbus (Ubuntu)
** Changed in: juju
Milestone: 2.2-beta3 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for worke
With Chris's help we got the tests to get past the D-Bus errors on Zesty
by creating a file /etc/polkit-1/localauthority/50-local.d/manage-
units.pkla on the test system with the following contents:
# Allow the "ubuntu" user to manage systemd units unconditionally
for testing
[Allow manag
Anastasia asked me to take a look at this. I'm still not sure what the
underlying cause is, but here is some of what I've discovered so far.
1. There has been a change in policykit-1 that sounds like it might be
relevant. Namely:
[ Martin Pitt ]
* Use PAM's common-session-noninteractive mod
** Changed in: juju
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for w
I should also note that the test runs as the ubuntu user whish does has
sudo access to the whole machine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
Machin
These tests are run across different archs using the same script (the
same user etc.). Nothing has changed in how it's run but we're only
seeing this failure on Zesty.
I should be able to get the PolicyKit output from the journal in case
that is of use.
--
You received this bug notification beca
** Changed in: juju
Milestone: 2.2-beta2 => 2.2-beta3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for
Is the unit test messing with the services on the host system? I hope
not.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed
** Changed in: juju
Milestone: 2.2-alpha1 => 2.2-rc1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for w
** Changed in: juju
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for w
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 -
12 matches
Mail list logo