2018-05-15 15:37:38 |
Martin Steigerwald |
bug |
|
|
added bug |
2018-05-16 10:21:32 |
Martin Steigerwald |
summary |
ds-identify caches errors |
ds-identify: fails to recognize NoCloud datasource on boot, ERROR: failed running [127]: blkid -c /dev/null -o export |
|
2018-05-16 11:41:07 |
Martin Steigerwald |
summary |
ds-identify: fails to recognize NoCloud datasource on boot, ERROR: failed running [127]: blkid -c /dev/null -o export |
ds-identify: fails to recognize NoCloud datasource on boot cause it does not have /sbin in $PATH and thus does not find blkid |
|
2018-05-16 12:02:45 |
Martin Steigerwald |
bug watch added |
|
https://bugzilla.opensuse.org/show_bug.cgi?id=1093501 |
|
2018-05-16 12:02:45 |
Martin Steigerwald |
bug task added |
|
cloud-init (openSUSE) |
|
2018-05-16 12:23:30 |
Bug Watch Updater |
cloud-init (openSUSE): status |
Unknown |
Confirmed |
|
2018-05-16 12:23:30 |
Bug Watch Updater |
cloud-init (openSUSE): importance |
Unknown |
Medium |
|
2018-05-17 12:43:33 |
Bug Watch Updater |
cloud-init (openSUSE): status |
Confirmed |
Fix Released |
|
2018-05-17 20:05:07 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345786 |
|
2018-05-18 13:39:47 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
2018-05-18 13:39:49 |
Scott Moser |
cloud-init: importance |
Undecided |
Low |
|
2018-05-22 14:11:10 |
Scott Moser |
cloud-init: status |
Confirmed |
Fix Committed |
|
2018-05-22 14:13:34 |
Bug Watch Updater |
cloud-init (openSUSE): status |
Fix Released |
Confirmed |
|
2018-05-23 15:03:28 |
Bug Watch Updater |
cloud-init (openSUSE): status |
Confirmed |
Fix Released |
|
2018-06-20 18:06:00 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
2018-09-11 19:44:29 |
Scott Moser |
description |
cloud-init 18.2 from http://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP3/ on SLES 12 SP 3 with NoCloud data source via Cloud Init drive made by Proxmox.
On SLES 12 SP3 NoCloud data source was not working, despite
slestemplate:~ # blkid -c /dev/null -o export
[…]
DEVNAME=/dev/sr0
UUID=2018-05-15-16-34-27-00
LABEL=cidata
TYPE=iso9660
[…]
with necessary files on it. blkid gives 0 as returncode
Why?
I only kept parts of the output:
slestemplate:/etc/cloud # cat /run/cloud-init/ds-identify.log
[up 8.63s] ds-identify
policy loaded: mode=search report=false found=all maybe=all notfound=disabled
no datasource_list found, using default: MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack DigitalOcean AliYun Ec2 GCE OpenNebula OpenStack OVF SmartOS Scaleway Hetzner IBMCloud
ERROR: failed running [127]: blkid -c /dev/null -o export
[…]
FS_LABELS=unavailable:error
ISO9660_DEVS=unavailable:error
It might have been that I did not yet add the CloudInit drive in Proxmox yet.
A subsequent call to
slestemplate:~ # /usr/lib/cloud-init/ds-identify
did not yet yield a different result.
Only by analysing the source I found that it caches results and I can use the `--force` option to override this. I did this and the NoCloud datasource got detected properly. Apparently this is cached now.
The tool would only inform of the caching as a DEBUG message. However I set logging to INFO for all parts of Cloud Init as the FileHandler clutters the log with tons of messages how many bytes it read from each file. Sure, I could use INFO only for FileHandler.
Several issues reduce the ease of administration here:
1. Don´t cache errors. Really… just… don´t.
2. Don´t cache errors almost *silently* (just as a debug message).
3. Decide wisely what is a debug message and what is not.
4. A search for `ds-identify` in the documentation available at https://cloudinit.readthedocs.io/en/latest/ did not yield any result.
5. And in general: Keep it short and simple.
IMHO the first is the most important: Don´t cache errors. If the resource now is there, recognize it, without further discussion. |
cloud-init 18.2 from http://download.opensuse.org/repositories/Cloud:/Tools/SLE_12_SP3/ on SLES 12 SP 3 with NoCloud data source via Cloud Init drive made by Proxmox.
On SLES 12 SP3 NoCloud data source was not working, despite
slestemplate:~ # blkid -c /dev/null -o export
[…]
DEVNAME=/dev/sr0
UUID=2018-05-15-16-34-27-00
LABEL=cidata
TYPE=iso9660
[…]
with necessary files on it. blkid gives 0 as returncode
Why?
I only kept parts of the output:
slestemplate:/etc/cloud # cat /run/cloud-init/ds-identify.log
[up 8.63s] ds-identify
policy loaded: mode=search report=false found=all maybe=all notfound=disabled
no datasource_list found, using default: MAAS ConfigDrive NoCloud AltCloud Azure Bigstep CloudSigma CloudStack DigitalOcean AliYun Ec2 GCE OpenNebula OpenStack OVF SmartOS Scaleway Hetzner IBMCloud
ERROR: failed running [127]: blkid -c /dev/null -o export
[…]
FS_LABELS=unavailable:error
ISO9660_DEVS=unavailable:error
It might have been that I did not yet add the CloudInit drive in Proxmox yet.
A subsequent call to
slestemplate:~ # /usr/lib/cloud-init/ds-identify
did not yet yield a different result.
Only by analysing the source I found that it caches results and I can use the `--force` option to override this. I did this and the NoCloud datasource got detected properly. Apparently this is cached now.
The tool would only inform of the caching as a DEBUG message. However I set logging to INFO for all parts of Cloud Init as the FileHandler clutters the log with tons of messages how many bytes it read from each file. Sure, I could use INFO only for FileHandler.
Several issues reduce the ease of administration here:
1. Don´t cache errors. Really… just… don´t.
2. Don´t cache errors almost *silently* (just as a debug message).
3. Decide wisely what is a debug message and what is not.
4. A search for `ds-identify` in the documentation available at https://cloudinit.readthedocs.io/en/latest/ did not yield any result.
5. And in general: Keep it short and simple.
IMHO the first is the most important: Don´t cache errors. If the resource now is there, recognize it, without further discussion.
Related bugs:
* bug 1791691: [systemd] PATH broken in systemd units |
|
2023-05-11 13:56:15 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/3182 |
|