We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
问题描述/What happened: 主机没有正常关联到IP,导致default-host-xxxx 启动失败,实际上包含这个IP的子网有两个,物理机类型、虚拟机类型各一个,删除虚拟机类型网络后,启动正常。
环境/Environment: 3.11.8
cat /etc/os-release
uname -a
dmidecode | egrep -i 'manufacturer|product' |sort -u
kubectl exec -n onecloud $(kubectl get pods -n onecloud | grep climc | awk '{print $1}') -- climc version-list
The text was updated successfully, but these errors were encountered:
@nashzosi 理论上平台不允许在扁平网络创建两个 ip 重合的子网,你是怎么创建出来的?
Sorry, something went wrong.
如图所示 我最近做vsphere迁移可能是其中网络有过更改导致; 我做了测试并且复现了
不同云平台的,具有两个 ip 重合的IP子网,可以成功更换两个子网的二层网络,应该是更换时候并没有校验现存网络的ip是否会重合
No branches or pull requests
问题描述/What happened:
主机没有正常关联到IP,导致default-host-xxxx 启动失败,实际上包含这个IP的子网有两个,物理机类型、虚拟机类型各一个,删除虚拟机类型网络后,启动正常。
环境/Environment:
3.11.8
cat /etc/os-release
):openEuler 22.03 (LTS-SP3)
uname -a
):Linux Node63Primary 5.10.0-182.0.0.95.oe2203sp3.aarch64 scheduler: fix specified network not enough still pass. #1 SMP Sat Dec 30 13:16:24 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
dmidecode | egrep -i 'manufacturer|product' |sort -u
)Manufacturer: HiSilicon
Manufacturer: HUAWEI
Manufacturer: Hynix
Manufacturer: PowerLeader
Memory Subsystem Controller Manufacturer ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Module Manufacturer ID: Unknown
Module Product ID: Unknown
Product Name: BC82AMDYA
Product Name: PR210K
kubectl exec -n onecloud $(kubectl get pods -n onecloud | grep climc | awk '{print $1}') -- climc version-list
):+---------------+--------------------------------------------+
| Field | Value |
+---------------+--------------------------------------------+
| ansible | release/3.11.8(2c25b737c924101412) |
| apimap | release/3.11.8(2c25b737c924101412) |
| cloudevent | release/3.11.8(2c25b737c924101412) |
| cloudid | release/3.11.8(2c25b737c924101412) |
| cloudmon | release/3.11.8(2c25b737c924101412) |
| cloudproxy | release/3.11.8(2c25b737c924101412) |
| compute_v2 | release/3.11.8(2c25b737c924101412) |
| devtool | release/3.11.8(2c25b737c924101412) |
| identity | release/3.11.8(2c25b737c924101412) |
| image | release/3.11.8(2c25b737c924101412) |
| k8s | heads/v3.11.8-20241013.0(28e38d5b24101411) |
| log | release/3.11.8(2c25b737c924101412) |
| monitor | release/3.11.8(2c25b737c924101412) |
| notify | release/3.11.8(2c25b737c924101412) |
| scheduledtask | release/3.11.8(2c25b737c924101412) |
| scheduler | release/3.11.8(2c25b737c924101412) |
| vpcagent | release/3.11.8(2c25b737c924101412) |
| webconsole | release/3.11.8(2c25b737c924101412) |
| yunionconf | release/3.11.8(2c25b737c924101412) |
+---------------+--------------------------------------------+
The text was updated successfully, but these errors were encountered: