vsphere --keep-missing still destroys vm

Bug #1746813 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

I get an error bootstrapping to vsphere, and I pass --keep-broken expecting that my vm will remain around. Apparently it doesn't under this condition, leading to me having a hard time debugging.

Debug output:

ubuntu@maas2:~⟫ juju bootstrap lsvmware vmwarecontroller --config primary-network="VM Network" --config external-network="pub202" --config datastore=SpindleDisks1 --debug --keep-broken
15:47:13 INFO juju.cmd supercommand.go:56 running juju [2.3.2 gc go1.9.2]
15:47:13 DEBUG juju.cmd supercommand.go:57 args: []string{"/snap/juju/3230/bin/juju", "bootstrap", "lsvmware", "vmwarecontroller", "--config", "primary-network=VM Network", "--config",
 "external-network=pub202", "--config", "datastore=SpindleDisks1", "--debug", "--keep-broken"}
15:47:13 DEBUG juju.cmd.juju.commands bootstrap.go:826 authenticating with region "" and credential "Administrator" ()
15:47:13 DEBUG juju.cmd.juju.commands bootstrap.go:954 provider attrs: map[]
15:47:14 INFO cmd authkeys.go:114 Adding contents of "/home/ubuntu/.local/share/juju/ssh/juju_id_rsa.pub" to authorized-keys
15:47:14 DEBUG juju.cmd.juju.commands bootstrap.go:1010 preparing controller with config: map[firewall-mode:instance net-bond-reconfigure-delay:17 fan-config: apt-no-proxy: ftp-proxy: ap
t-mirror: update-status-hook-interval:5m transmit-vendor-metrics:true name:controller default-series:xenial type:vsphere apt-ftp-proxy: cloudinit-userdata: image-metadata-url: enable-os-
upgrade:true apt-http-proxy: agent-metadata-url: logforward-enabled:false max-status-history-age:336h provisioner-harvest-mode:destroyed datastore:SpindleDisks1 development:false max-act
ion-results-age:336h ignore-machine-addresses:false no-proxy:127.0.0.1,localhost,::1 agent-stream:released uuid:c8d9a2c7-28d0-46a9-8c28-a07e265a4635 container-networking-method: ssl-host
name-verification:true max-action-results-size:5G external-network:pub202 logging-config: egress-subnets: enable-os-refresh-update:true test-mode:false https-proxy: automatically-retry-h
ooks:true apt-https-proxy: resource-tags: max-status-history-size:5G primary-network:VM Network disable-network-management:false proxy-ssh:false authorized-keys:ssh-rsa AAAAB3NzaC1yc2EAA
AADAQABAAABAQDgQG/OlYz0wQ7B0G7pcTRT+cEG4Hu1SJ7A4Ch4m62TQh+VZDfG7nBA22EYl1fldQPD+h2CZd0KBpLeUMl1DnZBv2qfhTpNUfEqayDl3E+q7NNfbt2hQdigX8LmXlcseseCEHtwnQbu/Wd09yRQUke8Sp6cHZ+HJzGNcynw5W+F0ED
iDfSCnV43IhuwQOw7pCC4PwehUK4++5cgZMpH/dmQFF3O5aiVhtXXU8qZSjkJNP7LaGgjAtv3OwXNC4E2aNzsxTApkmFsiI35Gs+ifUPReKNCLzoqxxE97iQO+EzMrWct+R9QKP1Hyb+N9hYzUfTIPjMwI+tgjIFbyA8NyiB3 juju-client-key
 http-proxy: image-stream:released]
15:47:14 INFO cmd bootstrap.go:499 Creating Juju controller "vmwarecontroller" on lsvmware/Datacenter1
15:47:14 INFO juju.cmd.juju.commands bootstrap.go:563 combined bootstrap constraints:
15:47:14 DEBUG juju.environs.bootstrap bootstrap.go:199 model "controller" supports service/machine networks: false
15:47:14 DEBUG juju.environs.bootstrap bootstrap.go:201 network management by juju enabled: true
15:47:14 INFO cmd bootstrap.go:233 Loading image metadata
15:47:14 INFO cmd bootstrap.go:296 Looking for packaged Juju agent version 2.3.2 for amd64
15:47:14 INFO juju.environs.bootstrap tools.go:72 looking for bootstrap agent binaries: version=2.3.2
15:47:14 DEBUG juju.environs.tools tools.go:102 finding agent binaries in stream: "released"
15:47:14 DEBUG juju.environs.tools tools.go:104 reading agent binaries with major.minor version 2.3
15:47:14 DEBUG juju.environs.tools tools.go:112 filtering agent binaries by version: 2.3.2
15:47:14 DEBUG juju.environs.tools tools.go:118 filtering agent binaries by architecture: amd64
15:47:14 DEBUG juju.environs.tools urls.go:109 trying datasource "keystone catalog"
15:47:14 DEBUG juju.environs.simplestreams simplestreams.go:683 using default candidate for content id "com.ubuntu.juju:released:tools" are {20161007 mirrors:1.0 content-download streams
/v1/cpc-mirrors.sjson []}
15:47:15 INFO juju.environs.bootstrap tools.go:74 found 16 packaged agent binaries
15:47:15 INFO cmd bootstrap.go:371 Starting new instance for initial controller
15:47:16 INFO cmd bootstrap.go:151 Launching controller instance(s) on lsvmware/Datacenter1...
15:47:17 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default cloud images"
15:47:17 DEBUG juju.environs imagemetadata.go:112 obtained image datasource "default ubuntu cloud images"
15:47:18 DEBUG juju.environs.simplestreams simplestreams.go:457 skipping index "https://streams.canonical.com/juju/images/releases/streams/v1/index.sjson" because of missing information:
 "image-downloads" data not found
