[BUG] "trident-type-for-unkonw-vtap" in legacy agent documentation

[Unprincess17]

Search before asking

• [X] I had searched in the issues and found no similar feature requirement.

DeepFlow Component

Docs

What you expected to happen

There is a typo in legacy server documentation:

configmap:
  server.yaml:
    controller:
      genesis:
        local_ip_ranges:
          - 10.0.0.0/8
          - 172.16.0.0/12
          - 192.168.0.0/16
          - 169.254.0.0/15
          - 224.0.0.0-240.255.255.255
          - 100.42.32.0/24 # FIXME
      trisolaris:
        trident-type-for-unkonw-vtap: 3 # required

The trident-type-for-unkonw-vtap should be trident-type-for-unknow-vtap

$ grep trident-type server.log
  trident-type-for-unknow-vtap: 3

How to reproduce

https://deepflow.io/docs/ce-install/legacy-host/

DeepFlow version

Name: deepflow-server community edition Branch: v6.6.6 CommitID: d5e26dd2618cf3dbac2c10594d06d75aab3a38e1 RevCount: 11227 Compiler: go version go1.21.13 linux/amd64 CompileTime: 2024-10-11 05:20:20

DeepFlow agent list

No response

Kubernetes CNI

No response

Operation-System/Kernel version

No response

Anything else

No response

Are you willing to submit a PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[LeoDemoniac]

this config change can cause agent register in server error. In server.log [WARN] [cloud] cloud.go:343 get cloud (test) data, verify is (false), error state (4), error message (invalid vm count (0).) [ERRO] [trisolaris.vtap] vtap_discovery.go:230 failed to register agent(10.19.15.8-32:40:32:96:8e:c3) by querying DB table host_device(ip in ([10.19.15.8])) without finding data, err:record not found In legacy-host, change the trident-type-for-unkonw-vtap to trident-type-for-unknow-vtap will be normal

[1473371932]

this config change can cause agent register in server error. In server.log [WARN] [cloud] cloud.go:343 get cloud (test) data, verify is (false), error state (4), error message (invalid vm count (0).) [ERRO] [trisolaris.vtap] vtap_discovery.go:230 failed to register agent(10.19.15.8-32:40:32:96:8e:c3) by querying DB table host_device(ip in ([10.19.15.8])) without finding data, err:record not found In legacy-host, change the trident-type-for-unkonw-vtap to trident-type-for-unknow-vtap will be normal

Hi, in the subsequent v6.6.6 release, we have made these two parameters compatible, so as to avoid agent registration failures after upgrading for those who have used the previous version