All devstack-tempest jobs are failing due to 'gabbi_tempest_path' is undefined

Bug #1821072 reported by Ghanshyam Mann on 2019-03-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ghanshyam Mann

Bug Description

devstack-tempest job has the gabbi_tempest_path var set for gabbit-tempest plugin[1]. Which is only set by the gabbit-tempest plugin jobs[2].

With new ansible version 2.7, all jobs derived from devstack-tempest fail due to undefined var.



The field 'environment' has an invalid value, which includes an undefined variable. The error was: 'gabbi_tempest_path' is undefined

The error appears to have been in '/var/lib/zuul/builds/d500cd5dcb3a42e68e9219abe2a5bb4d/untrusted/project_5/': line 1, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: Set tempest as owner of Tempest run folder
  ^ here

Ghanshyam Mann (ghanshyammann) wrote :

workaround has been merged for this bug to unblock the gate -

But we need to move this var to gabbi-tempest plugin jobs side which is the only place it is being used. This var is specific to gabbi-tempest not used for any other devstack-tempest jobs so defining it in devstack-tempest base job is not the correct way. We might face such issue again in future which can end up blocking all gate jobs.

Changed in tempest:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ghanshyam Mann (ghanshyammann)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers