Hi, I was able to install 3-node RDO juno-1 (rdo-release-juno-1.noarch) over CentOS7, but at the end of install it gave me this ... Questions prefixed with Q: inline below: Additional information: * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components. *Q: Do i need to sue ntpd to ensure all my systems are in sync, whats the recommended way here ?*

* Warning: NetworkManager is active on <IP1>, <IP2> and <IP3>. OpenStack networking currently does not work on systems that have the Network Manager service enabled. *Q: Do i need to disable NetworkManager.service on all or is it safe to ignore this? What exactly doesn't work with NetworkManager ?

> You need to disable NetworkManager and enable network service. Before you run Packstack you will also need to setup the ifcfg-XXXX network interfaces on all nodes and activate them. Why can't packstack handle this itself if it doesn't support NM? I m

concerned about the manual steps involved and losing on my n/w connections in case i do anything wrong.

Is there any reference on how to do this, i couldn't find anything specific on the quickstart page.

Thanks patrick. Are you aware of any link that can give me some insights on what exactly doesn't work in networking with NM enabled, i m guessing that if it some specific stuff i can just avoid using it maybe!

On Mon, Dec 29, 2014 at 9:04 PM, Patrick Laimbock <patrick(a)laimbock.com&gt; wrote: > On 29-12-14 15:39, Deepak Shetty wrote: > >> > You need to disable NetworkManager and enable network service. Before >> you run Packstack you will also need to setup the ifcfg-XXXX network >> interfaces on all nodes and activate them. >> >> Why can't packstack handle this itself if it doesn't support NM? I m >> > > Ask the developers. Patches welcome. > > concerned about the manual steps involved and losing on my n/w >> connections in case i do anything wrong. >> > > Yes that's a risk so make sure to have the steps figured out before doing > anything. Having direct access to a (serial) console comes in handy if > things fall apart. > > Is there any reference on how >> to do this, i couldn't find anything specific on the quickstart page. >> > > I'm not aware of an RDO guide on this subject. The steps on each node are: > - create appropriate ifcfg-XXX files > - stop NetworkManager > - disable NetworkManager > - enable network > - start network > > You probably want to do the last 4 steps in one long command or else you > will loose connectivity after stopping NetworkManager if you are not using > a console. My current ifcfg-em1 is : [root@rhsdev1 network-scripts]# cat ifcfg-em1 # Generated by dracut initrd DEVICE="em1" ONBOOT=yes NETBOOT=yes UUID="fd67c34e-9aad-44b7-a980-b5288ad3c442" IPV6INIT=yes BOOTPROTO=dhcp HWADDR="c8:1f:66:c6:d5:fc" TYPE=Ethernet NAME="em1" I did this: # systemctl stop NetworkManager.service ; chkconfig NetworkManager off; systemctl restart network.service ; chkconfig network on Note: Forwarding request to 'systemctl disable NetworkManager.service'. rm '/etc/systemd/system/multi-user.target.wants/NetworkManager.service' rm '/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service' rm '/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service' Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details. [root@rhsdev1 network-scripts]# systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Tue 2014-12-30 17:01:00 IST; 30s ago Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com network[24948]: RTNETLINK answers: File exists Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]: network.service: control process exited, code=exited status=1 Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Failed to start LSB: Bring up/down networking. Dec 30 17:01:00 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit network.service entered failed state. I modified em1 to: [root@rhsdev1 network-scripts]# cat ifcfg-em1 # Generated by dracut initrd DEVICE="em1" ONBOOT=yes NETBOOT=yes UUID="fd67c34e-9aad-44b7-a980-b5288ad3c442" IPV6INIT=yes BOOTPROTO=dhcp #HWADDR="c8:1f:66:c6:d5:fc" NM_CONTROLLED=no TYPE=Ethernet NAME="em1" [root@rhsdev1 network-scripts]# service network restart Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details. [FAILED] [root@rhsdev1 network-scripts]# systemctl restart network.service Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details. [root@rhsdev1 network-scripts]# systemctl status network.service network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Tue 2014-12-30 17:07:34 IST; 6s ago Process: 26318 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]: network.service: control process exited, code=exited status=1 Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Failed to start LSB: Bring up/down networking. Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com systemd[1]: Unit network.service entered failed state. *So in short, disabling NM and enabling/restarting network isn't working as my network service is getting into error state*thanx, deepak > > HTH, > Patrick > > _______________________________________________ > Rdo-list mailing list > Rdo-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/rdo-list >

On 29-12-14 14:06, Deepak Shetty wrote: > Hi, > I was able to install 3-node RDO juno-1 (rdo-release-juno-1.noarch) > over CentOS7, but at the end of install it gave me this ... > Questions prefixed with Q: inline below: > > Additional information: > * Time synchronization installation was skipped. Please note that > unsynchronized time on server instances might be problem for some > OpenStack components. > > *Q: Do i need to sue ntpd to ensure all my systems are in sync, whats > the recommended way here ?* > All your nodes need to have the correct time. You can specify an NTP server in the Packstack answer file or as a CLI option and then Packstack will configure your nodes to use that NTP server. If you don't specify an NTP server then Packstack doesn't handle NTP so you will have to do it yourself. Either way, make sure that all nodes always have the correct time.

