Bug 1626385
| Summary: | Refresh caps event are not sent on IPv6 stateless autoconf attachment | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Michael Burman <mburman> | ||||
| Component: | Core | Assignee: | Edward Haas <edwardh> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 4.20.23 | CC: | bugs, ylavi | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-10-03 07:43:53 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
We do not plan to support dynamic addressing for IPv6 anytime soon. Therefore closing. |
Created attachment 1481514 [details] logs Description of problem: Refresh caps event are not sent on IPv6 stateless autoconf attachment When attaching network with IPv6 autoconf and sending setup networks via the engine, on the host the network reported at first(for few minutes) as local net autoconf-net1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 fe80::214:5eff:fe17:8ed4/64 scope link valid_lft forever preferred_lft forever "autoconf-net1": { "ipv6autoconf": true, "addr": "", "ipv4defaultroute": false, "ipv6addrs": [], I'm not sure if this delay is expected at all. After few minutes the IPv6 address reported for the network on the host and in vdsm-client as well. After this delay, the change doesn't reflected in the engine UI and we don't see the IPv6 address until doing a manual refresh caps. Version-Release number of selected component (if applicable): vdsm-4.20.39-1.el7ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Attach network with IPv6 autoconf and approve operation Actual results: On host the network reported as local address for few minutes and only after a delay the IPv6 address reported on the host. The change doesn't get reflected in the engine side. If doing manual refresh caps it does. Expected results: 1. I'm not sure if the delay is expected 2. The change should be reflected in the engine and IPv6 address should appear