| Summary: | neutron puppet: invalid value for Integer(): "" | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Martin Pavlásek <mpavlase> | ||||||||||
| Component: | openstack-packstack | Assignee: | Ivan Chavero <ichavero> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | yeylon <yeylon> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 8.0 (Liberty) | CC: | aopincar, aortega, jguiditt, jschluet, mmagr, mpavlase, srevivo, yeylon | ||||||||||
| Target Milestone: | ga | Keywords: | Automation, AutomationBlocker, Reopened | ||||||||||
| Target Release: | 8.0 (Liberty) | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2016-02-03 04:07:33 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Martin Pavlásek
2016-01-07 16:02:58 UTC
Created attachment 1112492 [details]
logs.tar.gz
Created attachment 1112493 [details]
answerfile.txt
This problem does not appear in an allinone packstack run from master source. I'm gonna check with the latest liberty package. Adding keywords back Red Hat Bugzilla's database reported a query serialization error. Most likely this occurred because another user or process attempted to change the same data that you were attempting to change. I'm sorry for messing with flags in previous step, but I blame Buzilla I cannot reproduce this either with the same version of packstack and OPM. Considering the error message: Error: invalid value for Integer(): "" at /var/tmp/packstack/fe1a41f8b77f47fab4855d3165e1fe69/modules/neutron/manifests/agents/ml2/ovs.pp:207 on node agzx0-mpavlase-rh-pud-pksk-network.novalocal The failing line [0] is checking size of array given as CONFIG_NEUTRON_OVS_TUNNEL_TYPES [1], which is basically value of CONFIG_NEUTRON_ML2_TYPE_DRIVERS [2]. According to your answer file, your value was: CONFIG_NEUTRON_ML2_TYPE_DRIVERS=local,flat,vlan,gre,vxlan I tried the same value and the installation was successful. Can you please try to reproduce this again and attach here also /var/tmp/packstack/<snip>/manifests/<IP>_neutron.pp and also /var/tmp/packstack/<snip>/hieradata/defaults.yaml? [0] https://github.com/redhat-openstack/openstack-puppet-modules/blob/stable/liberty/neutron/manifests/agents/ml2/ovs.pp#L207 [1] https://github.com/openstack/packstack/blob/stable/liberty/packstack/puppet/templates/neutron_ovs_agent.pp#L28 [2] https://github.com/openstack/packstack/blob/stable/liberty/packstack/plugins/neutron_350.py#L824 Could not reproduce either with the current pacsktack package: openstack-packstack-7.0.0-0.10.dev1684.g87ec498.el7ost Closing this bug, pelease reopen if the problem persists I've forgotten to note, that the bug has appear in multinode topology (1 controller, 2 compute, 1 network node). Maybe on all-in-one deployment it works as expected. See answerfile: CONFIG_COMPUTE_HOSTS=172.16.32.81,172.16.32.12 CONFIG_CONTROLLER_HOST=172.16.32.85 CONFIG_NETWORK_HOSTS=172.16.32.76 Created attachment 1115788 [details]
192.168.1.15_neutron.pp
Created attachment 1115790 [details]
defaults.yaml
/var/tmp/packstack/<snip>/hieradata/defaults.yaml
*** Bug 1292028 has been marked as a duplicate of this bug. *** Huh, now I'm even more confused. The error "invalid value for Integer()" is raised in ::neutron::agents::ml2::ovs class, but it is not even used in manifest from comment #11. Ah-hah ... it's because the error actually was raised on host 192.168.1.16 :). Ok, so 2 node (1controller+compute/network) install passed for me. Gonna try separate network. I'm closing this bug since it appears to be a configuration issue. Feel free to reopen it if the problem persists. The problem was in misconfiguration in packstack's answerfile (unsupported combination of networking), so this is not a real bug. |