Release Date: 30/Jul/2019
Bug
[SCALRCORE-12670] - VMware > Additional storage hot resize on Windows (requires Scalr Agent ≥ v7.15.3)
[SCALRCORE-12967] - VMware > Customization task never completes when it failed with error
[SCALRCORE-13077] - Azure > Servers provisioning stuck when added and linked identical credentials more than once
[SCALRCORE-12930] - UI > Farm designer > Save issue in not allowed LightsOut frame
[SCALRCORE-12945] - UI > Account > Users > Invalid Farm Ownership check
[SCALRCORE-12960] - UI > Accounts > Wrong redirect after account creation (since 7.14.7)
[SCALRCORE-13064] - UI > Azure & AWS > Remove Disk Size Default value
[SCALRCORE-13093] - UI > Service Catalog offering ACL issue
[SCALRCORE-13040] - Installer > scalr-server-ctl reconfigure > changes to scalr-server.rb are not being set correctly in config.yml
[SCALRCORE-13047] - Openstack > OTC > Selected Server Group is not applied for created instances
[SCALRCORE-13053] - Core > Azure Resource group name is not available as system GV in orchestration and webhooks
[SCALRCORE-13054] - Core > Fatmouse > If agent's rabbitmq user permissions somehow get lost, agent.reconfigure doesn't restore them
[SCALRCORE-12998] - Core > Upgrade to 7.15.4 failing (NO_ZERO_IN_DATE issue for some platforms)
[SCALRCORE-13086] - Cost > Imported servers not reporting correctly in cost analytics
[SCALRCORE-13068] - Core > Sanitize non-utf8 characters in `css` and `projects` database tables
[SCALRCORE-13074] - AWS > Add support for m5a.* instance types
[SCALRCORE-13080] - AWS > Add support for m5ad.* instance types
[SCALRCORE-13083] - AWS > Add support for m5d.* instance types
[SCALRCORE-13084] - AWS > Add support for r5a.*, r5ad.* instance types
[SCALRCORE-13029] - AWS > Add support for m5.8xlarge, m5.16xlarge, r5(d).8xlarge, r5(d).16xlarge instance types in canada central
Sync AWS t3a.*, c5n.*, i3en.* instance types which became available recently in new cloud locations
Release Date: 16/Jul/2019
Bug
[SCALRCORE-12896] - UI > Service Catalog > Auto-fetch VMware storage diskObjectId
[SCALRCORE-12394] - UI > Farm designer > Policy cloud.networks issue when select VPC Router
[SCALRCORE-12916] - UI > Policy with role tag > vmware.storage.provisioning_type policy not being enforced
[SCALRCORE-12910] - Azure > Snapshot creation errors: source disk is not displayed and dialog box does not disappear
[SCALRCORE-12914] - VMware > Servers fail to build under some circumstances (since 7.15.0)
[SCALRCORE-12952] - VMware > Unable to provision virtual machine against datastore cluster (since 7.15.4)
[SCALRCORE-11306] - VMware > Long delay between RequestHostname webhook and AllocateIP webhook (Change in behavior)
[SCALRCORE-12801] - Add proxy support for Service Catalog -> farm template fetch
1. Change in behavior
Before: IPs were requested from remote IP Pool AFTER VM launch on VMware
After: IPs will be requested from remote IP Pool BEFORE VM launch on VMware and AFTER RequestHostname call
Release Date: 04/Jul/2019
Bug
[SCALRCORE-12730] - OTC > Issue w/ Availability zone determining in Distribute Equally mode
[SCALRCORE-12865] - VMware > some farms stuck in pending when deploying server (Affected version 7.14.0)
[SCALRCORE-12895] - VMware > Servers Don't Move Out of "Provision Server in Cloud Platform" (since 7.15.0)
[SCALRCORE-12822] - AWS > New instance types c5.12xlarge, c5.24xlarge, c5.metal
[SCALRCORE-12867] - AWS > Spot instance pricing is incorrect
[SCALRCORE-12841] - AWS > EMR Support for the latest version (5.24)
[SCALRCORE-12764] - Core > ZMQ Services > Cloud Resource Poller > mysqli error: 1062: Duplicate entry 'i3-s-FXP' for key 'PRIMARY'
[SCALRCORE-12742] - Core > Enhancement to environment cloning script
[SCALRCORE-12817] - Core > Hostname webhook sends to requests, second always fails with "hostname is already set"
[SCALRCORE-12771] - UI > Image replace > Not all used images listed for autoreplace
[SCALRCORE-12806] - UI > AWS > RDS > Add GovCloud support for Aurora
[SCALRCORE-12780] - Cost Analytics > AWS Gov Cloud account billing corrections
[SCALRCORE-12843] - Kubernetes > Field Bearer token issue