[Bug 1267393] Juju MIR resposne
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 torn down so shortly after including 1.18 in a release with > five-year support? I believe that this change was primarily brought about by the change from using bzr to git. The build and test infrastructure had to be re-tooled to make this work. > Have there been any similar changes in process that > would prevent or delay issuing an update to the currently supported > versions of juju already in the archive? We are unlikely to change from git. > It is currently impossible to upgrade from 14.04 LTS to 15.04 due to > incorrect version numbers. Has anyone else noticed this yet? When will > this be fixed? Are there any changes in process needed to ensure this > doesn't happen in the future? The older versions of Juju were not very good at handling unknown series. I have targeted a previously created bug to address this: https://bugs.launchpad.net/juju-core/+bug/1403689 There are work-arounds that have been used by IS to upgrade older environments. We do test a number of upgrade combinations, and I'm curious as to why you say it is impossible to upgrade? What exactly is the situation you are attempting? > Will the juju team be asking for an MRE? Is it anticipated that new series > (e.g., the 1.18 to 1.22 change) would be included as an MRE? What > processes are in place to test updates before including updates into the > archive? What processes are available to the security team to test > updates that we would prepare? There are CI tests around upgrading from older versions to the current tested release. I believe that one of these tests includes going from 1.18 to the current tested release. > I had more trouble reading the Juju code this review cycle than last > review cycle -- the Facade indirection mechanism makes code navigating > harder. I'm worried about it for a few reasons: > - Strings to reference method names are brittle and can't be checked at > compile time. What methods are in place to ensure that these aren't > typoed? There are unit tests in place that test both the client and server side of every call, and in addition to that there are full feature tests that make sure all the parts align. > - Generic args and return types defeat type checking. What ensures types > being returned or accepted have the desired properties? The specified unit and feature tests. > - Java has had significant problems with their Reflection mechanism, > probably dozens of issues per year. At what points of a process > lifetimes is the Facade mechanism dynamic? During the low level RPC call from the client to the API server. > Here's a few issues I found: > > - ./apiserver/apiserver.go logs passwords when tracing is enabled -- this > is fine IFF this is loudly documented somewhere obvious. Is it? It'd be > best to filter out passwords regardless. I have created a bug to address this more completely: https://bugs.launchpad.net/juju-core/+bug/1500298 > - Chown() doesn't quote the user or group In which cases is this really necessary? All the chowns that the Juju code base does is to either ubuntu, syslog or adm. Other chowns copy the uid/gid directly from the source. > - ./api/client.go WatchDebugLog() claims to read a line but looks like it > may read up to 4096 bytes -- is this correct? The first line returned in the WatchDebugLog is a serialized error, and only a serialized error. The size of the error is always less than 200 bytes, but 4k is a nice block size. Once this initial error has been returned, the websocket is used as a stream. > - significant number of TODO comments; is there a method in place to find > unowned comments and assign them somewhere? is there a process in place > to ensure they get revisited? I don't believe we have a formal process at this stage. New TODO comments are expected to have an associated bug, and a date. > - Which versions of the client work with which versions of the servers? > Where's that described? All clients from 1.18 on should work with any API server. This is the expected behaviour until at least Juju 2.0. > - ./api/keyupdater/authorisedkeys.go AuthorisedKeys(), > WatchAuthorisedKeys() expects exactly one authorized key, this seems > fragile I believe it expects one string, which may be multi-line, and each key is on a different line. > - Is -static-libgo still being used? No idea sorry. > I'm concerned with how previous issues have been handled -- the three > referenced bug reports have combined to represent the single most > expensive consequence I've personally seen and all were known issues five > months earlier. So I need reassurance that the Juju team will help the > security team maintain Juju in our supported
[Bug 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** 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/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1348386] Re: lxc template fails to stop
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 option -- 'L' Usage: lxc-start --name=NAME -- COMMAND lxc-start start COMMAND in specified container NAME Options : -n, --name=NAME NAME for name of the container -d, --daemon daemonize the container -f, --rcfile=FILELoad configuration file FILE -c, --console=FILE Set the file output for the container console -C, --close-all-fds If any fds are inherited, close them If not specified, exit with failure instead Note: --daemon implies --close-all-fds -s, --define KEY=VAL Assign VAL to configuration variable KEY Common options : -o, --logfile=FILE Output log to FILE instead of stderr -l, --logpriority=LEVEL Set log priority to LEVEL -q, --quiet Don't produce any output -?, --help Give this help list --usage Give a short usage message Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. See the lxc-start man page for further information. ubuntu@clean-precise:~$ echo $? 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1348386 Title: lxc template fails to stop To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1348386/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: template container contains user log mount in error
I found that the code was committed back in march to not mount the log dir in the container. My juju-precise-template lxc container had a line that include a mount to /home/tim/.juju/local/log, which caused cgroups to complain when logged in as my other local user. Removing the juju-precise-template and getting juju to recreate it fixed the problem for me. My template container was created about a week before the code landed in trunk. @pitti, can I get you to take a look inside the config file for the lxc container to see if you have a similar problem? ** Changed in: juju-core 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 notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: non-default lxc-dir breaks local provider
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/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** 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 of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: template container contains user log mount in error To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
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 created, the log mount points are added. What this means is that other users on the same machine will not be able to mount the log directory as specified in the container lxc config file, and the cgroup setting will fail. One solution to this is to have a template container per user rather than a shared one. ** Tags added: local lxc regression ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New = Triaged ** Changed in: juju-core Importance: Undecided = High -- 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 LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** 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 LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1208430] Re: mongodb runs as root user
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://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
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 networking' ** Branch linked: lp:~thumper/juju-core/maas-no-restart-networking -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1292353] Re: juju must install the libgo.so.5 library when required
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 Status: Triaged = 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/1292353 Title: juju must install the libgo.so.5 library when required To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1292353/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** 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 architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
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: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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 service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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 on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** 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/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
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 explain the change? hallyn juju uses autostart? stgraber thumper: yes, autostart settings are now upstream and use the container's config instead thumper hallyn: yep, stgraber thumper: I believe I already told someone this morning wrt juju stgraber thumper: use lxc.start.auto = 1 in the container config thumper stgraber: don't expect us to talk to each other :-) hallyn stgraber: remind me, is there any attempt at auto-conversion for /etc/lxc/auto/ users? stgraber hallyn: yes, there's migration code, but it won't do them much good for new juju containers hallyn heh yah stgraber any container on the system at the time of the upgrade to beta2 should have been automatically converted (symlink removed, /etc/lxc/auto removed and lxc.start.auto = 1 added to the container config) thumper stgraber: is this lxc going into the cloud archive? thumper stgraber: for precise? thumper is there a way we can work out if this is supported? stgraber thumper: maybe hallyn knows, I usually ignore the existence of that external archive entirely -*- thumper nods stgraber thumper: rule of thumb would be, if /etc/lxc/auto exists, use it, if not, use lxc.start.auto = 1 thumper stgraber: that makes sense... thumper should be able to handle that pretty easily -- 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 service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1240709] Re: local provider fails to start
** 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 notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240709/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1246556] Re: lxc containers broken with maas
** 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 this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** 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 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by 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 Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
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] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204302] Re: fails to bootstrap, returns error: no reachable servers
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1204302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** 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 notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** 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 you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1210054 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1210431] [NEW] syslog stops logging when lxc containers autostart
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 reboot fixed this problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Fri Aug 9 09:06:45 2013 InstallationDate: Installed on 2012-04-26 (469 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-02-22 (168 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1210431 Title: syslog stops logging when lxc containers autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1210431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1078213] Re: juju-machine-agent.log/logs are not logrotated
** 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://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
