Fail to get default route device in CI jobs
Bug #1902002 reported by
Slawek Kaplonski
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Medium
|
Nate Johnston |
Bug Description
Since few days I see error like "[ERROR] /opt/stack/
Logstash query: http://
From logstash it seems that it started happening around 23 or 24 of October 2020.
I'm not sure if that is Devstack issue, it looks for me more likely like some change in the Ubuntu OS which is used on the CI nodes but I don't know exactly where to report such "infra" issue so IMHO devstack can be good starting point hopefully.
Changed in devstack: | |
assignee: | Dr. Jens Harbott (j-harbott) → Nate Johnston (nate-johnston) |
To post a comment you must log in.
Usually CI nodes should always have an IPv4 address and default route, but sometimes this seems to be broken.
I proposed a workaround in devstack to only query this when needed for linuxbridge-agent https:/ /review. opendev. org/760325, maybe one can also extend the code to check for an IPv6 default route when no v4 route is found.