Azure Stack Hub 上的应用服务 Update 6 发行说明App Service on Azure Stack Hub update 6 release notes

这些发行说明介绍 Azure Stack Hub 上的 Azure 应用服务 Update 6 中的新功能、修复和已知问题。These release notes describe new features, fixes, and known issues in Azure App Service on Azure Stack Hub update 6. 已知问题分为两部分:与升级过程相关的问题,以及内部版本(安装后)的问题。Known issues are divided into two sections: issues related to the upgrade process and issues with the build (post-installation).

重要

请将 1904 更新应用于 Azure Stack Hub 集成系统,或部署最新的 Azure Stack 开发工具包 (ASDK),然后部署 Azure 应用服务 1.6。Apply the 1904 update to your Azure Stack Hub integrated system or deploy the latest Azure Stack Development Kit (ASDK) before deploying Azure App Service 1.6.

内部版本参考Build reference

Azure Stack Hub 上的应用服务 Update 6 的内部版本号为 82.0.1.50****。The App Service on Azure Stack Hub update 6 build number is 82.0.1.50.

先决条件Prerequisites

在开始部署之前,请参阅在 Azure Stack Hub 上部署应用服务的先决条件See Prerequisites for deploying App Service on Azure Stack Hub before you begin deployment.

开始将 Azure Stack Hub 上的 Azure 应用服务升级到 1.6 之前:Before you begin the upgrade of Azure App Service on Azure Stack Hub to 1.6:

  • 请确保所有角色在 Azure Stack Hub 管理员门户的 Azure 应用服务管理中处于“就绪”状态。Ensure all roles are ready in Azure App Service administration in the Azure Stack Hub administrator portal.

  • 在 Azure Stack Hub 管理员门户中使用应用服务管理来备份应用服务机密Backup App Service Secrets using the App Service Administration in the Azure Stack Hub Admin Portal

  • 备份应用服务和 master 数据库:Back up the App Service and master Databases:

    • AppService_Hosting;AppService_Hosting;
    • AppService_Metering;AppService_Metering;
    • master
  • 备份租户应用内容文件共享。Back up the tenant app content file share.

    重要

    云操作员负责文件服务器和 SQL Server 的维护和操作。Cloud operators are responsible for the maintenance and operation of the File Server and SQL Server. 资源提供程序不管理这些资源。The resource provider does not manage these resources. 云操作员负责备份应用服务数据库和租户内容文件共享。The cloud operator is responsible for backing up the App Service databases and tenant content file share.

  • 同步发布 Azure Stack Hub 市场的自定义脚本扩展版本 1.9.1**** ****。Syndicate the Custom Script Extension version 1.9.1 from the Azure Stack Hub Marketplace.

新功能和修复New features and fixes

Azure Stack Hub 上的 Azure 应用服务 Update 6 包含以下改进和修复:Azure App Service on Azure Stack Hub update 6 includes the following improvements and fixes:

  • 针对应用服务租户、管理员、函数门户和 Kudu 工具的更新****。Updates to App Service tenant, admin, functions portals, and Kudu tools. 与 Azure Stack Hub 门户 SDK 版本一致。Consistent with Azure Stack Hub portal SDK version.

  • Azure Functions 运行时更新到 v1.0.12299Updates Azure Functions runtime to v1.0.12299.

  • 针对核心服务的更新,用于提高可靠性和错误消息传递,以便更轻松地诊断常见问题。Updates to core service to improve reliability and error messaging enabling easier diagnosis of common issues.

  • 针对以下应用框架和工具的更新Updates to the following app frameworks and tools:

    • ASP.NET Core 2.2.4ASP.NET Core 2.2.4
    • NodeJS 10.15.2NodeJS 10.15.2
    • Zulu OpenJDK 8.36.0.1Zulu OpenJDK 8.36.0.1
    • Tomcat 7.0.81Tomcat 7.0.81
    • Tomcat 8.5.37Tomcat 8.5.37
    • Tomcat 9.0.14Tomcat 9.0.14
    • PHP 5.6.39PHP 5.6.39
    • PHP 7.0.33PHP 7.0.33
    • PHP 7.1.25PHP 7.1.25
    • PHP 7.2.13PHP 7.2.13
    • 已将 Kudu 更新到 81.10329.3844Updated Kudu to 81.10329.3844
  • 对所有角色的基础操作系统的更新Updates to underlying operating system of all roles:

部署后步骤Post-deployment Steps

重要

