Project

General

Profile

Bug #9434

when configuring an alias interface user should get some warning if bootmode is set to 'DHCP' under provisioning subnet

Added by Bryan Kearney over 7 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Network
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1193007
Description of problem:
we know that alias interfaces can be configured statically, you can't configure when dhcp is set on same subnet. And currently when you configure a alias interface on same subnet where provisioning is configured and obviously for which bootmode is set to 'DHCP', UI doesn't raise any error/warning on UI.

And user can't set static because provisioning is configured on same subnet. So only way is to add new subnet and use that to configure aliases statically.

I'm not how this can be handled in current design. But I think its a valid case.

Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150210.0
Sat6.1.0 beta snap2

How reproducible:
always

Steps to Reproduce:
1. create a alias interface on same subnet where provisioning is configured and BootMode set to 'DHCP'
2.
3.

Actual results:
Add_interface form doesn'r raise any warning or error. User gets to know only when alias interface will not be configured on provisioned host.

Expected results:
UI should give some way or raise a warning when submiting the add_interface form for alias interface with bootmode set to dhcp on same subnet.

Additional info:

Associated revisions

Revision a45253c2 (diff)
Added by Marek Hulán over 7 years ago

Fixes #9434 - managed alias accepts only static boot mode subnet

Revision 6afdddf1 (diff)
Added by Marek Hulán over 7 years ago

Fixes #9434 - managed alias accepts only static boot mode subnet

(cherry picked from commit a45253c2b7c747b15506dddc4efa86396c6ef53f)

History

#1 Updated by Dominic Cleal over 7 years ago

  • Category set to Network
  • Assignee deleted (Ohad Levy)
  • Priority changed from Normal to Low

#2 Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2197 added
  • Pull request deleted ()

#3 Updated by Marek Hulán over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Dominic Cleal over 7 years ago

  • Assignee set to Marek Hulán
  • Legacy Backlogs Release (now unused) set to 35

#5 Updated by Dominic Cleal over 7 years ago

  • Legacy Backlogs Release (now unused) changed from 35 to 28

#6 Updated by Lukas Zapletal over 3 years ago

  • Triaged set to No

Update 2018 for the record: This constraint is too strict, it is perfectly fine to have an alias interface configured with DHCP as long as the physical interface is not configured with DHCP. So the correct check is to verify on the host level that all interfaces with same MAC address (e.g. aliases) have only one subnet with DHCP mode on. And also this should be only warning I guess.

#7 Updated by Tomer Brisker over 3 years ago

  • Status changed from Closed to Rejected

Also available in: Atom PDF