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.

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

networkmanager: Reset static addresses when switching to DHCP #5918

Closed

Conversation

mvollmer
Copy link
Member

This is what people expect.

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1401426

@dperpeet
Copy link
Contributor

I'm not entirely sure about this. The bug contains both opinions also.

Resetting the list of addresses means they have to be entered again - from memory? Or from another source? If we leave them, they can be easily deleted by clicking on a button per address, which is much easier. Cockpit doesn't hide the fact that there are static addresses in addition to the automatically assigned one.

Before we change this behavior, we should probably consider the user stories and see whether we might just have to clarify the way cockpit presents these cases. @garrett

@dperpeet dperpeet added the blocked Don't land until something else happens first (see task list) label Feb 21, 2017
@dperpeet
Copy link
Contributor

I'm setting this to blocked until the discussion is resolved

@andreasn
Copy link
Contributor

Sorry for adding more complexities to this. It seems that selecting some of the items in the dropdown will clear the IP address, while other won't.
This is what I did:

  • I changed from DHCP to Manual. Entered the IP address.
  • Changed back to DHCP. Address remains.
  • Changed to Link Local. Address is gone. Even if I switch back to Manual or DHCP.

@andreasn
Copy link
Contributor

The UI suggests I get the Address automatically if I select DHCP, but I still set a manual address? What address do I get? The automatic or the custom one? Do I get both?

I think selecting DHCP clearing the manual address sounds like a good behaviour.

@andreasn
Copy link
Contributor

Because the Manual address fields belong to the Manual parent dropdown.
The children of DHCP is a separate thing.

@martinpitt
Copy link
Member

@mvollmer: Is this still relevant? By now this sounds like it could be established behaviour which is hard to change?

@mvollmer
Copy link
Member Author

mvollmer commented Sep 6, 2018

I can't really answer this, I am afraid. But absent stronger evidence that the current UI behavior is unexpected and confusing, I would not make any changes.

@andreasn, can we get usability testing for this? Scenario would be something like this:

  • Configure a static IP address for a network interface
  • Now change the same interface to use DHCP

If they remove the manual IP address by themselves: Did you expect that you have to do this extra step? Would you want Cockpit to do this step automatically for you?

If they don't remove the manual IP address: Are you aware that the interface now has both DHCP and a manual address? Is that what you want? How can Cockpit help you?

@andreasn
Copy link
Contributor

andreasn commented Sep 6, 2018

@marusak
Copy link
Member

marusak commented Jul 23, 2019

Needs to rebase to master since #12367 changed tests names

@mvollmer mvollmer force-pushed the networking-reset-manual-ips branch from 7f58430 to a06935c Compare July 23, 2019 10:00
@mvollmer mvollmer force-pushed the networking-reset-manual-ips branch from a06935c to 23163b5 Compare July 23, 2019 10:29
@martinpitt
Copy link
Member

Closing for now, this is way too stale, and until someone complains let's not change this.

@martinpitt martinpitt closed this Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Don't land until something else happens first (see task list)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants