Page MenuHomeVyOS Platform
Create Task
Maniphest T7040

Loosing configuration after a power failure/reset
Open, NormalPublicBUG
Actions

Description

The issue is mostly observed when the task scheduler is configured and the script is executed during the power failure/reset attempted multiple times.
Steps to reproduce in the GNS3 lab:

  • Create a new 1.4.1 VM.
  • Create a task-scheduler and the script must contain the commit and save functions. (Attached the script{F7454259})
set high-availability vrrp group vrrp0 address 192.168.0.1/24
set high-availability vrrp group vrrp0 interface 'eth2'
set high-availability vrrp group vrrp0 peer-address '192.168.0.3'
set high-availability vrrp group vrrp0 priority '200'
set high-availability vrrp group vrrp0 vrid '1'
set system task-scheduler task update-vip executable arguments '/config/scripts/migrate_vip.sh'
set system task-scheduler task update-vip executable path '/bin/bash'
set system task-scheduler task update-vip interval '1'
  • Stop and start the VM multiple times. (the issues does not occur with an initiated reboot)
  • The boot process got stuck at the message as seen in the screenshot.

image.png (185×1 px, 115 KB)

Whereas in VMWare ESXi, the login prompt is received with hostname as localhost but the no configuration details found in the config.boot file, only see the last file, attached the file for reference.

config.boot609 BDownload
.

Details

Version
1.4.1
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

SrividyaA created this task.Fri, Jan 10, 3:05 PM
SrividyaA triaged this task as Normal priority.
gbr subscribed.Fri, Jan 10, 4:47 PM
syncer edited projects, added VyOS Rolling, VyOS 1.4 Sagitta (1.4.2); removed VyOS 1.4 Sagitta (1.4.1).Fri, Jan 10, 7:21 PM
dmbaturin subscribed.Fri, Jan 10, 7:27 PM

@SrividyaA What exactly do you mean by mostly? Have you seen the problem occur without a script that modifies the config?

pasik subscribed.Sat, Jan 11, 6:59 AM
SrividyaA added a comment.Thu, Jan 16, 7:02 AM

@dmbaturin I have not seen issue without scripting, what I meant is the problem occurs when the config is modified. When I tested with the configured script, it checks the reachability of an ip address if unreachable then it calls to commit the changes so when this condition was not met, the issue was not reproduced.