the 10.0.0.250 is a red herring - we don't know what name resolution is used when the error hits as we have no logs in those cases.
to clarify a bit because we are confusing two things here (and it is in large part my fault).
1. We DONT have actual logs from RETRY jobs. so we don't know what is in resolv.conf in those cases.
2. THe 10.0.0.250 is from successful jobs, where we've already done all the tripleo undercloud/overcloud config etc.
the 10.0.0.250 is a red herring - we don't know what name resolution is used when the error hits as we have no logs in those cases.
to clarify a bit because we are confusing two things here (and it is in large part my fault).
1. We DONT have actual logs from RETRY jobs. so we don't know what is in resolv.conf in those cases.
2. THe 10.0.0.250 is from successful jobs, where we've already done all the tripleo undercloud/ overcloud config etc.