search

canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.99k stars 882 forks source link

[2.0 rc1] juju can't access vSphere VM deployed with Xenial, cloud-init fails to set SSH keys #2673

Closed ubuntu-server-builder closed 1 year ago

ubuntu-server-builder commented 1 year ago

This bug was originally filed in Launchpad as LP: #1588041

Launchpad details 
affected_projects = ['juju']
assignee = None
assignee_name = None
date_closed = 2017-08-25T21:24:42.037188+00:00
date_created = 2016-06-01T19:27:36.560606+00:00
date_fix_committed = 2017-08-25T21:24:42.037188+00:00
date_fix_released = 2017-08-25T21:24:42.037188+00:00
id = 1588041
importance = undecided
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1588041
milestone = None
owner = sinzui
owner_name = Curtis Hovey
private = False
status = fix_released
submitter = lmic
submitter_name = Larry Michel
tags = ['ci', 'jujuqa', 'landscape', 'oil', 'oil-2.0', 'vsphere']
duplicates = []

Launchpad user Larry Michel(lmic) wrote on 2016-06-01T19:27:36.560606+00:00

I tried to do a bootstrap with vsphere as a provider using vsphere 6.0 and juju 1.25.5.

  vsphere:     type: vsphere     host: '**.*..'     user: 'administrator@vsphere.oil'     password: '**'     datacenter: 'dc0'     bootstrap-timeout: 1800     logging-config: "=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"     agent-stream: released

Initially, I did not specify the default series and bootstrap VM deployed with Xenial, however, juju could not connect to it after getting the address and seems stuck trying to connect and I had to CTRL-C:

$ juju bootstrap -e vsphere ERROR the "vsphere" provider is provisional in this version of Juju. To use it anyway, set JUJU_DEV_FEATURE_FLAGS="vsphere-provider" in your shell environment $ export JUJU_DEV_FEATURE_FLAGS="vsphere-provider" $ juju bootstrap -e vsphere Bootstrapping environment "vsphere" Starting new instance for initial state server Launching instance  - juju-e33e5800-edd9-4af7-8654-6d59b1e98eb9-machine-0 Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 10.245.39.94:22 Attempting to connect to fe80::250:56ff:fead:1b03:22 ^CInterrupt signalled: waiting for bootstrap to exit ERROR failed to bootstrap environment: interrupted

When I specified the default series to be trusty, it worked:

  vsphere:     type: vsphere     host: '**.*..'     user: 'administrator@vsphere.oil'     password: '**'     datacenter: 'dc0'     default-series: trusty     bootstrap-timeout: 1800     logging-config: "=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"     agent-stream: released

This was the output:

$ juju bootstrap -e vsphere Bootstrapping environment "vsphere" Starting new instance for initial state server Launching instance  - juju-b157863b-3ed4-4ae5-8c3c-82ae7629bff7-machine-0 Installing Juju agent on bootstrap instance Waiting for address Attempting to connect to 10.245.45.153:22 Attempting to connect to fe80::250:56ff:fead:3fa2:22 Warning: Permanently added '10.245.45.153' (ECDSA) to the list of known hosts. sudo: unable to resolve host ubuntuguest Logging to /var/log/cloud-init-output.log on remote host Running apt-get update Running apt-get upgrade Installing package: curl Installing package: cpu-checker Installing package: bridge-utils Installing package: rsyslog-gnutls Installing package: cloud-utils Installing package: cloud-image-utils Installing package: tmux Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/agent/1.25.5/juju-1.25.5-trusty-amd64.tgz]> Bootstrapping Juju machine agent Starting Juju machine agent (jujud-machine-0) Bootstrap agent installed vsphere -> vsphere Waiting for API to become available Waiting for API to become available Waiting for API to become available Waiting for API to become available Bootstrap complete

ubuntu-server-builder commented 1 year ago

Launchpad user James Tunnicliffe(dooferlad) wrote on 2016-06-03T14:46:49.845597+00:00

Can you confirm that Xenial boots if you just launch it using vsphere as a host? If it does can we have all of /var/log please? My hunch is cloud-init is running something that hangs, which we may be responsible for.

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-06-06T19:00:31.950455+00:00

James, Xenial does boot. I can see it on the console but I don't have the keys to ssh into it. Where do I get those?

ubuntu-server-builder commented 1 year ago

Launchpad user Cheryl Jennings(cherylj) wrote on 2016-06-06T19:48:22.320325+00:00

