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] 虚拟机重启后, EIP 和 私有地址都无法访问。 #19818

Closed
khw934 opened this issue Mar 27, 2024 · 3 comments
Closed

[BUG] 虚拟机重启后, EIP 和 私有地址都无法访问。 #19818

khw934 opened this issue Mar 27, 2024 · 3 comments
Labels

Comments

@khw934
Copy link

khw934 commented Mar 27, 2024

问题描述/What happened:
虚拟机重启后, EIP 和 私有地址都无法访问。
环境/Environment:

  • OS (e.g. cat /etc/os-release):

  • Kernel (e.g. uname -a):
    [root@centosbase ~]# uname -a
    Linux centosbase 5.4.130-1.yn20230805.el7.x86_64 scheduler: fix specified network not enough still pass. #1 SMP Wed Oct 11 03:26:01 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
    [root@centosbase ~]#

  • Host: (e.g. dmidecode | egrep -i 'manufacturer|product' |sort -u)

[root@centosbase ~]# dmidecode | egrep -i 'manufacturer|product' |sort -u
Manufacturer: QEMU
Product Name: Standard PC (i440FX + PIIX, 1996)
[root@centosbase ~]#

  • Service Version (e.g. kubectl exec -n onecloud $(kubectl get pods -n onecloud | grep climc | awk '{print $1}') -- climc version-list):

image

@khw934 khw934 added the bug Something isn't working label Mar 27, 2024
@wanyaoqi
Copy link
Member

@khw934 看下 vpcagent是否有报错,重启一下 vpcagent试试。

@wanyaoqi
Copy link
Member

如果是vpcagent的问题的话,近期已经修复了

@github-actions github-actions bot added the stale label Apr 29, 2024
Copy link

github-actions bot commented May 6, 2024

If you do not provide feedback for more than 37 days, we will close the issue and you can either reopen it or submit a new issue.

您超过 37 天未反馈信息,我们将关闭该 issue,如有需求您可以重新打开或者提交新的 issue。

@github-actions github-actions bot closed this as completed May 6, 2024
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