** 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:
https
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 r
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 t
** 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
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 ne
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.
https
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 c
** 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
** 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
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 rece
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.
https://bugs.launchpad.net/bu
** 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 notificatio
** 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 ma
** 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 notificati
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] ju
** 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,
** 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 about
** 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 n
** 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.
hallyn: has the autostart behaviour for lxc changed in trusty?
thumper: yes, stgraber's new autostart setup may be in now. certainly
in the ppa
hallyn: yep, it landed with beta2 last week
hallyn: hmm... managed to break juju's behaviour
hallyn: can you explain the change?
juju uses autostar
** 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
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 serv
** 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 a
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:
erro
** 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.
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 o
** 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.
https://bugs.launchpad.net/bugs
29 matches
Mail list logo
