Comment 2 for bug 2045086

Thanks, Heinrich, for reporting this and making cloud-init better.

I can confirm this is reproducible in noble. Those warnings are not hard errors and apt works correctly, but having two sources of config could lead to conflicts / unexpected behavior / hard apt errors in the future. In addition to that, the warnings could be a concern for users, so I think this is a bug that has to be fixed.

cloud-init upstream bug: https://github.com/canonical/cloud-init/issues/4691