canonical / canonical/cloud-init

fs_label not supported by ds-identify

Open
#3,694 4 comments 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: #1880499](https://bugs.launchpad.net/cloud-init/+bug/1880499)

Launchpad details

affected_projects = []

assignee = None
assignee_name = None
date_closed = None
date_created = 2020-05-25T04:18:52.087084+00:00
date_fix_committed = None
date_fix_released = None
id = 1880499
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1880499
milestone = None
owner = ov2k
owner_name = ov2k
private = False
status = triaged
submitter = ov2k
submitter_name = ov2k
tags = []
duplicates = []

_Launchpad user **ov2k(ov2k)** wrote on 2020-05-25T04:18:52.087084+00:00_

The NoCloud fs_label setting is not respected by ds-identify when set in cloud.cfg or cloud.cfg.d/*. DataSourceNoCloud.py handles the setting correctly, but ds-identify is hardcoded to only look for cidata and CIDATA.

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.