cloud-images

eks-ami fails to join cluster when not using cloudformation

Bug #1800939 reported by Daniel Richardson on 2018-10-31

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	cloud-images	Expired	Undecided	Unassigned

The commit below adds functionality to "Signal success/failure to cloudformation". The problem is that if you use any other method besides cloudformation to launch the ubuntu-eks nodes, the tag "aws:cloudformation:stack-name" will not exist and the bootstrap script on the image (/var/lib/cloud/scripts/per-instance/00-EKS-config.sh) will fail.
https://git.launchpad.net/~cloud-images-release-managers/cloud-images/+git/aws-eks-website/commit/?id=2d2433a4add30472e49b465b88a6da242956d072

build_name: minimal
serial: 20180814

Revision history for this message

Thomas Bechtold (toabctl) wrote on 2023-09-01:

Daniel, is this still relevant?

Changed in cloud-images:
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2023-11-01:

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

Changed in cloud-images:
status:	Incomplete → Expired

This report contains Public information

Everyone can see this information.

You are

Subscribing...

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