Skip to content
New issue

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

[BUG] 宿主机注册失败,注册时去找虚拟机的子网 #21416

Open
nashzosi opened this issue Oct 16, 2024 · 2 comments
Open

[BUG] 宿主机注册失败,注册时去找虚拟机的子网 #21416

nashzosi opened this issue Oct 16, 2024 · 2 comments
Labels

Comments

@nashzosi
Copy link

nashzosi commented Oct 16, 2024

问题描述/What happened:
主机没有正常关联到IP,导致default-host-xxxx 启动失败,实际上包含这个IP的子网有两个,物理机类型、虚拟机类型各一个,删除虚拟机类型网络后,启动正常。

image

环境/Environment:
3.11.8

  • OS (e.g. cat /etc/os-release):
    openEuler 22.03 (LTS-SP3)
  • Kernel (e.g. 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
  • Host: (e.g. 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
  • Service Version (e.g. 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) |
    +---------------+--------------------------------------------+
@nashzosi nashzosi added the bug Something isn't working label Oct 16, 2024
@zexi zexi changed the title [BUG] [BUG] 物理机注册失败,物理机不应该去找虚拟机的子网的 Oct 16, 2024
@zexi zexi changed the title [BUG] 物理机注册失败,物理机不应该去找虚拟机的子网的 [BUG] 宿主机注册失败,注册时去找虚拟机的子网 Oct 16, 2024
@zexi
Copy link
Member

zexi commented Oct 18, 2024

@nashzosi 理论上平台不允许在扁平网络创建两个 ip 重合的子网,你是怎么创建出来的?

@nashzosi
Copy link
Author

nashzosi commented Oct 18, 2024

image

如图所示
我最近做vsphere迁移可能是其中网络有过更改导致;
我做了测试并且复现了

不同云平台的,具有两个 ip 重合的IP子网,可以成功更换两个子网的二层网络,应该是更换时候并没有校验现存网络的ip是否会重合

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants