Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Resolved Issues

 

These sections list the limitations that are resolved with Juke Multicloud Release 2.2.1 and Juke Multicloud Release 2.2.

Resolved Issues in Juke Multicloud Release 2.2.1

This section lists limitations that are resolved with Juke Multicloud Release 2.2.1.

  • JUKE-813 Storage replication—Cloud storage rules allow a maximum of 120 replicas (copies) of a storage volume to be taken. Currently there is no limit on the number of replicas that are taken. When more than 120 replicas are requested, the storage volume will fail to restart when the server is rebooted.

  • JUKE-814 Issue with user permissions—Users can view cloud providers that they have access to.

  • JUKE-816 Adding a node to a Kubernetes cluster—Once a Kubernetes node has been removed from a cluster, the node can not be added to the same cluster or another cluster.

    This issue has been resolved.

  • JUKE-822 Region not enabled on the Juke Multicloud UI —When the default VPS that is used on AWS is not present, Region is not enabled on the Juke Multicloud UI.

    This issue has been resolved.

  • JUKE-829 Issue with using Fedora and Debian images—LXC (Linux) containers that use Fedora and Debian images do not generate IP addresses.

    This issue has been resolved.

  • JUKE-830 – Issue with shared storage volume—Shared storage volume for containers that are located on different nodes affects other containers.

    This issue has been resolved.

  • JUKE-835 Issue with time-out option for on-prem nodes—The on-prem nodes call time-out option holds the call request for a long time.

    This issue has been resolved.

  • JUKE-836 Issue with handling error message for default cloud VPC

    This issue has been resolved.

  • JUKE-846 Issue with updating API calls when creating a security group on AWS

    This issue has been resolved.

  • JUKE-864 Netdata does not work on port 8001

    This issue has been resolved.

Resolved Issues in Juke Multicloud Release 2.2

This section lists limitations that are resolved with Juke Multicloud Release 2.2.

  • JUKE-597 Unable to access web pages from Juke Multicloud UI—Accessing certain web pages from the Juke Multicloud UI renders a 505 error message. This is due to a credential issue.

    This issue has been resolved.

  • JUKE-598 No admin cloud credentials required—A user can perform background tasks without entering admin cloud credentials.

    This issue has been resolved. The user has to enter admin cloud credentials in order to perform background tasks.

  • JUKE-600 Deletion of resources not updated in the database—When an admin user deletes resources such as a container or a cluster, the record is not updated in the database. This affects the other available resources.

    This issue has been resolved.

  • JUKE-602 Incorrect number of workloads displayed—An incorrect number of workloads is displayed on the dashboard.

    This issue has been resolved.

  • JUKE-626 Reading and writing storage volumes on the on-prem node—Users can not write or read storage volumes that are attached to containers on the on-prem node due to a permission issue.

    This issue has been resolved.

  • Removing left disk information from Juke FS cloud file system—When removing nodes that have disks attached to it, an API call is made to remove metadata from the Juke FS cloud file system. However, the API calls do not remove metadata completely.

    This issue has been resolved by deleting all metadata information when a node is removed.

  • JUKE-723 Issue when selecting a node—When a user has selected a node type in a group, a message is displayed asking the user to select at least one node type. This is due to a permission issue.

    This issue has been resolved.

  • JUKE-739 Unable to switch from a workload or a cluster—The user can not switch from one workload or cluster to another by selecting another workload or cluster from the list of options.

    This issue has been resolved.

  • JUKE-743 Permission to view nodes in a group—A use can only access nodes assigned to the group they belong to. For example, a user who is a part of GCP group cannot view nodes that are a part of AWS group. This is due to a permission issue.

    This issue has been resolved.

  • JUKE-754 Network API calls—Network API calls can not identify nodes by name.

    This issue has been resolved by identifying nodes by using the IP address of the node.

  • JUKE-772 AWS PEM file permissions—An API call with region name as the only parameters enables users to delete AWS PEM file for cloud regions that are not part of their user group.

  • JUKE-815 Assigning PEM for AWS—Admin can not assign PEM (private key) for different AWS user groups.

    This issue has been resolved.

  • JUKE-818 Deactivate region for AWS—Users can not deactivate a region for AWS.

    This issue has been resolved.