Lines Matching refs:log

25     [Documentation]  Check event log after BMC rebooted.
40 [Documentation] Check event log after host has booted.
61 [Documentation] Delete Redfish event log and verify via Redfish.
107 # "Id": "1", <----- Event log ID
131 # After issuing Redfish purge event log, there will be one informational error log
132 # in BMC with ID 1. Due to this the newly generated error log would have ID as 2.
133 Should Be Equal ${elogs[0]["Id"]} 2 msg=Event log entry is not 2
137 [Documentation] Reboot BMC and verify event log.
186 # The event log generated is associated with the epoc time and unique
196 … [Documentation] Verify modified field of error log is updated when error log is marked resolved.
202 # Wait for 5 seconds after creating error log.
205 # Mark error log as resolved by setting it to true.
210 # Example error log with resolve field set to true:
227 # Difference created and modified time of error log should be around 5 seconds.
263 [Documentation] Create an event log and delete it.
299 [Documentation] Trigger watchdog timed out and verify event log generated.
335 [Documentation] Verify event log entries wraps when 200 max cap is reached.
338 # Restarting logging service in order to clear logs and get the next log
360 # Create event log and verify the entry ID, ${max_num_event_logs + 1}.
371 # Event log 1 should be wrapped.
377 ... msg=The event log should have wrapped such that entry ID 1 is now purged.
381 [Documentation] Verify the Resolve field status is false for an error log from Redfish.
387 # Check resolve field value of created error log.
442 [Documentation] Event log entries should not exist.
445 Should Be Empty ${elogs} msg=System event log entry is not empty.
449 [Documentation] Event log entries should exist.
452 Should Not Be Empty ${elogs} msg=System event log entry is not empty.
456 [Documentation] Verify watchdog event log content.
484 [Documentation] Check if the give log entry matches specific watchdog error.
488 # elog Error log entry dictionary data.
493 ... msg=Watchdog timeout event log was not found.