The spike may be related to jenkins01 crashing. If it reused any slave nodes when it came back up (because nodepool didn't get the appropriate events due to jenkins crashing) then keystone could have been running on those nodes preventing it from starting when the second jobs ran.
The spike may be related to jenkins01 crashing. If it reused any slave nodes when it came back up (because nodepool didn't get the appropriate events due to jenkins crashing) then keystone could have been running on those nodes preventing it from starting when the second jobs ran.