Bug 1034779

Summary: OpenVPN NetworkManager-gnome; 'Add' greyed out
Product: [Fedora] Fedora Reporter: ant.aja
Component: NetworkManager-openvpnAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: axel.thimm, choeger, davide.poletto, dcbw, huzaifas, steve, thaller
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:24:46 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:
Attachments:
Description Flags
NetworkManager service stop/start with DEBUG Log active (only lo and p33p1 interfaces were active). none

Description ant.aja 2013-11-26 13:49:12 UTC
Description of problem:
OpenVPN networks cannot be manually added in NetworkManager (Gnome), it just leaves the 'Add' button greyed out even with all details filled in.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Open Network Manager and click '+' to add Network
2. Select VPN -> OpenVPN
3. Fill in details. I used a hostname with password authentication; Password set to 'always ask', with no CA.

Actual results:
Add button remains greyed out and connection can't be added.

Expected results:
Add button should be active and allow the VPN connection to be added.

Additional info:

Comment 1 Davide Poletto 2014-10-08 06:49:22 UTC
Same exact situation after my very recent upgrade from Fedora 19 to Fedora 20: in my case is the "Save..." button which is greyed out (connection add is permitted) when I try to save the VPN connection as user (no matter which connection detail's I fill in when I select OpenVPN or if I import an existing ovpn configuration file).
Worked in F19. OpenVPN doesn't work anymore from CLI (as root) too after the upgrade to F20.

Here my actual RPM list (F20 fully updated at present date):

openvpn-2.3.2-6.fc20.x86_64
libnm-gtk-0.9.9.0-10.git20140123.fc20.x86_64
libgcrypt-1.5.3-2.fc20.x86_64
NetworkManager-0.9.9.0-45.git20131003.fc20.x86_64
NetworkManager-config-connectivity-fedora-0.9.9.0-45.git20131003.fc20.x86_64
NetworkManager-glib-0.9.9.0-45.git20131003.fc20.x86_64
NetworkManager-openvpn-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-openvpn-gnome-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-pptp-0.9.8.2-3.fc20.x86_64
NetworkManager-pptp-gnome-0.9.8.2-3.fc20.x86_64
NetworkManager-vpnc.x86_64-0.9.8.2-3.fc20.x86_64
NetworkManager-vpnc-gnome-0.9.8.2-3.fc20.x86_64

No NetworkManager Debug Logs appears after enabling them into /etc/NetworkManager/NetworkManager.conf and restarting NetworkManager service.

Simply the "Save..." button is and remain greyed out.

Comment 2 Davide Poletto 2014-10-08 06:58:37 UTC
Created attachment 944868 [details]
NetworkManager service stop/start with DEBUG Log active (only lo and p33p1 interfaces were active).

Comment 3 Davide Poletto 2014-10-08 07:02:12 UTC
Sorry DEBUG Logs were available (I missed them). I attached a txt file. By the way no other logs appear when adding a VPN connection (The "Save..." button is always greyed out).

Comment 4 Fedora End Of Life 2015-01-09 20:42:11 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 5 Fedora End Of Life 2015-02-17 19:24:46 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.