2.0.0: cannot start bootstrap instance: no matching tools available for ppc64el node (or arm64)

Bug #1623330 reported by Larry Michel
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned

Bug Description

Up to beta15 we had been able to use ppc64el VMs. We first observed the failure with beta16 and have recreated with beta17:

This from console:

2016-09-14 03:56:09,758 [INFO] oil_ci.deploy.oil_deployer: Bootstrapping to huffman-vm-05
2016-09-14 03:56:09,759 [INFO] oil_ci.juju.juju2: bootstrapping: juju-2.0 bootstrap --debug --config bootstrap-timeout=1800 --config test-mode=true ci-oil-slave15 ci-oil-slave15 --to=huffman-vm-05
03:56:09 INFO juju.cmd supercommand.go:63 running juju [2.0-beta17 gc go1.6]
03:56:09 DEBUG juju.cmd.juju.commands bootstrap.go:473 provider attrs: map[]
03:56:10 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
03:56:10 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.ssh/id_rsa.pub" to authorized-keys
03:56:10 DEBUG juju.cmd.juju.commands bootstrap.go:522 preparing controller with config: map[type:maas name:controller uuid:9ff73a6c-dd9c-4eea-88a4-bccb63d20815 authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDVtkoSiW5zKGAijTUKPbbfhe3u6nvuNwUgSZnCU2/anXzwV9L7ymdJJVXCXHuwqb6XGw08pwnH5w9UMPOuGKDqT4PvIPnpoF7uH/B2GlZ+36b4V7975zGVSgqGcwFp6Po5JJK35eItMTgjhUJ7sB2SnHWJ13YCCVvVWYnvyIDtOhqe/2itcMAkTUvqJBg+ydy2aK9427rSN0Pjm6kq0DXOuLiNDoIsL0lLWq/Ib5682JdiKaXPBfLxI417ZbFlEHtL+RNYNR81rRKON0iaAOLAC2ikr/wRD4DtW7u0s8yrY0vXOoe2yI/QakbTE5l3NM8gnxSx/t+Zo4KQI9ZqV4cP juju-client-key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot
 test-mode:true]
03:56:10 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
03:56:10 INFO cmd cmd.go:129 Creating Juju controller "ci-oil-slave15" on ci-oil-slave15
03:56:10 INFO juju.cmd.juju.commands bootstrap.go:665 combined bootstrap constraints:
03:56:10 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
03:56:10 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
03:56:10 INFO cmd cmd.go:141 Loading image metadata
03:56:11 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0-beta17 for amd64
03:56:11 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0-beta17
03:56:11 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "devel"
03:56:11 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.0
03:56:11 INFO juju.environs.tools tools.go:111 filtering agent binaries by version: 2.0-beta17
03:56:11 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: amd64
03:56:11 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
03:56:11 DEBUG juju.environs.simplestreams simplestreams.go:680 using default candidate for content id "com.ubuntu.juju:devel:tools" are {20160220 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
03:56:11 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent binaries
03:56:12 INFO cmd cmd.go:141 Starting new instance for initial controller
Launching controller instance(s) on ci-oil-slave15...
03:56:13 INFO juju.provider.common destroy.go:20 destroying model "controller"
03:56:13 INFO juju.provider.common destroy.go:31 destroying instances
03:56:13 INFO juju.provider.common destroy.go:51 destroying storage
03:56:14 ERROR cmd supercommand.go:458 failed to bootstrap model: cannot start bootstrap instance: no matching tools available
03:56:14 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:734: failed to bootstrap model} {github.com/juju/juju/provider/common/bootstrap.go:171: cannot start bootstrap instance} {github.com/juju/juju/provider/maas/environ.go:937: } {github.com/juju/juju/tools/list.go:19: no matching tools available}])
2016-09-14 03:56:14,054 [ERROR] oil_ci.deploy.oil_deployer: Deployment failed: Command '['juju-2.0', 'bootstrap', '--debug', '--config', 'bootstrap-timeout=1800', '--config', 'test-mode=true', u'ci-oil-slave15', u'ci-oil-slave15', u'--to=huffman-vm-05']' returned non-zero exit status 1
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/oil_ci/deploy/oil_deployer.py", line 205, in deploy
    juju2.bootstrap(self.env_name, self.bootstrap_hostname)
  File "/usr/lib/python2.7/dist-packages/oil_ci/juju/juju2.py", line 53, in bootstrap
    check_call(cmd)
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['juju-2.0', 'bootstrap', '--debug', '--config', 'bootstrap-timeout=1800', '--config', 'test-mode=true', u'ci-oil-slave15', u'ci-oil-slave15', u'--to=huffman-vm-05']' returned non-zero exit status 1

Since bootstrap failed because tools are not available, there's no other log collected.

I also recreated with a bare metal ppc64el system.

05:07:35 ERROR cmd supercommand.go:458 failed to bootstrap model: cannot start bootstrap instance: no matching tools available
05:07:35 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:734: failed to bootstrap model} {github.com/juju/juju/provider/common/bootstrap.go:171: cannot start bootstrap instance} {github.com/juju/juju/provider/maas/environ.go:937: } {github.com/juju/juju/tools/list.go:19: no matching tools available}])
jenkins@lmic-s9-instance:~$ dpkg -l|grep juju
ii juju 2.0-beta17-0ubuntu1~14.04.1~juju1 all next generation service orchestration system
ii juju-2.0 2.0-beta17-0ubuntu1~14.04.1~juju1 amd64 Juju is devops distilled - client

Tags: arm64 oil oil-2.0
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-rc1
Revision history for this message
Curtis Hovey (sinzui) wrote :

We can see the agents are precent in devel streams at streams.canonical.com

$ sstream-query http://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.sjson version=2.0-beta17 --output-format="%(item_name)s"|sort
2.0-beta17-centos7-amd64
2.0-beta17-precise-amd64
2.0-beta17-trusty-amd64
2.0-beta17-trusty-arm64
2.0-beta17-trusty-ppc64el
2.0-beta17-win10-amd64
2.0-beta17-win2012-amd64
2.0-beta17-win2012hv-amd64
2.0-beta17-win2012hvr2-amd64
2.0-beta17-win2012r2-amd64
2.0-beta17-win2016-amd64
2.0-beta17-win2016nano-amd64
2.0-beta17-win7-amd64
2.0-beta17-win8-amd64
2.0-beta17-win81-amd64
2.0-beta17-xenial-amd64
2.0-beta17-xenial-arm64
2.0-beta17-xenial-ppc64el
2.0-beta17-xenial-s390x
2.0-beta17-yakkety-amd64
2.0-beta17-yakkety-arm64
2.0-beta17-yakkety-ppc64el
2.0-beta17-yakkety-s390x

Changed in juju:
milestone: 2.0-rc1 → 2.0.0
Revision history for this message
Alexis Bruemmer (alexis-bruemmer) wrote :

larrym, are you still seeing this with rc1?? if so we will need access to the failing environment as we are not seeing this in our testing.

Changed in juju:
status: Triaged → Incomplete
Revision history for this message
Larry Michel (lmic) wrote :
Download full text (8.4 KiB)

Alexis, I am able to recreate this with 2.0 rc1 and I recreated it on trusty and xenial (from my laptop). I tried adding agent-stream: devel but that did not change anything. I've also recreated with both baremetal and vm on rc1.

This is where it's trying to get the tools:
00:51:59 DEBUG juju.environs.simplestreams simplestreams.go:680 using default candidate for content id "com.ubuntu.juju:devel:tools" are {20160220 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}

  larry:
    type: maas
    auth-types: [oauth1]
    endpoint: http://10.245.0.10/MAAS/
    agent-stream: devel

and here's output on trusty:

jenkins@lmic-s9-instance:~/.local/share/juju$ juju --debug bootstrap ppccontroller larry --to entei --config default-series
=xenial
00:51:57 INFO juju.cmd supercommand.go:63 running juju [2.0-rc1 gc go1.6]
00:51:57 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "--debug", "bootstrap", "ppccontroller", "larry", "--to", "entei", "--config", "default-series=xenial"}
00:51:57 DEBUG juju.cmd.juju.commands bootstrap.go:513 provider attrs: map[]
00:51:58 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
00:51:58 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.ssh/id_rsa.pub" to authorized-keys
00:51:58 DEBUG juju.cmd.juju.commands bootstrap.go:562 preparing controller with config: map[type:maas name:controller uuid:05f12ffe-e65b-4f73-84dc-c05a77cb9ebe default-series:xenial authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC4TpUCjjeLCbB1hG4rVodYaUrgMICQYhCCVf3NW+fg/gSY7bCZDwViVMFdbZ7eYBfmHJ8aehi4kX/Qvn9PWQxCcwT14dSWNR9cd2Nj+ZD8/tEf/gHug0ZeQkrjYMb3m6TQxmJKbJ/rmGa/ES0viYurJ7rgdO0+iL/PsoGhNDcGHz7FRl0N4O8eYk3bWYs3+kfuCiKmX/4OQkX09I4OL7+LaKJIv2qDF7TR7lY0peI6Y4BE8a0Q1KxJvsCGv3YrKvVLWxV5z3Z9xzjnb3mn4IkWtgudDUs5qbJbEXiZq5HyA8Wpmug2Xz3jciyKhm2LbqfQkYOCAtwqi2UZYKTP5IGN juju-client-key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot
]
00:51:58 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
00:51:58 INFO cmd cmd.go:129 Creating Juju controller "ppccontroller" on larry
00:51:58 INFO juju.cmd.juju.commands bootstrap.go:705 combined bootstrap constraints:
00:51:58 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
00:51:58 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
00:51:58 INFO cmd cmd.go:141 Loading image metadata
00:51:58 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0-rc1 for amd64
00:51:58 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0-rc1
00:51:58 INFO juju.environs.tools tools.go:101 finding agent binaries i...

Read more...

Changed in juju:
status: Incomplete → New
Changed in juju:
status: New → Triaged
assignee: nobody → Alexis Bruemmer (alexis-bruemmer)
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Larry,

Unfortunately, all interesting information is happening in TRACE level and you are in DEBUG here.
cloud0init-output would provide more information especially URL that we are going through while looking for tools...

However, from:
1. the paste above [20160220 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}]
2. and combining with Curtis's observation,

I *think* we are looking in http://streams.canonical.com/juju/tools/streams/v1/cpc-mirrors.sjson

And in that file, I cannot see any tools for rc1 release. I am not sure who maintains mirror files.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Mirrors are not relevant to this issue. Mirrors point users to public clouds to use a local copy of the agent. The mirror is only selected when your region matches a region in the mirror. Otherwise juju will continue to use streams. canonical.com to get the agent. ppc64el is not supported by aws, azure, or joyent, so you cannot get an image to get to the agent issue

BTW, the mirrors do have ppc64el machines, because we mirror all agents. We put the agents on aws, joyent, and azure *before* they were made the default streams
    http://juju-dist.s3.amazonaws.com/parallel-testing/agents/streams/v1/index2.json

Revision history for this message
Curtis Hovey (sinzui) wrote :

Form the output in comment #3, I see
    19:50:10 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: amd64

The juju client selects amd64 when you do not specify "--constraints arch=ppc64el". Can you bootstrap/add-machine/deploy the arch of you choice if you pass "--constraints arch=ppc64el"

Revision history for this message
Larry Michel (lmic) wrote :
Download full text (9.8 KiB)

Curtis, the bootstrap completed after specifying the arch constraints:

