You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 7,8
Ruby: *
Distribution: Debian 12 EL9 Ubuntu 22.04
Module version: 4.1.0
How to reproduce (e.g Puppet code you use)
start keepalived service without configuration on new versione with updated unit-file
What are you seeing
Service fail to start in acceptance test when try to run service without minimal configuration of vrrp_instance
What behaviour did you expect instead
Output log
Mar 12 18:26:19 debian12-64-puppet8.example.com systemd[1]: keepalived.service - Keepalive Daemon (LVS and VRRP) was skipped because of an unmet condition check (ConditionFileNotEmpty=/etc/keepalived/keepalived.conf).
Mar 12 18:26:20 debian12-64-puppet8.example.com systemd[1]: Starting keepalived.service - Keepalive Daemon (LVS and VRRP)...
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: Starting Keepalived v2.2.7 (01/16,2022)
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: WARNING - keepalived was built for newer Linux 5.19.11, running on Linux 5.15.0-1057-azure #65~20.04.1-Ubuntu SMP Mon Feb 12 17:26:40 UTC 2024
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: Command line: '/usr/sbin/keepalived' '--dont-fork' '-D' '--vrrp'
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: Opening file '/etc/keepalived/keepalived.conf'.
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: Configuration file /etc/keepalived/keepalived.conf
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: NOTICE: setting config option max_auto_priority should result in better keepalived performance
Mar 12 18:26:20 debian12-64-puppet8.example.com Keepalived[1347]: Warning - keepalived has no configuration to run
Mar 12 18:27:50 debian12-64-puppet8.example.com systemd[1]: keepalived.service: start operation timed out. Terminating.
Mar 12 18:27:50 debian12-64-puppet8.example.com Keepalived[1347]: Stopping
Mar 12 18:27:50 debian12-64-puppet8.example.com Keepalived[1347]: CPU usage (self/children) user: 0.005619/0.000000 system: 0.000000/0.000000
Mar 12 18:27:50 debian12-64-puppet8.example.com Keepalived[1347]: Stopped Keepalived v2.2.7 (01/16,2022)
Mar 12 18:27:50 debian12-64-puppet8.example.com systemd[1]: keepalived.service: Failed with result 'timeout'.
Mar 12 18:27:50 debian12-64-puppet8.example.com systemd[1]: Failed to start keepalived.service - Keepalive Daemon (LVS and VRRP).
Any additional information you'd like to impart
Unit-file non new distribution change Service Type from simple to notify
As expected keepalived not start without a valid configuration.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
start keepalived service without configuration on new versione with updated unit-file
What are you seeing
Service fail to start in acceptance test when try to run service without minimal configuration of vrrp_instance
What behaviour did you expect instead
Output log
Any additional information you'd like to impart
Unit-file non new distribution change Service Type from
simple
tonotify
As expected keepalived not start without a valid configuration.
#296 #299 #297
The text was updated successfully, but these errors were encountered: