App Service Azure Stack Hub 2020 年第3季版本資訊App Service on Azure Stack Hub 2020 Q3 release notes

這些版本資訊說明 Azure Stack Hub 2020 年的 Azure App Service 以及任何已知問題的增強功能與修正。These release notes describe the improvements and fixes in Azure App Service on Azure Stack Hub 2020 Q3 and any known issues. 已知問題分為直接與部署、更新程序相關的問題,以及組建 (安裝後) 的相關問題。Known issues are divided into issues directly related to the deployment, update process, and issues with the build (post-installation).

重要

將 Azure Stack Hub 更新為支援的版本 (或部署最新的 Azure Stack 開發套件) (如有必要),然後再部署或更新 App Service RP (的) 資源提供者。Update Azure Stack Hub to a supported version (or deploy the latest Azure Stack Development Kit) if necessary, before deploying or updating the App Service resource provider (RP). 請務必閱讀 RP 版本資訊,以瞭解有哪些新功能、修正,以及任何可能會影響您部署的已知問題。Be sure to read the RP release notes to learn about new functionality, fixes, and any known issues that could affect your deployment.

支援的 Azure Stack Hub 版本Supported Azure Stack Hub version App Service RP 版本App Service RP version
20082008 2020. 第3季 安裝程式 (版本 資訊) 2020.Q3 Installer (release notes)
20052005 2020. Q2 安裝程式 (版本 資訊) 2020.Q2 Installer (release notes)
20022002 2020. Q2 安裝程式 (版本 資訊) 2020.Q2 Installer (release notes)

建置參考Build reference

Azure Stack Hub 2020 年第3季組建編號上的 App Service 為 89.0.2.15The App Service on Azure Stack Hub 2020 Q3 build number is 89.0.2.15

PrerequisitesPrerequisites

開始部署之前,請參閱「在您開始之前」文件Refer to the Before You Get Started documentation before beginning deployment.

開始將 Azure Stack 上的 Azure App Service 升級至2020年3:Before you begin the upgrade of Azure App Service on Azure Stack to 2020 Q3:

  • 確定 Azure Stack Hub 管理入口網站的 Azure App Service 管理中所有角色都已就緒Ensure all roles are Ready in the Azure App Service Administration in the Azure Stack Hub Admin Portal

  • 在 Azure Stack Hub 管理入口網站中使用 App Service 管理來備份 App Service 祕密Backup App Service Secrets using the App Service Administration in the Azure Stack Hub Admin Portal

  • 備份 App Service 和 Master 資料庫:Back up the App Service and Master Databases:

    • AppService_Hosting;AppService_Hosting;
    • AppService_Metering;AppService_Metering;
    • MasterMaster
  • 備份租用戶應用程式內容檔案共用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. 雲端操作員負責備份 App Service 資料庫和租用戶內容檔案共用。The cloud operator is responsible for backing up the App Service databases and tenant content file share.

  • 從 Marketplace 同步發佈 自訂指令碼擴充功能 1.9.3Syndicate the Custom Script Extension version 1.9.3 from the Marketplace

更新Updates

Azure App Service on Azure Stack 更新 Q3 包含下列改良功能和修正:Azure App Service on Azure Stack Update Q3 includes the following improvements and fixes:

  • App Service 租用戶、系統管理員、Functions 入口網站和 Kudu 工具 的更新。Updates to App Service Tenant, Admin, Functions portals and Kudu tools. 與 Azure Stack 入口網站 SDK 版本保持一致。Consistent with Azure Stack Portal SDK version.

  • 為 Web 和函數應用程式新增全螢幕建立體驗Addition of Full Screen Create experience for Web and Function Apps

  • 新的 Azure Functions 入口網站體驗,以與 Web Apps 一致New Azure Functions Portal Experience to be consistent with Web Apps

  • Azure Functions 運行 時間更新為 v 1.0.13154Updates Azure Functions runtime to v1.0.13154.

  • 用來改善可靠性和錯誤訊息以利進行常見問題診斷的核心服務更新。Updates to core service to improve reliability and error messaging enabling easier diagnosis of common issues.

  • 下列應用程式架構和工具的更新Updates to the following application frameworks and tools:

    • ASP.NET Core 2.1.22ASP.NET Core 2.1.22
    • ASP.NET Core 2.2.14ASP.NET Core 2.2.14
    • ASP.NET Core 3.1。8ASP.NET Core 3.1.8
    • ASP.NET Core Module v2 13.1.19331.0ASP.NET Core Module v2 13.1.19331.0
    • Azul OpenJDKAzul OpenJDK
      • 8.42.0.238.42.0.23
      • 8.44.0.118.44.0.11
      • 11.35.1511.35.15
      • 11.37.1711.37.17
    • 捲曲7.55。1Curl 7.55.1
    • Git for Windows 2.28.0。1Git for Windows 2.28.0.1
    • Msdeploy.exe 3.5.90702.36MSDeploy 3.5.90702.36
    • NodeJSNodeJS
      • 14.10.114.10.1
    • NPMNPM
      • 6.14.86.14.8
    • PHP 7.4。5PHP 7.4.5
    • TomcatTomcat
      • 8.5.478.5.47
      • 8.5.518.5.51
      • 9.0.2739.0.273
      • 9.0.319.0.31
    • 已將 Kudu 更新為90.21005.4823Updated Kudu to 90.21005.4823
  • 所有角色的基礎作業系統更新Updates to underlying operating system of all roles:

  • 適用於 Windows Server 的累積更新現在會在部署和升級期間套用至控制器角色Cumulative Updates for Windows Server are now applied to Controller roles as part of deployment and upgrade

本版已修正的問題Issues fixed in this release

  • 租使用者現在可以使用租使用者入口網站中 App Service 方案視圖上的 [新增] 來建立 App Service 方案Tenants can now create App Service Plan using new on App Service Plan view in tenant portal

  • 租使用者可以在租使用者入口網站中管理其應用程式的憑證Tenants can manage certificates for their applications in the tenant portal

  • 函數監視現在可以從強制執行 TLS 1.2 的儲存體端點取出資料Functions monitoring can now retrieve data from storage endpoints enforcing TLS 1.2

  • 在安裝期間,已將等待管理伺服器的步驟移至部署雲端以外的步驟,以改善部署和升級的可靠性Moved wait for Management Servers step outside of Deploy Cloud step during installation to improve reliability of deployment and upgrade

  • 因為背景工作執行時間記錄檔資料夾大小違反了清除邏輯錯誤後的配額限制,所以工作者無法完成健康情況檢查練習的問題。Issue whereby workers fail to complete the health check exercise due to worker runtime log file folder size violating quota limit after error in clean-up logic. 此更新已修正清除邏輯。Clean-up logic has been fixed in this update.

更新前步驟Pre-Update steps

請檢閱更新的已知問題,並採取任何指定的動作。Review the known issues for update and take any action prescribed.

部署後步驟Post-deployment steps

重要

如果您已對 App Service 資源提供者提供 SQL Always On 執行個體,就必須將 appservice_hosting 和 appservice_metering 資料庫新增至可用性群組並同步處理資料庫,以避免在資料庫進行容錯移轉時中斷服務。If you have 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 (update)

  • 在客戶已將 appservice_hosting 和 appservice_metering 資料庫轉換成自主資料庫的情況下,如果登入尚未成功遷移到自主使用者,升級可能會失敗In situations where a customer has converted the appservice_hosting and appservice_metering databases to contained database, upgrade may fail if logins have not been successfully migrated to contained users

已將 appservice_hosting 和 appservice_metering 資料庫轉換成自主資料庫後續部署,且尚未成功將資料庫登入遷移到自主使用者的客戶,可能會遇到升級失敗。Customers that have converted the appservice_hosting and appservice_metering databases to contained database post deployment, and have not successfully migrated the database logins to contained users, may experience upgrade failures.

客戶必須針對 SQL Server 裝載 appservice_hosting 和 appservice_metering 執行下列腳本,然後才能將 Azure Stack Hub 安裝上的 Azure App Service 升級為 2020 Q3。Customers must execute the following script against the SQL Server hosting appservice_hosting and appservice_metering before upgrading your Azure App Service on Azure Stack Hub installation to 2020 Q3. 此指令碼不具破壞性,而且不會造成停機This script is non-destructive and will not cause downtime.

