Comment 2 for bug 1685043

It appears that defining "services:" as a top-level bundle definition name ends up overriding the juju model services when running through yaml definition validate tests. It also changes yaml version parsing from V3 to V4 code.

Found that changing services: top level bundle header to openstack-services: resolved the placements issue and used the standard V3 bundle parser class.

it's not "invalid yaml" so it wouldn't get picked up by lint routines, but it should be caught as a different type of exception in juju-deployer as it is a very misleading error.

Perhaps searching for "services:" (or other reserved words like overrides: or version:) at top level in any conf files (not just the first -c conf.yaml file) should be called out as an error.