Bug 1956732

Summary:	[RHOSP13/16.1]: VMs do not get DHCP IP address from StorageNFS network of manila.
Product:	Red Hat OpenStack	Reporter:	Shravan Kumar Tiwari <shtiwari>
Component:	openstack-manila	Assignee:	Tom Barron <tbarron>
Status:	CLOSED NOTABUG	QA Contact:	vhariria
Severity:	medium	Docs Contact:	RHOS Documentation Team <rhos-docs>
Priority:	medium
Version:	13.0 (Queens)	CC:	dsneddon, gcharot, gouthamr, hjensas, scohen, skaplons, vimartin
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-13 12:29:19 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 Shravan Kumar Tiwari 2021-05-04 10:17:06 UTC

Description of problem:

Configured Manila and it is observed that VMs do not get DHCP IP address from the defined StorageNFS network interface.
(NFS shares are accessible and working fine when assigning IP address to VM manually))

- The DHCP discoveries are seen comming from source VM to compute node and also observed on controller node bond interface but nothing is visible on qdhcp namespace of this network present in controller.


Version-Release number of selected component (if applicable):
RHOSP13
RHOSP16.1


Actual results:
VMs do not get IP from DHCP for StorageNFS network configured for Manila NFS shares.

Expected results:
VMs should get IP from DHCP for StorageNFS network configured for Manila NFS shares.


Additional info:

- The same behavior is observed in both RHOSP13 and RHOSP16.1 environment (as the case was initially opened for RHOSP13 and data captured from 13 env. so BZ is opened against RHOSP13).
- All other networks DHCP is wokring fine it is only this 'StorageNFS' network that is not allocating IP to Vm via DHCP.

Comment 23 Tom Barron 2021-10-13 12:29:19 UTC

No code change is expected; the associated customer case was closed with a suggested configuration change.