-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #437 from GrahamDumpleton/2.7.x-backport-fixes
Backport fixes for workshop environment state getting stuck.
- Loading branch information
Showing
6 changed files
with
61 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
Version 2.7.2 | ||
============= | ||
|
||
Upcoming Changes | ||
---------------- | ||
|
||
For details on significant changes in future versions, including feature | ||
deprecations and removals which may necessitate updates to existing workshops, | ||
see [Upcoming changes](upcoming-changes). | ||
|
||
Bugs Fixed | ||
---------- | ||
|
||
* A workshop environment could technically get stuck in `STARTING` state as seen | ||
by the training portal if the kopf operator framework coalesced events for | ||
`ADDED` and `MODIFIED` together and only reported a single `ADDED` event. This | ||
is because the training portal was only looking for a `MODIFIED` event. Thus | ||
it could miss when the workshop details were updated in `WorkshopEnvironment` | ||
and so not mark the workshop environment as `RUNNING`. | ||
|
||
* It was not possible through the training portal admin pages to forcibly | ||
refresh a workshop environment that was stuck in `STARTING` state. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters