The deployment count parameters change back if you're too fast
Bug #1699773 reported by
Udi Kalifon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
If you decrement and increment the deployment counter on one of the roles faster than the message "Parameters updated" can appear - the counter will go back to the value it had a second ago when the update process began.
To recreate:
1) Quickly decrement one of the counters to 0 and increment it back to 1 again
=> The message "Parameters updated" appears, and the counter rolls back to the value 0 :)
| Changed in tripleo: | |
| status: | New → Triaged |
| milestone: | none → pike-3 |
| importance: | Undecided → Medium |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in tripleo: | |
| milestone: | queens-1 → queens-2 |
| Changed in tripleo: | |
| milestone: | queens-2 → queens-3 |
| Changed in tripleo: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in tripleo: | |
| milestone: | queens-rc1 → rocky-1 |
| Changed in tripleo: | |
| milestone: | rocky-1 → rocky-2 |
Revision history for this message
| Udi Kalifon (ukalifon) wrote | #1 |
| Changed in tripleo: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
The behaviour described in this bug won't happen any more, so the bug can be closed. Today, the user gets a "save" button after changing the counters, so only 1 save is made after all the changes are inputted without risking race conditions.