vnf monitoring fails after multiple vnf create/delete operations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tacker |
Expired
|
Medium
|
Unassigned |
Bug Description
1. Use following template to create a vnfd.
template_name: http-ping
description: http-ping-
service_properties:
Id: cirros-
vendor: canonical
version: 1
vdus:
vdu1:
id: vdu1
vm_image: cirros-
instance_type: m1.small
user_
user_data: |
#!/bin/sh
cd /tmp
rm -f httpsrv.sh
cat > httpsrv.sh << EOL
while true; do echo -e "HTTP/1.0 200 OK\r\n\r\nWelcome to $eth0_ip" | sudo nc -l -p 80 ; done&
EOL
sudo chmod +x httpsrv.sh
sudo ./httpsrv.sh &
sleep 180
cat > kill << EOL
cat <<'EOF' > kill
pid = `ps -ef | grep httpsrv | grep exe | grep -v grep | awk '{print $1}'`
echo "killing $pid"
kill -9 $pid
EOF
sudo chmod +x kill
network_
management:
network: net_mgmt
management: true
placement_
availabil
monitoring_
http_ping:
retry: 5
timeout: 10
port: 80
actions:
failure: respawn
config:
param0: key0
param1: key1
2. Create 8 vnfs with above template. Notice, vnf should respawn approximately every 3 minutes.
Verify all vnfs respawn after every 3 mins.
3. Run the functionality testcases using "tox -e functional" . In functionality test, there are multiple create/delete vnfs .
4. After the tests are run some of vnfs will go to ERROR state (because of lack or resource - assuming only 10 vm instances is maximum possible). At this point you will notice monitoring doesn't happen and vnfs are not restarted at all
Changed in tacker: | |
importance: | Undecided → Medium |
Changed in tacker: | |
assignee: | nobody → Anshu Kumar (anshu-choubey) |
Changed in tacker: | |
assignee: | Anshu Kumar (anshu-choubey) → nobody |
I tested this scenario on current master code with user_data/config mentioned in bug description.
But could not reproduce it.
@Santosh,
Could you please mention the tacker version, Or please test on master.