App Service on Azure Stack Hub 2020 Q2 版本資訊App Service on Azure Stack Hub 2020 Q2 release notes

這些版本資訊說明 Azure App Service on Azure Stack Hub 2020 Q2 的改進和修正,以及任何已知問題。These release notes describe the improvements and fixes in Azure App Service on Azure Stack Hub 2020 Q2 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

App Service on Azure Stack Hub 2020 Q2 組建編號是 87.0.2.10The App Service on Azure Stack Hub 2020 Q2 build number is 87.0.2.10

PrerequisitesPrerequisites

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

開始將 Azure Stack 上的 Azure App Service 升級至 2020 Q2 之前:Before you begin the upgrade of Azure App Service on Azure Stack to 2020 Q2:

  • 確定 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 Stack 上的 Azure App Service Q2 更新包含下列改進和修正:Azure App Service on Azure Stack Update Q2 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.

  • Azure Functions 執行階段 更新至 v1.0.13021Updates Azure Functions runtime to v1.0.13021.

  • 用來改善可靠性和錯誤訊息以利進行常見問題診斷的核心服務更新。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 Framework 4.7.2ASP.NET Framework 4.7.2
    • ASP.NET Core 3.1.3ASP.NET Core 3.1.3
    • ASP.NET Core Module v2 13.1.19331.0ASP.NET Core Module v2 13.1.19331.0
    • PHP 7.4.2PHP 7.4.2
    • 已將 Kudu 更新至 86.20224.4450Updated Kudu to 86.20224.4450
    • NodeJSNodeJS
      • 8.17.08.17.0
      • 10.19.010.19.0
      • 12.13.012.13.0
      • 12.15.012.15.0
    • NPMNPM
      • 5.6.05.6.0
      • 6.1.06.1.0
      • 6.12.06.12.0
      • 6.13.46.13.4
  • 所有角色的基礎作業系統更新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

  • 已更新新部署的預設虛擬機器和擴展集 SKU:為了與公用雲端服務保持一致,Azure Stack Hub 上的新 Azure App Service 部署將會針對用來操作資源提供者的基礎機器和擴展集使用下列 SKUUpdated default Virtual Machine and Scale set skus for new deployments: To maintain consistency with our public cloud service, new deployments of Azure App Service on Azure Stack Hub will use the following SKUs for the underlying machines and scale sets used to operate the resource provider

    角色Role 最低 SKUMinimum SKU
    控制器Controller Standard_A4_v2 - (四核心,8192 MB)Standard_A4_v2 - (4 cores, 8192 MB)
    管理性Management Standard_D3_v2 - (四核心,14336 MB)Standard_D3_v2 - (4 cores, 14336 MB)
    發行者Publisher Standard_A2_v2 - (雙核心,4096 MB)Standard_A2_v2 - (2 cores, 4096 MB)
    FrontEndFrontEnd Standard_A4_v2 - (四核心,8192 MB)Standard_A4_v2 - (4 cores, 8192 MB)
    共用背景工作Shared Worker Standard_A4_v2 - (四核心,8192 MB)Standard_A4_v2 - (4 cores, 8192 MB)
    小型專用背景工作Small dedicated worker Standard_A1_v2 - (單核心,2048 MB)Standard_A1_v2 - (1 cores, 2048 MB)
    中型專用背景工作Medium dedicated worker Standard_A2_v2 - (雙核心,4096 MB)Standard_A2_v2 - (2 cores, 4096 MB)
    大型專用背景工作Large dedicated worker Standard_A4_v2 - (四核心,8192 MB)Standard_A4_v2 - (4 cores, 8192 MB)

