Bug 1956732 - [RHOSP13/16.1]: VMs do not get DHCP IP address from StorageNFS network of manila.
Summary: [RHOSP13/16.1]: VMs do not get DHCP IP address from StorageNFS network of man...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-manila
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tom Barron
QA Contact: vhariria
RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 10:17 UTC by Shravan Kumar Tiwari
Modified: 2022-08-23 10:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-13 12:29:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3585 0 None None None 2022-08-23 10:39:16 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.