Comment 1 for bug 1816644

Last time I checked, devstack-based josb weren't inheriting the magic behavior of required-projects, which was inherited via tox-siblings. Are we sure that simply rewriting the job as a non-legacy job would be sufficient ?

(moving to a zuulv3 job is certainly a good idea, I'm just wondering if it will be sufficient to solve this bug)