Bug 1148949

Summary: openstack-packstack: installed "packstack --allinone" on Centos7.0 and configured private networking. The booted VMs are not able to communicate with each other, nor ping the gateway.
Product: [Community] RDO Reporter: Alexander Chuzhoy <sasha>
Component: openstack-packstackAssignee: Javier Peña <jpena>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: aortega, chris.brown, derekh, dkranz, ihrachys, jpena, sasha, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-18 06:35:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
neutron/* and /var/log/messages none

Description Alexander Chuzhoy 2014-10-02 17:48:26 UTC 
openstack-packstack: installed  "packstack --allinone"  on Centos7.0 and configured private networking. The booted VMs are not able to communicate with each other, nor ping the gateway.


Environment: openstack-packstack-2014.1.1-0.28.dev1238.el7.noarch

Steps to reproduce:
1. install openstack-packstack
2. run packstack --allinone
3. Login to the horizon and configure private networking with dhcp
4. Allow ICMP in the security group "default".
5. Launch 2 instances. 

Result:
The instances aren't able to communicate with each other nor ping the gateway.


Expected result:
The VMs should be able to communicate with each other (ping).
Comment 1 Alexander Chuzhoy 2014-10-02 17:52:27 UTC 
Created attachment 943498 [details]
neutron/* and /var/log/messages
Comment 2 Javier Peña 2014-10-24 10:16:10 UTC 
Most error messages in neutron.log seem to be related to the l3-agent:

2014-10-01 22:56:37.104 690 TRACE neutron.openstack.common.rpc.amqp AgentNotFoundByTypeHost: Agent with agent_type=L3 agent and host=rhos-compute-node-04.lab.eng.rdu2.redhat.com could not be found

2014-10-02 00:59:24.158 690 WARNING neutron.scheduler.l3_agent_scheduler [req-959c8d26-2f7f-46e5-9e4e-0238f6f77bc9 None] No routers compatible with L3 agent configuration on host rhos-compute-node-04.lab.eng.rdu2.redhat.com

That would explain lack of ping connectivity to the gateway, but not between the instances. I think https://review.openstack.org/#/c/126321/24..25/packstack/plugins/neutron_350.py would help here, will test that and see if that fixes some or all the issues.
Comment 3 Javier Peña 2014-10-24 13:28:28 UTC 
I tested the patch mentioned in comment #2, and everything seems to go fine. 

I found an unrelated issue (still investigating), only if I tried to boot the VMs within one minute of starting the Packstack-installed machine. Aleksander, did you reboot the system between installing and login into Horizon? If not, I will just push the patch for review.
Comment 4 Javier Peña 2014-10-24 15:16:52 UTC 
Created https://review.openstack.org/130818 as a fix for the L3 agent issue. With that, the L3 agent works fine after installing Packstack. Still waiting for Aleksander's confirmation on the reboot.
Comment 5 Alexander Chuzhoy 2014-10-24 15:48:37 UTC 
I didn't reboot the system.
Comment 6 Javier Peña 2014-10-27 09:27:16 UTC 
*** Bug 1149292 has been marked as a duplicate of this bug. ***
Comment 7 Javier Peña 2014-10-27 15:40:39 UTC 
*** Bug 1157666 has been marked as a duplicate of this bug. ***
Comment 9 Mike McCune 2016-03-28 22:48:26 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 11 Christopher Brown 2017-06-17 16:42:51 UTC 
I think this is stale and should be closed.