Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1175951

Summary:	NM OpenConnect doesn't remember group
Product:	[Fedora] Fedora	Reporter:	Paul Dugas <paul>
Component:	openconnect	Assignee:	David Woodhouse <dwmw2>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	21	CC:	danw, dcbw, dwmw2, nmavrogi, psimerda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openconnect-7.02-1.fc21	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-29 10:02:25 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 Paul Dugas 2014-12-18 23:28:48 UTC

Description of problem:

  The group setting is not set when connecting an OpenConnect VPN.  

Version-Release number of selected component (if applicable):
  NetworkManager-0.9.10.0-14.git20140704.fc21.x86_64
  NetworkManager-openconnect-0.9.8.6-2.fc21.x86_64

How reproducible:
  Every time.

Steps to Reproduce:
1. Create an OpenConnect VPN connection in NetworkManager
2. Enter the gateway name/IP
3. Connect the VPN selecting the group and entering the login name and password
4. Check the "remember" box.
5. Click Connect and verify the connection is up.
6. Disconnect
7. Select the VPN profile again to reconnect
8. Note that the login name and password are populated but the group is not set to the correct value.

Actual results:
  Wrong group selected.

Expected results:
  Correct group selected.

Additional info:
  This used to work with an older version of NM on another machine.  My current
  machine is a new laptop running F21 and the problem is occurring now.

Comment 1 David Woodhouse 2014-12-19 00:23:43 UTC

Should be fixed by http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/376ead11aff752

Please try scratch build at http://koji.fedoraproject.org/koji/taskinfo?taskID=8431591

Comment 2 Paul Dugas 2014-12-19 01:22:35 UTC

I installed the updated openconnect-7.01-2.fc21.x86_64 package from Koji and the issue appears to be resolved.  Thanks much.

Comment 3 Fedora Update System 2014-12-19 11:30:52 UTC

openconnect-7.02-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/openconnect-7.02-1.fc21

Comment 4 Fedora Update System 2014-12-20 08:40:05 UTC

Package openconnect-7.02-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openconnect-7.02-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-17331/openconnect-7.02-1.fc21
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-12-29 10:02:25 UTC

openconnect-7.02-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.