Larry - you can try to bootstrap with xenial and use the --keep-broken flag for it to not tear down the machine upon failure. Then you should be able to juju ssh into it (as long as the machine got far enough along to import the keys).

Once you can ssh into the machine, it would be useful to have:

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-06-07T17:43:05.803610+00:00

Per our conversation, it does not look like cloud-init sets things up correctly if it runs at all. Adding pastebin output from debug session that you requested Cheryl: https://pastebin.canonical.com/158212/

ubuntu-server-builder commented 1 year ago

Launchpad user Cheryl Jennings(cherylj) wrote on 2016-06-07T18:17:40.557837+00:00

This error is puzzling: 2016-06-07 16:37:40 DEBUG juju.provider.common bootstrap.go:326 connection attempt for fe80::250:56ff:fead:d9ff failed: ssh: connect to host fe80::250:56ff:fead:d9ff port 22: Invalid argument

Pinged Larry on IRC to run the bootstrap with TRACE to see the actual command being used for ssh.

ubuntu-server-builder commented 1 year ago

Launchpad user Cheryl Jennings(cherylj) wrote on 2016-06-07T20:08:06.354696+00:00

Worked with Larry and determined that the cloud-config.txt file is empty on xenial and not on trusty. Going to take another look at how juju is putting this there before pulling in smoser.

ubuntu-server-builder commented 1 year ago

Launchpad user Anastasia(anastasia-macmood) wrote on 2016-08-08T22:45:27.078077+00:00

It's Critical for Larry's project

ubuntu-server-builder commented 1 year ago

Launchpad user Curtis Hovey(sinzui) wrote on 2016-09-03T17:11:19.624547+00:00

This issue affect juju ci.

$ cat vs.yaml bootstrap-timeout: 1200 default-series: xenial enable-os-upgrade: false test-mode: true authorized-keys: | ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC9aoIHpnF4Y4w3PvUP0rhruNRaCFf0kPpYqM8V8uHvm/z//S2EE4wjIN3mxBv97kwGRmJWTYm8wu2ZepKxqsiH1LMpPiLHM2vOZyRkrz7wprHwxwH0ler6lZvM6hrWG7Pae6UcQuDASkV89hNdLPE20whyhIl07uPt+hjpMXJM82aSAhT57/rdOSRMgV518j1Aq/xNpbIKIaXA9P/TTHtLOxJvItKialx+MS0BSiE7O9dE8MeR4SyaAQr+yH81I5TlB1D2Qot80CB7eCiV0gSGt/azLhWTX/sDItQ2VVBxaYcEj9eoOUiVCDKx6eQ7tMJdWE/63wKYCs07sbu5G4Z3 juju-client-key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDyEdd8eDyy2WA6Q+W4GV2NqKX+yfkkW5ogSu3/7DjlqjED7dCNkevq2qpdR1AMkbKTouihWdyc8QKl9lzuwn0zoocXJUVgIOPV+KFxSAhj1djGvryHDjYUwdrLYUMu3CUFeIsRao2cn7EgZs0w1Y1quqr9c8cEg7XsAs0ZMN9YksEjG000VupOIZJNtk+5EYJm/6vNFI83IOn7ctWfjXymBuh7XM8d8vszyYDRdeDXY5Q9VLqHOP7/CFteIvcdHnSC1ObQuKzXRWz+m9thgQnRQjvirdwvDUXhjjQk9MNJZj84EukB8HyAVSN863MfuVGoCsNn7iEdtT6W2nKTWyL3 abentley@speedy agent-metadata-url: https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/parallel-testing/agents

