Juju 2.0-rc1 is here!

Tue Sep 27 00:17:59 UTC 2016

Hi Chance,

Sorry that you're experiencing this issue.

I've filed a ticket here: https://bugs.launchpad.net/juju/+bug/1627894.
Could you possibly add details of the commands you ran leading up to this
error? If possible, can you also please attach Juju's logs? The most
straightforward way to get all available logs for the Juju model is:

    juju debug-log --replay | gzip > model.log.gz

This assumes the Juju model experiencing the problem is currently selected.
Use "juju switch" if necessary.
The Juju controller logs would also be helpful:

    juju debug-log -m controller --replay | gzip > controller.log.gz

In the mean time, we're investigating at this end.

- Menno

On 23 September 2016 at 09:58, Chance Ellis <chance_ellis at yahoo.com> wrote:

> Fresh install of juju 2.0 rc1 on a maas 2.0 cloud.
>
>
>
> I have been tracking the container network interface issues and hoping
> they would be fixed in rc1 for an openstack deployment. I tried deploying
> the openstack on this new install. The machines spin up in maas but the
> containers fail. In the juju debug log I keep seeing these errors over and
> over:
>
>
>
> machine-3: 17:34:26 ERROR juju.worker exited "3-container-watcher": worker
> "3-container-watcher" exited: panic resulted in: runtime error: invalid
> memory address or nil pointer dereference
>
> machine-1: 17:34:27 ERROR juju.worker exited "1-container-watcher": worker
> "1-container-watcher" exited: panic resulted in: runtime error: invalid
> memory address or nil pointer dereference
>
> machine-0: 17:34:27 ERROR juju.worker exited "0-container-watcher": worker
> "0-container-watcher" exited: panic resulted in: runtime error: invalid
> memory address or nil pointer dereference
>
> machine-2: 17:34:29 ERROR juju.worker exited "2-container-watcher": worker
> "2-container-watcher" exited: panic resulted in: runtime error: invalid
> memory address or nil pointer dereference
>
>
>
> If I ssh into the juju machine and “lxc list” there are no containers
> created.
>
>
>
> What info can I provide to help troubleshoot this?
>
>
>
>
>
>
>
> *From: *<juju-bounces at lists.ubuntu.com> on behalf of Andrew Wilkins <
> andrew.wilkins at canonical.com>
> *Date: *Wednesday, September 21, 2016 at 2:07 AM
> *To: *Curtis Hovey-Canonical <curtis at canonical.com>, Juju email list <
> juju at lists.ubuntu.com>, "juju-dev at lists.ubuntu.com" <
> juju-dev at lists.ubuntu.com>
> *Subject: *Re: Juju 2.0-rc1 is here!
>
>
>
> On Wed, Sep 21, 2016 at 1:56 PM Curtis Hovey-Canonical <
> curtis at canonical.com> wrote:
>
> A new development release of Juju, 2.0-rc1, is here!
>
>
>
> Woohoo!
>
>
>
>
> ## What's New in RC1
>
> * The Juju client now works on any Linux flavour. When bootstrapping
>   with local tools, it's now possible to create a controller of any
>   supported Linux series regardless of the Linux flavour the client
>   is running on.
> * Juju resolved command retries failed hooks by default:
>   juju resolved <unit> // marks unit errors resolved and retries failed
> hooks
>   juju resolved --no-retry <unit> //marks unit errors resolved w/o
> retrying hooks
> * MAAS 2.0 Juju provider has been updated to use MAAS API 2.0's owner
>   data for instance tagging.
> * Networking fixes for containers in MAAS 2.0 when the parent device is
>   unconfigured. (#1566791)
> * Azure provider performance has been enhanced, utilising Azure Resource
>   Manager templates, and improved parallelisation.
> * Azure provider now supports an "interactive" auth-type, making it much
>   easier to set up credentials for bootstrapping. The "userpass"
>   auth-type has been deprecated, and replaced with
>   "service-principal-secret".
>
>
>
> In case anyone jumps right on this, please note that https://streams.
> canonical.com/juju/public-clouds.syaml isn't yet updated. It will be
> updated soon, but in the mean time, if you want to try out the azure
> interactive add-credential, make sure you:
>
>  - delete ~/.local/share/juju/public-clouds.yaml (if it exists)
>
>  - *don't* run "juju update-clouds" until that file is updated
>
> Then Juju will use the cloud definitions built into the client.
>
>
>
> Cheers,
>
> Andrew
>
>
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get it from the juju devel ppa:
>
>     sudo add-apt-repository ppa:juju/devel
>     sudo apt-get update; sudo apt-get install juju-2.0
>
> Or install it from the snap store
>
>     snap install juju --beta --devmode
>
> Windows, Centos, and OS X users can get a corresponding installer at:
>
>     https://launchpad.net/juju/+milestone/2.0-rc1
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju at lists.ubuntu.com and join us on #juju on freenode. We would love
> to hear your feedback and usage of juju.
>
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing
> the release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-dev
>
> -- Juju mailing list Juju at lists.ubuntu.com Modify settings or unsubscribe
> at: https://lists.ubuntu.com/mailman/listinfo/juju
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160927/01665b1d/attachment.html>