** Changed in: juju-core/1.21
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/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** Tags added: lxc network
** 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/1402763
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
I think my test of juju-quickstart + juju-core failed because my env is
dirty. I get the same errors on trusty with the packages in release and
updates. I will retest with a clean trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to
the bootstraped start-server to deploy services.
18:40:09 WARNING app@connect:300 Retrying: unable to connect to the
Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510:
error:14090086:SSL
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
juju-quickstart 1.3.1 + juju-core 1.20.11 in trusty cannot connect to
the bootstraped start-server to deploy services.
18:40:09 WARNING app@connect:300 Retrying: unable to connect to the
Juju API server on wss://165.225.151.107:17070: [Errno 1] _ssl.c:510:
error:14090086:SSL
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
lxc*1.0.3 looks odd. That is one version I don't expect to see.
trusty has 1.0.6 which is what I think the host is and should be using.
a precise host has 1.0.4
found in the cloud tools archive
http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/
juju stable ppa provides
The host machine is trusty and was missing updated. We have updated the
lxc and other packages. We will watch the processes to see if the issue
is resolved or still exists.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags
lxc*1.0.3 looks odd. That is one version I don't expect to see.
trusty has 1.0.6 which is what I think the host is and should be using.
a precise host has 1.0.4
found in the cloud tools archive
http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/l/lxc/
juju stable ppa provides
The host machine is trusty and was missing updated. We have updated the
lxc and other packages. We will watch the processes to see if the issue
is resolved or still exists.
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags
** Changed in: juju-core
Milestone: 1.21 = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine
** Changed in: juju-core
Milestone: 1.21 = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
maas
To
Juju QA certifies that the trusty clients are suitable for local
development and production cloud deploys.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land
Juju QA certifies that the trusty clients are suitable for local
development and production cloud deploys.
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core = 1.20.11-0ubuntu1, but the trusty backport is
** Description changed:
juju-core 1.20.11 is proposed for release upstream.
We're now in a position to have this enter trusty-proposed and vivid-
proposed, but it should not land in trusty-updates or vivid until
upstream passes QA on our proposed binaries, published 1.20.11 tools in
Vivid testing is complete. It is suitable for local development and for
deploying to clouds.
Trusty testing is blocked by the missing juju-local package for 14.14.
The vivid local package can be forced to install, but it depends on
juju-core = 1.20.11-0ubuntu1, but the trusty backport is
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: upgrade-juju
** Tags added: lxc
** Changed in: juju-core
Milestone: None = 1.22
--
You
The juju-local package does not appear to have been built and published.
the i386 juju-core package was built but is not listed as published.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is a bug assignee.
https://bugs.launchpad.net/bugs/1386144
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Tags added: upgrade-juju
** Tags added: lxc
** Changed in: juju-core
Milestone: None = 1.22
--
You
The juju-local package does not appear to have been built and published.
the i386 juju-core package was built but is not listed as published.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386144
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/848529
Title:
Choose between binary prefixes and SI
** Changed in: create-project
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781350
Title:
Name: header is missing in several swatch
*** This bug is a duplicate of bug 848529 ***
https://bugs.launchpad.net/bugs/848529
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntuone-servers
Assignee: Registry Administrators (registry) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736786
Title:
Ubuntu One notes editor doesn't apply
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1078213
Title:
logs are not logrotated
To manage notifications
** 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/1078213
Title:
logs are not logrotated
To manage notifications about this bug go
** Tags added: cts-cloud-review
** Tags added: add-unit
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: placement
** Tags added: network
** Changed in: juju-core
Milestone: None = 1.22
** Changed in:
** Changed in: distro-info (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390133
Title:
Information about Vivid is not available in Precise
To manage
** Tags added: cts-cloud-review
** Tags added: add-unit
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: placement
** Tags added: network
** Changed in: juju-core
Milestone: None = 1.22
** Changed in:
Thank you. Our precise machine now sees the updated package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1390133
Title:
Information about Vivid is not available in Precise
To manage
** Changed in: juju-core
Milestone: 1.21-alpha3 = 1.21-beta1
--
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
** Tags removed: cts local
** Tags added: cts-cloud-review local-provider
--
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/1290920
Title:
non-default lxc-dir breaks local provider
** Changed in: juju-core
Milestone: 1.21-alpha3 = 1.21-beta1
--
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:
** Tags removed: cts local
** Tags added: cts-cloud-review local-provider
--
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:
non-default lxc-dir breaks local provider
To manage
** Changed in: juju-core
Importance: High = Medium
** 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 juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1318378
Title:
** Changed in: juju-core
Importance: High = Medium
** 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 juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1347322
Title:
** Changed in: juju-core
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To
** Changed in: juju-core
Importance: High = Medium
** 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/1318378
Title:
rsyslog starts
** Changed in: juju-core
Importance: High = Medium
** 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/1347322
Title:
juju ssh results in a
** Changed in: juju-core
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To manage notifications
** Changed in: juju-core
Milestone: 1.21-alpha2 = 1.21-alpha3
--
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
Milestone: 1.21-alpha2 = 1.21-alpha3
--
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
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
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
** 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:
** 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
** 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.
** 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
** 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
** 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
** 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 =
** 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.
@robie
cat /etc/cloud/build.info
^ this is a server image.
I can reproduce the error in the extraordinary condition of a server image
without an ubuntu user.
juju local-provider just works with desktop and servers. desktops don't
has an ubuntu user, servers have a default ubuntu user.
My
501 - 600 of 3430 matches
Mail list logo
