[05:48] <vijayendra> rharper, smoser1 I need a help on one of the issue I am facing on RHEL 8.1 env with cloudinit 18.5. I have ds-identify.cfg set as below(notfound=disabled), When no datasource is found ideally cloudinit suppose get disabled but what I see on my env is cloudinit continues to run and configures fallback network dhcp. Just trying to understand if I am missing something here? Do you any scenario where ds-identify.cfg is not honoured ? [root@rhel-26-
[05:48] <vijayendra> analysis cloud-init]# cat /etc/cloud/ds-identify.cfg policy: search,found=all,maybe=all,notfound=disabled
[05:49] <vijayendra> And again this is on power hardware JFYI
[13:28] <smoser1> vijayendra: i suspect that the issue is 'maybe=all'.
[13:29] <smoser1> on non-intel hardware, platforms like openstack do not identify themselves in any way.
[13:31] <smoser> so ds-identify will return a 'maybe'
[13:34] <smoser> https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid
[13:34] <smoser> https://bugs.launchpad.net/cloud-init/+bug/1663304
[13:35] <smoser> ds-identify returns maybe in very few cases. "AltCloud" , i'd suggest disabling that datasource... we should probably just rip it out of cloud-init.
[13:36] <smoser> Ec2 when explicitly configured to set 'strict_id=true' (default is false)
[13:41] <smoser> OpenStack on non-intel.
[13:50] <vijayendra> smoser, ok got it. is there way non ec2(non intel) can avoid this? like openstack power platform?
[13:51] <vijayendra> I mean do you suggest any change in this ---> policy: search,found=all,maybe=all,notfound=disabled
[13:59] <vijayendra> smoser, let me go over the defect shared and come back to you
[14:03] <vijayendra> smoser, No ds found [mode=search, notfound=disabled]. Disabled cloud-init [1]
[14:04] <vijayendra> In that case ds-identify.log shouldn't say above line right
[14:04] <vijayendra> here its getting disabled as per log but cloud-init is continues to be running