virtualbox Centos 7 : kolla-ansible prechecks failed with ansible-palybook

Bug #1581276 reported by DIY
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Low
Unassigned

Bug Description

install with all-in-one mode in virtualbox centos7,there are two networks for 10.0.2.1/24 and 192.168.161.1/24.When checking if kolla_interl_vip_address and kolla-external_vip_address are not pingable from ang node,failed ,but it is pingable for 10.0.2.4(eth0 ),with using win7 cmd it can ping to192.168.161.203(eth1),the ip of the host(win7) is 192.168.161.204.the error is from ansible-playboo -i /usr/share/kolla/ansible/inventory/all-in-one -e @/etc/kolla/golbals.yml..........
I want to slove it ,but have no idea. for help ,thanks.

Revision history for this message
zhubingbing (zhubingbing) wrote :

Can you show me your /etc/global.yml profile?
I need more information.

Changed in kolla:
milestone: none → newton-rc2
status: New → Triaged
Revision history for this message
Eduardo Gonzalez (egonzalez90) wrote :

I can't fully understand where your issue is.
kolla_internal_vip_address and kolla_external_vip_address should not be pingable from any node before deployment.

This is just because the IP in that variable is the IP which keepalived will assign to load balance.
Of course, the IPs need to be in a network range pingable from other nodes, but not active before deployment.

The precheck ensures if the IP is used by other node, if is used the task fails, which is the expected behaviour to avoid network conflicts.

If my understanding of your issue is wrong, paste /etc/kolla/globals.yml and error logs as @zhubingbing requested.

If more help is needed, take around #openstack-kolla irc channel, a lot of people will help you.
Regards

Changed in kolla:
status: Triaged → Incomplete
importance: Undecided → Low
Changed in kolla:
milestone: newton-rc2 → ocata-1
Changed in kolla:
milestone: ocata-1 → ocata-2
Changed in kolla:
milestone: ocata-2 → ocata-3
Revision history for this message
Christian Berendt (berendt) wrote :

Closing as invalid, reads like a configuration issue. Please re-open if this issue still occurs.

Changed in kolla:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.