canonical / canonical/cloud-init

Ephemeral w/o FS gets added to fstab

Open
#2,594 1 comment 0 reactions 0 assignees View on GitHub
bug launchpad
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

This bug was originally filed in Launchpad as [LP: #1513109](https://bugs.launchpad.net/cloud-init/+bug/1513109)

Launchpad details

affected_projects = []

assignee = None
assignee_name = None
date_closed = None
date_created = 2015-11-04T15:23:39.414961+00:00
date_fix_committed = None
date_fix_released = None
id = 1513109
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1513109
milestone = None
owner = nhouse
owner_name = Nate House
private = False
status = confirmed
submitter = nhouse
submitter_name = Nate House
tags = []
duplicates = []

_Launchpad user **Nate House(nhouse)** wrote on 2015-11-04T15:23:39.414961+00:00_

Using a DS that includes ec2 metadata with an ephemeral disk, even if the ephemeral disk is not formatted with a filesystem, cc_mounts adds an fstab entry that is likely invalid and potentially breaking reboot in some cases. I've seen this affect Debian based images and if needing to reproduce, Rax OnMetal I/O flavor is a good candidate. We are adjusting the base images cloud config to avoid hitting this but, any other cloud providers that provision non-formatted ephemeral disks would likely have similar issues.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.