Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 319.1
edited by Carlijn Kokkeler
on 2023/12/21 14:50
Change comment: There is no comment for this version
To version 317.1
edited by Carlijn Kokkeler
on 2023/12/21 14:45
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,14 +5,12 @@
5 5  
6 6  **Hi there, eMagiz developers!**
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
8 +== **TBD** ==
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
14 14  
15 -== **Overviews** ==
11 +
12 +== **Feedback Items** ==
13 +
16 16  //__Runtime overview__//
17 17  We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
18 18  
... ... @@ -23,15 +23,6 @@
23 23  
24 24  [[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
25 25  
26 -//__Runtime restart or redeploy overview__//
27 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
28 -
29 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
30 -
31 -
32 -== **Feedback Items** ==
33 -
34 -
35 35  //__Breaking changes pop-up__//
36 36  Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
37 37  
... ... @@ -46,7 +46,11 @@
46 46  //__Runtime image version__//
47 47  The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
48 48  
38 +//__Runtime restart or redeploy overview__//
39 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
49 49  
41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
42 +
50 50  == **Bug Fixes** ==
51 51  
52 52  //__Message throughput__//
... ... @@ -55,6 +55,12 @@
55 55  //__Cloud template upgrade unjust rollback__//
56 56  An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
57 57  
51 +//__Missing log entries__//
52 +We improved crash handling so that log messages clearly show when and why a container failed to start.
53 +
54 +//__Runtime logging__//
55 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
56 +
58 58  //__Next generation block__//
59 59  Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
60 60