Is it platform specific
generic
Importance or Severity
Critical
Description of the bug
The case test_ro_disk set read-only mode. After case finish, execute reboot to restore to RW mode.
Sometimes after reboot the /var/log/syslog is not generated (the current case will not fail), which affects other cases and break loganalyzer. The issue is not always reproduced
CMD: logrotate --force /etc/logrotate.d/rsyslog
STDERR:
error: stat of /var/log/syslog failed: Bad message
du: cannot access '/var/log/syslog': Bad message
du: cannot access '/var/log/swss/sairedis.rec.2.gz': Bad message
error: error renaming /var/log/swss/sairedis.rec.2.gz to /var/log/swss/sairedis.rec.3.gz: Bad message
logrotate_script: 10: [: -gt: unexpected operator
There was a fix about this issue (#12913), but can not avoid the issue. Create this github issue to track
Steps to Reproduce
Run test case test_ro_disk
Actual Behavior and Expected Behavior
File /var/log/syslog generate success after case finish
Relevant log output
Output of show version
Attach files (if any)
No response
Is it platform specific
generic
Importance or Severity
Critical
Description of the bug
The case
test_ro_diskset read-only mode. After case finish, execute reboot to restore to RW mode.Sometimes after reboot the
/var/log/syslogis not generated (the current case will not fail), which affects other cases and break loganalyzer. The issue is not always reproducedThere was a fix about this issue (#12913), but can not avoid the issue. Create this github issue to track
Steps to Reproduce
Run test case
test_ro_diskActual Behavior and Expected Behavior
File /var/log/syslog generate success after case finish
Relevant log output
Output of
show versionAttach files (if any)
No response