=== meena3 is now known as meena === cpaelzer__ is now known as cpaelzer [05:48] 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] analysis cloud-init]# cat /etc/cloud/ds-identify.cfg policy: search,found=all,maybe=all,notfound=disabled [05:49] And again this is on power hardware JFYI === cpaelzer__ is now known as cpaelzer === hjensas|afk is now known as hjensas [13:28] vijayendra: i suspect that the issue is 'maybe=all'. [13:29] on non-intel hardware, platforms like openstack do not identify themselves in any way. === smoser1 is now known as smoser [13:31] so ds-identify will return a 'maybe' [13:34] https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid [13:34] https://bugs.launchpad.net/cloud-init/+bug/1663304 [13:34] Ubuntu bug 1663304 in cloud-init "identify openstack kvm platform on arm64" [Medium,Confirmed] [13:35] 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] Ec2 when explicitly configured to set 'strict_id=true' (default is false) [13:41] OpenStack on non-intel. [13:50] smoser, ok got it. is there way non ec2(non intel) can avoid this? like openstack power platform? [13:51] I mean do you suggest any change in this ---> policy: search,found=all,maybe=all,notfound=disabled [13:59] smoser, let me go over the defect shared and come back to you [14:03] smoser, No ds found [mode=search, notfound=disabled]. Disabled cloud-init [1] [14:04] In that case ds-identify.log shouldn't say above line right [14:04] here its getting disabled as per log but cloud-init is continues to be running