Description of problem: When the Node boots to stand-alone mode the user is given the option to configure a persistent logging partition and specify the max size of the logs. However, on reboot all logs (for example the setup/boot logs) are not saved so there is no way to do any troubleshooting after the first boot. In addition, the /var/log partition should probably be bind mounted to the logging partition on the persistent disk. For /config we bind mount selective files but for logging we should probably just bind mount the entire /var/log directory so that we don't need to individually bind mount files. Version-Release number of selected component (if applicable): 0.97-0 How reproducible: Steps to Reproduce: 1. boot node via USB disk using ovirt_standalone mode 2. configure node to use local disk for logging 3. configure log size to be 1000k or so 4. continue to exit firstboot 5. logs are in /var/log for all ovirt setup tasks 6. reboot the node Actual results: setup logs are not persisted because /var/log is not persisted to the logging partition Expected results: all logs should be persisted if the user elects to have a persistent log partition Additional info:
Please see the patch in https://www.redhat.com/archives/ovirt-devel/2009-January/msg00093.html The patch will mount the local logging partition if it exists, and backs up the current log files into /var/log-backups. There is one hole, and that is on the initial boot. if the user does the following: 1. boot node via USB disk using ovirt_standalone mode 2. configure node to use local disk for logging 3. configure log size to be 1000k or so 4. configure the disk partitioning 5. continue to exit firstboot 6. logs are in /var/log for all ovirt setup tasks 7. reboot the node Then the logs are lost. The way to to ensure that the data is not lost is to configure the disk partitioning, then reboot, then continue the configuration.