New controller can not be added to the ready cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Fuel Python (Deprecated) | ||
7.0.x |
Fix Committed
|
High
|
Unassigned |
Bug Description
ISO info:
#######
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "7.0"
openstack_
api: "1.0"
build_number: "263"
build_id: "263"
#######
Steps to reproduce:
1. update FM node from 5.1 to 7.0 release
2. create ubuntu cluster 3 ctrl/mongo + 2 compute
3. deploy it
4. add one more controller node to the cluster when deployment process will be finished
5. start deploy
Expected results:
Cluster with new controller is sucessfully deployed
Real results:
Deployment is failed on cluster-haproxy task:
################
priority: 1500
type: puppet
uids:
- '15'
parameters:
puppet_modules: "/etc/puppet/
puppet_manifest: "/etc/puppet/
timeout: 3600
cwd: "/"
################
puppet log from failed node: http://
I'm digging little bit dipper and have found that new node has built its own cluster(etc. haproxy resource has not been found in its cib)
################
root@node-15:~# crm_mon --one-shot
Last updated: Thu Sep 10 21:37:00 2015
Last change: Thu Sep 10 13:49:03 2015
Stack: corosync
Current DC: node-15.
Version: 1.1.12-561c4cf
1 Nodes configured
7 Resources configured
Online: [ node-15.
Clone Set: clone_p_vrouter [p_vrouter]
Started: [ node-15.
vip__management (ocf::fuel:
vip__vrouter_pub (ocf::fuel:
vip__vrouter (ocf::fuel:
vip__public (ocf::fuel:
vip__zbx_vip_mgmt (ocf::fuel:
Master/Slave Set: master_p_conntrackd [p_conntrackd]
Masters: [ node-15.
#################
I have inspected /etc/corosync/
################
- priority: 1100
type: puppet
uids:
- '15'
parameters:
puppet_modules: "/etc/puppet/
puppet_
timeout: 3600
cwd: "/"
###############
So, it seems that we don't re-apply this task for new controller nodes and cluster nodes can not sucessfully communicate with new one. I don't know how we calculate set of tasks for ready controller nodes , but it seems that we should consider 'cluster' task in current case.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
milestone: | none → 7.0 |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Oleg S. Gelbukh (gelbuhos) |
status: | Incomplete → In Progress |
Changed in fuel: | |
importance: | Undecided → High |
milestone: | 7.0 → 7.0-updates |
no longer affects: | fuel/8.0.x |
tags: | added: feature-upgrade |
tags: | added: module-octane |
tags: | added: area-octane |
tags: |
added: area-python removed: area-octane |
tags: | added: on-verification |
tags: | removed: on-verification |
Astute log from the FM node. 'node-15' - name of the new controller node.