Bug 470015

Summary: [TAHI] dhcpv6 client do not return confirm message
Product: Red Hat Enterprise Linux 5 Reporter: Yang Ren <ryang>
Component: dhcpv6Assignee: David Cantrell <dcantrell>
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: desktop-bugs, iboverma, llim, szhou
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-24 03:02:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dhcp6c log none

Description Yang Ren 2008-11-05 10:18:05 UTC 
Created attachment 322559 [details]
dhcp6c log

Description of problem:
In TAHI test client mode test. There are three test case failed cause "Could not get Confirm Message".

42 Part D : Maximum Retransmission Duration of Confirm message
http://focus.bne.redhat.com/~ryang/DHCPv6_Self_Test_P2_1_0_13_client/rfc3315/42.html
43 Part E : Reserved Address Information
http://focus.bne.redhat.com/~ryang/DHCPv6_Self_Test_P2_1_0_13_client/rfc3315/43.html
72 Part E : Reply message in response to a Confirm message
http://focus.bne.redhat.com/~ryang/DHCPv6_Self_Test_P2_1_0_13_client/rfc3315/72.html

All these three test case failed with the process.
ifconfig eth0 down
ifconfig eth0 up

After restart interface The dhcp6c is stop.

I do a test manually.
First I set a server and a client.
After client get advertise message, I input 
ifconfig eth0 down
ifconfig eth0 up
in client. 
dhcpv6 client return a "Segmentation fault" and stop.
Then I try to restart dhcp6c but all fail with "Segmentation fault"

Attached is the log from client.

Version-Release number of selected component (if applicable):
dhcpv6-client-1.0.10-16.el5
libdhcp6client-1.0.10-16.el5
libdhcp6client-devel-1.0.10-16.el5

How reproducible:
always

Steps to Reproduce:
1.setup a client and a server
2.After client get address run commend `ifconfig eth0 down` and `ifconfig eth0 up`
3.The client crash
4.Try to restart dhcp6c
5.Still crash
  
Actual results:
Crash

Expected results:
It should not crash. It should still work.

Additional info:
Comment 1 Lawrence Lim 2008-11-05 14:53:54 UTC 
For the crashing, is it a regression or a new bug?
Comment 2 Lawrence Lim 2008-11-05 14:54:40 UTC 
Could you please attach the track for the crash?
Comment 3 Lawrence Lim 2008-11-05 14:58:13 UTC 
2 bugs outstanding for us to obtain the certification.

Bug 470015 and Bug 470017.
Comment 4 Yang Ren 2008-11-06 01:15:22 UTC 
I think it's a new bug.
The attachment is the log when the client crash.
From the client begin to Segmentation fault
Comment 5 Shirley Zhou 2009-03-24 02:53:34 UTC 
I retest these test cases, they are passed. you may check test result at :http://focus.bne.redhat.com/~szhou/DHCP_Test/DHCPv6_Self_Test_P2_1_0_17/DHCPv6_Self_Test_P2_1_0_17_Client/rfc3315/index.html. I will close the bug.Thanks.
Comment 6 David Cantrell 2009-03-24 03:02:08 UTC 
Closing per comment #5.