Description of problem:
When trying to change a setting which is read-only using CLI (hammer), the first attempt prints a message that the setting was updated successfully and returns 0, although the setting is not modified.
How reproducible:
sometimes (first attempt)
Is this issue a regression from an earlier version:
no
Steps to Reproduce:
- Pick some read-only setting (e.g. websockets_encrypt)
- Attempt to change it (hammer settings set --name websockets_encrypt --value false)
Actual behavior:
# hammer settings set --name websockets_encrypt --value false Setting [websockets_encrypt] updated to [true]. # echo $? 0 # hammer settings set --name websockets_encrypt --value false Could not update the setting: Setting is marked as readonly # echo $? 70 # hammer settings info --name websockets_encrypt Id: websockets_encrypt Name: websockets_encrypt Description: VNC/SPICE websocket proxy console access encryption (websockets_ssl_key/cert setting required) Category: Authentication Settings type: boolean Value: true
Expected behavior:
Any attempt to change read-only value should return a message that it's not possible and return a non-zero value.
Business Impact / Additional info:
Only the first attempt is accompanied by this error. There might be some retention (cache), but I was not yet able to resolve how to "reset" it.
Discovered with Satellite stream snap 111 @RHEL9.6, same behavior with older Satellite versions (e.g. 6.16)