15:47:19 DEBUG juju.cloudconfig.instancecfg instancecfg.go:835 Setting numa ctl preference to false
15:47:19 DEBUG juju.service discovery.go:63 discovered init system "systemd" from series "xenial"
15:47:19 DEBUG juju.provider.vmware environ_broker.go:158 Vmware user data; 5272 bytes
15:47:19 DEBUG juju.provider.vmware environ_broker.go:207 attempting to create VM in availability zone Autopilot
15:47:19 DEBUG juju.provider.vmware vmdk.go:115 uploading http://cloud-images.ubuntu.com/releases/server/releases/xenial/release-20180126/ubuntu-16.04-server-cloudimg-amd64.ova contents
to juju-vmdks/8d37e0f5-b868-4ac8-842b-01c0ba54a27a/xenial/b07093a95f3b7244f0b2583a728cf0cc2e9574422fc0023b38f70e7a0786eb2a.vmdk.tmp
 - uploading juju-vmdks/8d37e0f5-b868-4ac8-842b-01c0ba54a27a/xenial/b07093a95f3b7244f0b2583a728cf0cc2e9574422fc0023b38f70e7a0786eb2a.vmdk.tmp: 37.72% (16.8M - uploading juju-vmdks/8d37e0
f5-b868-4ac8-842b-01c0ba54a27a/xenial/b07093a95f3b7244f0b2583a728cf0cc2e9574422fc0023b38f70e7a0786eb2a.vmdk.tmp: 79.43% (33.8M15:47:31 DEBUG juju.provider.vmware createvm.go:312 VM confi
gured to use network "VM Network": &{ManagedEntity:{ExtensibleManagedObject:{Self:Network:network-11 Value:[] AvailableField:[]} Parent:Folder:group-n6 CustomValue:[] OverallStatus:green
 ConfigStatus:green ConfigIssue:[] EffectiveRole:[-1] Permission:[] Name: DisabledMethod:[] RecentTask:[] DeclaredAlarmState:[] TriggeredAlarmState:[] AlarmActionsEnabled:0xc42121b4e0 Ta
g:[]} Name:VM Network Summary:0xc4222c3080 Host:[HostSystem:host-9 HostSystem:host-17] Vm:[VirtualMachine:vm-12 VirtualMachine:vm-124 VirtualMachine:vm-126 VirtualMachine:vm-127 VirtualM
achine:vm-128 VirtualMachine:vm-129 VirtualMachine:vm-148 VirtualMachine:vm-151 VirtualMachine:vm-58 VirtualMachine:vm-168 VirtualMachine:vm-176 VirtualMachine:vm-178 VirtualMachine:vm-8
5 VirtualMachine:vm-86 VirtualMachine:vm-91]}
15:47:31 DEBUG juju.provider.vmware createvm.go:362 external network device: &{VirtualVmxnet:{VirtualEthernetCard:{VirtualDevice:{DynamicData:{} Key:0 DeviceInfo:<nil> Backing:0xc4226a7c
20 Connectable:0xc4221bdba0 SlotInfo:<nil> ControllerKey:0 UnitNumber:<nil>} AddressType: MacAddress: WakeOnLanEnabled:0xc420ba14b9 ResourceAllocation:<nil> ExternalId: UptCompatibilityE
nabled:<nil>}}}
15:47:31 DEBUG juju.provider.vmware createvm.go:169 creating temporary VM in folder Folder:group-v242 @ /Datacenter1/vm/Juju Controller (8d37e0f5-b868-4ac8-842b-01c0ba54a27a)/Model "cont
roller" (c8d9a2c7-28d0-46a9-8c28-a07e265a4635)
15:47:32 DEBUG juju.provider.vmware createvm.go:193 cloning VM
15:47:49 INFO cmd bootstrap.go:508 bootstrap failed but --keep-broken was specified.
This means that cloud resources are left behind, but not registered to
your local client, as the controller was not successfully created.
However, you should be able to ssh into the machine using the user "ubuntu" and
their IP address for diagnosis and investigation.
When you are ready to clean up the failed controller, use your cloud console or
equivalent CLI tools to terminate the instances and remove remaining resources.

See `juju kill-controller`.
ERROR failed to bootstrap model: cannot start bootstrap instance in availability zone "Autopilot": A general system error occurred: Connection refused
15:47:49 DEBUG cmd supercommand.go:459 error stack:
A general system error occurred: Connection refused
github.com/juju/juju/provider/vsphere/internal/vsphereclient/status.go:36:
github.com/juju/juju/provider/vsphere/internal/vsphereclient/createvm.go:234:
github.com/juju/juju/provider/vsphere/environ_broker.go:216:
github.com/juju/juju/provider/vsphere/environ_broker.go:88:
github.com/juju/juju/provider/common/bootstrap.go:216: cannot start bootstrap instance in availability zone "Autopilot"
github.com/juju/juju/provider/common/bootstrap.go:50:
github.com/juju/juju/cmd/juju/commands/bootstrap.go:611: failed to bootstrap model
1 ubuntu@maas2:~⟫

Revision history for this message
David Britton (dpb) wrote :
Revision history for this message
Tim Penhey (thumper) wrote :

I don't think it got as far as actually creating the VM in which to keep.

Revision history for this message
Tim Penhey (thumper) wrote :

Hmm... perhaps one part thought it was there, and another part didn't? That's my best guess at the moment.

tags: added: bootstrap vsphere-provider
Changed in juju:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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