I modified em1 to: [root@rhsdev1 network-scripts]# cat ifcfg-em1 # Generated by dracut initrd DEVICE="em1" ONBOOT=yes NETBOOT=yes UUID="fd67c34e-9aad-44b7-a980-b5288ad3c442" IPV6INIT=yes BOOTPROTO=dhcp #HWADDR="c8:1f:66:c6:d5:fc"

NM_CONTROLLED=no TYPE=Ethernet NAME="em1"

[root@rhsdev1 network-scripts]# service network restart Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.

Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com <http://rhsdev1.lab.eng.blr.redhat.com> network[26318]: RTNETLINK answers: File exists Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com <http://rhsdev1.lab.eng.blr.redhat.com> systemd[1]: network.service: control process exited, code=exited status=1 Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com <http://rhsdev1.lab.eng.blr.redhat.com> systemd[1]: Failed to start LSB: Bring up/down networking. Dec 30 17:07:34 rhsdev1.lab.eng.blr.redhat.com <http://rhsdev1.lab.eng.blr.redhat.com> systemd[1]: Unit network.service entered failed state. *So in short, disabling NM and enabling/restarting network isn't working as my network service is getting into error state

On 12/29/2014 09:39 AM, Deepak Shetty wrote: > > On Dec 29, 2014 8:00 PM, "Patrick Laimbock" <patrick(a)laimbock.com > <mailto:patrick@laimbock.com>> wrote: >> >> On 29-12-14 14:06, Deepak Shetty wrote: >>> >>> Hi, >>> I was able to install 3-node RDO juno-1 (rdo-release-juno-1.noarch) >>> over CentOS7, but at the end of install it gave me this ... >>> Questions prefixed with Q: inline below: >>> >>> Additional information: >>> * Time synchronization installation was skipped. Please note that >>> unsynchronized time on server instances might be problem for some >>> OpenStack components. >>> >>> *Q: Do i need to sue ntpd to ensure all my systems are in sync, whats >>> >>> the recommended way here ?* >> >> >> All your nodes need to have the correct time. You can specify an NTP > server in the Packstack answer file or as a CLI option and then > Packstack will configure your nodes to use that NTP server. If you don't > specify an NTP server then Packstack doesn't handle NTP so you will have > to do it yourself. Either way, make sure that all nodes always have the > correct time. > > Thanks, will try this. > >> >>> * Warning: NetworkManager is active on <IP1>, <IP2> and <IP3>. OpenStack >>> networking currently does not work on systems that have the Network >>> Manager service enabled. >>> >>> *Q: Do i need to disable NetworkManager.service on all or is it safe to >>> >>> ignore this? What exactly doesn't work with NetworkManager ? >> >> >> You need to disable NetworkManager and enable network service. Before >> you run Packstack you will also need to setup the ifcfg-XXXX network >> interfaces on all nodes and activate them. > > Why can't packstack handle this itself if it doesn't support NM? I m > concerned about the manual steps involved and losing on my n/w > connections in case i do anything wrong. Is there any reference on how > to do this, i couldn't find anything specific on the quickstart page. Packstack uses SSH to remotely configure hosts. Trying to disable NM and enable standard ifcfg networking while using an ssh session is very tricky and often results in hosts that have completely lost networking. So, we don't attempt to do this. Instead, we recommend using a kickstart to deploy your machines that disables NM at host install time As for why NM needs to be disabled, there are a bunch of open bugs against NM targeted at RHEL 7.1 (or maybe later) where NM and Neutron networking conflict with each other. I think for Nova networking NM might be fine, but for Neutron there are known issues. Livnat might have a list of NM bugs handy that would need to be resolved before we can begin looking at testing NM + Neutron together again to determine if there are more issues lying in wait, or if we can green-light that combination Perry

On 12/31/2014 09:34 AM, Deepak Shetty wrote: > In which case RDO quickstart or some other place should have good info > on how to disable NM and enable ifcfg networking for started who look at > quickstart or RDO faqs to get hints google search for 'rdo disable network manager' turned up this: https://openstack.redhat.com/Fedora_20_with_existing_network it's a bit more than you would need, but in there are simple steps for disabling network manager But I agree that having more accessible HOWTOs for this specific area would make sense. This wiki page is Fedora specific (though the same steps should work on CentOS 7 I believe) and doesn't cover initial installation, only after install how to disable NM. I believe though, that removing network manager in a kickstart based installation of CentOS or Fedora is as simple as adding NetworkManager to the list of blacklisted packages. (i.e. under %packages add -NetworkManager) [1] Perry [1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/...

Also the current list of bugs that blocks us from enabling NM are - https://bugzilla.redhat.com/buglist.cgi?cmdtype=dorem&list_id=3123976...

On 01/01/2015 05:03 AM, Deepak Shetty wrote: > Thanks perry, i googled too, but having instructions as part of the rdo > quickstart is ideal as it is in the flow of things. For eg. I installed > centos7 via pxe install and since rdo quick start didn't say anything > specific abt Nm i just followed basic install process, only to know > later that nm need to be disabled, which is not easy for someone not > fairly expert in networking stuff so having the right cmds as part of > rdo quick start pre reqs would help rdo beginerrs a lot > I agree we should document that in the quick start. Kuba - can you please add the steps to turn-off NM in the quickstart page.