I tested 1.22.5 from wily-proposed. It is suitable to create and
maintain cloud deployments. It is compatible with both juju-quickstart
and juju-deployer. Note, as with Vivid, 1.22.x is not fit for local
charm development and testing because it is not systemd aware. We expect
to propose juju 1.24
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Devel Fix]
-
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Devel Fix]
-
Hi Robie.
I prepared a backport of 1.22.5 to trusting using the trusty-updates spb as a
base plus debian/* changes from the wily spb.
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.22.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Robie.
I prepared a backport of 1.22.5 to trusting using the trusty-updates spb as a
base plus debian/* changes from the wily spb.
lp:~sinzui/ubuntu/trusty/juju-core/trusty-1.22.5
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: juju-core
Status: Fix Released = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface
Hi Robie.
I updated the source package to include distro-info in build-depends.
lp:~sinzui/ubuntu/wily/juju-core/juju-1.22.5
This ensure juju can learn about every Ubuntu distro that is know to the host
system. I think this addresses the case where Ubuntu chooses to rebuild an old
package.
Hi Robie.
I updated the source package to include distro-info in build-depends.
lp:~sinzui/ubuntu/wily/juju-core/juju-1.22.5
This ensure juju can learn about every Ubuntu distro that is know to the host
system. I think this addresses the case where Ubuntu chooses to rebuild an old
package.
I pushed the debian/copyright updates to lp:~sinzui/ubuntu/wily/juju-
core/juju-1.22.5. I hope this branch is suitable to make the wily
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462001
I pushed the debian/copyright updates to lp:~sinzui/ubuntu/wily/juju-
core/juju-1.22.5. I hope this branch is suitable to make the wily
package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
The src/github.com/juju/txn issue is fixed in commit
99ec629d0066a4d73c54d8e021a7fc1dc07df614 in upstream master
https://github.com/juju/txn/commit/99ec629d0066a4d73c54d8e021a7fc1dc07df614
The files are LGPL. Upstream juju is also switching to
src/github.com/juju/txn tip.
--
You received
The src/github.com/juju/txn issue is fixed in commit
99ec629d0066a4d73c54d8e021a7fc1dc07df614 in upstream master
https://github.com/juju/txn/commit/99ec629d0066a4d73c54d8e021a7fc1dc07df614
The files are LGPL. Upstream juju is also switching to
src/github.com/juju/txn tip.
--
You received
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
+ [Devel Fix]
+ [sinzui]
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
+ [Devel Fix]
+ [sinzui]
** Changed in: juju-core (Ubuntu)
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/1447200
Title:
juju-core 1.23.1 is not packaged in Ubuntu
To manage
** Changed in: juju-core (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/1447200
Title:
juju-core 1.23.1 is not packaged in Ubuntu
To manage notifications about
Public bug reported:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Development Fix]
Upload of new upstream
Public bug reported:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
[Development Fix]
Upload of new upstream
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
- [Development Fix]
-
-
** Description changed:
We're now in a position to have 1.22.5 enter trusty-proposed.
[SRU Information]
juju-core has a stable release exception in
https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions,
including for major version updates.
- [Development Fix]
-
-
** Summary changed:
- juju ssh/scp commands cause spurious key errors
+ juju ssh/scp/run commands cause spurious key errors
** Also affects: juju-deployer
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- juju ssh/scp commands cause spurious key errors
+ juju ssh/scp/run commands cause spurious key errors
** Also affects: juju-deployer
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
I do not want 1.22.1 going into updates because there is a compatibility
issue. Bug 1454829 is about a case were a 1.20.11 client cannot talk to
an env bootstrapped with. 1.22.x. The certificate rules are different,
preventing the client from talking. This is not an issue for envs
upgraded from
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
Hi Oleg.
I am happy to continue with 1.22.1 going into updates first. I am a
little concerned about perception of churn in Trusty. Juju 1.22.4 will
arrive a few weeks later. What of 1.23.x? 1.23.3 is currently proposed,
but Core's desire to put 1.22.4 in means we delay the .1.23 going into
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
@Oleg, et al.
I understand that there is a plan to release a 1.22.4 soon. The intent is to
support this version as well as the current 1.23. There are orgs committed to
using 1.22 for some time and that there are stability fixes that are being
backported.
If we think that Ubuntu users don't
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
Juju requires a newer version of mongodb to address this issue, one that
supports the quiet flag. We can see that the packages with the required version
do not exist yet in.
http://www.mongodb.org/dl/linux/x86_64-ubuntu1404
There is nothing that can be done. The fix described in comment #9
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
I have certified juju 1.20.1 in trusty proposed is compatible with juju agent
streams and with the ecosystem of tools in trusty. I verified:
* The binary archs in proposed work with the archs in agent streams.
* Juju is suitable for local testing and charm development
* juju-deployer can deployed
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** No longer affects: gdp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374297
Title:
Plugins cannot be activated from preferences - plugins
To manage notifications about this bug go to:
** No longer affects: gdp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1306363
Title:
Session-Saver Plugin Missing from gedit-plugins
To manage notifications about this bug go to:
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
Ubuntu juju 1.22.1 on vivid is compatible with 1.22.x from upstream
Juju. It is suitable deploying and maintaining environments in public
and private clouds. Juju is compatible with the versions of quickstart
(and deployer) provide by Ubuntu main and proposed.
Note that 1.22.1 does not support
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
** Description changed:
We're now in a position to have 1.22.1 enter trusty-proposed and vivid-
proposed, but it should not land in trusty or vivid until upstream
passes QA on our proposed binaries, published the tools in their stable
simplestream and announces the release for general
juju 1.22.0 is fit for purpose. The client can work with agents and
servers in public and private clouds. The Juju charm store only supports
LTS services. It is not possible to place a vivid charm in the store.
The only vivid users impaired by missing systemd support are charm
developers and
juju 1.22.0 is fit for purpose. The client can work with agents and
servers in public and private clouds. The Juju charm store only supports
LTS services. It is not possible to place a vivid charm in the store.
The only vivid users impaired by missing systemd support are charm
developers and
** Changed in: juju-core (Ubuntu)
Status: New = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
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.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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
** Changed in: juju-core (Ubuntu)
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/1304407
Title:
juju bootstrap defaults to i386
To manage notifications about
** Changed in: juju-core (Ubuntu)
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/1304407
Title:
juju bootstrap defaults to i386
To manage
** Changed in: juju-core (Ubuntu)
Status: New = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: New = 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/1302205
** Changed in: juju-core (Ubuntu)
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/1318366
Title:
jujud on state server panic misses transaction in queue
To
** Changed in: juju-core (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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
** Changed in: juju-core (Ubuntu)
Status: Triaged = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: juju-core (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
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 (Ubuntu)
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/1318366
Title:
jujud on state server panic misses
** Changed in: juju-core (Ubuntu)
Status: Confirmed = 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
** Changed in: juju-core (Ubuntu)
Status: Triaged = Fix Released
** Changed in: juju-core (Ubuntu Trusty)
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.
I tested juju 1.22.0 on vivid with streams and with quickstart (from
vivid). All is good. The client is good for working with all providers
and state servers on trusty and precise.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but
I tested juju 1.22.0 on vivid with streams and with quickstart (from
vivid). All is good. The client is good for working with all providers
and state servers on trusty and precise.
** Description changed:
We're now in a position to have 1.22.0 enter trusty-proposed and vivid-
proposed, but
** Description changed:
We're now in a position to have 1.22.0 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 the tools in
their stable simplestream and announces the release for
** Description changed:
We're now in a position to have 1.22.0 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 the tools in
their stable simplestream and announces the release for
** 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/1409639
Title:
juju needs to support systemd for = vivid
To manage notifications
** 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/1409639
Title:
juju needs to support systemd for = vivid
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/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
From James's duplicate bug:
In our MAAS based openstack deployment, we provide MTU via DHCP to all
servers to enable jumbo frames.
This works fine until juju creates the bridge devices for LXC or KVM
containers, at which point we reliably lose the MTU 9000 setting on the
bridge, resulting in all
** 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/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
To
The stilson machines that run the tests have 9.8G RAM. They always have.
** Changed in: gccgo-go (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393825
** Changed in: juju-release-tools
Status: Triaged = Invalid
** Changed in: gccgo-go (Ubuntu Vivid)
Status: Confirmed = Fix Released
** Changed in: gccgo-5 (Ubuntu Vivid)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of
** Changed in: juju-release-tools
Status: Triaged = Invalid
** Changed in: gccgo-go (Ubuntu Vivid)
Status: Confirmed = Fix Released
** Changed in: gccgo-5 (Ubuntu Vivid)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of
There has been a lot confusion about this bug. As the reporter, I am
happy to say vivid packaging (or cloud/builder images) were fixed last
week. Without any changes to juju packaging. Launchpad and lxc can
again built vivid ppc64el packages without explicitly setting the GOARCH
to match the dpkg
The last 2 Lp builds of juju packages succeeded, as does my own builds.
I think this issue resolved itself since I did not change packaging
rules. I will do a little more investigation, but hope to close this bug
in a few hours.
--
You received this bug notification because you are a member of
** Tags added: maas-provider network
** Changed in: juju-core
Status: New = Triaged
** Changed in: juju-core
Importance: Undecided = Medium
** Tags added: oil
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We captured a snippet of the private build log and we can see the issue
is the same as the report. The first call to access bin/juju fails
because it is not there, it is in $GOPATH/bin/linux__ppc64le. VIvid's
gccgo-go thinks it is cross-compiling.
mkdir -p
** Description changed:
The vivid ppc64el builds are failing. The last success was on
2015-01.20. their first failure was on 2015-01-23.
We suspect that golang-go sets the wrong GOARCH in vivid.
We cannot see the build logs because Lp is a punk. The builds were in the
~juju-package
: High
Assignee: Curtis Hovey (sinzui)
Status: Triaged
** Affects: gccgo-go (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging ppc64el vivid
** Changed in: juju-release-tools
Assignee: (unassigned) = Curtis Hovey (sinzui)
** Also affects: gccgo-go (Ubuntu
: High
Assignee: Curtis Hovey (sinzui)
Status: Triaged
** Affects: gccgo-go (Ubuntu)
Importance: Undecided
Status: New
** Tags: packaging ppc64el vivid
** Changed in: juju-release-tools
Assignee: (unassigned) = Curtis Hovey (sinzui)
** Also affects: gccgo-go (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/1355813
Title:
Interface MTU management across MAAS/juju
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/1355813
Title:
Interface MTU management across MAAS/juju
To manage notifications
** Changed in: juju-core
Status: Incomplete = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine managed by
** Changed in: juju-core
Status: Incomplete = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on
** Changed in: juju-core
Milestone: 1.23 = None
** 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-core in Ubuntu.
https://bugs.launchpad.net/bugs/1393444
Title:
machine
** Changed in: juju-core
Milestone: 1.23 = None
** 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/1393444
Title:
machine unit connects 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/1328958
Title:
Local provider fails when an unrelated /home/ubuntu directory
** 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/1328958
Title:
Local provider fails when an unrelated
We have frozen juju 1.22. We expect it to ship with vivid. This feature
will need to be back-ported. How does Ubuntu feel about adding a feature
to 1.22.1? If this is bad, then we will wait for 1.23 to be backported
to w, v and t.
** Changed in: juju-core
Milestone: None = 1.23
** Changed
We have frozen juju 1.22. We expect it to ship with vivid. This feature
will need to be back-ported. How does Ubuntu feel about adding a feature
to 1.22.1? If this is bad, then we will wait for 1.23 to be backported
to w, v and t.
** Changed in: juju-core
Milestone: None = 1.23
** Changed
** 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/1402005
Title:
agent-state-info: 'error executing lxc-start: command get_cgroup
failed 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/1402005
Title:
agent-state-info: 'error executing lxc-start: command get_cgroup
** Changed in: juju-core
Milestone: 1.22 = 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/1316579
Title:
--upload-tools doesn't work with bootstrap on armhf machine
** Changed in: juju-core
Milestone: 1.22 = None
--
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
This is unsetting. That is the error I saw, but with a different juju
and series. 1.20.13 on MY trusty saw that error. Older jujus or newer
quick-starts worked. The juju-gui team had not seen the issue before,
the concluded my setup had tainted the test. When we retested with a
pristine trusty, it
This is unsetting. That is the error I saw, but with a different juju
and series. 1.20.13 on MY trusty saw that error. Older jujus or newer
quick-starts worked. The juju-gui team had not seen the issue before,
the concluded my setup had tainted the test. When we retested with a
pristine trusty, it
Ubuntu has old packages
https://launchpad.net/~sinzui/+archive/ubuntu/ppa?field.series_filter=trusty
1.1.0+661-0~gdp~ubuntu13.10.1 was rebuilt for trusty and it works well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The restricted-network test fails because of the upstream dep. We are
changing the test to use trusty (as series is not relevant).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
The restricted-network test fails because of the upstream dep. We are
changing the test to use trusty (as series is not relevant).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407699
Title:
** 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 cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1407699
Title:
Precise services cannot be deployed
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/1407699
Title:
Precise services cannot be deployed
To manage notifications about
** Changed in: juju-core/1.21
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/1328958
Title:
Local provider fails when an unrelated
** 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
Server Team, which is subscribed to lxc in Ubuntu.
401 - 500 of 3430 matches
Mail list logo
