Run packstack newton in OpenPOWER host

Bug #1635133 reported by junfengzhao
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
New
Undecided
Unassigned

Bug Description

I run packstack script in a OpenPOWER host for RDO all in one test.But I have some error,I don't know why it was wrong.

cd /var/tmp/packstack/20161019-103202-YRulkG/hieradata
tar --dereference -cpzf - ../hieradata | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@172.30.121.201 tar -C /var/tmp/packstack/61b865ca183f45fda314c044a0cd12d9 -xpzf -
cd /usr/lib/python2.7/site-packages/packstack/puppet
cd /var/tmp/packstack/20161019-103202-YRulkG/manifests
tar --dereference -cpzf - ../manifests | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@172.30.121.201 tar -C /var/tmp/packstack/61b865ca183f45fda314c044a0cd12d9 -xpzf -
cd /usr/share/openstack-puppet/modules
tar --dereference -cpzf - aodh apache ceilometer certmonger cinder concat firewall glance gnocchi heat horizon inifile ironic keystone manila memcached mongodb mysql neutron nova nssdb openstack openstacklib oslo packstack rabbitmq redis remote rsync sahara ssh stdlib swift sysctl tempest trove vcsrepo vswitch xinetd | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@172.30.121.201 tar -C /var/tmp/packstack/61b865ca183f45fda314c044a0cd12d9/modules -xpzf -
2016-10-19 10:39:07::ERROR::run_setup::1018::root:: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 1013, in main
    _main(options, confFile, logFile)
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 660, in _main
    runSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 627, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 81, in runAllSequences
    sequence.run(config=self.CONF, messages=self.MESSAGES)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 109, in run
    step.run(config=config, messages=messages)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 50, in run
    self.function(config, messages)
  File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 214, in apply_puppet_manifest
    wait_for_puppet(currently_running, messages)
  File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 128, in wait_for_puppet
    validate_logfile(log)
  File "/usr/lib/python2.7/site-packages/packstack/modules/puppet.py", line 107, in validate_logfile
    raise PuppetError(message)
PuppetError: Error appeared during Puppet run: 172.30.121.201_network.pp
Error: member(): Wrong number of arguments given (1 for 2) at /var/tmp/packstack/61b865ca183f45fda314c044a0cd12d9/modules/packstack/manifests/neutron/ovs_agent.pp:29 on node localhost
You will find full trace in log /var/tmp/packstack/20161019-103202-YRulkG/manifests/172.30.121.201_network.pp.log

2016-10-19 10:39:07::INFO::shell::94::root:: [172.30.121.201] Executing script:
rm -rf /var/tmp/packstack/61b865ca183f45fda314c044a0cd12d9

maybe is my OpenPOWER host's network interface name too long?

[root@localhost latest]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enP4p1s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:0e:1e:52:f7:a0 brd ff:ff:ff:ff:ff:ff
3: enP3p3s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:0a:f7:86:b3:70 brd ff:ff:ff:ff:ff:ff
4: enP4p1s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:0e:1e:52:f7:a2 brd ff:ff:ff:ff:ff:ff
5: enP3p3s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:0a:f7:86:b3:71 brd ff:ff:ff:ff:ff:ff
    inet 172.30.121.201/24 brd 172.30.121.255 scope global enP3p3s0f1
       valid_lft forever preferred_lft forever
    inet6 fe80::20a:f7ff:fe86:b371/64 scope link
       valid_lft forever preferred_lft forever
6: enP3p3s0f2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:0a:f7:86:b3:72 brd ff:ff:ff:ff:ff:ff
7: enP3p3s0f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:0a:f7:86:b3:73 brd ff:ff:ff:ff:ff:ff

Revision history for this message
Javier Peña (jpena-c) wrote :

The line where it failed is:

if member($network_hosts, choose_my_ip(hiera('HOST_LIST'))) {

So the best bet is that choose_my_ip provided an empty output.

From the function code (https://github.com/openstack/packstack/blob/master/packstack/puppet/modules/packstack/lib/puppet/parser/functions/choose_my_ip.rb) I see it checks for the facter output of "interfaces", and tries to match the IP address for each interface with the provided list. So could you try the following:

# facter interfaces (and paste the output)
# facter ipaddress_enP3p3s0f1 (same)

...and check their output against your answer file? If you do not find anything, please do the following:

# packstack --answer-file <path to answer file> --debug

After it fails, collect the hiera file from /var/tmp/packstack/latest/hieradata and share it in the bug.

That should give us enough information to find out what is going wrong.

Revision history for this message
junfengzhao (junfengzhao) wrote :

Sorry,my host os have reinstalled.But i have another OpenPOWER host installed packstack(newton).Maybe I could find the wrong reason.

[root@controller ~]# facter interfaces
br_ex,br_int,br_tun,enP3p3s0f0,enP3p3s0f1,enP3p3s0f2,enP3p3s0f3,enP4p1s0f0,enP4p1s0f1,lo,ovs_system

[root@controller ~]# facter ipaddress
172.30.241.112

[root@controller ~]# facter |grep enp3p3s0f0
ipaddress_enp3p3s0f0 => 172.30.241.112
macaddress_enp3p3s0f0 => 00:0a:f7:86:be:fc
mtu_enp3p3s0f0 => 1500
netmask_enp3p3s0f0 => 255.255.255.0
network_enp3p3s0f0 => 172.30.241.0

facter interfaces command returns the correct network adapter name enP3p3s0f0
But ipaddress_enp3p3s0f0 variable are lower case.

Revision history for this message
Bruce Tan (brucetan) wrote :

I am having the same issue on my POWER 8 machine.

It's not some environment that I can use freely, but I do have the output for "facter" as follows:

[root@rdop5 ~]# facter interfaces
enP1p12s0f0,enP1p12s0f1,lo
[root@rdop5 ~]# facter ipaddress_enP1p12s0f0

[root@rdop5 ~]# facter ipaddress_enP1p12s0f1
192.168.1.5
[root@rdop5 ~]# facter ipaddress_lo
127.0.0.1

I never had such issue on VM before, so is it possible that the first NIC being down(no IP) is
causing this issue?

Revision history for this message
Florian Ermisch (0xf10e) wrote :

I've got the same problem on a x64 machine.
Adding an IPv4 address to the 2nd NIC (which
was lacking one) didn't fix the problem, the
error message is still the same.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.