Regression error for Operator 1.1

[Yisaer]

Bug Report

In #7920 , we want tikv provide advertise-status-addr flag.

In #7944 provide this flag but introduce an regression error with operator 1.1 ga like following.

[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:93] ["Welcome to TiKV"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Release Version:   4.1.0-alpha"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Edition:           Community"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Git Commit Hash:   446eadd9705f502d40ff90f748e04b815b0a35e4"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Git Commit Branch: master"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["UTC Build Time:    2020-06-03 02:50:24"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Rust Version:      rustc 1.44.0-nightly (b2e36e6c2 2020-04-22)"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Enable Features:   jemalloc portable sse protobuf-codec"]
[2020/06/04 02:15:22.403 +00:00] [INFO] [lib.rs:95] ["Profile:           dist_release"]
[2020/06/04 02:15:22.406 +00:00] [INFO] [mod.rs:48] ["memory limit in bytes: 128834490368, cpu cores quota: 16"]
[2020/06/04 02:15:22.406 +00:00] [WARN] [server.rs:843] ["check: kernel"] [err="kernel parameters net.core.somaxconn got 128, expect 32768"]
[2020/06/04 02:15:22.407 +00:00] [WARN] [server.rs:843] ["check: kernel"] [err="kernel parameters net.ipv4.tcp_syncookies got 1, expect 0"]
[2020/06/04 02:15:22.407 +00:00] [WARN] [server.rs:843] ["check: kernel"] [err="kernel parameters vm.swappiness got 60, expect 0"]
[2020/06/04 02:15:22.408 +00:00] [INFO] [util.rs:407] ["connecting to PD endpoint"] [endpoints=https://db-pd:2379]
[2020/06/04 02:15:22.408 +00:00] [INFO] [<unknown>] ["Disabling AF_INET6 sockets because ::1 is not available."]
[2020/06/04 02:15:22.415 +00:00] [INFO] [<unknown>] ["New connected subchannel at 0x7f6a8d018ba0 for subchannel 0x7f6a8d0a1000"]
[2020/06/04 02:15:22.417 +00:00] [INFO] [util.rs:407] ["connecting to PD endpoint"] [endpoints=https://db-pd-1.db-pd-peer.tidb1268362842659098624.svc:2379]
[2020/06/04 02:15:22.466 +00:00] [INFO] [<unknown>] ["New connected subchannel at 0x7f6a8d019650 for subchannel 0x7f6a8d0a1380"]
[2020/06/04 02:15:22.468 +00:00] [INFO] [util.rs:407] ["connecting to PD endpoint"] [endpoints=https://db-pd-0.db-pd-peer.tidb1268362842659098624.svc:2379]
[2020/06/04 02:15:22.480 +00:00] [INFO] [<unknown>] ["New connected subchannel at 0x7f6a8d01a340 for subchannel 0x7f6a8d0a1540"]
[2020/06/04 02:15:22.481 +00:00] [INFO] [util.rs:472] ["connected to PD leader"] [endpoints=https://db-pd-0.db-pd-peer.tidb1268362842659098624.svc:2379]
[2020/06/04 02:15:22.481 +00:00] [INFO] [util.rs:395] ["all PD endpoints are consistent"] [endpoints="[\"https://db-pd:2379\"]"]
[2020/06/04 02:15:22.481 +00:00] [INFO] [server.rs:242] ["connect to PD cluster"] [cluster_id=6834308959592489949]
[2020/06/04 02:15:22.481 +00:00] [INFO] [config.rs:1726] ["readpool.storage.use-unified-pool is not set, set to false by default"]
[2020/06/04 02:15:22.482 +00:00] [INFO] [config.rs:1769] ["readpool.coprocessor.use-unified-pool is not set, set to true by default"]
[2020/06/04 02:15:22.482 +00:00] [INFO] [config.rs:202] ["no advertise-status-addr is specified, falling back to status-addr"] [status-addr=0.0.0.0:20180]
[2020/06/04 02:15:22.482 +00:00] [FATAL] [setup.rs:204] ["invalid configuration: \"[src/server/config.rs:209]: invalid advertise-status-addr: \\\"0.0.0.0:20180\\\"\""]

What did you expect?

Nightly Tikv could still start and work with Operator 1.1 ga with setting status-addr as wildcard address.

What did happened?

Operator 1.1 ga couldn't work with Nightly tikv.

[Yisaer]

@overvenus @NingLin-P PTAL

[mahjonp]

We have met the same problem on Tipocket: pingcap/tipocket#265

[NingLin-P]

Thanks for the report, #8016 will fix it.