ds-identify fails on nocloud datasource when /var is a separate filesystem

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

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2020-06-24T14:10:35.725425+00:00

date_fix_committed = None

date_fix_released = None

id = 1884949

importance = low

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1884949

milestone = None

owner = mdrangula

owner_name = Mike Drangula

private = False

status = triaged

submitter = mdrangula

submitter_name = Mike Drangula

tags = []

duplicates = []

_Launchpad user **Mike Drangula(mdrangula)** wrote on 2020-06-24T14:10:35.725425+00:00_

I'm running CentOS 7.8.2003 with cloud-init 18.5. At least in CentOS, systemd is running the generators, including the cloud-init generator, before any secondary filesystems are mounted.

Thus, in ds-identify/dscheck_NoCloud/check_seed_dir, this line of code is invalid:

local dir="${PATH_VAR_LIB_CLOUD}/seed/$name"
[ -d "$dir" ] || return 1

because PATH_VAR_LIB_CLOUD is set to /var/lib/cloud and when this code is running /var is not yet mounted.

I'm sorry but I am not setup to test using a more recent version of cloud-init.