Bug 1778670

Summary:	[machines][RFE] Maybe a notification is needed if creating network without DHCP setting
Product:	Red Hat Enterprise Linux 8	Reporter:	YunmingYang <yunyang>
Component:	cockpit-appstream	Assignee:	Katerina Koukiou <kkoukiou>
Status:	NEW ---	QA Contact:	YunmingYang <yunyang>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	kkoukiou, leiwang, mpitt, wshi, xchen, ymao
Target Milestone:	rc	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-02 07:30:15 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 YunmingYang 2019-12-02 09:40:19 UTC

Description of problem:
If creating a network without DHCP, the VM whose network interface is from this network will not get the IP address automatically. So, maybe a notification shown on the Network creation dialog is needed, to make the user notice that.

Version-Release number of selected component (if applicable):
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create a network without setting DHCP
2. Create a VM with using the network interface from the network which is created in step 1

Actual results:
1. There is no notification shown on the network creation dialog, and the VM will not get the IP address

Expected results:
1. There is a notification shown on the network creation dialog to make the user notice that

Additional info:

Comment 3 Katerina Koukiou 2021-03-22 11:58:30 UTC

I would not go with adding a warning. But we should make the 'Enable DHCPv4' checkbox enabled by default with proper range prefilled. If a user decided to disable it it probably means they know what they 're going.

Comment 5 RHEL Program Management 2021-06-02 07:30:15 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.