Re: Juju 2.0.1 is here!

Tue Nov 1 16:30:25 UTC 2016

This has been filed under https://bugs.launchpad.net/juju/+bug/1638304. 
Please continue discussion there.

Thanks for the feedback Malte!

Nicholas

On 11/01/2016 08:19 AM, Malte Menkhoff wrote:
> Dear Juju-dev list,
>
> I am currently testing the different between Juju 2.0.0 and Juju 2.0.1 
> examplen an OpenStack provider which is based on Huawei FusionSphere.
> Juju 2.0.0 was able to get to the status of “Waiting for address” 
> because we are using nova API calls instead of neutron API calls - 
> this is known.
> But Juju 2.0.1 is now not able to come to that state while bootstrapping.
>
> The actual bootstrap output is:
> JUJU_STARTUP_LOGGING_CONFIG=TRACE juju bootstrap example --debug 
> --verbose  --metadata-source /home/ubuntu/simplestreams --config 
> bootstrap-timeout=300 --config use-floating-ip=false
> 11:57:00 TRACE juju.apiserver.common registry.go:47 Registered facade 
> "CharmRevisionUpdater" v2
> 11:57:00 TRACE juju.apiserver.common registry.go:47 Registered facade 
> "Backups" v1
> 11:57:00 DEBUG juju.environs imagemetadata.go:62 new model image 
> datasource registered: cloud sigma image source
> 11:57:00 DEBUG juju.environs imagemetadata.go:62 new model image 
> datasource registered: keystone catalog
> 11:57:00 TRACE cmd aliasfile.go:23 unable to read alias file 
> "/home/ubuntu/.local/share/juju/aliases": open 
> /home/ubuntu/.local/share/juju/aliases: no such file or directory
> 11:57:00 INFO  juju.cmd supercommand.go:63 running juju [2.0.1 gc go1.6.2]
> 11:57:00 DEBUG juju.cmd supercommand.go:64   args: []string{"juju", 
> "bootstrap", "example", "--debug", "--verbose", "--metadata-source", 
> "/home/ubuntu/simplestreams", "--config", "bootstrap-timeout=300", 
> "--config", "use-floating-ip=false"}
> 11:57:00 DEBUG juju.cmd.juju.commands bootstrap.go:834 provider attrs: 
> map[network: use-floating-ip:false use-default-secgroup:false]
> 11:57:00 INFO  cmd cmd.go:141 Adding contents of 
> "/home/ubuntu/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
> 11:57:00 DEBUG juju.cmd.juju.commands bootstrap.go:890 preparing 
> controller with config: map[apt-mirror: name:controller 
> test-mode:false apt-https-proxy: type:openstack logging-config: 
> enable-os-refresh-update:true provisioner-harvest-mode:destroyed 
> agent-metadata-url: use-default-secgroup:false apt-http-proxy: 
> agent-stream:released firewall-mode:instance image-stream:released 
> use-floating-ip:false disable-network-management:false 
> default-series:xenial development:false https-proxy: 
> ssl-hostname-verification:true resource-tags: network: proxy-ssh:false 
> transmit-vendor-metrics:true automatically-retry-hooks:true 
> uuid:691a5ca9-76b7-4503-8158-6dc341fdb32f 
> ignore-machine-addresses:false apt-ftp-proxy: enable-os-upgrade:true 
> http-proxy: no-proxy: logforward-enabled:false ftp-proxy: 
> image-metadata-url: authorized-keys:ssh-rsa 
> AAAAB3NzaC1yc2EAAAADAQABAAABAQC6vSnam5/qIFGSs7T1zSj2qamU+dOxMnpt9m+sGdXpkeuHYYbEDdmzWdPQCGCniUfMm9ffWl3KkOqMDsoRjFfcPaRITc3USKgzkR+zKDTxvoTaDaL3gcg3eNiZGrPYFZ1J49uV4Oo3Y913zbbTyj6ViyHE8ILqO4SssfNBRiWMdbJbrmOGJeVZkJyKt2xTkmOZ8Ne1KB34q66TNCMP81z1DdaDA/YiMseqnGH+c/39Qd/0MoASNQua5qLnaNN6FyHgeme3dhaQpzcYnH2vBIf0UMA+aFYyUrm7y5lhDrcI9FRLWYfyqZz0Y/qdzS6J48nSov5P22yDF8/9RZkzIVUH 
> juju-client-key
> ]
> 11:57:00 INFO  juju.provider.openstack provider.go:76 opening model 
> "controller"
> 11:57:00 INFO  cmd cmd.go:129 Creating Juju controller "example-eu-de" 
> on example/eu-de
> 11:57:00 INFO  juju.provider.common destroy.go:20 destroying model 
> "controller"
> 11:57:00 INFO  juju.provider.common destroy.go:31 destroying instances
> 11:57:00 ERROR juju.cmd.juju.commands bootstrap.go:1021 error cleaning 
> up: destroying controller model: destroying instances: failed to get 
> list of server details
> caused by: Resource at https://ecs.eu-de.example.com/ not found
> caused by: request (https://ecs.eu-de.example.com/) returned 
> unexpected status: 404; error info: {"message":"Api does not 
> exist","request_id":"281C2FBB-0D3A-4676-BAA5-3CC91C9ADED6"}
> 11:57:00 ERROR cmd supercommand.go:458 failed to get list of flavour 
> details
> caused by: Resource at https://ecs.eu-de.example.com/ not found
> caused by: request (https://ecs.eu-de.example.com/) returned 
> unexpected status: 404; error info: {"message":"Api does not 
> exist","request_id":"83A781AE-9A0C-43C7-B405-310A5A94566E"}
> 11:57:00 DEBUG cmd supercommand.go:459 (error details: 
> [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:499: 
> <http://github.com/juju/juju/cmd/juju/commands/bootstrap.go:499:> } 
> {failed to get list of flavour details
> caused by: Resource at https://ecs.eu-de.example.com/ not found
> caused by: request (https://ecs.eu-de.example.com/) returned 
> unexpected status: 404; error info: {"message":"Api does not 
> exist","request_id":"83A781AE-9A0C-43C7-B405-310A5A94566E"}}])
>
> Could this occur due to the new version of goose according to:
>
> Merge pull request #6501 <https://github.com/juju/juju/issues/6501> 
> from axw/lp1636648-openstack-update-goose
>
> provider/openstack: update goose
>
> Use new version of goose, to omit the device
> field on volume attachment requests when no
> device is specified.
>
> This branch also uses the new OpenStack API
> version discovery code in goose.
>
> Fixes https://bugs.launchpad.net/juju/+bug/1636648
>
> Any advice or help here how to debug it and provide better quality for 
> a bug report is appreciate.
>
> Best regards,
> Malte Menkhoff
>
>> On 31 Oct 2016, at 23:33, Nicholas Skaggs 
>> <nicholas.skaggs at canonical.com 
>> <mailto:nicholas.skaggs at canonical.com>> wrote:
>>
>> Our first update to Juju 2 is here! This Juju 2.0.1 release brings 
>> some improvements including;
>>
>>    * Support for the new AWS region us-east-2
>>    * Correct OSX Sierra support
>>    * Update list-models output to show cloud/region vs owner
>>    * Update model-migrations with support for endpoints, cloud 
>> credentials
>>
>> ## New to juju 2?
>>
>> https://jujucharms.com/docs/2.0/introducing-2
>>
>> ## Ready to install it?
>>
>> If you are running Ubuntu, you can get it from the juju stable ppa:
>>
>>    sudo add-apt-repository ppa:juju/stable
>>    sudo apt update; sudo apt install juju-2.0
>>
>> Or install it from the snap store
>>
>>    snap install juju --beta --devmode
>>
>> Windows, Centos, and MacOS users can get a corresponding installer at:
>>
>> https://launchpad.net/juju/+milestone/2.0.1
>>
>> ## What else is in it?
>>
>> Notable bug fixes include:
>>    * #1623136, #1629452 Vsphere improvements
>>    * #1614239 use-floating-ip is not honored from clouds.yaml config
>>    * #1619808 bootstrap-timeout ignored in --config
>>    * #1602840 juju show-machines should show all addresses a machine has
>>    * #1616098 Juju 2.0 uses random IP for 'PUBLIC-ADDRESS' with MAAS 2.0
>>
>> For the full list of bugs addressed, checkout the milestone: 
>> https://launchpad.net/juju/+milestone/2.0.1
>>
>> ## 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.
>>
>>
>> -- 
>> Juju-dev mailing list
>> Juju-dev at lists.ubuntu.com
>> Modify settings or unsubscribe at: 
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
>
>

Re: Juju 2.0.1 is here!​

Re: Juju 2.0.1 is here!