juju-core 1.20.13
A new stable release of Juju, juju-core 1.20.13, is now available.
This release replaces stable 1.20.12.
Getting Juju
juju-core 1.20.13 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Notable
Looking great!!
There's any news about the Vagrant flow?
Abs,
Sebas.
2014-11-26 10:15 GMT-02:00 Rick Harding rick.hard...@canonical.com:
I looked into this but didn't see mod_spdy in the repos for use. Google
does provide debs, we can look at pulling it into our PPA we use for
deployment.
Juju gurus,
$(unit-get public-address) from within a hook is failing for us right
now on AWS. It returns the private address instead. I heard a fix will
be available in juju v1.21. Is there any way workaround, as we really
want to ship the Gluu Server charm ASAP.
thx,
Mike
Yesterday and today, I reviewed the following merge proposals:
* [approve] mongodb, explicitly using public-address for rs.initiate()
to resolved issues with unresolvable host name on MAAS
Hi Mike,
Sounds like you're hitting https://bugs.launchpad.net/juju-core/+bug/1308374
.
There's a workaround described in the bug description: use an external DNS.
Alternatively, you could (temporarily) do something EC2-specific in your
charm:
$(ec2metadata --public-ipv4)
Cheers,
Andrew
After upgrading from 1.20.12-trusty-amd64 to master (commit
2807fed7fad5619079c98ea105674d8a724d2e66), all unit logs continually
spew errors similar to the following:
// ~/.juju/local/log/unit-mysql-0.log
2014-11-26 09:09:07 ERROR juju.worker runner.go:219 exited uniter:
failed to initialize
PS kudos and thanks to Martin Hilton for the godeps fix.
On 26 November 2014 at 14:32, roger peppe roger.pe...@canonical.com wrote:
TL;DR go get -u launchpad.net/godeps
I have just fixed a bug in godeps where it could
omit some testing dependencies from its output.
The specific issue was
juju-core 1.20.13
A new stable release of Juju, juju-core 1.20.13, is now available.
This release replaces stable 1.20.12.
Getting Juju
juju-core 1.20.13 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Notable
+1 for feature flags in general and +1 for using environment variables
in upstart to get them to the servers agents.
I think it'd be nice to have an environment variable per flag, with a
common prefix JUJU_FEATURE_. That way, if you need to check one in a
package init(), you don't have to parse
During our team's testing with many upgrade scenarios we have found a
problem with tools and the jujuc commands on upgrades from 1.20 to
1.21-beta3.
We are investigating.
Tim
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
On 27/11/14 10:07, Tim Penhey wrote:
During our team's testing with many upgrade scenarios we have found a
problem with tools and the jujuc commands on upgrades from 1.20 to
1.21-beta3.
We are investigating.
Definitely a problem. Critical bug created:
The fix for this is merging into master and 1.21 now.
The problem was that for local provider based environments, unit and
machine agents weren't including the required namespace in their log
message tags. rsyslogd on the server was expecting to see the namespace so
it filtered out the unexpected
12 matches
Mail list logo
