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

When a CN is Down the Instances on that CN are listed as "running" #35

Open
Smithx10 opened this issue Apr 13, 2018 · 0 comments
Open

Comments

@Smithx10
Copy link

Smithx10 commented Apr 13, 2018

All these LX Branded zones are running on the CNs that are in the unknown state. I'd imagine Instances on those CNs should be also marked as unknown.

[root@headnode (bs-1) ~]# sdc-server list
HOSTNAME             UUID                                 VERSION    SETUP    STATUS      RAM  ADMIN_IP
c4-54-44-72-c3-36    0a416e76-c97b-0010-bdb3-c4544472c3fc     7.0     true   unknown   184273  10.1.101.41
headnode             7e8f2c31-2296-4446-9a68-5039c501dc21     7.0     true   running    32654  10.1.101.2
c4-54-44-72-c3-c4    a92fa576-c97b-0010-a443-c4544472c443     7.0     true   unknown   147416  10.1.101.44
c4-54-44-64-35-80    be233e0c-c67b-0010-82d4-c4544464394f     7.0     true   unknown   196568  10.1.101.43
[root@headnode (bs-1) ~]# sdc-vmadm list | grep lx
e33437f1-28bb-c6fc-f485-d8de2f9abfc9  lx              4096  running  proxy
5bfe70e7-0366-cd75-b9a2-bf3b4d62e804  lx              128   running  prom_consul_2
5e308d73-9a1e-ee2c-c905-f7b188378b42  lx              128   running  prom_consul_3
47e9d054-f627-e8c1-bb13-84e180d53c4e  lx              128   running  prom_consul_1
29c61870-f876-e852-f841-8b489dc5acd5  lx              4096  running  prom_prom_1
dfad9100-12b5-6e50-90fb-e939c28eb21b  lx              1024  running  grafana
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant