** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870758
Title:
[nvidia] Display scaling results in a blank screen (power save state)
To manage notifications about this bug
Hey there, tested the proposed -48 kernel. Did 15 reboot cycles and
everything started every time. Last time it succeeded approximately 90%
of the time. That is whey I went to 15 this time. Seems good.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You
** Changed in: juju
Status: New => Triaged
** Changed in: juju
Importance: Undecided => High
** Changed in: juju
Assignee: (unassigned) => Richard Harding (rharding)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes I intend to test the mainline kernel when I'm back home from the
sprint
On 20/02/19 2:59 AM, Kai-Heng Feng wrote:
> Hi Tim,
>
> Would it be possible for you to test mainline kernel [1]? It probably
> requires more commits to be backported. But first let's make sure it's
> fully fixed in
It seems my install was missing the linux-generic package. After
installing that I was able to get linux-generic 4.15.0.46.48 from
bionic-proposed.
Installing this removed the windows boot option from my grub config.
Rebooting 12 times, 10 times were good, twice I got dumped into
initramfs.
Will this fix make its way back into the bionic-updates?
Tim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811755
Title:
X1 Extreme: only one of the two SSDs is loaded
To manage notifications
got the packages installed in the end, and so far has booted every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811755
Title:
X1 Extreme: only one of the two SSDs is loaded
To manage
hit the following error installing the test kernel
tim@terry:~/Downloads$ ls *.deb
linux-headers-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb
linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb
linux-modules-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb
Yes, I can boot into the 512G disk approximately 50% of the time :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811755
Title:
X1 Extreme: only one of the two SSDs is loaded
To manage
Public bug reported:
I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one
256G and the other 512G with the intention of keeping the windows on the
256G disk and using the 512G for linux.
When dealing with the installer, it only ever saw one of the SSDs. I did
manged to get
** Changed in: juju-core
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727355
Title:
Juju attempts to bootstrap bionic by default
To manage notifications about
** Changed in: juju
Milestone: None => 2.3.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729127
Title:
storage: No available machine matches constraints
To manage notifications about this
** Changed in: juju
Milestone: 2.3.0 => 2.3-beta3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729127
Title:
storage: No available machine matches constraints
To manage notifications about
This appears to be happening once or twice a day.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708058
Title:
machine locks up - completely non-responsive
To manage notifications about this bug
Public bug reported:
Starting a few days ago, machine will just lock up. After the most
recent lock up, I looked in /var/log/syslog, and found the following:
Aug 2 12:17:01 elwood kernel: [58062.900931] BUG: unable to handle kernel NULL
pointer dereference at 0018
Aug 2 12:17:01
Added above stacktrace to pastebin for easier reading:
http://pastebin.ubuntu.com/25223455/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708058
Title:
machine locks up - completely non-responsive
** No longer affects: juju
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1602192
Title:
when starting many LXD containers, they start failing to boot with
"Too many open files"
To manage
Is at least fixed on 2.1.3
** Changed in: juju
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475260
Title:
instances cannot resolve their own hostname
To
WARNING: don't use the script in comment #16, but instead use this one:
http://pastebin.ubuntu.com/24186473/
This is a copy of the earlier script but adds in the txn-revno and txn-
queue fields that are required for when juju wants to update the status
to something new.
--
You received this
** 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/1543660
Title:
juju needs to fix the yaml parser
To manage notifications about this
Pull request up for the upstream project: https://github.com/go-
yaml/yaml/pull/241.
Juju patching the upstream for its builds:
https://github.com/juju/juju/pull/6983
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju
Assignee: (unassigned) => Tim Penhey (thumper)
** Changed in: juju
Status: Triaged => In Progress
** Changed in: juju
Milestone: 2.2.0 => 2.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Having to push this off the 2.1 milestone due to the dependent library
not supporting this use case.
** Changed in: juju
Milestone: 2.1.0 => 2.2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/go-yaml/yaml/issues/157 has been closed, but the PR
mentioned doesn't fix this issue.
Juju is being updated, but until go-yaml fixes it, we still have a
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: indicator-appmenu (Ubuntu)
Assignee: Tim Penhey (thumper) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026088
Title:
HUD should support applications using b
This is an answer to some of the questions Seth asked
> In 1339770, in May 2015, it was mentioned that 1.18 was end-of-life and no
> further updates could be prepared for it. 1.18.0 was released just 13
> months earlier and 1.18.1 had been included in 14.04 LTS. Why was the 1.18
> infrastructure
This is an answer to some of the questions Seth asked
> In 1339770, in May 2015, it was mentioned that 1.18 was end-of-life and no
> further updates could be prepared for it. 1.18.0 was released just 13
> months earlier and 1.18.1 had been included in 14.04 LTS. Why was the 1.18
> infrastructure
Dave has done some testing, and we are pretty sure that this is due to
lack of memory. Can you confirm please the amount of memory on the
machine or VM running these tests, and the memory use of the test
process?
We were not able to reproduce these problems on a VM running with 8gig
or ram.
**
** Also affects: juju-core/1.21
Importance: Undecided
Status: New
** Changed in: juju-core
Milestone: 1.21-beta4 = 1.22
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Also affects: juju-core/1.21
Importance: Undecided
Status: New
** Changed in: juju-core
Milestone: 1.21-beta4 = 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:
I can verify that with the above package from trusty-proposed, I was
able to bootstrap a local juju environment on rockne-02.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
However rockne-02 has a 4k page :-(
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304754
Title:
gccgo has issues when page size is not 4kB
To manage
Gah, must have looked at the page size of my laptop instead:
ubuntu@rockne-02:~$ juju status
environment: local
machines:
0:
agent-state: down
agent-state-info: (started)
agent-version: 1.18.4.1
dns-name: localhost
instance-id: localhost
series: trusty
services: {}
Tested on a precise lxc container I have:
it seems we could try with -L (or even better --console-log) and fall
back to -c (or --console) if that fails with exit code 1 (we could even
check the output for invalid option.
ubuntu@clean-precise:~$ lxc-start -n foo -L omg
lxc-start: invalid
Tested on a precise lxc container I have:
it seems we could try with -L (or even better --console-log) and fall
back to -c (or --console) if that fails with exit code 1 (we could even
check the output for invalid option.
ubuntu@clean-precise:~$ lxc-start -n foo -L omg
lxc-start: invalid
Assignee: Tim Penhey (thumper) = (unassigned)
** Changed in: juju-core
Importance: High = Low
** Changed in: juju-core
Milestone: next-stable = None
** Summary changed:
- template container contains user log mount in error
+ non-default lxc-dir breaks local provider
--
You received this bug
Gah, I should read the entire description before changing things. This
was a different problem to me that had exactly the same error message.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
Assignee: Tim Penhey (thumper) = (unassigned)
** Changed in: juju-core
Importance: High = Low
** Changed in: juju-core
Milestone: next-stable = None
** Summary changed:
- template container contains user log mount in error
+ non-default lxc-dir breaks local provider
--
You received this bug
Gah, I should read the entire description before changing things. This
was a different problem to me that had exactly the same error message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290920
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Summary changed:
- fails to start container with local provider with non-default LXC path
+ template container contains user log mount in error
--
You received this bug notification because you are a member
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Summary changed:
- fails to start container with local provider with non-default LXC path
+ template container contains user log mount in error
--
You received this bug notification because you are a member
It seems to me that the bug isn't in the different container directory,
but the way that the log directory is mounted.
I have just hit this same problem locally, and I don't have a non-
default directory.
What I do have though is two different users locally.
When the juju conatiner template is
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
fails to start container with local provider with non-default
It seems to me that the bug isn't in the different container directory,
but the way that the log directory is mounted.
I have just hit this same problem locally, and I don't have a non-
default directory.
What I do have though is two different users locally.
When the juju conatiner template is
** Changed in: juju-core
Milestone: None = next-stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290920
Title:
fails to start container with local provider with non-default LXC path
To
Critical is a stop the line type bug. No one is being assigned to it
right now, so it isn't Critical.
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
Critical is a stop the line type bug. No one is being assigned to it
right now, so it isn't Critical.
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can someone please test this?
lp:~thumper/juju-core/maas-no-restart-networking
I don't have a MAAS setup to hand, but according to the code above, this
*should* work.
Now we go
ifdown eth0
before messing with the network config, and
ifup eth0
ifup br0
after, and no 'restart
Can someone please test this?
lp:~thumper/juju-core/maas-no-restart-networking
I don't have a MAAS setup to hand, but according to the code above, this
*should* work.
Now we go
ifdown eth0
before messing with the network config, and
ifup eth0
ifup br0
after, and no 'restart
** 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/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
I have two users on my laptop, in an attempt to have different sessions
for different work.
Switching from one user to another takes me to the greeter to enter my
password, but when the new session starts, it immediately takes me to
the new lockscreen and requests the password again. This is very
** Changed in: juju-core
Status: In Progress = Fix Released
** Changed in: juju-core
Milestone: 1.20.0 = 1.17.6
--
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/1276909
Marking as fix committed for trunk developers.
We should also make sure the build commands for the package are updated.
** Branch linked: lp:~thumper/juju-core/power-static-link-make
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
** Changed in: juju-core
Status: In Progress = Fix Released
** Changed in: juju-core
Milestone: 1.20.0 = 1.17.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276909
Title:
error
:~thumper/juju-core/local-provider-aufs-default-off
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Marking as fix committed for trunk developers.
We should also make sure the build commands for the package are updated.
** Branch linked: lp:~thumper/juju-core/power-static-link-make
** Also affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: juju-core
or a chown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes filesystem permission
breakages
To manage notifications about this bug go to:
Shouldn't aufs catch a chmod to a directory that isn't in the delta and
copy it across?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549
Title:
Filesystem mount from lxc template causes
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
--
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
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
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/1276909
Title
** Branch linked: lp:~thumper/juju-core/arm64-identification
--
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/1276909
Title:
error detecting hardware characteristics: unrecognised
I've made a branch out of the patches (well, manually did it). @dann can
I get you to give the diff a once over?
--
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/1276909
Title:
** Branch linked: lp:~thumper/juju-core/arm64-identification
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276909
Title:
error detecting hardware characteristics: unrecognised architecture:
I've made a branch out of the patches (well, manually did it). @dann can
I get you to give the diff a once over?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276909
Title:
error detecting
** 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/1271941
Title:
lxc container creation fails on trusty host
** 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/1271941
Title:
lxc container creation fails on trusty host service units
To manage
** Changed in: juju-core
Assignee: Tim Penhey (thumper) = Jesse Meek (waigani)
--
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/1271941
Title:
lxc container creation fails
** Changed in: juju-core
Assignee: Tim Penhey (thumper) = Jesse Meek (waigani)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271941
Title:
lxc container creation fails on trusty host service
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
--
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
thumper hallyn: has the autostart behaviour for lxc changed in trusty?
hallyn thumper: yes, stgraber's new autostart setup may be in now. certainly
in the ppa
stgraber hallyn: yep, it landed with beta2 last week
thumper hallyn: hmm... managed to break juju's behaviour
thumper hallyn: can you
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
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/1271941
Title
thumper hallyn: has the autostart behaviour for lxc changed in trusty?
hallyn thumper: yes, stgraber's new autostart setup may be in now. certainly
in the ppa
stgraber hallyn: yep, it landed with beta2 last week
thumper hallyn: hmm... managed to break juju's behaviour
thumper hallyn: can you
I am currently running saucy, and on a different laptop. No longer
experiencing this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043562
Title:
[gm45] GPU lockup EIR: 0x0010
** Changed in: juju-core (Ubuntu Saucy)
Status: New = Fix Released
--
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/1240709
Title:
local provider fails to start
To manage
** Changed in: juju-core (Ubuntu Saucy)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240709
Title:
local provider fails to start
To manage notifications about
cgroups doesn't come in with build-essential, but it is being brought in
by mistake because the lxc package was being installed by mistake in the
local provider machines.
** Branch linked: lp:~thumper/juju-core/local-provider-machines-no-lxc
--
You received this bug notification because you are
** Also affects: juju-core/1.16
Importance: Undecided
Status: New
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core/1.16
Milestone: None = 1.16.3
** Changed in: juju
** Branch linked: lp:~thumper/juju-core/fix-local-lxc-install-1.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247299
Title:
apparmor blocks cgroup-lite from mounting
To manage notifications
** Changed in: juju-core
Status: In Progress = Fix Committed
** Changed in: juju-core/1.16
Status: In Progress = Fix Committed
** Summary changed:
- apparmor blocks cgroup-lite from mounting
+ local provider deploys fail with 'install hook failed'
--
You received this bug
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: local-provider
** Changed in: juju-core
Milestone: None = 1.17.0
--
You received this bug
** Branch linked: lp:~thumper/juju-core/maas-lxc-trunk
--
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/1246556
Title:
lxc containers broken with maas
To manage notifications
** Branch linked: lp:~thumper/juju-core/maas-lxc-trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246556
Title:
lxc containers broken with maas
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: 1.15.0 = 1.15.1
** 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/1210054
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Milestone: None = 2.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: juju-core
Milestone: 1.15.0 = 1.15.1
** 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/1210054
Title:
juju
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Milestone: None = 2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1.16 will also fix the local provider, which is broken on saucy with
1.14 due to changes in upstart and lxc.
--
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/1219879
Title:
[FFe]
1.16 will also fix the local provider, which is broken on saucy with
1.14 due to changes in upstart and lxc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219879
Title:
[FFe] juju-core 1.16 for
** Changed in: juju-core
Status: New = Invalid
--
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/1204302
Title:
fails to bootstrap, returns error: no reachable servers
To
** Tags added: maas
** Summary changed:
- juju destroy-environment also destroys nodes that are not controlled by juju
+ [maas] juju destroy-environment also destroys nodes that are not controlled
by juju
** Changed in: juju
Importance: Undecided = High
--
You received this bug
** Changed in: juju-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204302
Title:
fails to bootstrap, returns error: no reachable servers
To manage notifications
** Tags added: maas
** Summary changed:
- juju destroy-environment also destroys nodes that are not controlled by juju
+ [maas] juju destroy-environment also destroys nodes that are not controlled
by juju
** Changed in: juju
Importance: Undecided = High
--
You received this bug
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Milestone: None = 1.15.0
** Branch linked: lp:~thumper/juju-core/lxc-stopping
--
You received this bug notification because
** Changed in: juju-core
Status: Triaged = In Progress
** Changed in: juju-core
Assignee: (unassigned) = Tim Penhey (thumper)
** Changed in: juju-core
Milestone: None = 1.15.0
** Branch linked: lp:~thumper/juju-core/lxc-stopping
--
You received this bug notification because
Public bug reported:
I noticed that my syslog file was empty, and some cursory googling
suggested that it may be libvirt.
I had a juju local environment set up which had some containers
autostarting. Destroying this environment, and making sure there were
no autostart containers, followed by a
Public bug reported:
I noticed that my syslog file was empty, and some cursory googling
suggested that it may be libvirt.
I had a juju local environment set up which had some containers
autostarting. Destroying this environment, and making sure there were
no autostart containers, followed by a
** Tags added: logging
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage notifications about this bug go to:
** Tags added: logging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
juju-machine-agent.log/logs are not logrotated
To manage notifications about this bug go to:
On 10/04/13 03:01, Brian Murray wrote:
Tim the log files from your upgrade may still be helpful in sorting out
why this did not get installed.
Which files do you want to see?
$ ll /var/log/dist-upgrade/20130222-1012/
total 436
drwxr-xr-x 2 root root 4096 Feb 22 10:12 ./
drwxr-xr-x 5 root
On 09/04/13 06:02, Brian Murray wrote:
gnome-control-center-unity is part of the following tasks:
Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb
$ apt-cache policy gnome-control-center-unity
gnome-control-center-unity:
Installed: (none)
Candidate:
1 - 100 of 1042 matches
Mail list logo