jenkins@lmic-s9-instance:~$ juju --debug bootstrap ppccontroller larry --to huffman-vm-05 --constraints arch=ppc64el
22:24:57 INFO juju.cmd supercommand.go:63 running juju [2.0-rc1 gc go1.6]
22:24:57 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "--debug", "bootstrap", "ppccontroller", "larry", "--to", "huffman-vm-05", "--constraints", "arch=ppc64el"}
22:24:57 DEBUG juju.cmd.juju.commands bootstrap.go:513 provider attrs: map[]
22:24:57 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
22:24:57 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.ssh/id_rsa.pub" to authorized-keys
22:24:57 DEBUG juju.cmd.juju.commands bootstrap.go:562 preparing controller with config: map[type:maas name:controller uuid:5eb05048-2117-4d41-868d-777f5796ea58 authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC4TpUCjjeLCbB1hG4rVodYaUrgMICQYhCCVf3NW+fg/gSY7bCZDwViVMFdbZ7eYBfmHJ8aehi4kX/Qvn9PWQxCcwT14dSWNR9cd2Nj+ZD8/tEf/gHug0ZeQkrjYMb3m6TQxmJKbJ/rmGa/ES0viYurJ7rgdO0+iL/PsoGhNDcGHz7FRl0N4O8eYk3bWYs3+kfuCiKmX/4OQkX09I4OL7+LaKJIv2qDF7TR7lY0peI6Y4BE8a0Q1KxJvsCGv3YrKvVLWxV5z3Z9xzjnb3mn4IkWtgudDUs5qbJbEXiZq5HyA8Wpmug2Xz3jciyKhm2LbqfQkYOCAtwqi2UZYKTP5IGN juju-client-key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot
]
22:24:57 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
22:24:57 INFO cmd cmd.go:129 Creating Juju controller "ppccontroller" on larry
22:24:57 INFO juju.cmd.juju.commands bootstrap.go:705 combined bootstrap constraints: arch=ppc64el
22:24:57 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
22:24:57 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
22:24:57 INFO cmd cmd.go:141 Loading image metadata
22:24:58 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0-rc1 for ppc64el
22:24:58 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0-rc1
22:24:58 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "devel"
22:24:58 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.0
22:24:58 INFO juju.environs.tools tools.go:111 filtering agent binaries by version: 2.0-rc1
22:24:58 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: ppc64el
22:24:58 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
22:24:58 DEBUG juju.environs.simplestreams simplestreams.go:680 using default candidate for content id "com.ubuntu.juju:devel:tools" are {20160220 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
22:25:00 INFO juju.environs.bootstrap tools.go:74 found 3 packaged agent binaries
22:25:...

Read more...

Revision history for this message
Anastasia (anastasia-macmood) wrote :

\o/

Changed in juju:
status: Triaged → Invalid
milestone: 2.0.0 → none
Revision history for this message
Larry Michel (lmic) wrote :

@anastasia and @sinzui, please keep in mind that having to specify arch=ppc64el for bootstrapping ppc64el VMs does represent a change in behaviour since the arch flag was never needed prior to beta16 nor is it needed for Juju 1.25 and prior versions. So, bringing that up in case there's a documentation need for this bug. Also, please correct me if I am wrong, my current understanding is that the arch flag had perhaps been implemented to replace the architecture detection mechanism, but that mechanism wasn't removed until beta16.

Revision history for this message
Anastasia (anastasia-macmood) wrote :

@Larry
If you strongly believe that current behavior is undesirable, I think it's worthwhile opening a separate, dedicated bug :D

Revision history for this message
mahmoh (mahmoh) wrote :

@Larry, this is also the case for arm64 so did you open a bug yet? Juju should detect the arch automatically and match it, not assume amd64. Let me know if you did or will, if not I will. Thank you.

summary: 2.0 beta17: cannot start bootstrap instance: no matching tools
- available for ppc64el node
+ available for ppc64el node (or arm64)
Revision history for this message
Larry Michel (lmic) wrote : Re: 2.0 beta17: cannot start bootstrap instance: no matching tools available for ppc64el node (or arm64)

@mahmoh, I will re-open this bug but I still need to re-test for GA. I'll update the bug later.

Changed in juju:
status: Invalid → New
Revision history for this message
Sean Feole (sfeole) wrote :
Download full text (5.5 KiB)

This is affecting arm64 hosts as well.

When the JuJu client is installed on a AMD64 host, I'm unable to bootstrap any ARM64 hosts that live in the specified Cloud.

See below my client is amd64:

Linux jenkins 3.13.0-96-generic #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ apt-cache policy juju
juju:
  Installed: 1:2.0.0-0ubuntu1~16.04.2~juju1
  Candidate: 1:2.0.0-0ubuntu1~16.04.2~juju1

$ juju list-clouds
Cloud Regions Default Type Description
aws 11 us-east-1 ec2 Amazon Web Services
aws-china 1 cn-north-1 ec2 Amazon China
aws-gov 1 us-gov-west-1 ec2 Amazon (USA Government)
azure 18 centralus azure Microsoft Azure
azure-china 2 chinaeast azure Microsoft Azure China
cloudsigma 5 hnl cloudsigma CloudSigma Cloud
google 4 us-east1 gce Google Cloud Platform
joyent 6 eu-ams-1 joyent Joyent Cloud
rackspace 6 dfw rackspace Rackspace Cloud
localhost 1 localhost lxd LXD Container Hypervisor
qa 0 maas Metal As A Service

I'm going to bootstrap to "qa" which is my maas server.

jenkins@jenkins:~$ juju bootstrap --debug qa qa
13:38:29 INFO juju.cmd supercommand.go:63 running juju [2.0.0 gc go1.6.2]
13:38:29 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "--debug", "qa", "qa"}
13:38:29 DEBUG juju.cmd.juju.commands bootstrap.go:538 provider attrs: map[]
13:38:30 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
13:38:30 DEBUG juju.cmd.juju.commands bootstrap.go:601 preparing controller with config: map[type:maas name:controller uuid:b9c6aacc-c04f-4c37-8604-83c74afe7124 authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDGUiVfF/i0ATgzI5TGcvvwta02LVao5ISo3tIqRT/EuSf7V1YPXwtu6FbfR2Db+2tzRIgvREsZ95rimi+qP+O85FcNHWg7faV/Pa+IoVSt6C0CayRwFTjXHIjdVJu0FFJ3/1lITMNO0X/moBYtzRakiio71QM4rBVj2FsMX25gYdhI3FnHjtu7JwoMGGsjdFmXOKwWYuHu/di0hinWFpB1Nkzx78pYLEDkFJX48vY1+3yzRr8C1Z0tGeboyPn86f/rNoX+/M9832gipLdW9SjCllSIJSRQpzQnvsCTfWQHxsGmv9EMzfNMiHjHCze/9z0icq2l/UAZdFU76n1j2rfp juju-client-key
]
13:38:30 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
13:38:30 INFO cmd cmd.go:129 Creating Juju controller "qa" on qa
13:38:30 INFO juju.cmd.juju.commands bootstrap.go:744 combined bootstrap constraints:
13:38:30 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
13:38:30 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
13:38:30 INFO cmd cmd.go:141 Loading image metadata
13:38:30 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0.0 for amd64
13:38:30 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0.0
13:38:30 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "released"
13:38:30 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor versio...

Read more...

tags: added: arm64
Revision history for this message
Larry Michel (lmic) wrote :
Download full text (3.9 KiB)

I recreated with juju2.0 GA. It doesn't work unless the arch=ppc64el constraints is specified.

jenkins@lmic-s9-instance:~$ juju bootstrap larry --debug --config default-series=xenial --to entei
14:15:22 INFO juju.cmd supercommand.go:63 running juju [2.0.0 gc go1.6]
14:15:22 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "bootstrap", "larry", "--debug", "--config", "default-series=xenial", "--to", "entei"}
14:15:22 DEBUG juju.cmd.juju.commands bootstrap.go:538 provider attrs: map[]
14:15:22 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
14:15:22 INFO cmd cmd.go:141 Adding contents of "/var/lib/jenkins/.ssh/id_rsa.pub" to authorized-keys
14:15:22 DEBUG juju.cmd.juju.commands bootstrap.go:601 preparing controller with config: map[authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC4TpUCjjeLCbB1hG4rVodYaUrgMICQYhCCVf3NW+fg/gSY7bCZDwViVMFdbZ7eYBfmHJ8aehi4kX/Qvn9PWQxCcwT14dSWNR9cd2Nj+ZD8/tEf/gHug0ZeQkrjYMb3m6TQxmJKbJ/rmGa/ES0viYurJ7rgdO0+iL/PsoGhNDcGHz7FRl0N4O8eYk3bWYs3+kfuCiKmX/4OQkX09I4OL7+LaKJIv2qDF7TR7lY0peI6Y4BE8a0Q1KxJvsCGv3YrKvVLWxV5z3Z9xzjnb3mn4IkWtgudDUs5qbJbEXiZq5HyA8Wpmug2Xz3jciyKhm2LbqfQkYOCAtwqi2UZYKTP5IGN juju-client-key
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot
 type:maas name:controller uuid:2c470697-7a6f-47f6-8a75-4bd3646a46f4 default-series:xenial]
14:15:22 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
14:15:22 INFO cmd cmd.go:129 Creating Juju controller "larry" on larry
14:15:22 INFO juju.cmd.juju.commands bootstrap.go:744 combined bootstrap constraints:
14:15:22 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true
14:15:22 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true
14:15:22 INFO cmd cmd.go:141 Loading image metadata
14:15:23 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0.0 for amd64
14:15:23 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0.0
14:15:23 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "released"
14:15:23 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.0
14:15:23 INFO juju.environs.tools tools.go:111 filtering agent binaries by version: 2.0.0
14:15:23 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: amd64
14:15:23 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
14:15:23 DEBUG juju.environs.simplestreams simplestreams.go:680 using default candidate for content id "com.ubuntu.juju:released:tools" are {20161007 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}
14:15:24 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent binaries
14:15:24 INFO cmd cmd.g...

Read more...

summary: - 2.0 beta17: cannot start bootstrap instance: no matching tools
- available for ppc64el node (or arm64)
+ 2.0.0: cannot start bootstrap instance: no matching tools available for
+ ppc64el node (or arm64)
Changed in juju:
status: New → Triaged
milestone: none → 2.0.1
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.0.1 → none
Changed in juju:
assignee: Alexis Bruemmer (alexis-bruemmer) → nobody
milestone: none → 2.2.0
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Curtis Hovey (sinzui)
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Revision history for this message
Tim Penhey (thumper) wrote :

As far as I'm aware this has been fixed for a while as we have CI tests bootstrapping in s390x.

Changed in juju:
milestone: 2.2-rc1 → none
status: Triaged → Fix Released
Revision history for this message
Tim Penhey (thumper) wrote :

And other non 99% architectures

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.