tempest-dsvm jobs don't pull required projects from source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
BaGPipe |
New
|
Undecided
|
Unassigned | ||
Tricircle |
New
|
Undecided
|
Unassigned | ||
networking-bgpvpn |
New
|
Undecided
|
Unassigned |
Bug Description
The failures of the legacy-
However this use of neutron.db.api was removed in sfc with [3].
That said it doesn't appear these legacy jobs are pulling the dependencies from source for devstack. I chatted with the infra team [4] and they recommend that these legacy jobs [5][6] for bagpipe be migrated to zuul v3 format.
There's a migration guide for that [7] and as much as I might be willing to help, this is a bit beyond my current scope for bagpipe.
[1] https:/
[2] http://
[3] https:/
[4] http://
[5] https:/
[6] https:/
[7] https:/
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)