| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 108.out | 13 The following inconsistencies were found and repaired:
37 The following inconsistencies were found and repaired:
54 The following inconsistencies were found and repaired:
71 The following inconsistencies were found and repaired:
87 The following inconsistencies were found and repaired:
103 The following inconsistencies were found and repaired:
121 The following inconsistencies were found and repaired:
143 The following inconsistencies were found and repaired:
184 The following inconsistencies were found and repaired:
|
| H A D | 060.out | 47 The following inconsistencies were found and repaired:
83 The following inconsistencies were found and repaired:
198 The following inconsistencies were found and repaired:
220 The following inconsistencies were found and repaired:
240 The following inconsistencies were found and repaired:
262 The following inconsistencies were found and repaired:
277 The following inconsistencies were found and repaired:
306 The following inconsistencies were found and repaired:
325 The following inconsistencies were found and repaired:
356 The following inconsistencies were found and repaired:
[all …]
|
| H A D | 261.out | 57 The following inconsistencies were found and repaired:
194 The following inconsistencies were found and repaired:
221 The following inconsistencies were found and repaired:
250 The following inconsistencies were found and repaired:
352 The following inconsistencies were found and repaired:
|
| H A D | 070.out | 11 The following inconsistencies were found and repaired:
|
| H A D | 217.out | 35 The following inconsistencies were found and repaired:
|
| H A D | 214.out | 24 The following inconsistencies were found and repaired:
|
| H A D | 039.out | 32 The following inconsistencies were found and repaired:
|
| H A D | 214 | 87 # This can be repaired by qemu-img check by increasing the refcount of
|
| H A D | 112.out | 135 The following inconsistencies were found and repaired:
|
| H A D | 108 | 4 # Test case for repairing qcow2 images which cannot be repaired using
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | parallels-checks.out | 23 The following inconsistencies were found and repaired:
51 The following inconsistencies were found and repaired:
122 The following inconsistencies were found and repaired:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/HardwareIsolation/ |
| H A D | Entry.interface.yaml | 29 the isolated hardware is repaired or replaced. Setting this to "true"
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NICTA-1.0 | 57 iv. the payment of the cost of having the goods repaired; or
|
| H A D | CC-BY-3.0-AU | 98 * the payment of the cost of having the goods repaired; or
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | LogService.v1_8_1.json | 59 …sponding to user actions. Finally, an entry showing the fan failure is repaired with `FanRestored…
60 …repaired status, but automatically clears other entries within the same `EventGroupId`. For examp…
|
| H A D | LogEntry.v1_20_0.json | 553 … "description": "Indicates if the cause of the log entry has been resolved or repaired.",
554 …try has been resolved or repaired. The value `true` shall indicate if the cause of the log entry …
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | LogService.v1_8_1.json | 59 …sponding to user actions. Finally, an entry showing the fan failure is repaired with `FanRestored…
60 …repaired status, but automatically clears other entries within the same `EventGroupId`. For examp…
|
| H A D | LogEntry.v1_20_0.json | 553 … "description": "Indicates if the cause of the log entry has been resolved or repaired.",
554 …try has been resolved or repaired. The value `true` shall indicate if the cause of the log entry …
|
| /openbmc/qemu/block/ |
| H A D | qed-check.c | 201 * Mark an image clean once it passes check or has been repaired
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | environmental_message_registry.hpp | 117 "Indicates that a fan was repaired or restored to normal operation.",
165 "Indicates that a filter was repaired or restored to normal operation.",
992 "Indicates that a pump was repaired or restored to normal operation.",
|
| H A D | sensor_event_message_registry.hpp | 275 …"Indicates that a sensor was repaired or communications were restored. It may also indicate that …
|
| /openbmc/docs/designs/ |
| H A D | guard-on-bmc.md | 130 - Used to indicate whether guarded hardware is repaired or replaced.
|
| H A D | vpd-collection.md | 102 in scenarios where the FRU containing the system VPD is repaired in the field.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | LogService_v1.xml | 834 <Annotation Term="OData.LongDescription" String="This value shall indicate this log service retains the entries containing the original cause and the final resolution, but automatically clears other entries containing the intermediate results within the same `EventGroupId`. For example, the original cause of a fan failure is indicated by an entry containing the `FanFailed` message key in the `MessageId` property, followed by the entries containing `FanRemoved` and `FanInserted` message keys corresponding to user actions. Finally, an entry showing the fan failure is repaired with `FanRestored` message key in the `MessageId` property. In this case, the entries with `FanFailed` and `FanRestored` message keys are retained, but other entries within the same `EventGroupId` are automatically cleared."/>
838 <Annotation Term="OData.LongDescription" String="This value shall indicate this log service updates the entry containing the original cause for the repaired status, but automatically clears other entries within the same `EventGroupId`. For example, the original cause of a fan failure is indicated by an entry containing `FanFailed` message key in the `MessageId` property, followed by the entries containing `FanRemoved` and `FanInserted` message keys corresponding to user actions. Finally, an entry showing the fan failure is repaired with `FanRestored` message key in the `MessageId` property. In this case, the entry with `FanFailed` message key is updated to show the repaired status, such as updating the value of Resolved property to `true` and the timestamp contained by the `Modified` property, but other entries within the same `EventGroupId` are automatically cleared."/>
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | LogService_v1.xml | 834 …sponding to user actions. Finally, an entry showing the fan failure is repaired with `FanRestored…
838 …repaired status, but automatically clears other entries within the same `EventGroupId`. For examp…
|