** Changed in: juju
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network] Race-condition between "apt update" and dhcp request
causes
** Changed in: juju
Milestone: 2.5.1 => 2.5.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756040
Title:
bionic: LXD containers don't get fan network IP addresses
To manage notifications
Public bug reported:
I have a new Thinkpad Carbon X1 Extreme and the fingerprint scanner does
not appear to be supported.
$ fprintd-enroll $USER
list_devices failed: No devices available
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-13-generic 4.18.0-13.14
** Changed in: juju
Milestone: 2.5-beta2 => 2.5-beta3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798117
Title:
juju sends "network" top level key to user.network-config in lxd
containers
Yes, you are 100% correct. We can determine from distro info if the
labelled LTS release is ready or not. Juju 2.2.6 does do this check now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Although the effect of Juju using the series flagged by distro data as
latest LTS means that it will attempt to use bionic before it is ready.
We could change Juju code to hard code the preferred LTS as one we know
works but this means we need to change Juju each time we want to update
the
This issue is not that Juju breaks when a new series is released. The
problem is that Juju defaults to using the latest LTS as the series for
which to bring up machines if none is specified by the user. If bionic
becomes the latest LTS, Juju will try and find agent binaries to match.
And if we are
** Changed in: juju
Milestone: 2.1-rc1 => 2.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654116
Title:
Attempts to write leadership settings when not the leader during
relation-changed
One possible root cause may be that if the machine running the unit is
loaded, the time between checking for leadership and the lease expiring
may have passed before the hook gets to write the leadership settings.
It's very unusual that the unit leader changes so often as seen in the
logs. This
I'm thinking also that a controller log (at debug or even trace level)
may be useful to see how the controller is handling leadership changes.
Just the part of the log around the time of the issue and what leads up
to it.
--
You received this bug notification because you are a member of Ubuntu
Looking at the rabbitmq logs, it appears to me (I could be
misinterpreting):
At 21:39:23 -> unit 2 becomes the leader (the leader-elected hook is run)
At 21:47:25 -> unit 0 becomes the leader (the leader-elected hook is run)
At 22:01:27 -> unit 1 becomes the leader (the leader-elected hook is
** Changed in: juju
Assignee: Menno Smits (menno.smits) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654116
Title:
Attempts to write leadership settings when not the leader
** Changed in: juju
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564157
Title:
juju list-credentials fails to display
To manage notifications about
** Changed in: juju
Assignee: Alexis Bruemmer (alexis-bruemmer) => Ian Booth (wallyworld)
** Changed in: juju
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
+1 from me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612116
Title:
please remove juju-core-1 and juju-mongodb packages from yakkety
To manage notifications about this bug go to:
We are only doing *critical* fixes for 1.25. Upgrading mongo version is
not a critical fix as far as I know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570650
Title:
Use juju-mongodb2.6 for
We do not need juju-mongodb2.6 on yakkety.
This package was to allow direct upgrades from Juju 1.25 to 2.x, since
upgrading mongo 2.4 to 3.x needed to go via 2.6.
However, Juju upgrades from 1.25 will be implemented via model migration so
this mongo upgrade step is no longer necessary.
--
You
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => Critical
** Changed in: juju-core
Assignee: (unassigned) => Michael Hudson-Doyle (mwhudson)
** Changed in: juju-core
Milestone: None => 2.0-beta7
** Changed in: juju-core
I have just tried again with the latest 4.5 kernel downloaded from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
No luck.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.5
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this
Progress - using the next intel kernel works *with* nvidia installed also. ie
prime-select intel | nvidia works.
It hangs on shutdown, but at least I can log in now.
A 4.4.x kernel is not scheduled for inclusion in xenial is it. The 4.4.x
is the only one that works for me from what I can tell.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4553111/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
I totally purged nvidia drivers and blacklisted nouveau. Everything was
straight intel.
The machine would boot to the greeter and attempts to login would result
in a freeze; console was not obtainable.
Attached is the dmesg log, and to follow the Xorg log. I couldn't see
any obvious errors.
**
The login screen shows ok. But when I type the password and hit enter,
the cursor freezes. I can't even switch to a console login at that
point. I got the logs by going straight to a console login instead of
attempting to login normally.
When trying to install wily direct from a USB stick, I also
Attached is dmesg as requested
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4551811/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also lsmod | grep 915
parport49152 3 lp,ppdev,parport_pc
i915 1204224 3
i2c_algo_bit 16384 1 i915
drm_kms_helper135168 1 i915
drm 360448 5 i915,drm_kms_helper,nvidia
video 40960 1 i915
Yes, I have
Sorry, meant to say nvidia-361 in last comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
Booting with intel graphics enabled results in a lockup
To manage notifications about
I've never run gpu-manager.
I use prime-select to choose between nvidia and intel.
I could not install wily on this laptop from a usb stick as the install
process locked up trying to load the graphics drivers. I had to start
with vivid as the older kernel did work. Upgrading to wily, the only way
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552209/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552213/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
Title:
And the dmesg output.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4552204/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the X log after adding the debug line.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1533221/+attachment/4552203/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Originally described in bug 1533221. This is a new bug to track this
additional issue separately.
The above bug has h/w info attached etc. This is a new skylake chipset.
Backlight function keys are not working. I have tried various
combinations of:
acpi_osi=Linux
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552211/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552210/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552217/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552214/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552212/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552215/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
apport information
** Tags added: apport-collected wily
** Description changed:
Originally described in bug 1533221. This is a new bug to track this
additional issue separately.
The above bug has h/w info attached etc. This is a new skylake chipset.
Backlight function keys are not
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552220/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552218/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552216/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552221/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1535470/+attachment/4552219/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535470
Title:
Using the latest 4.4.0 kernel, I can now boot. But only with nvidia
graphics card enabled. Intel graphics is still broken.
Backlight function keys are still not working. I have tried various
combinations of:
acpi_osi=Linux acpi_backlight=native
acpi_osi=Linux acpi_backlight=vendor
etc
with no
I have the nvidia binary drivers installed from the graphics-drivers ppa.
I use prime-select to choose either "nvidia" or "intel".
Using nvidia boots fine. When intel is selected:
- lightdm greeter screen displays in low res (maybe 640x480, not sure)
- logging in simply returns to the greeter
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549801/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549790/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549794/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549787/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549797/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549789/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The only kernel I can get to work at all in terms of allowing lightdm to
run and me to log in is 3.19.x
All Ubuntu kernels I have tried
- 4.2.0-23
- 4.3.0-6
- 4.4.0-0
cause boot to lock up. It's not just lightdm that fails. You can't even
Alt-Shift F1 to a console.
The only 4.x kernel that
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549791/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549793/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549798/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549795/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549799/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549800/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549796/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549792/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4549788/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533221
Title:
Public bug reported:
I have various hardware issues on a new Skylake laptop. The laptop has a
Nvidia GTX730 graphics card which can be switched off via bumblebee or
prime
1. Intel HD graphics
Booting with intel graphics enabled results in a lockup loading lightdm or
logging in results in the
apport information
** Tags added: apport-collected wily
** Description changed:
I have various hardware issues on a new Skylake laptop. The laptop has a
Nvidia GTX730 graphics card which can be switched off via bumblebee or
prime
1. Intel HD graphics
Booting with intel graphics
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1533221/+attachment/4548584/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Stephane,
Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?
--
You received this bug notification because you are a
Stephane, you are right. We can change Juju to use mangle the output of
the cloud-image-query to add "root.tar.xz". Is this guaranteed to always
work for all series / arch? Are there the correct root.tar.xz files on
cloud-image.ubuntu.com ?
--
You received this bug notification because you are a
Stephane,
Juju doesn't decide what images to use directly. It uses ubuntu-cloudimg-query
for that.
So this utility will need to be changed. It is in the cloud-image-utils package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My problem is worse than described Jim's previous comment - I don't need
to suspend or bring the interface down to see the issue. It happens
randomly, sometimes at very short intervals. Each time requires a reboot
to reset the network card/chipset so that it starts working again (for
an
Any update on this? It's still happening quite regularly on wily on
kernel 4.2.0-15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361646
Title:
Atheros wireless AR9285 keeps disconnecting
To
*** This bug is a duplicate of bug 1459912 ***
https://bugs.launchpad.net/bugs/1459912
This issue is supposed to be fixed in the latest Juju 1.24 release
https://launchpad.net/juju-core/+milestone/1.24.5
Please re-open if the issue is still observed.
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 1459912 ***
https://bugs.launchpad.net/bugs/1459912
This issue is supposed to be fixed in the latest Juju 1.24 release
https://launchpad.net/juju-core/+milestone/1.24.5
Please re-open if the issue is still observed.
** This bug has been marked a duplicate
@Seth, with the user mode containers - lxc didn't support that when the
local provider feature was first developed. And now we have lxd on the
horizon so we will be re-tooling local provider to use lxd and this will
be delivered for Juju 1.26 around end of January 2016. We don't plan on
making any
@Seth, with the user mode containers - lxc didn't support that when the
local provider feature was first developed. And now we have lxd on the
horizon so we will be re-tooling local provider to use lxd and this will
be delivered for Juju 1.26 around end of January 2016. We don't plan on
making any
RE: some of the issues raised in comment 48
- juju-backup shell script uses incorrect quoting method needlessly
Juju no longer uses a shell script for backup. That was a short term
implementation which has now been replaced by server side functionality
written in go.
- The local environment
RE: some of the issues raised in comment 48
- juju-backup shell script uses incorrect quoting method needlessly
Juju no longer uses a shell script for backup. That was a short term
implementation which has now been replaced by server side functionality
written in go.
- The local environment
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
On 28/07/15 18:26, Christian Reis wrote:
The code which sets up the role lives here:
https://github.com/juju/juju/blame/8da94246468a4da71e62894f7a8a1bbbce112697/mongo/admin.go#L136
The roles we are setting up are:
Roles: []mgo.Role{
mgo.RoleDBAdminAny,
Marked as Fixed Released, does it still occur?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications
Marked as Fixed Released, does it still occur?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications about this bug go to:
I have run up a precise instance in EC2 and added the cloud-tools-
proposed repo. The apt install of cloud-image-utils works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418568
Title:
Hi Brian and Scott,
The issue itself only appears on precise. On trusty, apt-get install
cloud-image-utils works fine. So would we not need to test with a fix to
the debs in precise-proposed in order to validate that things will now
work on precise?
--
You received this bug notification because
As per the cloud init output log in comment #2, on a precise system, if
you do:
apt-get install cloud-image-utils
apt-decides it needs to remove the cloud-init package (amongst others).
Suggested fix along the lines of:
smoser we can fix that with a packaging change to cloud-init in precise.
For now, I've worked around in Juju by not explicitly installing cloud-
image-utils. Where tis matter, in local providers, I've added a check to
ensure that cloud-image-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As per the cloud init output log in comment #2, on a precise system, if
you do:
apt-get install cloud-image-utils
apt-decides it needs to remove the cloud-init package (amongst others).
Suggested fix along the lines of:
smoser we can fix that with a packaging change to cloud-init in precise.
For now, I've worked around in Juju by not explicitly installing cloud-
image-utils. Where tis matter, in local providers, I've added a check to
ensure that cloud-image-utils is installed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory exists
** Changed in: juju-core
Milestone: 1.22 = 1.21-beta4
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: juju-core/1.21
Importance: Undecided = Medium
** Changed in: juju-core/1.21
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.21
Milestone: None = 1.21-beta4
** Changed in: juju-core/1.21
Status: New = In Progress
--
You received
** Changed in: juju-core/1.21
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated
** Changed in: juju-core
Milestone: 1.22 = 1.21-beta4
** Changed in: juju-core
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: juju-core/1.21
Importance: Undecided = Medium
** Changed in: juju-core/1.21
Assignee: (unassigned) = Ian Booth (wallyworld)
** Changed in: juju-core/1.21
Milestone: None = 1.21-beta4
** Changed in: juju-core/1.21
Status: New = In Progress
--
You received
** Changed in: juju-core/1.21
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Changed in: juju-core
Milestone: None = 1.22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Changed in: juju-core
Milestone: None = 1.22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory exists
To manage
** Changed in: juju-core
Status: Triaged = Incomplete
** Changed in: juju-core (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-core
Status: Triaged = Incomplete
** Changed in: juju-core (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316579
Title:
Removing this bug from juju-core as the issue required a cloud init fix.
** No longer affects: juju-core
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1353008
Title:
MAAS
1 - 100 of 211 matches
Mail list logo
