Actions
Bug #36588
closedhammer settings set returns incomplete message for False values
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2221673
Description of problem:
hammer settings set returns incomplete message when setting some boolean with False value.
Version-Release number of selected component (if applicable):
6.14.0 snap 6
How reproducible:
always
1. Try to set some (no matter which) boolean setting to False:
- hammer settings set --name db_pending_seed --value 0
Actual results:
Setting [db_pending_seed] updated to [].
Expected results:
Setting [db_pending_seed] updated to [false].
Works fine for True values
- hammer settings set --name db_pending_seed --value False
Setting [db_pending_seed] updated to []. - hammer settings set --name db_pending_seed --value false
Setting [db_pending_seed] updated to []. - hammer settings set --name db_pending_seed --value 0
Setting [db_pending_seed] updated to [].
- hammer settings set --name db_pending_seed --value True
Setting [db_pending_seed] updated to [true]. - hammer settings set --name db_pending_seed --value true
Setting [db_pending_seed] updated to [true]. - hammer settings set --name db_pending_seed --value 1
Setting [db_pending_seed] updated to [true].
Updated by Oleh Fedorenko over 1 year ago
- Status changed from New to Assigned
- Assignee set to Oleh Fedorenko
- Triaged changed from No to Yes
Updated by The Foreman Bot over 1 year ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/hammer-cli/pull/371 added
Updated by The Foreman Bot over 1 year ago
- Fixed in Releases hammer-cli-3.8.0 added
Updated by Oleh Fedorenko over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset 464f5942c1768b1449fd52b6591dd59d6114b6a7.
Actions