[FFe] netcfg should ask if dhcp should be used on s390x
Bug #1567688 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| netcfg (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Unlike typical platforms, mainframes do not usually run a dhcp server or automatically assign networking information. Therefore on s390x, the question whether dhcp should be used should be higher priority, with default answer "no".
Or possibly it should default to false on s390x, and simply static network configuration be asked straight away with dhcp as a interactive fallback.
Related branches
Revision history for this message
| Dimitri John Ledkov (xnox) wrote | #1 |
| tags: | added: patch |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in netcfg (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package netcfg - 1.135ubuntu3
---------------
netcfg (1.135ubuntu3) xenial; urgency=medium
* On s390x ask the user if DHCP network autoconfiguration should be
proceeded or not. DHCP should be supported in KVM|MAAS|OpenStack
deployements, however at the same time most LPAR|z/VM deployments use
static network configuration on s390x. LP: #1567688
-- Dimitri John Ledkov <email address hidden> Fri, 08 Apr 2016 07:53:27 +0100