I think it's very hard to predict packstack --allinone or packstack behavior during multinode deployment when SELINUX is enabled. It might be unexpected (weird as wrote Antonio ). It seems to be a persistent problem - coexistence SELINIX and RDO Openstack (Havana,IceHouse,Juno). Anyway, to make any conclusions packstack has to be run with SELINUX either set to permissive mode or just disabled. Analyzing corresponding logs after packstack completion will clearly show SELINUX related problems during packstack installation and may explain why internal interface DOWN state on neutron demo's router for demo_private sub-net has been set.
I think it's very hard to predict packstack --allinone or packstack behavior during multinode deployment when SELINUX is enabled. It might be unexpected (weird as wrote Antonio ). It seems to be a persistent problem - coexistence SELINIX and RDO Openstack (Havana,IceHouse,Juno). Anyway, to make any conclusions packstack has to be run with SELINUX either set to permissive mode or just disabled. Analyzing In particular case (Antonio's install) analyzing corresponding logs after packstack completion completion will clearly show SELINUX related problems during packstack installation and may explain why internal interface DOWN DOWN state on neutron demo's router for demo_private sub-net has been set.
I think it's very hard to predict packstack --allinone or packstack behavior during multinode deployment when SELINUX is enabled. It might be unexpected (weird as wrote Antonio ). It seems to be a persistent problem - coexistence SELINIX and RDO Openstack (Havana,IceHouse,Juno). Anyway, to make any conclusions packstack has to be run with SELINUX either set to permissive mode or just disabled. mode. In particular case (Antonio's install) analyzing corresponding logs after packstack completion will clearly show SELINUX related problems during packstack installation and may explain why internal interface DOWN state on neutron demo's router for demo_private sub-net has been set.