Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle no key-management set for wireless #81

Closed
jcronenberg opened this issue Apr 18, 2024 · 0 comments · Fixed by #92
Closed

Handle no key-management set for wireless #81

jcronenberg opened this issue Apr 18, 2024 · 0 comments · Fixed by #92
Assignees
@cfconrad
Labels
bug Something isn't working migration Something needs to be changed/implemented in the wicked migration
Milestone
YaST2 lan parity

Comments

@jcronenberg
Copy link
Owner

This is a valid config but isn't handled by the migration currently.
@jcronenberg jcronenberg added bug Something isn't working migration Something needs to be changed/implemented in the wicked migration labels Apr 18, 2024
@jcronenberg jcronenberg self-assigned this Apr 18, 2024
@cfconrad cfconrad added this to the YaST2 lan parity milestone May 27, 2024
@jcronenberg jcronenberg assigned cfconrad and unassigned jcronenberg Sep 3, 2024
@cfconrad cfconrad mentioned this issue Sep 16, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cfconrad cfconrad

Labels
bug Something isn't working migration Something needs to be changed/implemented in the wicked migration
Projects
None yet
Milestone
YaST2 lan parity
Development

Successfully merging a pull request may close this issue.

Set security from key-management or guess if not available cfconrad/agama
2 participants
@cfconrad @jcronenberg