Update-OVServerProfile failing to update any component

[KeithS011]

Expected Behavior

When Running Update-OVServerProfile -SANStorage -Connections -Reapply -Confirm:$False
Server Profile should update these components without issue or error.

ps>$Profile = "servername"
ps>$b = Get-OVServerProfile -Name $Profile | Update-OVServerProfile -SANStorage -Connections -Reapply -Confirm:$False

ps>$b

Appliance     Name    Owner      Created                            Duration   TaskState PercentComplete
servername  reapply    user       11/17/2023 10:15:04 AM 00:00:04       Error     100            

Actual Behavior

Fails due to not being powered off for firmware, even when firmware is not being selected in the update syntax, and firmware is not staged or pending otherwise.

ps> $b.taskErrors

data               : 
details            : 
errorCode          : ServerNotOffWithCauseForNoServerChange
errorSource        : 
message            : The requested changes cannot be applied because {"name":"<location>", "uri":"/rest/server-hardware/61323050-3931-584A-5133-3333301D3034"} is powered 
                     on and the changes made to the following sections can only be applied when the power is off: 
                     * Firmware
nestedErrors       : {}
recommendedActions : {Power off the server or adjust the settings and retry. {"name":"Learn more", "uri":"/doc#/cic/profiles/edit"}}

Steps to reproduce

ps>$Profile = "servername"
ps>$b = Get-OVServerProfile -Name $Profile | Update-OVServerProfile -SANStorage -Connections -Reapply -Confirm:$False
ps>$b.taskerrors

Version Information

HPEOneView.630 PoSH Module

Major  Minor  Build  Revision
-----  -----  -----  --------
6      30     3188   1900  


ApplianceVersion: 8.30.01.482646.00 6.30.3188.1900 


Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.14393
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[ChrisLynchHPE]

This is behaving by design. The Cmdlet will only generate a terminating error when the API rejects the attempted call (ex. malformed API call). You will need to monitor the returned async task for completion, success or failure.