針對 ASDK 部署,您可以將執行個體縮小為較低的 SKU,以減少核心和記憶體認可,但會遇到效能降低的情況。For ASDK deployments, you can scale the instances down to lower SKUs to reduce the core and memory commit but you will experience a performance degradation.

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

  • 現在如果 SQL Always On 叢集已容錯移轉至次要節點時,升級仍會完成Upgrades will now complete if SQL Always On Cluster has failed over to secondary node
  • Azure App Service on Azure Stack Hub 的新部署不再需要將資料庫手動轉換成自主資料庫New deployments of Azure App Service on Azure Stack Hub no longer require databases to be manually converted to contained databases
  • 新增額外的背景工作或基礎結構角色執行個體會正確完成,不必手動介入Adding additional workers or infrastructure role instances will complete correctly without manual intervention
  • 新增自訂背景工作層會正確完成,不必手動介入Adding custom worker tiers will complete correctly without manual intervention
  • 自訂背景工作層的移除現在可正常完成而不會有入口網站錯誤Removal of custom worker tiers now completes without portal errors
  • 如果本機磁碟空間不足,背景工作將不再標示為已就緒Workers are no longer marked as ready if the local disk is out of space
  • 擷取 Azure Resource Manager 憑證的逾時值已增加Time out increased for retrieving the Azure Resource Manager Certificate
  • 從伺服器記錄擷取並顯示在管理入口網站的訊息數目,會限制為保持在 Azure Resource Manager 要求大小上限之下The number of messages retrieved, from server logs and displayed in the Admin Portal, is limited to stay underneath the max Azure Resource Manager Request size
  • 造成使用量服務啟動問題的逾時問題Time out issue causing usage service startup issues
  • 已解決建立 Orchard CMS 網站時的資料庫部署問題Resolved database deployment issue when creating Orchard CMS sites
  • 在部署和升級過程中,控制器現在會使用 Windows 累積更新來加以更新Controllers are now updated with Windows Cumulative Updates as part of deployment and upgrade
  • 當自訂網域驗證失敗時,App Service 不會再鎖定作業App Service no longer locks operations when custom domain verification fails

更新前步驟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.

客戶必須先針對裝載 appservice_hosting 和 appservice_metering 的 SQL Server 執行下列指令碼,然後才能將 Azure App Service on Azure Stack Hub 安裝升級到 2020 Q2。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 Q2. 此指令碼不具破壞性,而且不會造成停機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

  • 租用戶無法使用租用戶入口網站中 App Service 方案檢視上的新功能來建立 App Service 方案Tenants unable to create App Service Plan using new on App Service Plan view in tenant portal

在建立新的應用程式時,租用戶可以在建立應用程式工作流程期間、在變更目前應用程式的 App Service 方案時,或透過 App Service 方案市集項目,來建立 App Service 方案When creating a new application, tenants can create App Service Plans during the create app workflow, or when changing the App Service Plan for a current app, or via the App Service Plan marketplace item

  • 已中斷連線的環境不支援自訂網域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.

  • 在某些情況下,工作者無法滿足健康情況檢查 (磁碟空間不足) In some cases workers fail to satisfy health checks (insufficient disk space)

在某些情況下,配置給背景工作角色或網站的大量網站正在處理大量的要求時,背景工作會在 C:\DWAS\LogFiles. 中產生大量的執行時間記錄檔。In some cases, where a high number of sites are allocated to a worker or a site is handling a large number of requests, the worker will generate a large number of runtime log files in C:\DWAS\LogFiles. 這是因為這些記錄檔的清除邏輯中有錯誤。This is due to a bug in the clean-up logic for these log files.

若要從遠端對個別工作者解決此問題,並清除資料夾的內容。To mitigate this issue remote to the individual worker and clear out the contents of the folder.

此問題已在2020年 第3季的 Azure Stack Hub App Service中修正,我們建議客戶儘快升級至 2020 Q3 版本。This issue has been fixed in App Service on Azure Stack Hub 2020 Q3, we encourage customers to upgrade to the 2020 Q3 release as soon as possible.

重要

若要更新為 Azure Stack Hub 2020 年第3季的 Azure App Service,您 必須 升級至 Azure Stack Hub 2008In order to update to Azure App Service on Azure Stack Hub 2020 Q3 you must upgrade to Azure Stack Hub 2008

後續步驟Next steps