Add older dhcrelay syntax to "Deploying Overcloud with L3 routed networking"

Bug #1774637 reported by Ian Pilcher
6
This bug affects 1 person
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://ask.openstack.org
 - The mailing list: http://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 0.0.1.dev800 on 2018-05-31 00:25
SHA: b80ce896a20fa5ffcd800f500ee8bd9c012d0396
Source: https://git.openstack.org/cgit/openstack/tripleo-docs/tree/doc/source/install/advanced_deployment/routed_spine_leaf_network.rst
URL: https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/routed_spine_leaf_network.html

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
Revision history for this message
Ian Pilcher (arequipeno) wrote :

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

Changed in tripleo:
milestone: rocky-2 → rocky-3
Revision history for this message
Harald Jensås (harald-jensas) wrote :

@Ian

Did you test the above?

I cannot get dhcprelay to work with the version shipped in CentOS|RHEL) I have to download source code from ICS and compile the new version (or use Fedora).

What happens with dhcrelay shipped in CentOS is:
 - dhcp request recived by relay
 - relay forwards request
 - dhcpserver recives request
 - dhcpserver responds to request
 - dhcprelay sees the resopons
 - ISSUE: The dhcp respons never gets to the client

Revision history for this message
Ian Pilcher (arequipeno) wrote :

@Harald -

Yes. I did get the dhcrelay in CentOS 7.5 to work. As noted in comment #1, I had to specifically tell dhcrelay to listen on the *response* network, as well as the request network.

Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-docs (master)

Fix proposed to branch: master
Review: https://review.openstack.org/616390

Changed in tripleo:
assignee: nobody → Harald Jensås (harald-jensas)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-docs (master)

Reviewed: https://review.openstack.org/616390
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=d3699dbe872354bdbab0ad70d2eb0698e186de8f
Submitter: Zuul
Branch: master

commit d3699dbe872354bdbab0ad70d2eb0698e186de8f
Author: Harald Jensås <email address hidden>
Date: Thu Nov 8 02:09:59 2018 +0100

    Add dhcrelay example to using old syntax

    "DHCP relay configuration (Example)" section works for
    more recent versions 4.3.6 (in Fedora), but it doesn't
    work with the version in 4.2.5 (CentOS 7).

    Add example configuration for version 4.2.5 (Centos)
    as well.

    Closes-Bug: #1774637
    Change-Id: Ifa828c572d3c6dfc408d2fbebc52f4aa2c571615

Changed in tripleo:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.