Actions
Bug #9548
closedcompute profile storage allocation does not change with {none, size, full} button selections
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - libvirt
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1186863
Description of problem:
When creating a new compute profile for a libvirt instance, the Storage section for the Allocation text box does not change when depressing the Full button. The compute profile must first be saved and then reopened for editing. Then the Full button must be depressed again for the value to change from 0G to a positive value. This also can be unreliable. There are combination of depressing the button that can get the value out of sync and go back to 0G and then get stuck at 0G again until you save and reopen for editing.
See screenshot attached.
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2205 added
- Pull request deleted (
)
Updated by Dominic Cleal over 9 years ago
- Category set to Compute resources - libvirt
Updated by Dominic Cleal over 9 years ago
- Translation missing: en.field_release set to 28
Updated by Shimon Shtein over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset fe8b40825eb0e5ddde14d53d8634a6fe6f642340.
Actions