-
-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beta branch - feedback on use #686
Comments
I've just built a copy of this beta version with "rpmbuild" and currently running it on my centos7 VM servers, without problems so far. I'm also testing building packages under mock and the keepalived failed to build in this environment. I've listed below the tail end of the log file, is there anything else that's need from me and is this a supported build environment? Keepalived configurationKeepalived version : 1.3.9
/usr/bin/systemd-nspawn -q -M 87e1080a067146ae8e0cf7bc410e7d5a -D /var/lib/mock/epel-7-x86_64/root --private-network --setenv=LANG=en_GB.UTF-8 --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOSTNAME=mock --setenv=PROMPT_COMMAND=printf "\033]0;\007" --setenv=HOME=/builddir --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PS1= \s-\v$ -u mockbuild bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/keepalived.spec |
I've just pushed an update to the beta branch that should fix your compilation issues. Unfortunately I hadn't included a check that the kernel headers supported RTEXT_FILTER_SKIP_STATS. Many thanks for your feedback. |
Thanks for the quick update. A build now seems to fail on a missing systemd service file: RPM build errors:
|
Unfortunately I don't have experience of mock builds. Doing an rpm build outside a mock environment completes successfully for me. The only thing I can think of is that maybe the lines
in keepalived/Makefile.am have a problem. Could you attach the full log of the mock build so we can try and see where the keepalived.service file is being installed. |
Same for me, the normal rpmbuild works fine and only the mock build is failing. I've attached the build log: This is a CentOS7 VM running on ESXi, it has 2GB Ram and a non-standard (updated) kernel: |
@fenice2 I've found a problem with mock builds, that I've resolved at least on my system. I can now do a mock build on Fedora 26 with a Fedora 26 target. If I try doing a mock build on my Fedora 26 system with an EPEL7 target it fails, but that looks more like a mock problem. I've pushed the fixes upstream so if you pull the beta branch I hope mock builds will be fixed for you. |
Fantastic, that worked a treat - it's all built, installs and works. :) As always, many thanks for your quick response and all your work on this project. Regards Bill |
Hi. A bit of feedback: We've been running "Keepalived v2.0.0 (04/11,2018)" in production on ubuntu bionic for about three weeks now. No IPVS, just a single VRRP group with a single IPv4 VIP. No IPv6. No issues seen so far. Thanks for writing keepalived! |
Running in a configuration where some track_scripts are used to control the priority of a VRRP instance, I notice that when the priority of the Master falls below that of the Backup, there is no (immediate) re-election. Most of the times I try this there is a state change (on Backup) after ignoring the received adverts with lower prio 3 times:
But I've also seen a few times that the Backup keeps ignoring the lower prio adverts for ever... There is a difference to this respect in the code compared with master (i.e. 1.4.4) where the received lower priority does trigger a re-election:
[beta] vrrp.c:1736
Is it intentional to postpone to force the change from Backup to Master upon receiving a lower priority adverts? (Keepalived v2.0.0 (05/08,2018), git commit 1.4.3-19-g9b8680a+ on CentOS6.9) |
@rwgroenenberg The RFC for VRRPv3 (RFC 5798) states:
Note: The comment at (465) should state (465) and (470) describe what to do in the event of a lower priority advert being received - i.e. discard it, and this is how keepalived now behaves (sending an advert wasn't simply discarding the lower priority advert). So far as I remember, one of the problems with the old code was that if it received a lower priority advert, it reset the received advert timer and consequently it never transitioned to master. I decided when fixing this to do in in accordance with the RFC. |
I see, well then I'll keep an eye out for the situation of remaining in Backup forever despite receiving lower prio adverts. I'm quite sure that occurred on a clean beta version, but I'm currently trying to get the concept of an advert_group in (like you suggested as alternative to my multi i/f on a single VRRP instance). |
Beta branch now merged into master. Any issues with what was the beta branch should be tested against the keepalived v2.0 code, and if they still exist please report a new issue. |
Please add comments to this issue if you have successfully used the new beta branch of keepalived. In particular it would be helpful to describe the way that you are using keepalived, what platform you are running on, any benefits you have found with the new code and any suggested enhancements.
If you have found any issues with the beta code, please raise a separate issue report, add the
beta
label and include the following in the issue report:keepalived -v
The text was updated successfully, but these errors were encountered: