commit | 494c6edb54d3f2d22f7e494820003540e3edf0b8 | [log] [tgz] |
---|---|---|
author | Tim Lee <timlee660101@gmail.com> | Wed Mar 18 17:17:27 2020 +0800 |
committer | Tim Lee <timlee660101@gmail.com> | Tue Mar 24 11:20:50 2020 +0800 |
tree | 1c2154202ef3f8e8dc309274280920aaf1b194a9 | |
parent | 4148f2eee6313068d3223871005160b2902abb18 [diff] |
Fix "Clear Oem Logs" functionality in System Logs Issue Symptom: 1. "Clear Oem Logs" button didn't show on webui when type select to "Oem". 2. "Clear Oem Logs" button was showed on then pressed with fix, but the function didn't work correctly. Event logs were deleted instead of Oem logs. Root cause: 1. getSystemLogs() always get Event logs by default no matter type be selected to "Oem". 2. clearSystemLogs() always clear Event logs by default no matter type be selected to "Oem". Solution: 1. According "recordType" to get Oem logs from uri: '/redfish/v1/Systems/' + DataService.systemName + '/LogServices/Crashdump/Entries' 2. According "selectedRecordType" to clear Oem logs by action: uri = '/redfish/v1/Systems/' + DataService.systemName + '/LogServices/Crashdump/Actions/LogService.ClearLog' Modified files: webui/app/common/services/api-utils.js webui/app/server-health/controllers/syslog-controller.html webui/app/server-health/controllers/syslog-controller.js Tested by: 1. In WebUI/Server health/System Logs, select system log type as "Oem", then click "Clear Oem Logs" button. The Oem logs (CPU Crashdump log) all were deleted. 2. Select system log type as "Event", then click "Clear Event Logs" button. The System Event Log all were deleted. Signed-off-by: Tim Lee <timlee660101@gmail.com> Change-Id: I2a3d42a61f53df84b88585cf7c65a10688eaef05
The OpenBMC WebUI is a Web-based user interface for the OpenBMC firmware stack. The WebUI uses AngularJS. Features include:
nodejs (>= 4.2.6) npm (>= 6.0.1)
Note The default installation of your Linux distro may not come with the required versions above. See the following for more information on updating:
https://docs.npmjs.com/troubleshooting/try-the-latest-stable-version-of-node https://docs.npmjs.com/troubleshooting/try-the-latest-stable-version-of-npm
npm install
Note This must be run from within the phosphor-webui git repository.
npm run-script server
This will start a server instance and begin listening for connections at http://localhost:8080
. This development server provides live reloading on code changes. NOTE: Browsing to https://<BMC>
and accepting the self-signed certificate might be required to prevent your browser from blocking traffic to the BMC.
Enter the BMC Host or BMC IP address, username, and password. The default username and password are root
/0penBmc
.
Note that some OpenBMC implementations use bmcweb for its backend. For security reasons, bmcweb will need to be recompiled and loaded onto the target BMC Host before the above redirect command will work. The option to turn on within bmcweb is BMCWEB_INSECURE_DISABLE_XSS_PREVENTION
. In order to test locally, you will also need to disable CSRF by turning on BMCWEB_INSECURE_DISABLE_CSRF_PREVENTION
.