Invalid Bifrost ConfigDrive gateway assignment when seed SNAT is disabled
Bug #2045926 reported by
Pierre Riteau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kayobe |
Fix Released
|
Critical
|
Pierre Riteau | ||
Antelope |
Fix Released
|
Undecided
|
Unassigned | ||
Bobcat |
Fix Released
|
Critical
|
Pierre Riteau | ||
Yoga |
Fix Released
|
Undecided
|
Unassigned | ||
Zed |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When seed SNAT is disabled, the Bifrost host vars used to generate the ConfigDrive have the IPv4 gateway variable unset even if a gateway is defined on the admin network.
This is a regression in https:/
Changed in kayobe: | |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
importance: | Undecided → Critical |
assignee: | nobody → Pierre Riteau (priteau) |
Changed in kayobe: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /kayobe/ +/902113 /opendev. org/openstack/ kayobe/ commit/ 49f91043c6c3b05 49a8625baba1e6e 218eb69160
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 49f91043c6c3b05 49a8625baba1e6e 218eb69160
Author: Stig Telfer <email address hidden>
Date: Tue Nov 28 21:55:32 2023 +0000
Fix gateway assignment when seed SNAT is disabled
Fix a logic issue when seed SNAT is not enabled. In this circumstance 4cec067cd8af519 b510be04120 [1].
Bifrost was generating ConfigDrive data with the default gateway unset
even when one is available on the admin network. This regression was
introduced in Ib847d3420dee37
[1] https:/ /review. opendev. org/c/openstack /kayobe/ +/898434
Closes-Bug: #2045926 448fc91dba74f8f 09595698b55
Change-Id: Ifd9f9cd389ac09