Changes for page 212 - Failover Fiesta
Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 321.1
edited by Carlijn Kokkeler
on 2023/12/21 15:01
on 2023/12/21 15:01
Change comment:
There is no comment for this version
To version 317.1
edited by Carlijn Kokkeler
on 2023/12/21 14:45
on 2023/12/21 14:45
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -5,17 +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 -//__Deployment execution error message__// 16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up. 17 17 18 -== **Overviews** == 12 +== **Feedback Items** == 13 + 19 19 //__Runtime overview__// 20 20 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. 21 21 ... ... @@ -26,15 +26,6 @@ 26 26 27 27 [[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 28 28 29 -//__Runtime restart or redeploy overview__// 30 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes. 31 - 32 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 33 - 34 - 35 -== **Feedback Items** == 36 - 37 - 38 38 //__Breaking changes pop-up__// 39 39 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'. 40 40 ... ... @@ -49,7 +49,11 @@ 49 49 //__Runtime image version__// 50 50 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. 51 51 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. 52 52 41 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 42 + 53 53 == **Bug Fixes** == 54 54 55 55 //__Message throughput__// ... ... @@ -58,9 +58,18 @@ 58 58 //__Cloud template upgrade unjust rollback__// 59 59 An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks. 60 60 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 + 61 61 //__Next generation block__// 62 62 Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model. 63 63 60 +//__Deployment execution error message__// 61 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up. 62 + 64 64 == **Fancy Forum Answers** == 65 65 66 66 As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers: