** Changed in: juju-core
Milestone: next-stable = None
--
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/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
** Tags added: scalability
--
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/1318378
Title:
rsyslog starts dropping connections in large environments
To manage notifications about
** Changed in: juju-core
Status: Triaged = Invalid
--
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/1314409
Title:
parallel juju deployments race on the same maas
To manage
** Changed in: juju-core
Milestone: next-stable = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications
** Tags added: scalability
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318378
Title:
rsyslog starts dropping connections in large environments
To manage notifications about this bug go to:
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314409
Title:
parallel juju deployments race on the same maas
To manage notifications about
** Tags added: rsyslog
--
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/1318378
Title:
rsyslog starts dropping connections in large environments
To manage notifications about this
** Tags added: rsyslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318378
Title:
rsyslog starts dropping connections in large environments
To manage notifications about this bug go to:
** Changed in: juju-core
Status: Triaged = Invalid
--
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/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
** Changed in: juju-core
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications
Used this in conjunction with Ubuntu 12.04 and Gnome Shell to display
CPU, Network, and Disk graphs in the top bar . After upgrading to 14.04
and continuing to use Gnome Shell, the graphs no longer work, but the
right click pull-down does work. Additionally, only one graph is now
shown, despite
Public bug reported:
This occurred during an upgrade from 12.04 to 14.04
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: manpages-dev 3.35-0.1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-59.90-generic 3.2.54
Uname: Linux 3.2.0-59-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Error messages such as:
Error fsyncing/closing /dev/sdb: Remote I/O error
Remote I/O error during write on /dev/sdb
often imply a hardware problem. This can be as simple as a loose cable,
all the way up to a failing hard drive.
If the drive supports smart monitoring, you can use the
Hmm... using sudo is how I would have run gsmartcontrol. It works
on my computer with kubuntu 12.04. Perhaps this is a new problem with
the latest xubuntu release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1.18.1 and 1.18.4 are compatible. We have verified that either version
acting as the client or the state-server can maintain a juju environment
though its life-cycle.
** Attachment added: Log of compatability test
** Changed in: juju-core
Milestone: 1.21-alpha1 = 1.21-alpha2
--
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:
logs are not logrotated
To manage notifications about
** Changed in: juju-core
Status: Fix Committed = 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/1322302
Title:
local provider is very slow to tranistion from
1.18.1 and 1.18.4 are compatible. We have verified that either version
acting as the client or the state-server can maintain a juju environment
though its life-cycle.
** Attachment added: Log of compatability test
** Changed in: juju-core
Milestone: 1.21-alpha1 = 1.21-alpha2
--
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:
logs are not logrotated
To manage notifications about this bug go to:
** Changed in: juju-core
Status: Fix Committed = 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/1322302
Title:
local provider is very slow to tranistion from agent-status:
** Changed in: juju-core
Status: Fix Committed = 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/1318366
Title:
jujud on state server panic misses transaction
** Changed in: juju-core
Status: Fix Committed = 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/1365480
Title:
new compiler breaks ppc64el unit tests in many ways
To manage
** Changed in: juju-core
Status: Fix Committed = 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/1318366
Title:
jujud on state server panic misses transaction in queue
To manage
In case you are wondering, I am the Debian package maintainer.
Please sync.
** Summary changed:
- Please update to latest Debian release (1.15.1-5)
+ Please sync openal-soft 1.15.1-3 (universe) from Debian unstable (main)
** Description changed:
- The latest updates fixes issues in packaging
These appear to be hardware errors. You might check to ensure that all
cables are securely plugged in and then try again.
The output from the following command would also be useful:
sudo parted -l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If there are fragmented NTFS or FAT16/32 file systems on a device, then
this can cause GParted to take a very long time to scan. This is
because the ntfsresize command and the dosfsck command can take a long
time to determine used and unused sectors.
One way to check for this issue is with the
In the past I tried which udisks2-inhibit to find the location of the
command, but this always returned no results. I didn't dig any deeper
because I regularly use Kubuntu and Ubuntu and the problem with
automounting does not occur.
Today I started my Ubuntu 14.04 Virtual Machine and ran the
** Summary changed:
- ppc64el unit tests fail in many ways
+ new compiler breaks ppc64el unit tests in many ways
** Also affects: gcc-4.9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gcc-4.9 (Ubuntu)
Status: New = Confirmed
** Changed in: juju-core
Importance:
Thanks Chris for your interest in improving GParted.
As far as I know, udisks2 *does not* contain a command to inhibit
automounting of devices.
In the past I was told that a udisks2-inhibit command existed, but I
have not been able to locate it.
If anyone knows how to inhibit or prevent
Thanks Alexander for reporting back that GParted with libparted 3.2
successfully works with fat32.
With the GParted option Partion - Check, GParted first runs a file
system check and then it will perform a file system resize to maximum to
ensure the file sytem uses the entire partition.
It
Alexander, would you be able to try the latest GParted Live 0.19.1-4?
This newest Live image include gparted 0.19.1 linked with libparted
3.2-5. In my testing of fat32 resizes, all completed successfully with
this newer libparted version.
--
You received this bug notification because you are a
This problem has been resolved upstream. See:
Prevent GSource double-destroy warning messages
https://bugzilla.gnome.org/show_bug.cgi?id=729800
** Bug watch added: GNOME Bug Tracker #729800
https://bugzilla.gnome.org/show_bug.cgi?id=729800
--
You received this bug notification because you
Public bug reported:
The latest updates fixes issues in packaging that could cause
problems/headaches for users in Utopic.
libopenal-dev-bin has been split out to openal-info and makehrtf
libopenal-data now includes the sample /etc/openal/alsoft.conf, which
was missing in 1.15.1-3
** Affects:
Would you be able to try the latest version of GParted (currently
0.19.1). One way to do this is by booting from media containing GParted
Live. See http://gparted.org/livecd.php
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Alexander, I believe the problem is with the underlying libparted
library. The problem exists in Ubuntu 14.04 with libparted
2.3-19ubuntu1, and also with our latest GParted Live 0.19.1-1 with
libparted0debian1:i386 2.3-20.
As such, there is no need to perform the test I requested.
Instead I
This should be fixed, if this isn't the case, please re-open the bug.
** Changed in: openal-soft (Ubuntu)
Status: New = Incomplete
** Changed in: openal-soft (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: openal-soft (Ubuntu)
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/926779
Title:
no icon visual in unity and unity 2d
To manage notifications about this
I'm assuming that this is fixed upstream because I could on test on a
later version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750906
Title:
OpenAL default config file needs change to stop
I'm unable to reproduce, closing for lack of further testing.
Feel free to re-open if there is additional information.
** Changed in: openal-soft (Ubuntu)
Status: New = Incomplete
** Changed in: openal-soft (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug
** Tags added: panic
--
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/1347322
Title:
juju ssh results in a panic: runtime error
To manage notifications about this bug go to:
** Changed in: juju-core/1.20
Status: Fix Committed = 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/1318366
Title:
jujud on state server panic misses
** Tags added: panic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
juju ssh results in a panic: runtime error
To manage notifications about this bug go to:
** Changed in: juju-core/1.20
Status: Fix Committed = 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/1318366
Title:
jujud on state server panic misses transaction in queue
To
Public bug reported:
Attached is a comparison between Windows, Android, iOS(6) and tentative
Ubuntu icons. The first 3 application icons bare a striking similarity
to the IOS(6) equivalent while the last to Google Maps.
The browser icon assumes familiarity with Safari, or possibly Webkit. A
** Changed in: juju-core
Status: New = Incomplete
--
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/1355813
Title:
LXC containers reset bridge MTU on start/restart
To manage
** Changed in: juju-core
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/1355813
Title:
LXC containers reset bridge MTU on start/restart
To manage notifications about
** Tags added: ubuntu-engineering
** Changed in: juju-core
Importance: Medium = High
** 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 lxc in Ubuntu.
No point in keeping it open if it no longer a problem. ;)
Are you still getting this issue, even with 1.14?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719763
Title:
Segfault in MixSomeSources
** Tags added: ubuntu-engineering
** Changed in: juju-core
Importance: Medium = High
** 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.
We may find this issue is fixed in 1.20. We need to test this.
--
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/1349771
Title:
ppc64 architecture miss match for MAAS ppc64el
To
We may find this issue is fixed in 1.20. We need to test this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349771
Title:
ppc64 architecture miss match for MAAS ppc64el
To manage notifications
There is/was no maas for ppc64 to test with. I am not aware there is a
maas for ppc64 and that it support LE containers.
--
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/1349771
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: kvm streams
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
There is/was no maas for ppc64 to test with. I am not aware there is a
maas for ppc64 and that it support LE containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349771
Title:
ppc64
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: kvm streams
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317680
** Tags added: ppc64el
--
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/1349771
Title:
ppc64 architecture miss match for MAAS ppc64el
To manage notifications about this bug go to:
Juju uses golang's naming conventions. Juju *should* map ppc64el to
ppc64. Which version of Juju are you using?
This was a bug in Juju 1.18.x. where the wrong architecture was selected
for some cloud providers. I closed the bug when manual-provider and
local-kvm tests passed.
Since this issue
** Tags added: ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349771
Title:
ppc64 architecture miss match for MAAS ppc64el
To manage notifications about this bug go to:
Juju uses golang's naming conventions. Juju *should* map ppc64el to
ppc64. Which version of Juju are you using?
This was a bug in Juju 1.18.x. where the wrong architecture was selected
for some cloud providers. I closed the bug when manual-provider and
local-kvm tests passed.
Since this issue
Discussing the options now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1348393
Title:
OpenAL 1.15.x Breaks Multiarch
To manage notifications about this bug go to:
** Changed in: juju-core
Milestone: next-stable = 1.21-alpha1
--
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/1318366
Title:
jujud on state server panic misses transaction in
This was likely fixed in = 1.12, but not sure where. I just tested
with latest: 1.14 using speed-dreams to test:
00:00:10.618 Trace Loaded /home/bcurtis/.speed-dreams-2/config/sound.xml
(0x3079b70)
00:00:10.618 InfoInitializing sound engine (openal)
00:00:10.633 InfoOpenAL backend
This is outside the scope of Ubuntu, but I contacted Chris of OpenAL-
Soft to get his thoughts:
It's up to the app to specify the listener position/orientation (which
the sound panning is based on).
** Changed in: openal-soft (Ubuntu)
Status: New = Invalid
--
You received this bug
Have you tried lately, we're now so many releases further and according
to OpenAL-Soft's developers, that part of the code as been re-worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719763
I personally cannot reproduce this and I'm using PA (listening to music
in the background) and tried openarena without issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719763
Title:
Segfault
** Changed in: juju-core
Milestone: next-stable = 1.21-alpha1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318366
Title:
jujud on state server panic misses transaction in queue
To manage
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: ppc64el
--
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
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: ppc64el
--
You received this bug
** Changed in: juju-core
Status: New = Triaged
--
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/1307215
Title:
destroy-environment fails to clear lxc containers
To manage
** Changed in: juju-core
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307215
Title:
destroy-environment fails to clear lxc containers
To manage notifications about
Hi all. Yes, it's so frustrating, that this problem/crash happening for
a long time, without any reaction. I mean without any update for a
Precise. It seems, that this issue is not so important from a Developers
points of view. In fact, it is not a security or stability matter,
right?
Best
** Summary changed:
- [juju/lxc] juju local deploy on kvm machine using lxc failed with error:
error executing lxc-start
+ error: error executing lxc-start when juju client runs inside kvm
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided =
** Summary changed:
- [juju/lxc] juju local deploy on kvm machine using lxc failed with error:
error executing lxc-start
+ error: error executing lxc-start when juju client runs inside kvm
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided =
Is this still the case?
If there no further discussion after 30 days, we'll close this.
** Changed in: openal-soft (Ubuntu)
Status: Confirmed = New
** Changed in: openal-soft (Ubuntu)
Assignee: (unassigned) = Bret Curtis (psi29a)
--
You received this bug notification because you
** Changed in: openal-soft (Ubuntu)
Status: New = Invalid
** Changed in: openal-soft (Ubuntu)
Assignee: (unassigned) = Bret Curtis (psi29a)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
OpenAL 1.11 is a bit old (like this bug report), I'm going to ask that
you retry with the latest 1.14 release to see if you have the same
problem.
** Changed in: openal-soft (Ubuntu)
Assignee: (unassigned) = Bret Curtis (psi29a)
--
You received this bug notification because you
OSS isn't installed in Ubuntu, ALSA is. There are wrappers that emulate
OSS behaviour but are not installed by default.
Setting drivers=oss isn't really an option. Can you suggest another
alternative?
** Changed in: openal-soft (Ubuntu)
Assignee: (unassigned) = Bret Curtis (psi29a)
--
You
Bug was fixed with the latest release of OpenAL-Soft. Closing.
** Changed in: openal-soft (Ubuntu)
Assignee: (unassigned) = Bret Curtis (psi29a)
** Changed in: openal-soft (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member
** Changed in: juju-core
Status: Fix Committed = 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/1250007
Title:
Bootstrapping azure causes memory to fill
To
** Changed in: juju-core
Status: Fix Committed = 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/1250007
Title:
Bootstrapping azure causes memory to fill
To manage notifications
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: local-provider
** Summary changed:
- Local provider assumes a local ubuntu user exists
+ Local provider run on cloud images want ubuntu user
--
You received this
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
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/1332820
Title:
QA
** Summary changed:
- Local provider run on cloud images want ubuntu user
+ Local provider run on server images requires an ubuntu user
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
own local lxc bootstrap
ls -l /home/curtis/.juju/local/cloud-init-output.log
-rw-r--r-- 1 root root 4218 Jun 24 11:23
/home/curtis/.juju/local/cloud-init-output.log
Test of local lxc bootstrap on a trusty server as another user (which I expect
ubuntu to exist on)
$ ls -l $JUJU_HOME/local-trusty
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: local-provider
** Summary changed:
- Local provider assumes a local ubuntu user exists
+ Local provider run on cloud images want ubuntu user
--
You received this
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332820
Title:
QA tests provide a
** Summary changed:
- Local provider run on cloud images want ubuntu user
+ Local provider run on server images requires an ubuntu user
--
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:
own local lxc bootstrap
ls -l /home/curtis/.juju/local/cloud-init-output.log
-rw-r--r-- 1 root root 4218 Jun 24 11:23
/home/curtis/.juju/local/cloud-init-output.log
Test of local lxc bootstrap on a trusty server as another user (which I expect
ubuntu to exist on)
$ ls -l $JUJU_HOME/local-trusty
** Changed in: juju-core
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.
https://bugs.launchpad.net/bugs/1328958
Title:
Local provider assumes a local ubuntu user exists
To
Are you saying that the juju unittests require an ubuntu user to be
defined on the machine that runs the tests?
** Changed in: juju-core
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
The Juju CI tests do two non obvious things to test the local provider.
1. Never su to the testing account. Always log directly in.
2. Always export USER=jenkins so that juju knows which user owns the containers.
--
You received this bug notification because you are a member of Ubuntu
Server
I do not this issue. None of our own machines have an ubuntu user and
juju works. Juju requires the machines it provisions to have an ubuntu
user.
Juju uses the login user as the identity for the local db and
containers. The user account that is doing the deploy must export
USER=user, this is the
** Changed in: juju-core
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/1328958
Title:
Local provider assumes a local ubuntu user exists
To manage notifications
The Juju CI tests do two non obvious things to test the local provider.
1. Never su to the testing account. Always log directly in.
2. Always export USER=jenkins so that juju knows which user owns the containers.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Are you saying that the juju unittests require an ubuntu user to be
defined on the machine that runs the tests?
** Changed in: juju-core
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I do not this issue. None of our own machines have an ubuntu user and
juju works. Juju requires the machines it provisions to have an ubuntu
user.
Juju uses the login user as the identity for the local db and
containers. The user account that is doing the deploy must export
USER=user, this is the
** Summary changed:
- juju-machine-agent.log/logs are not logrotated
+ logs are not logrotated
--
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:
logs are not logrotated
** Summary changed:
- juju-machine-agent.log/logs are not logrotated
+ logs are not logrotated
--
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:
logs are not logrotated
To manage
The destruction of the local env is responsible for SIGABRTing mongod,
removing, local files (specifically .juu/local/db in the case) and
removing the env's upstart scripts. Uninstalling the package will remove
what the services and files it installed...it didn't install the local
db or the
This problem was fixed with the upstream release of GParted 0.19.0 on
June 10, 2014.
The link to the relevant upstream report is as follows:
Partition Information Dialog Warning not readable
https://bugzilla.gnome.org/show_bug.cgi?id=690542
** Bug watch added: GNOME Bug Tracker #690542
901 - 1000 of 5893 matches
Mail list logo
