Add older dhcrelay syntax to "Deploying Overcloud with L3 routed networking"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Harald Jensås |
Bug Description
This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:
- [ ] This doc is inaccurate in this way: ______
- [x] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.
If you have a troubleshooting or support issue, use the following resources:
- Ask OpenStack: http://
- The mailing list: http://
- IRC: 'openstack' channel on Freenode
-------
Release: 0.0.1.dev800 on 2018-05-31 00:25
SHA: b80ce896a20fa5f
Source: https:/
URL: https:/
It seems that dhcrelay's command-line options have changed recently. The syntax in the "DHCP relay configuration (Example)" section works for more recent versions (4.3.6 in Fedora, for example), but it doesn't work with the version in CentOS 7 (4.2.5).
AFAICT, the equivalent syntax for the older version version would be:
dhcrelay -d -i eth1 -i eth2 -i eth3 172.20.0.10 172.20.0.1
Changed in tripleo: | |
milestone: | none → rocky-2 |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
Correction, one also has to specify the interface(s) on which to listen for replies (despite what the man page says), so the correct syntax would be:
dhcrelay -d -i eth0 -i eth1 -i eth2 -i eth3 172.20.0.10 172.20.0.1