| 2016-03-24 11:47:31 |
Maksym Strukov |
description |
Steps:
1. Create env with Neutron Vlan network
2. Add two slaves: 1 controller and 1 compute
3. Move private network to enp0s5
4. Enable DPDK on enp0s5 for compute node
5. Configure HugePages for compute node: 2m = 5, 1g = 0, dpdk = 0
6. Run deployment
Actual result:
Deployment failed.
Puppet and astute log contain no errors. Only one warning in astute log about puppet-agent timeout on compute node.
Issue with openvswitch which can't start due to lack of memory:
EAL: Not enough memory available on socket 0! Requested: 64MB, available: 20MB
PANIC in rte_eal_init():
Cannot init memory
7: [ovs-vswitchd() [0x408aa3]]
6: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fe6a14aeec5]]
5: [ovs-vswitchd() [0x407289]]
4: [ovs-vswitchd() [0x505292]]
3: [/usr/lib/x86_64-linux-gnu/libdpdk.so(rte_eal_init+0x1071) [0x7fe6a23fb201]]
2: [/usr/lib/x86_64-linux-gnu/libdpdk.so(__rte_panic+0xc3) [0x7fe6a23c1bb9]]
1: [/usr/lib/x86_64-linux-gnu/libdpdk.so(rte_dump_stack+0x18) [0x7fe6a2400f08]]
Aborted (core dumped)
* Starting ovs-vswitchd
* Enabling remote OVSDB managers
root@node-2:~# echo $?
0
puppet freeze on starting openvswitch and don't report any error.
Expected result:
Puppet logs contain error which points engineer to issue with openvswitch and/or memory misconfiguration. |
Steps:
1. Create env with Neutron Vlan network
2. Add two slaves: 1 controller and 1 compute
3. Move private network to enp0s5
4. Enable DPDK on enp0s5 for compute node
5. Configure HugePages for compute node: 2m = 5, 1g = 0, dpdk = 0
6. Run deployment
Actual result:
Deployment failed.
Puppet and astute log contain no errors. Only one warning in astute log about puppet-agent timeout on compute node.
Issue with openvswitch which can't start due to lack of memory:
EAL: Not enough memory available on socket 0! Requested: 64MB, available: 20MB
PANIC in rte_eal_init():
Cannot init memory
7: [ovs-vswitchd() [0x408aa3]]
6: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7fe6a14aeec5]]
5: [ovs-vswitchd() [0x407289]]
4: [ovs-vswitchd() [0x505292]]
3: [/usr/lib/x86_64-linux-gnu/libdpdk.so(rte_eal_init+0x1071) [0x7fe6a23fb201]]
2: [/usr/lib/x86_64-linux-gnu/libdpdk.so(__rte_panic+0xc3) [0x7fe6a23c1bb9]]
1: [/usr/lib/x86_64-linux-gnu/libdpdk.so(rte_dump_stack+0x18) [0x7fe6a2400f08]]
Aborted (core dumped)
* Starting ovs-vswitchd
* Enabling remote OVSDB managers
root@node-2:~# echo $?
0
puppet freeze on starting openvswitch and don't report any error.
Expected result:
Puppet logs contain error which points engineer to issue with openvswitch and/or memory misconfiguration.
Env:
9.0 customm http://jenkins-product.srt.mirantis.net:8080/view/custom_iso/job/9.0.custom.iso/1205/ |
|
