If you are seeing this message, please file a bug against

[ubuntu-server-builder]

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

Launchpad details

affected_projects = []
assignee = None
assignee_name = None
date_closed = 2019-09-18T04:17:31.461571+00:00
date_created = 2018-06-24T08:49:58.157883+00:00
date_fix_committed = None
date_fix_released = None
id = 1778391
importance = undecided
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1778391
milestone = None
owner = hardcore-01
owner_name = admin
private = False
status = expired
submitter = hardcore-01
submitter_name = admin
tags = ['dsid']
duplicates = []

Launchpad user admin(hardcore-01) wrote on 2018-06-24T08:49:58.157883+00:00

running
fedora-atomic latest
fails to pull kubernets up via magnum on queens open-stack

going thru log on the master node via journalctl

hard crash corrupted stack frames

[ubuntu-server-builder]

Launchpad user admin(hardcore-01) wrote on 2018-06-24T08:49:58.157883+00:00

Launchpad attachments: bad init-startup

[ubuntu-server-builder]

Launchpad user Ryan Harper(raharper) wrote on 2019-07-19T18:42:29.148563+00:00

Thanks for filing the bug.
Here's my best guess:

Cloud-init's ds-identify isn't installed[1], which prevented cloud-init from detecting it was running on OpenStack. It eventually got there but it appeared that networking wasn't fully up by the time that it crawled the OpenStack URLs, and eventually the last datasource EC2 ran, and by that time, networking was up and the metadata URLs responded (OpenStack metadata service is compat with EC2 urls) so Ec2 Datasource was used but the system UUID didn't indicate that it was an Ec2 instance (because it isnt) so the warning was displayed.

We've recently fixed an issue with cloud-init upstream's packaging on redhat/fedora/centos where the ds-identify tool wasn't installed where it was expected.

https://bugs.launchpad.net/cloud-init/+bug/1833264

So it may be that's needed to get things working.

1. /run/cloud-init/ds-identify.log
   /usr/lib/systemd/system-generators/cloud-init-generator normal=/run/systemd/generator early=/run/systemd/generator.early late=/run/systemd/generator.late
   kernel command line (/proc/cmdline): BOOT_IMAGE=/ostree/fedora-atomic-8c75464537441e8641e67a04f0057750eb832264563daf35e6a720c854bcd5e6/vmlinuz-4.16.14-300.fc28.x86_64 no_timer_check console=tty1 console=ttyS0,115200n8 console=ttyAMA0 console=hvc0 net.ifnames=0 rd.lvm.lv=atomicos/root root=/dev/mapper/atomicos-root ostree=/ostree/boot.0/fedora-atomic/8c75464537441e8641e67a04f0057750eb832264563daf35e6a720c854bcd5e6/0
   kernel_cmdline found unset
   etc_file found unset
   default found enabled
   checking for datasource
   no ds-identify in /usr/lib/cloud-init/ds-identify. _RET=found
   enabled via /run/systemd/generator.early/multi-user.target.wants/cloud-init.target -> /lib/systemd/system/cloud-init.target

[ubuntu-server-builder]

Launchpad user Launchpad Janitor(janitor) wrote on 2019-09-18T04:17:31.332533+00:00

[Expired for cloud-init because there has been no activity for 60 days.]