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.

Sign up for GitHub

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

Jump to bottom

Services are not running when bringing up node after shutdown in B-series cluster #169

Open
pradvara opened this issue Aug 5, 2016 · 0 comments
Open

Services are not running when bringing up node after shutdown in B-series cluster #169

pradvara opened this issue Aug 5, 2016 · 0 comments

Comments

@pradvara
Copy link

pradvara commented Aug 5, 2016

Steps to reproduce:

Add nodes to cluster

[stack@contiv-b1 ~]$ clusterctl nodes get | grep " status"
contiv-b1-FCH1702J22M: status: Allocated
contiv-b2-FCH1701J2KV: status: Allocated
contiv-b3-FCH1828KBGQ: status: Allocated
contiv-b4-FCH1811JLXV: status: Allocated
contiv-b5-FCH1834JF2M: status: Allocated
contiv-b6-FCH1811JD9C: status: Allocated

Shutdown a node:

[stack@contiv-b1 ~]$ clusterctl node get contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: Inventory State
contiv-b5-FCH1834JF2M: name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: prev_state: Discovered
contiv-b5-FCH1834JF2M: prev_status: Allocated
contiv-b5-FCH1834JF2M: state: Disappeared
contiv-b5-FCH1834JF2M: status: Allocated
contiv-b5-FCH1834JF2M: Monitoring State
contiv-b5-FCH1834JF2M: label: contiv-b5
contiv-b5-FCH1834JF2M: management_address: 10.106.240.109
contiv-b5-FCH1834JF2M: serial_number: FCH1834JF2M
contiv-b5-FCH1834JF2M: Configuration State
contiv-b5-FCH1834JF2M: host_group: service-worker
contiv-b5-FCH1834JF2M: inventory_name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: inventory_vars:
contiv-b5-FCH1834JF2M: node_addr: 10.106.240.109
contiv-b5-FCH1834JF2M: node_name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: ssh_address: 10.106.240.109

The state of the node moves to "Disappeared"

Bring up the node again

[stack@contiv-b1 ~]$ clusterctl node get contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: Inventory State
contiv-b5-FCH1834JF2M: name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: prev_state: Disappeared
contiv-b5-FCH1834JF2M: prev_status: Allocated
contiv-b5-FCH1834JF2M: state: Discovered
contiv-b5-FCH1834JF2M: status: Allocated
contiv-b5-FCH1834JF2M: Monitoring State
contiv-b5-FCH1834JF2M: label: contiv-b5
contiv-b5-FCH1834JF2M: management_address: 10.106.240.109
contiv-b5-FCH1834JF2M: serial_number: FCH1834JF2M
contiv-b5-FCH1834JF2M: Configuration State
contiv-b5-FCH1834JF2M: host_group: service-worker
contiv-b5-FCH1834JF2M: inventory_name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: inventory_vars:
contiv-b5-FCH1834JF2M: node_addr: 10.106.240.109
contiv-b5-FCH1834JF2M: node_name: contiv-b5-FCH1834JF2M
contiv-b5-FCH1834JF2M: ssh_address: 10.106.240.109

The state is Discovered, and status is allocated.

Check wheather services are running in node

[stack@contiv-b5 ~]$ ps -ef | grep netplugin
stack 2992 2785 0 15:50 pts/0 00:00:00 grep --color=auto netplugin

[stack@contiv-b5 ~]$ systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/docker.service.d
└─env.conf
Active: inactive (dead)
Docs: https://docs.docker.com

[stack@contiv-b5 ~]$ sudo systemctl status etcd
● etcd.service - Etcd
Loaded: loaded (/etc/systemd/system/etcd.service; static; vendor preset: disabled)
Active: inactive (dead)

Services are not running, but the status is allocated
@pradvara pradvara changed the title Services are not running when bringing up node after shutdown. Services are not running when bringing up node after shutdown in B-series cluster Aug 5, 2016
mapuri added a commit to mapuri/cluster that referenced this issue Sep 9, 2016
@mapuri
Squashed 'vendor/ansible/' changes from 89f9ea1..e0c4503
4e80afe 
e0c4503 Merge pull request contiv-experimental#181 from mapuri/ucp
00f41eb bump up versions of contiv services
162a0f4 ucp: support for parallel multi-master bringup
e2b0550 Merge pull request contiv-experimental#177 from mapuri/misc
538a13d bump up versions of contiv services
4691926 remove the rbd devel packages that are not needed any more
d016fea Merge pull request contiv-experimental#172 from unclejack/bump_go_to_1.6.2
920aba0 roles/dev/tasks: bump Go to 1.6.2
fc91def Merge pull request contiv-experimental#170 from mapuri/clusterm
82cf863 Merge pull request contiv-experimental#171 from unclejack/vbox_linked_clone
745a104 Vagrantfile: use linked clones
e1bffaa remove clusterm cleanup from top-level cleanup.yml
8030718 Merge pull request contiv-experimental#168 from gaurav-dalvi/selinux-fix
5380c3e Merge pull request contiv-experimental#169 from vvb/ucp_replica_fix
89679a4 Update ovs_cleanup.yml
4002696 fix for selinux issue-326 contiv/netplugin
dad38cf misc fixes. ucp replica. cluster-control serf

git-subtree-dir: vendor/ansible
git-subtree-split: e0c4503c14ba90bc2a2dca986c56f6e4acc69118
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pradvara