[NETVIRT-889] CSIT 3node failures - instances do not get ip addresses Created: 06/Sep/17  Updated: 16/Aug/18  Resolved: 16/Aug/18

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Nitrogen
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Jamo Luhrsen Assignee: Ashwin B C
Resolution: Won't Do Votes: 0
Labels: csit:3node, csit:failures
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Duplicate
is duplicated by NETVIRT-814 CSIT 3node failures - instance not ge... Resolved
External issue ID: 9107

 Description   

https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-3node-openstack-ocata-upstream-stateful-nitrogen/156/log.html.gz#s1-s1-s1-t8-k13

in this job, it seems none of the instances in one subnet were able to
fetch their dhcp address. However, all the instances in another subnet
were ok.



 Comments   
Comment by Jamo Luhrsen [ 06/Sep/17 ]

(In reply to Jamo Luhrsen from comment #0)
> https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-3node-openstack-
> ocata-upstream-stateful-nitrogen/156/log.html.gz#s1-s1-s1-t8-k13
>
> in this job, it seems none of the instances in one subnet were able to
> fetch their dhcp address. However, all the instances in another subnet
> were ok.

in the same job, actually, the L3 external network suite had another
case where a VM didn't receive it's ip address. This time it was just
one instance of three that failed:

https://logs.opendaylight.org/releng/jenkins092/netvirt-csit-3node-openstack-ocata-upstream-stateful-nitrogen/156/log.html.gz#s1-s1-s2-t10-k19

Comment by Hanamantagoud Kandagal [ 28/Nov/17 ]

Hi Manu,

Please look into this issue , as VM is not getting IP.

Comment by Jamo Luhrsen [ 16/Aug/18 ]

Logs are now old and stale (it's been a year since this was opened). We will eventually be revisiting the netvirt 3node csit jobs more closely after we get more stable tests in upstream projects.

Generated at Wed Feb 07 20:22:43 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.