7:35 p.m.
I made a fresh install of CentOS 7.0 mini with cobbler again w/o yum update
and got after the first run:
ERROR : Error appeared during Puppet run: 20.0.0.11_ceilometer.pp
Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install
openstack-ceilometer-notification' returned :
You will find full trace in log
/var/tmp/packstack/20150430-193045-vAhnyX/manifests/212.224.122.82_ceilometer.pp.log
This was an issue with Juno too.
Disabled Ceilometer with:
sed -i 's/CONFIG_CEILOMETER_INSTALL=y/CONFIG_CEILOMETER_INSTALL=n/g'
packstack-aio
ran packstack again and it was successful
**** Installation completed successfully ******
Dashboard works on AIO, but spawning a cirros instance as a demo user in
dashboard gives:
*Error: *Failed to perform requested operation on instance "cirros1", the
instance has an error status: Please try again later [Error: No valid host
was found. There are not enough hosts available.].
And in fact the compute_nodes table is empty:
MariaDB [nova]> select * from compute_nodes;
*Empty set (0.00 sec)*
The warning that is shown about the NetworkManager after installation was
already with Juno and as I remember it could be ignored for AIO.
But for for our records I did:
[root@localhost ~]# yum update -y
[root@localhost ~]# systemctl stop NetworkManager.service
[root@localhost ~]# systemctl disable NetworkManager.service
[root@localhost ~]# packstack --answer-file=packstak-aio
**** Installation completed successfully ******
Tried to spawn cirros2 instance again and got the same result as above.
On Fri, May 1, 2015 at 1:01 AM, Arash Kaffamanesh <ak(a)cloudssky.com> wrote:
I did a CenOS fresh install with the following steps for AIO:
yum -y update
cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
yum install
http://rdoproject.org/repos/openstack-kilo/rdo-release-kilo.rpm
yum install epel-release
cd /etc/yum.repos.d/
curl -O
https://repos.fedorapeople.org/repos/openstack/openstack-trunk/epel-7/rc2...
yum install openstack-packstack
setenforce 0
packstack --allinone
and got again:
Error: nmcli (1.0.0) and NetworkManager (0.9.9.1) versions don't match.
Force execution using --nocheck, but the results are unpredictable.
But if I don't do a yum update and install AIO it finishes successfully
and I can yum update afterwards.
So if nobody can reproduce this issue, then something is wrong with my
base CentOS install, I'll try to install the latest CentOS from ISO now.
Thanks!
Arash
On Fri, May 1, 2015 at 12:42 AM, Arash Kaffamanesh <ak(a)cloudssky.com>
wrote:
> I'm installing CentOS with cobbler and kickstart (from centos7-mini) on 2
> machines
> and I'm trying a 2 node install. With rc1 it worked without yum update.
> I'll do a fresh install now with yum update and let you know.
>
> Thanks!
> Arash
>
>
>
> On Fri, May 1, 2015 at 12:23 AM, Alan Pevec <apevec(a)gmail.com> wrote:
>
>> 2015-05-01 0:12 GMT+02:00 Arash Kaffamanesh <ak(a)cloudssky.com>:
>> > But if I yum update it into 7.1, then we have the issue with nmcli:
>> >
>> > Error: nmcli (1.0.0) and NetworkManager (0.9.9.1) versions don't match.
>> > Force execution using --nocheck, but the results are unpredictable.
>>
>> Huh, again?! I thought that was solved after you did yum update...
>> My original answer to that is still the same "Not sure how could that
>> happen, nmcli is part of NetworkManager RPM."
>> Can you reproduce this w/o RDO in the picture, starting with the clean
>> centos installation? How are you installing centos?
>>
>> Cheers,
>> Alan
>>
>
>