мне не понятно, зачем он желая что-то получить с локалхоста, лезет на проксю

или я не понял что происходит

вроде и то что выше обошел

но это нормально что деплой уже 40 минут висит на TASK [migrate liftbridge partitions]

?

Нет

Ребята научите мак адреса собирать в базу

systemctl status liftbridge покажи пожал.
systemctl status nats-server

liftbridge.service - Liftbridge service
  Loaded: loaded (/lib/systemd/system/liftbridge.service; enabled; vendor preset: enabled)
  Active: active (running) since Fri 2021-08-27 05:56:33 UTC; 11h ago
Main PID: 8320 (liftbridge)
   Tasks: 7 (limit: 2314)
  CGroup: /system.slice/liftbridge.service
          └─8320 /bin/liftbridge --config=/etc/liftbridge/liftbridge.yml

Aug 27 05:56:33 TTK_node liftbridge[8320]: time="2021-08-27 05:56:33" level=info msg="Starting Liftbridge server on 10.99.128.131:9292..."
Aug 27 05:56:33 TTK_node liftbridge[8320]: time="2021-08-27 05:56:33" level=info msg=" raft: initial configuration: index=1 servers=\"[{Suffrage:Voter ID:TTK_node Addr
Aug 27 05:56:33 TTK_node liftbridge[8320]: time="2021-08-27 05:56:33" level=info msg=" raft: entering follower state: follower=\"Node at TTK_node [Follower]\" leader=\
Aug 27 05:56:34 TTK_node liftbridge[8320]: time="2021-08-27 05:56:34" level=warning msg=" raft: heartbeat timeout reached, starting election: last-leader=\n"
Aug 27 05:56:34 TTK_node liftbridge[8320]: time="2021-08-27 05:56:34" level=info msg=" raft: entering candidate state: node=\"Node at TTK_node [Candidate]\" term=3\n"
Aug 27 05:56:34 TTK_node liftbridge[8320]: time="2021-08-27 05:56:34" level=info msg=" raft: election won: tally=1\n"
Aug 27 05:56:34 TTK_node liftbridge[8320]: time="2021-08-27 05:56:34" level=info msg=" raft: entering leader state: leader=\"Node at TTK_node [Leader]\"\n"
Aug 27 05:56:34 TTK_node liftbridge[8320]: time="2021-08-27 05:56:34" level=info msg="Server became metadata leader, performing leader promotion actions"
Aug 27 05:56:34 TTK_node systemd[1]: /lib/systemd/system/liftbridge.service:27: Unknown lvalue 'LimitNOFILESoft' in section 'Service'
Aug 27 06:03:36 TTK_node systemd[1]: /lib/systemd/system/liftbridge.service:27: Unknown lvalue 'LimitNOFILESoft' in section 'Service

● nats-server.service - NATS Server
  Loaded: loaded (/lib/systemd/system/nats-server.service; enabled; vendor preset: enabled)
  Active: active (running) since Fri 2021-08-27 05:56:06 UTC; 11h ago
Main PID: 7707 (nats-server)
   Tasks: 7 (limit: 2314)
  CGroup: /system.slice/nats-server.service
          └─7707 /bin/nats-server -c /etc/nats/nats-server.conf

Aug 27 05:56:06 TTK_node nats-server[7707]: Starting nats-server version 2.1.8
Aug 27 05:56:06 TTK_node nats-server[7707]: Git commit [c0b574f]
Aug 27 05:56:06 TTK_node nats-server[7707]: Listening for client connections on 10.99.128.131:4222
Aug 27 05:56:06 TTK_node nats-server[7707]: Server id is NCVGOLIVGE6DVHYMVV6TD23JHGL5SYJPFB7PEHQOXM3EIQ3YXM44DHYM
Aug 27 05:56:06 TTK_node nats-server[7707]: Server is ready
Aug 27 05:56:06 TTK_node nats-server[7707]: Listening for route connections on 10.99.128.131:4248
Aug 27 05:56:06 TTK_node nats-server[7707]: 10.99.128.131:4248 - rid:1 - Route connection created
Aug 27 05:56:06 TTK_node nats-server[7707]: 10.99.128.131:58580 - rid:2 - Route connection created
Aug 27 05:56:06 TTK_node nats-server[7707]: 10.99.128.131:58580 - rid:2 - Router connection closed: Duplicate Route
Aug 27 05:56:06 TTK_node nats-server[7707]: 10.99.128.131:4248 - rid:1 - Router connection closed: Duplicate Route

Andrey Vertiprahov pushed to noc/noc/master
Dmitry Volodin: noc-agent: Restart collectors on configuration change
Andrey Vertiprahov: Merge branch 'noc-agent-restart-collector' into 'master'

noc-agent: Restart collectors on configuration change

See merge request noc/noc!5681

✅ CI: Upload #upload docs succeeded after 595.4 sec

то есть живые?
а если руками запустить в /opt/noc
./noc migrate-liftbridge ?

я думаю понял в чем проблема

021-08-27 20:42:26,072 [noc.core.ioloop.util] Setting up asyncio event loop policy
2021-08-27 20:42:26,072 [noc.core.ioloop.util] Setting up default event loop
2021-08-27 20:42:26,197 [noc.core.dcs.base] Resolve near service liftbridge
2021-08-27 20:42:26,204 [noc.core.dcs.base] Resolved near service liftbridge to ['10.99.128.131:9292']
и вот тут он думает

/etc/environment

в no_proxy=localhost,127.0.0.0/8 добавить еще и 10.99.128.131

ага

добавил и все пошло

2021-08-27 20:43:58,104 [noc.core.ioloop.util] Setting up asyncio event loop policy
2021-08-27 20:43:58,107 [noc.core.ioloop.util] Setting up default event loop
2021-08-27 20:43:58,231 [noc.core.dcs.base] Resolve near service liftbridge
2021-08-27 20:43:58,238 [noc.core.dcs.base] Resolved near service liftbridge to ['10.99.128.131:9292']
2021-08-27 20:43:58,662 [stub] Activating stub service
2021-08-27 20:43:58,662 [stub] Starting IOLoop
2021-08-27 20:43:58,663 [noc.core.dcs.base] Attempting to get slot
2021-08-27 20:43:58,667 [noc.core.dcs.base] Attempting to get slot
2021-08-27 20:43:58,671 [noc.core.dcs.base] [mongo] Starting resolver (near=False)
2021-08-27 20:43:58,675 [noc.core.dcs.base] [mongo] Set active services to: mongo: 10.99.128.131:27017
2021-08-27 20:43:58,675 [noc.core.dcs.base] [mongo] Stopping resolver
2021-08-27 20:43:58,677 [noc.core.mongo.connection] Connecting to MongoDB {'db': 'noc', 'username': 'noc', 'password': '********', 'authentication_source': 'noc', 'replicaSet': 'noc', 'readPreference': 'secondaryPreferred', 'maxIdleTimeMS': 60000, 'host': 'mongodb://noc:********@10.99.128.131:27017/noc'}
2021-08-27 20:43:58,719 [noc.core.dcs.base] Attempting to get slot
2021-08-27 20:43:58,724 [noc.core.dcs.base] Attempting to get slot
Ensuring stream events.default
Creating stream events.default with 2 partitions
CHANGED

а, у тебя прокся в системе вбита, да