Openstack Cloud-init 沒有為實例分配正確的網絡接口

Question

我有一個 Openstack 安裝，其中最近一些實例無法匹配附加到它們的虛擬接口，並且似乎正在嘗試將舊分配的 mac 鏈接到相同的 ip 但在某些時候從網絡維護中刪除並由 dhcp 重新生成（我在表格中看到“無法重命名 mac”）。

我試圖了解什么時候以及什么元數據服務 cloud-init 要求 ip-mac 對其進行配置，以及是否有某種緩存可以刪除以刷新實例。

任何想法？ 有一種方法可以恢復我自己提供的特定 IP 並清潔中子？

[   17.414605] cloud-init[627]: Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'init-local' at Tue, 11 Jan 2022 17:11:50 +0000. Up 17.05 seconds.
[   17.419674] cloud-init[627]: 2022-01-11 17:11:50,714 - stages.py[WARNING]: Failed to rename devices: [nic not present] Cannot rename mac=fa:16:3e:5f:c5:a3 to ens3, not available.
[[0;32m  OK  [0m] Finished [0;1;39mInitial cloud-init job (pre-networking)[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mNetwork (Pre)[0m.
         Starting [0;1;39mNetwork Service[0m...
[[0;32m  OK  [0m] Started [0;1;39mNetwork Service[0m.
         Starting [0;1;39mWait for Network to be Configured[0m...
         Starting [0;1;39mNetwork Name Resolution[0m...
[[0;32m  OK  [0m] Finished [0;1;39mWait for Network to be Configured[0m.
         Starting [0;1;39mInitial cloud-ini��� (metadata service crawler)[0m...
[[0;32m  OK  [0m] Started [0;1;39mNetwork Name Resolution[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mNetwork[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mHost and Network Name Lookups[0m.
[   18.702674] cloud-init[638]: Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'init' at Tue, 11 Jan 2022 17:11:51 +0000. Up 18.50 seconds.
[   18.706923] cloud-init[638]: ci-info: +++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
[   18.710320] cloud-init[638]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[   18.713541] cloud-init[638]: ci-info: | Device |   Up  |  Address  |    Mask   | Scope |     Hw-Address    |
[   18.716788] cloud-init[638]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[   18.719333] cloud-init[638]: ci-info: |  ens3  | False |     .     |     .     |   .   | fa:16:3e:db:2c:9b |
[   18.722036] cloud-init[638]: ci-info: |   lo   |  True | 127.0.0.1 | 255.0.0.0 |  host |         .         |
[   18.725660] cloud-init[638]: ci-info: |   lo   |  True |  ::1/128  |     .     |  host |         .         |
[   18.728025] cloud-init[638]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[   18.730341] cloud-init[638]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
[   18.732360] cloud-init[638]: ci-info: +-------+-------------+---------+-----------+-------+
[   18.734362] cloud-init[638]: ci-info: | Route | Destination | Gateway | Interface | Flags |
[   18.737230] cloud-init[638]: ci-info: +-------+-------------+---------+-----------+-------+
[   18.739237] cloud-init[638]: ci-info: +-------+-------------+---------+-----------+-------+
[   18.742121] cloud-init[638]: 2022-01-11 17:11:52,003 - stages.py[WARNING]: Failed to rename devices: [nic not present] Cannot rename mac=fa:16:3e:5f:c5:a3 to ens3, not available.
[[0;32m  OK  [0m] Finished [0;1;39mInitial cloud-ini���ob (metadata service crawler)[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mCloud-config availability[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mNetwork is Online[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSystem Initialization[0m.

Answer 1

我回答自己，以防將來對某人有所幫助。 元數據服務似乎不能很好地覆蓋來自 cloud-init 的配置，盡管在 cloud-init 日志中可以看到它恢復了 http://controller:8775/openstack/2016-10-06/network_data.json ...無論如何，為了解決這個問題，我只是安裝了磁盤並使用預期的 MAC 直接編輯 /mnt/atos-docker/etc/netplan/50-cloud-init.yaml 然后正確綁定。