Browse Source
When not using swift with the redfish virtual media boot interface, in other words local file storage, the file permissions for the /httpboot/redfish folder was incorrect upon initially being created, and new file ISOs were being created with permissions based upon the conductor process umask value which is OS environment dependent. Change-Id: I038ca335efa9b5443469ab8c8af12863deea0e38 (cherry picked from commitchanges/83/818183/2af6cd1093d
) (cherry picked from commitb1c8976d4b
)
4 changed files with 45 additions and 5 deletions
@ -0,0 +1,25 @@
|
||||
--- |
||||
upgrade: |
||||
- | |
||||
Operators may need to check their ``/httpboot/redfish`` folder permissions |
||||
if using ``redfish-virtual-media``. The conductor was previously creating |
||||
the folder with incorrect permissions. |
||||
- | |
||||
A permission setting has been added for ``redfish-virtual-media`` boot |
||||
interface, which allows for explicit file permission setting when the |
||||
driver is being used. The default for the new ``[redfish]file_permission |
||||
setting is ``0u644``, or 644 if manually changed using ``chmod`` on the |
||||
command line. Operators MAY need to adjust this if they were running the |
||||
conductor with a specific ``umask`` to work around the permission setting |
||||
defect. |
||||
fixes: |
||||
- | |
||||
Fixes the ``redfish-virtual-media`` and related based drivers to utilize |
||||
an explicit file permission instead of rely upon the ironic-conductor |
||||
umask, which may be incorrect. This can be tuned with the |
||||
``[redfish]file_permission`` setting. |
||||
- | |
||||
Fixes an issue where the default folder permission for the |
||||
``redfish-virtual-media`` driver where the folder permissions for the |
||||
``/httpboot/redfish`` folder was being created with incorrect |
||||
permissions. |
Loading…
Reference in new issue