packstack installation is stuck at copy_puppet_modules

[katherine]

Hi,

I am trying to install one more compute node in the existent installation. Installation process is stack at step on copy_puppet_modules..(It is last record in the log)

openstack-packstack.noarch 10.0.0-0.1.0rc1.el7 @centos-openstack-ocata

Preparing Puppet manifests [ DONE ]
Copying Puppet modules and manifests [ DONE ]
Applying 10.20.20.21_compute.pp
Testing if puppet apply is finished: 10.20.20.21_compute.pp [ | ]

2017-03-23 14:38:56::INFO::shell::94::root:: [10.20.20.21] Executing script:
systemctl is-enabled NetworkManager
2017-03-23 14:38:56::INFO::shell::94::root:: [10.20.20.21] Executing script:
systemctl is-active NetworkManager
2017-03-23 14:38:56::INFO::shell::94::root:: [10.20.20.20] Executing script:
echo $HOME
2017-03-23 14:38:56::INFO::shell::94::root:: [localhost] Executing script:
cd /var/tmp/packstack/20170323-143845-VDv7Yj/hieradata
tar --dereference -cpzf - ../hieradata | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.20.20.21 tar -C /var/tmp/packstack/2fc410a07558445397fc3678f1c61296 -xpzf -
cd /usr/lib/python2.7/site-packages/packstack/puppet
cd /var/tmp/packstack/20170323-143845-VDv7Yj/manifests
tar --dereference -cpzf - ../manifests | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.20.20.21 tar -C /var/tmp/packstack/2fc410a07558445397fc3678f1c61296 -xpzf -
cd /usr/share/openstack-puppet/modules
tar --dereference -cpzf - aodh apache ceilometer certmonger cinder concat firewall glance gnocchi heat horizon inifile ironic keystone magnum manila memcached mongodb mysql neutron nova nssdb openstack openstacklib oslo packstack panko rabbitmq redis remote rsync sahara ssh stdlib swift sysctl tempest trove vcsrepo vswitch xinetd | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.20.20.21 tar -C /var/tmp/packstack/2fc410a07558445397fc3678f1c61296/modules -xpzf -

I tried to manually execute command and all is ok. There are no errors/warning in the log file(/var/tmp/packstack/20170323-150021-mk3UuG/openstack-setup.log). I did not have such issue with newton. Can you shed the light on the issue?

[katherine (prozora)]

According to the strace the packstack was stuck on wait_for_puppet. The issue has gone after resetting CONFIG_NEUTRON_OVS_TUNNEL_SUBNETS to empty value.

[Javier Peña (jpena-c)]

I have run a local test and could not reproduce the issue, even setting CONFIG_NEUTRON_OVS_TUNNEL_SUBNETS with a subnet value.

Could you try to reproduce the issue (using packstack --debug answer-file.txt), and then upload the log files from /var/tmp/packstack/<uuid>/manifests/ somewhere?

[katherine (prozora)]

> Could you try to reproduce the issue (using packstack --debug answer-file.txt), and then upload the
> log files from /var/tmp/packstack/<uuid>/manifests/ somewhere?

I created two VMs in my test invironment and performed the same steps. And I had the same issue again. I have attached logs.

[jethro.sun (jethro-sun7)]

Hi,

I am experiencing a same one now. It didn't happen to me couple months back. Should I open a new issue or something else?

I did try to set NEUTRON_SUBNET to empty and set the WORKER to 1. It can't fix this deployment issue. The VM has 30G RAM so I don't think memory is causing the problem.

[sima (attarkhorasani)]

hi, have you been able to solve the problem??? If so, please let us know...

[Nurfadil Wiratama (adilwiratama)]

i have this problem too.. it's solved by checking the /etc/hosts file. make sure ur IP address is there and set the packstack file CONFIG_KEYSTONE_ADMIN_PW=<fill ur password>
also make sure u have good internet connection. because it depends on your internet connection too.