DNS service not working for System VMs on a fresh new install Cloudstack
- 主要言語
- Java
- スター
- 3.1k
- フォーク
- 1.4k
- 平均マージ
- 6日 19時間
- マージ済み PR(30日)
- 32
説明
##### ISSUE TYPE
* Other
##### COMPONENT NAME
~~~
UI, System VMs
~~~
##### CLOUDSTACK VERSION
~~~
CloudStack 4.18
~~~
##### CONFIGURATION
Zone with default Advanced networking with Isolation method as VLAN
Zone has only one "Physical Network 1" with all traffic types Guest, Management, Public, Storage passing through it
KVM
Management Server and KVM Host are same. Its a testing environment
OpenVswitch and DPDK enabled and created bridge interface using OpenVswitch commands
Primany and Secondary with NFS mount points
##### OS / ENVIRONMENT
Ubuntu 22.04.2 LTS
Codename: jammy
##### SUMMARY
The System VMs Agent state is not Up
##### STEPS TO REPRODUCE
~~~
Install a fresh new Ubuntu 22.04 LTS server
Enable OpenVswitch and dpdk over the interface and create bridge interface
Perform the install of cloudstack on a server. Also make this server as KVM Host.
Configure Cloudstack as zone with default advanced networking
Zone has only one "Physical Network 1" with all traffic types Guest, Management, Public, Storage
passing through it
~~~
##### EXPECTED RESULTS
~~~
The System VMs Agent state is OK
~~~
##### ACTUAL RESULTS
~~~
After the Cloudstack install and basic configuration of zone,
Go system vms section, we notice the state is "running" but the Agent state is not "OK"
Accessed one of the system vm using commands like ssh -i /root/.ssh/id_rsa.cloud -p 3922 root@link-local
Issued command /usr/local/cloud/systemvm/ssvm-check.sh
Noticed error ERROR: DNS not resolving cloudstack.apache.org
Confirmed Google DNS server is there at resolv.conf
Checked the service cloud status and noticed the system vm can't communicate with port 8250 of management server
over the management server IP
Further troubleshooting shows from inside system vm, only able to ping management server IP
but no connection with any active ports of management server like ssh port , management ports like 8250 etc
While checking the traffic over the bridge interface using ovs-tcpdump , we have noticed the
incoming traffic from system vms towards bridge interface are reaching but no outgoing response
towards system vms. Below is a sample captured traffic at bridge interface over
cloudstack port number 8250. We believe that we setup the openvswitch dpdk setup correctly
and not sure what we are missing from our side.
12:08:52.312394 IP SVMIP.33940 > MGMTIP.8250: Flags [S], seq 3467199111, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
<.............E..4\.@.@.....?...?... :..B.........................
12:08:53.314315 IP SVMIP.33940 > MGMTIP..8250: Flags [S], seq 3467199111, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
issued the command "ovs-ofctl dump-flows cloudbr0" and got below result. Looks like the rule is fine
cookie=0x0, duration=148279.131s, table=0, n_packets=7453119, n_bytes=2575374706, priority=0 actions=NORMAL
Not sure what we are missing.
~~~
コントリビューションガイド
調査の方向性
System VM のエントリポイント `ssvm-check.sh` から開始し、説明されている Ubuntu 22.04、KVM、Open vSwitch のセットアップで、記載されている DNS と管理サーバーのポート 8250 の障害を再現します。`cloudbr0` のトラフィックと接続経路を調査します。完了の条件は、System VM エージェントが OK であり、DNS が名前解決し、管理サーバーへの接続が応答を受け取ることです。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- linux, ubuntu
- 領域
- infrastructure, networking
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 30/100