Bug 1014716

Summary:	OpenConnect VPN connection will not connect
Product:	[Fedora] Fedora	Reporter:	Ade Fewings <adefewings>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	20	CC:	adefewings, danw, dcbw, dwmw2
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-0.9.9.0-14.git20131003.fc20	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-09 14:52:57 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 Ade Fewings 2013-10-02 15:19:59 UTC

Description of problem:

Post-upgrade to F20, OpenConnect will not connect to Cisco VPN via NetworkManager interface (GUI triggered).  Tried existing profile brought from working F19 install and new profile with no success.  Error in /var/log/messages:

Oct  2 16:01:00 its65 NetworkManager[763]: <info> VPN plugin state changed: starting (3)
Oct  2 16:01:00 its65 NetworkManager[763]: <info> VPN connection 'hpcw' (ConnectInteractive) reply received.
Oct  2 16:01:00 its65 NetworkManager[763]: <info> VPN connection 'hpcw' (Connect) reply received.
Oct  2 16:01:00 its65 NetworkManager[763]: <warn> VPN connection 'hpcw' failed to connect: 'Could not start connection: wrong plugin state 3'.
Oct  2 16:01:20 its65 NetworkManager[763]: <info> VPN service 'openconnect' disappeared


Version-Release number of selected component (if applicable):
openconnect-5.01-4.fc20.x86_64
NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Try to connect.
2. Certificate accepted.
3. Login.
4. Fails, no GUI indication, just messages notes.

Actual results:
No connection.

Expected results:
VPN up.

Additional info:

Comment 1 Dan Williams 2013-10-03 20:48:24 UTC

This is actually a NetworkManager bug.

Comment 2 Fedora Update System 2013-10-03 20:49:12 UTC

NetworkManager-0.9.9.0-14.git20131003.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-14.git20131003.fc20

Comment 3 Fedora Update System 2013-10-05 01:43:27 UTC

Package NetworkManager-0.9.9.0-14.git20131003.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-14.git20131003.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-18316/NetworkManager-0.9.9.0-14.git20131003.fc20
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-10-09 14:52:57 UTC

NetworkManager-0.9.9.0-14.git20131003.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.