此指令碼必須在下列情況下執行This script must be run under the following conditions

  • 由具有系統管理員權限的使用者 (例如 SQL SA 帳戶) 執行;By a user that has the system administrator privilege, for example the SQL SA Account;

  • 如果使用 SQL Always On,請確定指令碼是從包含所有 App Service 登入 (格式如下) 的 SQL 執行個體中執行的:If using SQL Always on, ensure the script is run from the SQL instance that contains all App Service logins in the form:

    • appservice_hosting_FileServerappservice_hosting_FileServer
    • appservice_hosting_HostingAdminappservice_hosting_HostingAdmin
    • appservice_hosting_LoadBalancerappservice_hosting_LoadBalancer
    • appservice_hosting_Operationsappservice_hosting_Operations
    • appservice_hosting_Publisherappservice_hosting_Publisher
    • appservice_hosting_SecurePublisherappservice_hosting_SecurePublisher
    • appservice_hosting_WebWorkerManagerappservice_hosting_WebWorkerManager
    • appservice_metering_Commonappservice_metering_Common
    • appservice_metering_Operationsappservice_metering_Operations
    • 所有 WebWorker 登入 - 格式為 WebWorker_All WebWorker logins - which are in the form WebWorker_
        USE appservice_hosting
        IF EXISTS(SELECT * FROM sys.databases WHERE Name=DB_NAME() AND containment = 1)
        BEGIN
        DECLARE @username sysname ;  
        DECLARE user_cursor CURSOR  
        FOR
            SELECT dp.name
            FROM sys.database_principals AS dp  
            JOIN sys.server_principals AS sp
                ON dp.sid = sp.sid  
                WHERE dp.authentication_type = 1 AND dp.name NOT IN ('dbo','sys','guest','INFORMATION_SCHEMA');
            OPEN user_cursor  
            FETCH NEXT FROM user_cursor INTO @username  
                WHILE @@FETCH_STATUS = 0  
                BEGIN  
                    EXECUTE sp_migrate_user_to_contained
                    @username = @username,  
                    @rename = N'copy_login_name',  
                    @disablelogin = N'do_not_disable_login';  
                FETCH NEXT FROM user_cursor INTO @username  
            END  
            CLOSE user_cursor ;  
            DEALLOCATE user_cursor ;
            END
        GO

        USE appservice_metering
        IF EXISTS(SELECT * FROM sys.databases WHERE Name=DB_NAME() AND containment = 1)
        BEGIN
        DECLARE @username sysname ;  
        DECLARE user_cursor CURSOR  
        FOR
            SELECT dp.name
            FROM sys.database_principals AS dp  
            JOIN sys.server_principals AS sp
                ON dp.sid = sp.sid  
                WHERE dp.authentication_type = 1 AND dp.name NOT IN ('dbo','sys','guest','INFORMATION_SCHEMA');
            OPEN user_cursor  
            FETCH NEXT FROM user_cursor INTO @username  
                WHILE @@FETCH_STATUS = 0  
                BEGIN  
                    EXECUTE sp_migrate_user_to_contained
                    @username = @username,  
                    @rename = N'copy_login_name',  
                    @disablelogin = N'do_not_disable_login';  
                FETCH NEXT FROM user_cursor INTO @username  
            END  
            CLOSE user_cursor ;  
            DEALLOCATE user_cursor ;
            END
        GO

已知問題 (安裝後)Known issues (post-installation)

  • 將應用程式服務部署在現有的虛擬網路中且只能在私人網路上使用檔案伺服器時,背景工作角色無法連線到檔案伺服器,如 Azure App Service on Azure Stack 部署文件中所述。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 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 Admin 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
    • 動作:AllowAction: Allow
    • 優先順序:700Priority: 700
    • 名稱:Outbound_Allow_SMB445Name: Outbound_Allow_SMB445

雲端管理員操作 Azure App Service on Azure Stack 時的已知問題Known issues for Cloud Admins operating Azure App Service on Azure Stack

  • 已中斷連線的環境不支援自訂網域Custom domains are not supported in disconnected environments

App Service 會針對公用 DNS 端點執行網域擁有權驗證,因此已中斷連線的案例不支援自訂網域。App Service performs domain ownership verification against public DNS endpoints, as a result custom domains are not supported in disconnected scenarios.

後續步驟Next steps