Update some releasenotes for 19.1 release
Change-Id: I9fe5cd295df33dd3af9bcbdc3fc5f35bd0c6df1b
This commit is contained in:
parent
66b4f59623
commit
cfa47c54b9
@ -3,5 +3,5 @@ fixes:
|
||||
- |
|
||||
Fixes hardware type ``redfish`` RAID interface deploy steps when completion
|
||||
requires rebooting system for non-immediate configuration application.
|
||||
Prior to this fix such nodes would remain in ``wait call-back`` state
|
||||
Prior to this fix, such nodes would remain in ``wait call-back`` state
|
||||
indefinitely.
|
||||
|
@ -2,5 +2,5 @@
|
||||
fixes:
|
||||
- |
|
||||
Fixes the determination of a failed RAID configuration task in the
|
||||
``redfish`` hardware type. Prior to this fix the tasks that have failed
|
||||
``redfish`` hardware type. Prior to this fix, the tasks that have failed
|
||||
were reported as successful.
|
||||
|
@ -1,7 +1,9 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
Updates ``idrac-redfish`` management interface export configuration step
|
||||
to not export iDRAC BMC connection settings to avoid overwriting those
|
||||
in another system when using unmodified configuration mold in import step.
|
||||
For import step it is still possible to add these settings back manually.
|
||||
Now the export configuration step from the ``idrac-redfish``
|
||||
management interface does not export iDRAC BMC connection
|
||||
settings to avoid overwriting those in another system when
|
||||
using unmodified configuration mold in import step.
|
||||
For import step it is still possible to add these settings
|
||||
back manually.
|
||||
|
Loading…
Reference in New Issue
Block a user