Known issues and limitations

Version 22.02

NK-3883 Cannot modify ASG max capacity via UI

When attempting to modify the ASG max capacity or desired capacity using the zCompute UI, validation begins on the first entered digit and can throw an error. For example, on changing the value from 20 to 30, on entering the “3” the UI displays an error indicating that the new max capacity value is lower than the current value (3 is less than 20). For example:

modify-asg-ki-nk-3883-via-ui

This issue occurs only when modifying the max or desired capacity in the UI, but the symp CLI is not affected. If the max or desired capacity is updated via the CLI, then the UI will display the correct updated value. For example:

modify-asg-ki-nk-3883-via-cli

NK-3153 Clusters with a mix of standard and premium instance types unsupported

There is no support yet for zCompute clusters with a mix of standard and premium instance types.

NK-2557 Data on NVMe disks is not deleted before VM start

Currently these instance types are only suitable for private clouds.

NK-1106 Data volume should be deleted explicitly by users

zCompute does not offer a checkbox to delete VM data volumes. The VM delete dialog clearly states that data volumes must be deleted by users.

NK-3835 zCompute Toolbox Fedora shows the old version for members in the Marketplace

This means that tenants will still continue to download the older version if using the Marketplace. Instead look for a pre-downloaded image in the image list. If it’s not there, please ask Zadara ops or your cloud administrator to download it for you and make it publicly available in the system.

NK-4055 zCompute Toolbox Fedora is missing the Symp offline pip dependencies

This means that the python dependencies installation requires you to be online (internet) when running symp-update.

NK-2921 Getting Action Failed status creating listener in ALB

Getting an Action Failed status when trying to create a listener in the ALB on an cluster upgraded to version 22.02-SP1, but with the previous LBAAS engine.

Workaround: Upgrade the LBAAS engine before creating a new load balancer.

NK-3247 zCompute load balancer service officially supports Terraform 2.47

Terraform AWS Provider versions higher than 3.33 fail on LBAAS ARN validation.

Important

The new action types are applicable only after a cluster is upgraded to version 22.02.1, and then the load balancer engine is upgraded.

After your zCompute account has been upgraded, all new load balancer instances will be created using the new engine image. The upgrade of already running load balancer instances is opt in. Users should upgrade their existing load balancer in order to receive the new functionality.

load-balancer-upgrade

The new load balancer target-group types (fixed-response, redirect) in older images are not supported and require upgrade.

NK-3786: Terraform not supported for custom policies

Terraform is not supported at the moment, since it uses a the AWS CreatePolicyVersion API, which is not supported.

Creation of new policies via APIs only (no GUI)

Creation of a new policy is only available via APIs and not from the GUI. Once the new policy has been created, the admin can apply it to users using the GUI.

Creation of direct subnet with desired MTU not possible in GUI

It is not possible to create a direct subnet in the GUI with desired MTU. However, the MTU can be updated post-creation.

Version 21.10

NK-2476 Download image from URL with Let’s Encrypt certificate will fail

The trusted certificate store holds a recently expired Let’s Encrypt root certificate. This may be amended per cloud, per customer request, and will be fixed on the next release for all the clouds.

NK-2169 When using Cloud Base Init, user can’t retrieve the Windows Admin password for remote connection

This is caused by an internal race in the update of the metadata service.

Workaround:

Either don’t use Cloud Base Init to create images, or add a startup script that will accept the initial admin password as user data and set it for the user.

NK-1873 DR: In order to restore a VM the user has to have admin role on the destination project

A user must have an admin or an MSP admin role in order to create a local snapshot from a remote snapshot. A bug has been created where the user needs to have an admin role in the destination project in order to restore a VM to that project. Ideally, the admin should be able to restore into a selected project without having a role on the project.

NK-1903 DR: No indication to user when a remote snapshot is ready

The DR metadata is written immediately to the NFS share while the actual snapshot mirror depends on when the VPSA has finished the transfer. The result is that the user may see a snapshot as ready on the remote site while a restore is not possible yet. Trying to restore the VM will lead to volume error which can be force deleted.

Workaround: Restore from snapshot N-1 or retry later if the original system is still active.

NK-1788 Some attributes are missing when creating an AMI image from a restored VM

When creating an image from a VM that was restored from a VM snapshot, the new image is missing some attributes. Specifically, it is missing the bus_type and disk type. The implication is that any VM created from the image VM won’t boot.

Workaround: Do not create images from a restored VM. Create the image from the volume snapshots.

NK-753 Tenant admin unable to see resources of all projects in the account

Tenant admins can create projects and assign users, but are unable to see the resources of these projects unless they give themselves an admin role on the project. This makes the account summary inaccurate, since only the resources from the current project are counted. In this image, you can see an empty project:

empty-project

While in this image, at the account level you can only see the default VPC resources from the first project:

default-resources

NK-1751 DR: Raise an error event when failed to create vm-snapshot

Currently if the system fails to create a VM-snapshot during the asynchronous part of the flow, no indication is given to the user.

Known issues and limitations introduced in R7

  • NK- 1582 - Placing a VM and it’s volumes into the same protection group causes some snapshots to go into error state

  • NK-1285, NK-1282 - Mirror is not cleaned when detaching a volume from a VM or removing an entity from a protection group

Known issues and limitations introduced in R5

  • NK-1076 - Reset password for predefined users in disabled accounts succeeds but the message claims failure

  • NK-1082 - There is no export to CSV on Monitoring → Events

  • NK-1115 - Windows VM may get data corruption if rebooted from the system

Known issues and limitations introduced in R4

  • NK-817 - Delete a NAT gateway fails with an error that resources could not be deleted due to dependencies/network associations/routes/etc. User must first delete the route to the NAT GW in the route table.

  • NK-831 - Deletion of ENI is not possible from the GUI

Known issues and limitations introduced in R3

  • NK-648 - Load Balancer creation menu allows selection of elastic IP that belong to an instance without a warning

  • NK-661 - Basic event filters do not work. Use the advanced mode instead (Click more filters)

Known issues and limitations introduced in previous releases

  • NK-234 - Direct-network is not listed as route in route-table. When creating a direct subnet, a route is added for local traffic but it is not displayed in the route table.

  • NK-502 - Restoring snapshot of VM always done to the default pool, even if the VM disks are not on that pool or the user explicitly selects a different pool.