Ensure that time is in sync on both nodes. It's the most common issue. С уважением, Станислав Ханжин-Цветков. 10.01.2013 18:29 пользователь "Nux!" <[email protected]> написал:
> Hi, > > Trying to add an additional node to an openstack deployment, I followed > http://fedoraproject.org/wiki/**Getting_started_with_** > OpenStack_EPEL#Adding_a_**Compute_Node<http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL#Adding_a_Compute_Node> > . > I started the openstack-nova-network and compute services on the new node; > the firewall is open for both sides, no errors in logs on either servers, > but when I do a service list all I get is: > > Binary Host Zone > Status State Updated_At > nova-cert server-4.local nova > enabled :-) 2013-01-10 14:30:08 > nova-scheduler server-4.local nova > enabled :-) 2013-01-10 14:30:08 > nova-compute server-4.local nova > enabled :-) 2013-01-10 14:30:09 > nova-network server-4.local nova > enabled :-) 2013-01-10 14:30:08 > nova-consoleauth server-4.local nova > enabled :-) 2013-01-10 14:30:08 > nova-console server-4.local nova > enabled :-) 2013-01-10 14:30:08 > nova-compute server-3 nova > enabled XXX 2013-01-10 14:27:50 > nova-network server-3 nova > enabled XXX 2013-01-10 14:27:56 > > server-4 also serves as controller and both know about each other through > /etc/hosts, so it's not a name problem. > > Where else could I look? > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > ______________________________**_________________ > cloud mailing list > [email protected] > https://admin.fedoraproject.**org/mailman/listinfo/cloud<https://admin.fedoraproject.org/mailman/listinfo/cloud> >
_______________________________________________ cloud mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/cloud
