The validate and deploy button appears after deployment has already started
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
To start a deployment you click on "Validate and Deploy" button in the deployment page, and then click on "Deploy" in the deployment dialog. You then have to wait about 30 seconds for deployment to begin and the progress bar to appear in the deployment page.
While you wait for the progress bar to appear, for a brief second, the "Validate and Deploy" button appears back on the deployment page and it may look like deployment failed to start. The "deployment in progress" progress bar then takes over and the button finally gets removed, so most users would probably never even notice the bug, but...
For the Selenium automation this might fail the test. If we happen to be checking the GUI at that brief second that the button re-appeared on the screen, we think that deployment was canceled.
| Changed in tripleo: | |
| status: | New → Triaged |
| milestone: | none → ocata-3 |
| Changed in tripleo: | |
| importance: | Undecided → Medium |
| milestone: | ocata-3 → pike-1 |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
| 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 |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
| Emilien Macchi (emilienm) wrote Cleanup EOL bug report | #1 |
| Changed in tripleo: | |
| importance: | Medium → Undecided |
| status: | Triaged → Expired |
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE