** 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:
@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
** 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
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
** Description changed:
When running 'juju bootstrap -e azure' my memory is completely filling
up (16GB +8GB swap) within about 1-2 minutes, leaving me with an
unusable system. I have also tried using the package in the ppa which I
experienced the same issue.
Distributor ID:
** Description changed:
When running 'juju bootstrap -e azure' my memory is completely filling
up (16GB +8GB swap) within about 1-2 minutes, leaving me with an
unusable system. I have also tried using the package in the ppa which I
experienced the same issue.
Distributor ID:
** Tags added: azure-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/1250007
Title:
Bootstrapping azure causes memory to fill
To manage notifications about this bug go
** Tags added: azure-provider
--
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 about this bug go to:
** Changed in: juju-core/1.18
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/1314686
Title:
Please add support for utopic
To manage
** Changed in: juju-core/1.18
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/1314686
Title:
Please add support for utopic
To manage notifications about
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gccgo-go in Ubuntu.
https://bugs.launchpad.net/bugs/1287879
Title:
fatal error running test suite on arm64
To manage
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287879
Title:
fatal error running test suite on arm64
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/1316272
Title:
juju destroy-environment =256 nodes fails
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/1316272
Title:
juju destroy-environment =256 nodes fails
To manage notifications
** 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1319525
Title:
juju-local LXC containers hang due to AppArmor denial of rpc_pipefs
I do think it is fine for the mount be allowed.
By Invalid, I mean there is no change we can make to the juju-core code to
solve this issue. If there is work for the juju-core developers, then I will
change the status for juju-core to triages and get it scheduled to be fixed in
time for the
** Changed in: juju-core
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319525
Title:
juju-local LXC containers hang due to AppArmor denial of rpc_pipefs
mount with
I do think it is fine for the mount be allowed.
By Invalid, I mean there is no change we can make to the juju-core code to
solve this issue. If there is work for the juju-core developers, then I will
change the status for juju-core to triages and get it scheduled to be fixed in
time for the
** Tags added: apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305280
Title:
apparmor get_cgroup fails when creating lxc with juju local provider
To manage notifications about this bug go
** Tags added: regression
** Summary changed:
- juju command get_cgroup fails when creating new machines, local provider
arm32
+ apparmor get_cgroup fails when creating lxc with juju local provider
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: panic performance
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: logging
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** 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: maas upload-tools
--
You received
We verified this happens with juju 1.18.3 as well.
--
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
Status: Triaged = 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/1261452
Title:
juju-core is unavailable for arm64
To manage
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: panic performance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = next-stable
** Tags added: logging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** 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: maas upload-tools
--
You received
We verified this happens with juju 1.18.3 as well.
--
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
** Changed in: juju-core
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1261452
Title:
juju-core is unavailable for arm64
To manage notifications about this
** Changed in: juju-core
Milestone: 1.19.2 = 1.19.3
--
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/1316272
Title:
juju destroy-environment =256 nodes fails
To manage
** Changed in: juju-core
Milestone: 1.19.2 = 1.19.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316272
Title:
juju destroy-environment =256 nodes fails
To manage notifications about this
This issue might be that the 1.19.1 client cannot ssh to 1.18.1/2
server. I cannot use juju ssh to get to Juju CI using this combination.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
I have confirmed that juju 1.18.2 can ssh into my one of my units, but
juju 1.19.1 cannot:
$ juju status
environment: juju-ci3
machines:
0:
agent-state: started
agent-version: 1.18.2
dns-name: ec2-54-84-244-38.compute-1.amazonaws.com
instance-id: i-59745278
instance-state:
This issue might be that the 1.19.1 client cannot ssh to 1.18.1/2
server. I cannot use juju ssh to get to Juju CI using this combination.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313785
Title:
I have confirmed that juju 1.18.2 can ssh into my one of my units, but
juju 1.19.1 cannot:
$ juju status
environment: juju-ci3
machines:
0:
agent-state: started
agent-version: 1.18.2
dns-name: ec2-54-84-244-38.compute-1.amazonaws.com
instance-id: i-59745278
instance-state:
** Changed in: juju-core
Assignee: Curtis Hovey (sinzui) = (unassigned)
** Changed in: juju-core
Milestone: None = 1.19.2
--
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
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = 1.19.2
** Tags added: destroy-environment maas-provider
--
You received this bug notification because you are a member of Ubuntu
Server
** Changed in: juju-core
Assignee: Curtis Hovey (sinzui) = (unassigned)
** Changed in: juju-core
Milestone: None = 1.19.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = 1.19.2
** Tags added: destroy-environment maas-provider
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1313785
Title:
Can't SSH with juju ssh command to EC2 instance.
To manage
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313785
Title:
Can't SSH with juju ssh command to EC2 instance.
To manage notifications about
** 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 juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1306315
Title:
juju-mongodb process hangs around after package removal
To
** Tags added: packaging
--
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/1314686
Title:
Please add support for utopic
To manage notifications about this bug go to:
: (unassigned) = Curtis Hovey (sinzui)
--
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/1314686
Title:
Please add support for utopic
To manage notifications about this bug go to:
https
** Changed in: juju-core/1.18
Milestone: 1.18.2 = 1.18.3
--
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/1304407
Title:
juju bootstrap defaults to i386
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/1306315
Title:
juju-mongodb process hangs around after package removal
To manage notifications
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title:
Please add support for utopic
To manage notifications about this bug go to:
: (unassigned) = Curtis Hovey (sinzui)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314686
Title:
Please add support for utopic
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Changed in: juju-core/1.18
Milestone: 1.18.2 = 1.18.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about this bug go
** 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/1304407
Title:
juju bootstrap defaults to i386
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/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about this
I have created a 1.18.2 milestone. I cannot reproduce this behaviour. I
don't see CI doing it as well.
** Changed in: juju-core/1.18
Milestone: None = 1.18.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** 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/1306208
Title:
juju scp no longer allows multiple extra
** 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/1306296
Title:
juju cannot downgrade to same major.minor
** 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/1303735
Title:
public-address change to internal bridge post
** 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/1303880
Title:
Juju 1.18.0, can not deploy local charms
** 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/1304135
Title:
panic: runtime error: index out of range
To
** 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/1303697
Title:
peer relation disappears during upgrade of juju
** 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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To
** 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/1299588
Title:
LXC permission denied issue with 1.17.7
To
I just saw this happen testing 1.19.0 deployment on aws fom my amd64
machine.
--
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/1304407
Title:
juju bootstrap defaults to i386
To
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
** Changed in: juju-core/1.18
Milestone: None = 1.18.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I have created a 1.18.2 milestone. I cannot reproduce this behaviour. I
don't see CI doing it as well.
** Changed in: juju-core/1.18
Milestone: None = 1.18.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core
Milestone: 1.19.0 = 1.19.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305280
Title:
juju command get_cgroup fails when creating new machines, local
provider arm32
** 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/1306208
Title:
juju scp no longer allows multiple extra arguments to pass throug
** 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/1306296
Title:
juju cannot downgrade to same major.minor version with earlier
** 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/1303880
Title:
Juju 1.18.0, can not deploy local charms without series
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/1304135
Title:
panic: runtime error: index out of range
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/1299588
Title:
LXC permission denied issue with 1.17.7
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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
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/1303697
Title:
peer relation disappears during upgrade of juju
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/1303735
Title:
public-address change to internal bridge post juju-upgrade
To
I just saw this happen testing 1.19.0 deployment on aws fom my amd64
machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304407
Title:
juju bootstrap defaults to i386
To manage notifications
** Changed in: juju-core/1.18
Status: Fix Committed = Fix Released
** Changed in: juju-core/1.18
Milestone: None = 1.18.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304135
Title:
** Changed in: juju-core
Status: New = Triaged
** Tags added: addressability openstack-provider
** Changed in: juju-core
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** 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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To manage
** 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/1303880
Title:
Juju 1.18.0, can not deploy local charms without series
To
** 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/1303697
Title:
peer relation disappears during upgrade of juju
To manage
** 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/1303735
Title:
public-address change to internal bridge post juju-upgrade
** 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/1306208
Title:
juju scp no longer allows multiple extra arguments to pass
** Changed in: juju-core
Status: New = Triaged
** Tags added: addressability openstack-provider
** Changed in: juju-core
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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/1305280
Title:
juju command get_cgroup fails when creating new machines, local
provider
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To manage notifications about this bug
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303735
Title:
public-address change to internal bridge post juju-upgrade
To manage
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303697
Title:
peer relation disappears during upgrade of juju
To manage notifications about
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303880
Title:
Juju 1.18.0, can not deploy local charms without series
To manage notifications
** Changed in: juju-core
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306208
Title:
juju scp no longer allows multiple extra arguments to pass throug
To manage
601 - 700 of 3430 matches
Mail list logo
