Skip to content

4.19 release notes #508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: 4.19
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 33 additions & 1 deletion source/releasenotes/about.rst
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,13 @@
What's New in |release|
=======================

Apache CloudStack |release| is a 4.19 LTS minor release with over 170 fixes
Apache CloudStack 4.19.3 is a minor release with a limited number of
assorted fixes.

What's New in 4.19.2
====================

Apache CloudStack 4.19.2 is a 4.19 LTS minor release with over 170 fixes
and improvements including prior releases this tallies up to over 480 since
the 4.19.0.0 release. Some of the highlights include:

Expand Down Expand Up @@ -71,6 +77,32 @@ https://docs.cloudstack.apache.org/en/4.19.0.0/releasenotes/changes.html

.. _guestosids

Issues with ISO/config drive on Xcpng/Xen
=========================================

A fix was created for Xen like systems to work with config drive. (see
https://github.com/apache/cloudstack/pull/10912) This had been broken
for multiple releases, and passed unnoticed. There are some
limitations to this fix. Noticably:

- When attaching an ISO, the new ISO is attached as the first ISO (the existing configdrive ISO is detached),
- Creating a VM from ISO on a network with ConfigDrive, is not expected to work (untested),
- `userdata` functionality using config drive doesn't work.

When upgrading from a new 4.19 installation
===========================================

Only new installations of 4.19.x will not have conservemode enabled by
default vor VPCs. Upgrades from earlier versions will be alright. In
order to make sure conserve mode is enabled for VPC-tiers, either
create a clone of the default guestnetwork offering with conservemode
enabled or execute the following sql:

::
-- Re-apply VPC: update default network offering for vpc tier to conserve_mode=1 (#8309)
UPDATE `cloud`.`network_offerings` SET conserve_mode=1 WHERE name='DefaultIsolatedNetworkOfferingForVpcNetworks’;


Possible Issue with volume snapshot revert with KVM
===================================================

Expand Down