$ juju --debug bootstrap curtis vsphere/dc0 --constraints mem=2G --config vs.yaml 16:31:55 INFO juju.cmd supercommand.go:63 running juju [2.0-beta17 gc go1.6] 16:31:55 DEBUG juju.cmd.juju.commands bootstrap.go:473 provider attrs: map[] 16:31:55 DEBUG juju.cmd.juju.commands bootstrap.go:522 preparing controller with config: map[enable-os-upgrade:false type:vsphere uuid:f4d002c5-ccc4-4373-8f1d-fb516597c67e test-mode:true authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCrXoztXs5X89N7SwxGjXYjL4M8Coclk+/blvzyiqZDaWsH234DETiv3Rwc2wJlEk3K1HSLnpBQHL6HQME7j/PpMaFGiJqD0tfF0JU2Kj6FEsgV43IR0YvXm0/2EvzO4NMplukmJVUPIAa++Tpl/72F+t8t2mSK73PwzeycpC+X9z/NC5EwsOMH87NYrM1HdwwZlz2GJswcG0IHDB/5oKV4nPMkm6EFweKt4N5HrRjA9l7y3tUbNhGMuEJVIbskfn6LTdir6CghRHY+OT70RrN+gqRVw3y/GvrfVE3m8ZqgbqAFE9UDBXDSI8AX2dYAlmvTI/B9X2QiMrNC0DXvnY/X oil-ci-bot ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC9aoIHpnF4Y4w3PvUP0rhruNRaCFf0kPpYqM8V8uHvm/z//S2EE4wjIN3mxBv97kwGRmJWTYm8wu2ZepKxqsiH1LMpPiLHM2vOZyRkrz7wprHwxwH0ler6lZvM6hrWG7Pae6UcQuDASkV89hNdLPE20whyhIl07uPt+hjpMXJM82aSAhT57/rdOSRMgV518j1Aq/xNpbIKIaXA9P/TTHtLOxJvItKialx+MS0BSiE7O9dE8MeR4SyaAQr+yH81I5TlB1D2Qot80CB7eCiV0gSGt/azLhWTX/sDItQ2VVBxaYcEj9eoOUiVCDKx6eQ7tMJdWE/63wKYCs07sbu5G4Z3 juju-client-key ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDyEdd8eDyy2WA6Q+W4GV2NqKX+yfkkW5ogSu3/7DjlqjED7dCNkevq2qpdR1AMkbKTouihWdyc8QKl9lzuwn0zoocXJUVgIOPV+KFxSAhj1djGvryHDjYUwdrLYUMu3CUFeIsRao2cn7EgZs0w1Y1quqr9c8cEg7XsAs0ZMN9YksEjG000VupOIZJNtk+5EYJm/6vNFI83IOn7ctWfjXymBuh7XM8d8vszyYDRdeDXY5Q9VLqHOP7/CFteIvcdHnSC1ObQuKzXRWz+m9thgQnRQjvirdwvDUXhjjQk9MNJZj84EukB8HyAVSN863MfuVGoCsNn7iEdtT6W2nKTWyL3 abentley@speedy agent-metadata-url:https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/parallel-testing/agents default-series:xenial name:controller] 16:31:55 INFO cmd cmd.go:129 Creating Juju controller "curtis" on vsphere/dc0 16:31:55 INFO juju.cmd.juju.commands bootstrap.go:665 combined bootstrap constraints: mem=2048M 16:31:55 DEBUG juju.environs.bootstrap bootstrap.go:185 model "controller" supports service/machine networks: true 16:31:55 DEBUG juju.environs.bootstrap bootstrap.go:187 network management by juju enabled: true 16:31:55 INFO cmd cmd.go:141 Loading image metadata 16:31:55 INFO cmd cmd.go:129 Looking for packaged Juju agent version 2.0-beta17 for amd64 16:31:55 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.0-beta17 16:31:55 INFO juju.environs.tools tools.go:101 finding agent binaries in stream "devel" 16:31:55 INFO juju.environs.tools tools.go:103 reading agent binaries with major.minor version 2.0 16:31:55 INFO juju.environs.tools tools.go:111 filtering agent binaries by version: 2.0-beta17 16:31:55 INFO juju.environs.tools tools.go:117 filtering agent binaries by architecture: amd64 16:31:55 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog" 16:31:57 DEBUG juju.environs.simplestreams simplestreams.go:454 skipping index "https://swift.canonistack.canonical.com/v1/AUTH_526ad877f3e3464589dc1145dfeaac60/juju-dist/parallel-testing/agents/streams/v1/index2.json" because of missing information: "content-download" data not found 16:31: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 []} 16:32:00 INFO juju.environs.bootstrap tools.go:74 found 15 packaged agent binaries 16:32:00 INFO cmd cmd.go:141 Starting new instance for initial controller Launching controller instance(s) on vsphere/dc0... 16:32:00 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default cloud images" 16:32:00 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default ubuntu cloud images" 16:32:01 DEBUG juju.environs.simplestreams simplestreams.go:454 skipping index "https://streams.canonical.com/juju/images/releases/streams/v1/index.sjson" because of missing information: "image-downloads" data not found 16:32:02 DEBUG juju.cloudconfig.instancecfg instancecfg.go:777 Setting numa ctl preference to false 16:32:02 DEBUG juju.service discovery.go:62 discovered init system "systemd" from series "xenial" 16:32:02 DEBUG juju.provider.vmware environ_broker.go:93 Vmware user data; 2940 bytes 16:32:03 INFO juju.provider.vmware environ_availzones.go:118 found 1 zones: [{10.245.0.130 []}] 16:32:03 DEBUG juju.provider.vmware ova_import_manager.go:180 Downloading ova file from url: http://cloud-images.ubuntu.com/releases/server/releases/xenial/release-20160830/ubuntu-16.04-server-cloudimg-amd64.ova 16:32:03 DEBUG juju.provider.vmware ova_import_manager.go:207 Extracting ova to path: /tmp/478292917 16:32:03 DEBUG juju.provider.vmware ova_import_manager.go:223 Writing file ubuntu-xenial-16.04-cloudimg.ovf 16:32:03 DEBUG juju.provider.vmware ova_import_manager.go:223 Writing file ubuntu-xenial-16.04-cloudimg.mf 16:32:03 DEBUG juju.provider.vmware ova_import_manager.go:223 Writing file ubuntu-xenial-16.04-cloudimg.vmdk 16:32:41 DEBUG juju.provider.vmware ova_import_manager.go:243 Ova extracted successfully 16:32:50 DEBUG juju.provider.vmware ova_import_manager.go:249 Uploading item from path: /tmp/478292917/ubuntu-xenial-16.04-cloudimg.vmdk 16:32:50 DEBUG juju.provider.vmware ova_import_manager.go:264 Uploading image to https://10.245.0.130/nfc/5260a1c6-e27f-69bf-cf63-1c9cbacf0c0a/disk-0.vmdk 16:33:13 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 10% 16:33:24 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 20% 16:33:36 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 30% 16:33:52 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 40% 16:34:05 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 50% 16:34:17 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 60% 16:34:30 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 70% 16:34:51 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 80% 16:35:14 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 90% 16:35:30 DEBUG juju.provider.vmware ova_import_manager.go:271 Progress: 100% 16:35:32 DEBUG juju.provider.vmware ova_import_manager.go:277 Image uploaded 16:35:41 INFO juju.provider.vmware environ_broker.go:47 started instance "juju-97c67e-0"

ubuntu-server-builder commented 1 year ago

Launchpad user Curtis Hovey(sinzui) wrote on 2016-09-03T17:19:47.502129+00:00

Juju selected http://cloud-images.ubuntu.com/releases/server/releases/xenial/release-20160830/ubuntu-16.04-server-cloudimg-amd64.ova . The trusty image (http://cloud-images.ubuntu.com/releases/server/releases/trusty/release-20160809.1/ubuntu-14.04-server-cloudimg-amd64.ova) works with juju.

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-09-21T16:00:01.927168+00:00

I tried to deploy a bundle with mixed series and all the Trusty came up and the Xenial one stayed pending. It looks to be related as the machines are up and keys are not set up.

jenkins@lmic-s9-instance:~/vmware$ juju status MODEL CONTROLLER CLOUD/REGION VERSION default vspherecontroller-beta18 vsphere/dc0 2.0-beta18

APP VERSION STATUS SCALE CHARM STORE REV OS NOTES elasticsearch active 2 elasticsearch jujucharms 18 ubuntu
etcd unknown 0/3 etcd jujucharms 8 ubuntu
filebeat unknown 0 filebeat jujucharms 4 ubuntu
kibana active 1 kibana jujucharms 14 ubuntu exposed kubernetes unknown 0/3 kubernetes jujucharms 8 ubuntu exposed topbeat unknown 0 topbeat jujucharms 4 ubuntu

RELATION PROVIDES CONSUMES TYPE peer elasticsearch elasticsearch peer elasticsearch elasticsearch filebeat regular rest elasticsearch kibana regular elasticsearch elasticsearch topbeat regular cluster etcd etcd peer beats-host etcd filebeat subordinate etcd etcd kubernetes regular beats-host etcd topbeat subordinate juju-info filebeat kubernetes regular beats-host kubernetes filebeat subordinate certificates kubernetes kubernetes peer beats-host kubernetes topbeat subordinate

UNIT WORKLOAD AGENT MACHINE PUBLIC-ADDRESS PORTS MESSAGE elasticsearch/0 active idle 0 10.245.61.122 9200/tcp Ready elasticsearch/1 active idle 1 10.245.61.121 9200/tcp Ready etcd/0 unknown allocating 2 10.245.61.123 Waiting for agent initialization to finish etcd/1 unknown allocating 3 10.245.61.124 Waiting for agent initialization to finish etcd/2 unknown allocating 4 10.245.61.125 Waiting for agent initialization to finish kibana/0 active idle 5 10.245.61.129 80/tcp,9200/tcp ready kubernetes/0 unknown allocating 6 10.245.61.126 Waiting for agent initialization to finish kubernetes/1 unknown allocating 7 10.245.61.127 Waiting for agent initialization to finish kubernetes/2 unknown allocating 8 10.245.61.128 Waiting for agent initialization to finish

MACHINE STATE DNS INS-ID SERIES AZ 0 started 10.245.61.122 juju-efa5c6-0 trusty
1 started 10.245.61.121 juju-efa5c6-1 trusty
2 pending 10.245.61.123 juju-efa5c6-2 xenial
3 pending 10.245.61.124 juju-efa5c6-3 xenial
4 pending 10.245.61.125 juju-efa5c6-4 xenial
5 started 10.245.61.129 juju-efa5c6-5 trusty
6 pending 10.245.61.126 juju-efa5c6-6 xenial
7 pending 10.245.61.127 juju-efa5c6-7 xenial
8 pending 10.245.61.128 juju-efa5c6-8 xenial

jenkins@lmic-s9-instance:~/vmware$ juju ssh etcd/0 ERROR retrieving SSH host keys for "etcd/0": keys not found

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T19:11:41.361265+00:00

Looking at the juju vsphere provider code I see that the metadata is passed in via the OVA during image import and have confirmed with Larry through cloud-init logs on trusty that the OVF cloud-init data source is used there via virtual CD-ROM to feed in the userdata and ssh keys.

Larry and I are working on grabbing the content of the virtual CD attached to the Xenial instance to ensure that it received user-data (previously there was a note in this bug that none was present and we need to confirm).

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T19:12:28.575857+00:00

I have downloaded the xenial ova used by the provider and confirmed that cloud-init is configured to make use of the OVF datasource.

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T19:25:20.562628+00:00

Verified that the user data from the ISO attached to the xenial instance looks decent (don't know that it'll work, but there's data) Launchpad attachments: Xenial meta-data ISO

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T20:25:21.066052+00:00

I have downloaded a drive image of a xenial VM that Juju attempted to boot and found that cloud-init could not parse the user-data attached to the instance. Here is the relevant error from /var/log/cloud-init.log. Attaching /var/lib/cloud, /var/log, and /etc/cloud to this bug for further research.

Sep 22 18:47:54 ubuntu [CLOUDINIT] init.py[DEBUG]: {'Content-Type': 'text/x-not-multipart', 'Content-Disposition': 'attachment; filename="part-001"', 'MIME-Version': '1.0'} Sep 22 18:47:54 ubuntu [CLOUDINIT] init.py[WARNING]: Unhandled non-multipart (text/x-not-multipart) userdata: 'b'I2Nsb3VkLWNvbmZpZwphcHRf'...'

Launchpad attachments: xenial-juju-vsphere-userdata-20160921.tar.gz

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T20:27:30.253482+00:00

Scott, can you review the user-data and advise?

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-09-22T20:32:56.721743+00:00

One more data point is that Yakkety works. I was able to bootstrap a new controller:

juju bootstrap vspherecontroller-beta-yak vsphere/dc0 --debug --config default-series=yakkety --config image-stream=daily

It downloaded the ova from:

Downloading ova file from url: http://cloud-images.ubuntu.com/daily/server/yakkety/20160918/yakkety-server-cloudimg-amd64.ova

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T20:43:45.677170+00:00

And this failure is occurring now with a xenial release image with serial 20160921 which contains cloud-init 0.7.7~bzr1256-0ubuntu1~16.04.1

http://cloud-images.ubuntu.com/releases/xenial/release/unpacked/ubuntu-16.04-server-cloudimg-amd64.manifest

ubuntu-server-builder commented 1 year ago

Launchpad user Scott Moser(smoser) wrote on 2016-09-22T20:44:06.266032+00:00

i have a hunch that this is a dupe of bug 1619394 which landed in xenial 2 hours ago. You'll need an image with cloud-init inside (or patch an image) to try.

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T20:47:34.938842+00:00

Larry, keep an eye on http://cloud-images.ubuntu.com/daily/server/xenial/ for a serial with a date of 20160923 or later. Then re-test by bootstrapping with "--config image-stream=daily". That should pick up the cloud-init package released today.

ubuntu-server-builder commented 1 year ago

Launchpad user Robert C Jennings(rcj) wrote on 2016-09-22T20:49:31.916973+00:00

And you can confirm by looking @ http://cloud-images.ubuntu.com/daily/server/xenial//unpacked/xenial-server-cloudimg-amd64.manifest to find the version of cloud-init, it will need to be 0.7.8-1-g3705bb5-0ubuntu1~16.04.1

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-09-23T15:30:54.804253+00:00

I tested this morning and looks like it is fixed as Juju is reporting the node as active now:

MACHINE STATE DNS INS-ID SERIES AZ 0 started 10.245.61.193 juju-a64e14-0 trusty
1 started 10.245.61.194 juju-a64e14-1 trusty
2 started fe80::1 juju-a64e14-2 xenial
3 started fe80::1 juju-a64e14-3 xenial
4 started fe80::1 juju-a64e14-4 xenial
5 started 10.245.61.197 juju-a64e14-5 trusty
6 started fe80::1 juju-a64e14-6 xenial
7 started fe80::1 juju-a64e14-7 xenial
8 started fe80::1 juju-a64e14-8 xenial

But they have a IPV6 IP address and that gives errors:

jenkins@lmic-s9-instance:~/kubernetes$ juju ssh 3 ssh: connect to host fe80::1 port 22: Invalid argument

It's not clear to me either how that's affecting the charms although most of them come up, but there are some errors and I'm not clear now whether they're related to this:

jenkins@lmic-s9-instance:~/kubernetes$ juju status MODEL CONTROLLER CLOUD/REGION VERSION default vspherecontroller-beta18 vsphere/dc0 2.0-rc1

APP VERSION STATUS SCALE CHARM STORE REV OS NOTES elasticsearch active 2 elasticsearch jujucharms 18 ubuntu
etcd error 3 etcd jujucharms 8 ubuntu
filebeat active 3 filebeat jujucharms 4 ubuntu
kibana active 1 kibana jujucharms 14 ubuntu exposed kubernetes error 3 kubernetes jujucharms 8 ubuntu exposed topbeat active 3 topbeat jujucharms 4 ubuntu

UNIT WORKLOAD AGENT MACHINE PUBLIC-ADDRESS PORTS MESSAGE elasticsearch/0 active idle 0 10.245.61.193 9200/tcp Ready elasticsearch/1 active idle 1 10.245.61.194 9200/tcp Ready etcd/0 error idle 2 fe80::1 2379/tcp hook failed: "certificates-relation-changed" filebeat/0 active idle fe80::1 Filebeat ready topbeat/0 active idle fe80::1 Topbeat ready etcd/1 maintenance idle 3 fe80::1 Attempting install of etcd from apt filebeat/2 active idle fe80::1 Filebeat ready topbeat/2 active idle fe80::1 Topbeat ready etcd/2 active idle 4 fe80::1 2379/tcp cluster is healthy filebeat/1 active idle fe80::1 Filebeat ready topbeat/1 active idle fe80::1 Topbeat ready kibana/0 active idle 5 10.245.61.197 80/tcp,9200/tcp ready kubernetes/0 maintenance executing 6 fe80::1 (install) Installing docker-engine from apt kubernetes/1 maintenance executing 7 fe80::1 (install) Installing docker-engine from apt kubernetes/2 error idle 8 fe80::1 hook failed: "install"

ubuntu-server-builder commented 1 year ago

Launchpad user Larry Michel(lmic) wrote on 2016-09-23T15:33:25.473501+00:00

Also to note is that the controller node is also Xenial and that worked.

This is the model config:

jenkins@lmic-s9-instance:~/kubernetes$ juju model-config ATTRIBUTE FROM VALUE agent-metadata-url default "" agent-stream default released agent-version model 2.0-rc1 apt-ftp-proxy default "" apt-http-proxy default "" apt-https-proxy default "" apt-mirror default "" automatically-retry-hooks default true default-series default xenial development default false disable-network-management default false enable-os-refresh-update default true enable-os-upgrade default true external-network model "" firewall-mode default instance ftp-proxy default "" http-proxy default "" https-proxy default "" ignore-machine-addresses default false image-metadata-url default "" image-stream model daily logforward-enabled default false logging-config model =DEBUG;unit=DEBUG no-proxy default "" provisioner-harvest-mode default destroyed proxy-ssh default false resource-tags model {} ssl-hostname-verification default true test-mode default false transmit-vendor-metrics default true