Kayobe overcloud provision wait_active_timeout doesn't work

Bug #2049964 reported by Martin Ananda Boeker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kayobe
Triaged
Medium
Unassigned

Bug Description

Using kayobe 14.1.

If you run "kayobe overcloud provision -e wait_active_timeout=1200" you always get this error:

Unexpected templating type error occurred on ({{ wait_active_timeout // wait_active_interval }}): unsupported operand type(s) for //: ''str'' and ''int''. unsupported operand type(s) for //: ''str'' and ''int''

Setting "kayobe overcloud provision -e wait_ssh_timeout=1200" works fine, but I would like to set both.

Revision history for this message
Will Szumski (willjs) wrote :

I wonder if we can fix this one by using the int filter e.g `wait_ssh_timeout | int`?

Will Szumski (willjs)
Changed in kayobe:
importance: Undecided → Medium
Will Szumski (willjs)
Changed in kayobe:
status: New → Triaged
Revision history for this message
Martin Ananda Boeker (mboeker) wrote :

That should work, or instead of doing fancy math in venvs/kayobe/share/kayobe/ansible/*-*provision.yml:

retries: "{{ wait_active_timeout // wait_active_interval }}"

just have those timeouts work the traditional way.

I see in overcloud-hardware-inspect (and only in that one) you already set int:

retries: "{{ wait_inspected_timeout | int // wait_inspected_interval | int }}"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.