如果已经为应用服务资源提供程序提供 SQL Always On 实例,则必须将 appservice_hosting 和 appservice_metering 数据库添加到可用性组并同步数据库,以免在进行数据库故障转移时丢失服务。If you've provided the App Service resource provider with a SQL Always On Instance, you MUST add the appservice_hosting and appservice_metering databases to an availability group and synchronize the databases to prevent any loss of service in the event of a database failover.

已知问题(安装后)Known issues (post-installation)

  • 如 Azure Stack Hub 上的 Azure 应用服务部署文档中所述,当应用服务部署在现有虚拟网络中并且文件服务器仅在专用网络上可用时,工作人员将无法访问文件服务器。Workers are unable to reach file server when App Service is deployed in an existing virtual network and the file server is only available on the private network, as called out in the Azure App Service on Azure Stack Hub deployment documentation.

如果选择部署到现有虚拟网络和内部 IP 地址以连接到文件服务器,则必须添加出站安全规则,以便在工作子网和文件服务器之间启用 SMB 流量。If you chose to deploy into an existing virtual network and an internal IP address to connect to your file server, you must add an outbound security rule, enabling SMB traffic between the worker subnet and the file server. 转到管理员门户中的 WorkersNsg 并添加包含以下属性的出站安全规则:Go to the WorkersNsg in the administrator portal and add an outbound security rule with the following properties:

  • 源:任意Source: Any
  • 源端口范围:*Source port range: *
  • 目标:IP 地址Destination: IP Addresses
  • 目标 IP 地址范围:文件服务器的 IP 范围Destination IP address range: Range of IPs for your file server
  • 目标端口范围:445Destination port range: 445
  • 协议:TCPProtocol: TCP
  • 操作:允许Action: Allow
  • 优先级:700Priority: 700
  • 姓名:Outbound_Allow_SMB445Name: Outbound_Allow_SMB445

云管理员在操作基于 Azure Stack Hub 的 Azure 应用服务时的已知问题Known issues for cloud admins operating Azure App Service on Azure Stack Hub

请参阅 Azure Stack Hub 1908 发行说明中的文档Refer to the documentation in the Azure Stack Hub 1908 release notes.

将应用程序部署到基于 Azure Stack Hub 的 Azure 应用服务的租户的已知问题Known issues for tenants deploying applications on Azure App Service on Azure Stack Hub

  • 部署中心灰显/不可用。Deployment Center is greyed out/unavailable.

    租户尚不能使用部署中心,该中心是在 2018 年年底的公有云中发布的一项功能。Tenants can't yet make use of Deployment Center, which is a feature that was released in the public cloud in late 2018. 租户仍可通过门户、CLI 和 PowerShell 使用标准部署方法(FTP、Web 部署、Git 等)。Tenants can still use the standard deployment methods (FTP, Web Deploy, Git, and so on) via the portal, CLI, and PowerShell.

  • 部署选项(经典)UX 和部署凭据门户选项不可用。Deployment options (classic) UX and deployment credentials portal options not available.

    若要访问 Azure Stack Hub 部署中的部署选项和部署凭据用户体验,租户应使用 https://portal.<*region*>.<*FQDN*>/?websitesExtension_oldvsts=true 这种 URL 格式(对于 ASDK,该格式为 https://portal.local.azurestack.external/?websitesExtension_oldvsts=true)来访问门户,然后导航到其应用。To reach the deployment options and deployment credentials user experience in the Azure Stack Hub deployment, tenants should access the portal using this URL format: https://portal.<*region*>.<*FQDN*>/?websitesExtension_oldvsts=true - which, for the ASDK would be https://portal.local.azurestack.external/?websitesExtension_oldvsts=true, and then navigate to their apps.

  • Azure Function 监视在门户中持续显示“正在加载”。Azure function monitoring continually shows "Loading" in the portal.

    尝试在用户门户中监视单个 Functions 时,将看不到调用日志、成功计数或错误计数。When you attempt to monitor individual functions in the user portal, you'll see no invocation log, success count, or error count. 若要重新启用此功能,请依次转到“Function App”、“平台功能”、“应用程序设置”。**** **** ****To re-enable this functionality, go to your Function App, go to Platform Features, and go to Application settings. 添加新的名为 AzureWebJobsDashboard 的应用设置,将其值设置为与 AzureWebJobsStorage 中设置的值相同****。Add a new app setting called AzureWebJobsDashboard and set the value to the same value as set in AzureWebJobsStorage. 然后转到函数的监视器视图,此时会看到监视信息。Then go to the monitor view on your function and you'll see the monitoring information.

后续步骤Next steps