Public bug reported:
when cloud-init writes mount entries into /etc/fstab, it adds:
x-systemd.requires=cloud-init.service
This is because a subsequent boot of cloud-init may need to remove that
entry (a new instance for example).
cloud-init has a feature where it can be disabled by:
sudo touch /etc/cloud/cloud-init.disabled
The generator for cloud-init then says that the cloud-init.target does
not need to run.
However, due to the (possibly stale) x-systemd.requires=cloud-
init.service entries, cloud-init will still run.
I think what I'd like is a:
x-systemd.after=cloud-init.service
** Affects: cloud-init
Importance: Medium
Status: Confirmed
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1667878
Title:
fstab entries with x-systemd.requires=cloud-init.service mean cloud-
init will always run.
Status in cloud-init:
Confirmed
Bug description:
when cloud-init writes mount entries into /etc/fstab, it adds:
x-systemd.requires=cloud-init.service
This is because a subsequent boot of cloud-init may need to remove
that entry (a new instance for example).
cloud-init has a feature where it can be disabled by:
sudo touch /etc/cloud/cloud-init.disabled
The generator for cloud-init then says that the cloud-init.target does
not need to run.
However, due to the (possibly stale) x-systemd.requires=cloud-
init.service entries, cloud-init will still run.
I think what I'd like is a:
x-systemd.after=cloud-init.service
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1667878/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
