Bug 1466476
| Summary: | Need f25 patch in f26: improve parsing of IP configuration from alias files | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dusty Mabe <dustymabe> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | bgalvani, dcbw, fgiudici, gottfried.haider, lkundrak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-29 11:25:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dusty Mabe
2017-06-29 18:15:29 UTC
Hi, NM 1.8, shipped in f26, already includes those patches: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a8f0d88596d8dd2b807a7b0adee272c4f077dade https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3cc00dd550fcbd83ec2f1af9eeb83bf5ec921d21 Hey Beniamino, Thank you! For some reason I was checking the cherry pick statements to see what was in what tag and I didn't see all of them in a tag so i thought some of them didn't make it into a release yet. That's what I get for multitasking while looking at this. +(cherry picked from commit a8f0d88596d8dd2b807a7b0adee272c4f077dade) +(cherry picked from commit be1daa4580267e448ad93b854da382026ea63281) +(cherry picked from commit faf1ffc5ccd94770250082e88885dcf1f70b43ac) +(cherry picked from commit 3cc00dd550fcbd83ec2f1af9eeb83bf5ec921d21) +(cherry picked from commit 4c595997f2037707fcc9800c38a8ee8a6630c0e3) +(cherry picked from commit e391fe98a9cd8b22673040efd0992e194584c36d) +(cherry picked from commit e824dd34f0dc1bda10ab4102fc27d90f85c1462a) +(cherry picked from commit 2ebc390734a9eaa65109ee989eed12282306aec7) +(cherry picked from commit 304615f30181a2a0a97878a1c14155426086e9a7) Another reason why we thought this didn't make it into f26 is because we are seeing the same behavior as described in the commit message for https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=3cc00dd550fcbd83ec2f1af9eeb83bf5ec921d21 - will dig on that more today. basically we have noticed an issue where having ipv6 enabled in digital ocean yields a system with no default route. still trying to dig to figure out the root cause. I believe I am having the same issue with IPv6 on F26 on DigitalOcean. Currently working a ticket with them, but things are going slowly. Is there anything I could do to workaround, or help debug this? @gohai, Fedora 26 atomic host or Fedora 26 cloud base image? It seems there are issues with ipv6 and static networking with cloud-init+networkmanager. I think a newer version of cloud-init will fix it. @dustymabe I am on the "regular" (i.e. non-atomic) image. Latest suggestion I got from DigitalOcean support was running this command: ip -6 route add default via [my public IPv6 gateway] dev eth0 Which indeed did the trick for me. To make this change persistent they had me add the same literal IPV6_DEFAULTGW to ifcfg-eth0:0. This seem to have worked also, but is not set by default when a F26 droplet is instantiated. Not sure if this is the same issue as you were looking at, or completely orthogonal. DigitalOcean support staff: "we've alerted engineers to fix this on the images". This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |