Bug 2000620 - When provisioning a host with Virtual NIC, the tag is not inherited from the subnet
Summary: When provisioning a host with Virtual NIC, the tag is not inherited from the ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-02 14:09 UTC by Rafael Cavalcanti
Modified: 2023-04-06 17:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-06 17:10:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34055 0 Normal New When provisioning a host with Virtual NIC, the tag is not inherited from the subnet 2021-12-01 13:54:38 UTC

Description Rafael Cavalcanti 2021-09-02 14:09:36 UTC
Description of problem:
When provisioning a host with Virtual NIC, the tag is not inherited from the subnet, as it is supposed to do, if we do not specify it.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.In the Satellite web UI, navigate to Hosts > All hosts.
2.Click Edit next to the host you want to edit.
3.On the Interfaces tab, click Add Interface.
4.Select the Virtual NIC check box
5.Do not enter the TAG
6.The template do not render with the VLAN option(vlan=vlan<vlanid>:<interface>)

Actual results:
The tag is not inherited from the subnet. Therefore, the system can't be provisioned.

Expected results:


Additional info:

With tag set explicitly:
---
# This file was deployed via 'Kickstart default PXEGrub' template

default=0
timeout=10

title Kickstart default PXEGrub
  root (nd)
  kernel (nd)/../boot/red-hat-enterprise-linux-7-for-scientific-computing-kickstart-x86_64-7-6-76-vmlinuz ks=http://recife.rguerra.lab/unattended/provision  network ksdevice=bootif ks.device=bootif kssendmac ks.sendmac inst.ks.sendmac ip=172.20.1.122:::255.255.0.0:essie-elberson.rguerra.lab:eth0.600:none vlan=vlan103:eth0
  initrd (nd)/../boot/red-hat-enterprise-linux-7-for-scientific-computing-kickstart-x86_64-7-6-76-initrd.img
---

With no tag set. It is supposed to inherit the tag from the Subnet:
---
# This file was deployed via 'Kickstart default PXEGrub' template

default=0
timeout=10

title Kickstart default PXEGrub
  root (nd)
  kernel (nd)/../boot/red-hat-enterprise-linux-7-for-scientific-computing-kickstart-x86_64-7-6-76-vmlinuz ks=http://recife.rguerra.lab/unattended/provision  network ksdevice=bootif ks.device=bootif kssendmac ks.sendmac inst.ks.sendmac ip=172.20.1.122:::255.255.0.0:essie-elberson.rguerra.lab:eth0.103:none
  initrd (nd)/../boot/red-hat-enterprise-linux-7-for-scientific-computing-kickstart-x86_64-7-6-76-initrd.img
---

Comment 1 Rafael Cavalcanti 2021-09-02 14:10:55 UTC
Same behavior on 6.9.

Comment 3 Tomer Brisker 2021-12-01 13:54:37 UTC
Created redmine issue https://projects.theforeman.org/issues/34055 from this bug

Comment 4 Brad Buckingham 2023-03-06 11:38:36 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 5 Brad Buckingham 2023-04-06 17:10:05 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.


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