Bug 491355
Summary: | Cannot export OpenVPN connection | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ajs <ajsfedora> | ||||
Component: | NetworkManager-openvpn | Assignee: | Dan Williams <dcbw> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 11 | CC: | choeger, dcbw, slawomir.czarko, steve, tim | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 0.7.2-1.fc11 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-12-24 20:43:48 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
ajs
2009-03-20 15:24:21 UTC
commit f6bebbfbd04cce2ab93ac9efb7b99bb54b5ba09d Author: Dan Williams <dcbw> Date: Fri Oct 30 13:48:57 2009 -0700 export: implement export and fix a few import/export bugs (bgo #573986) do_export() by Huzaifa S. Sidhpurwala <huzaifas> with cleanups by me. Testcases and import/export bugfixes by me. Will be fixed in an F10 update soon. This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Bumping the version to 11 as the bug occurs in F11 as well. Fix tagged and ready to build when NM 0.7.2 drops into f11-updates. NetworkManager-openconnect-0.7.2-1.fc11,NetworkManager-pptp-0.7.2-1.fc11,NetworkManager-openvpn-0.7.2-1.fc11,NetworkManager-vpnc-0.7.2-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/NetworkManager-openconnect-0.7.2-1.fc11,NetworkManager-pptp-0.7.2-1.fc11,NetworkManager-openvpn-0.7.2-1.fc11,NetworkManager-vpnc-0.7.2-1.fc11 NetworkManager-openconnect-0.7.2-1.fc11, NetworkManager-pptp-0.7.2-1.fc11, NetworkManager-openvpn-0.7.2-1.fc11, NetworkManager-vpnc-0.7.2-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager-openconnect NetworkManager-pptp NetworkManager-openvpn NetworkManager-vpnc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-13032 NetworkManager-openconnect-0.7.2-1.fc11, NetworkManager-pptp-0.7.2-1.fc11, NetworkManager-openvpn-0.7.2-1.fc11, NetworkManager-vpnc-0.7.2-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. This problem (or bug 480496) is still present in Fedora 12 (In reply to comment #8) > This problem (or bug 480496) is still present in Fedora 12 What kind of config are you trying to export? What's the exact problem, that when you hit export and pick a path, something fails? Or that export is not able to be clicked? (In reply to comment #9) > (In reply to comment #8) > > This problem (or bug 480496) is still present in Fedora 12 > > What kind of config are you trying to export? What's the exact problem, that > when you hit export and pick a path, something fails? Or that export is not > able to be clicked? The problem is the same as in the original bug. 1. Select OpenVPN connection in Network Manager. 2. Click Export 3. Select file name 4. Click Save 5. I get message box titled "Cannot export VPN connection" with text: The VPN connection 'blah' could not be exported to blah.conf. Error: unknown error. 6. The file which should be exported is not there. Ok, is this a "static key" connection? Do you have any messages from nm-connection-editor in ~/.xsession-errors right after exporting? (In reply to comment #11) > Ok, is this a "static key" connection? no, it's with certificates (TLS) > > Do you have any messages from nm-connection-editor in ~/.xsession-errors right > after exporting? nothing after exporting but I do get something when editing this connection: ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: ca ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: cert ** (nm-connection-editor:1649): WARNING **: Invalid setting VPN: key Created attachment 390348 [details]
VPN configuration screenshots
Here's the configuration of the connection in question.
(IP address was hidden)
|