堆棧內存溢出
  簡體   English   中英

Azure ARM模板 - DSC（新架構）沒有運行腳本而沒有返回錯誤？

[英]Azure ARM Templates - DSC (new schema) not running scripts and not returning an error?

 原文  2019-03-14 21:05:11  6   1    json/ azure/ templates/ dsc

問題描述

我剛剛轉換了ARM模板（DC部署）以使用較新的2016 DSC架構。 我以為我已經正確地格式化了我的JSON，當我部署模板時，它成功地設置了，快樂的日子！ 但事實並非如此，雖然模板正在成功部署，但DSC配置文件未運行，但仍安裝了DSC擴展。 配置文件保存在Azure blob上，在舊模式中，我使用URL和SAS令牌的參數構造了URL。 新架構將所有這些拆分開來，我認為問題是未將SAS令牌添加到URL中。

有關信息，配置文件提供ADDS功能並設置目錄林。

作為測試，我從blob存儲中刪除了配置文件並再次運行模板，並再次正確配置....它似乎正在跳過配置部分完成...非常奇怪。

這是DSC擴展代碼段，任何人都可以發現任何拼寫錯誤或錯誤放置括號嗎？ 我已經盯着這個看了大約5個小時，所以對我來說這只是一個很大的模糊。 

            "resources": [
                {
                    "type": "Microsoft.Compute/virtualMachines/extensions",
                    "name": "[concat(variables('dc2name'), '/CreateADBDC')]",
                    "apiVersion": "2019-03-01",
                    "location": "[resourceGroup().location]",
                    "dependsOn": [
                        "[resourceId('Microsoft.Compute/virtualMachines', variables('dc2name'))]",
                        "[resourceId('Microsoft.Compute/virtualMachines/extensions', variables('dc1name'), 'CreateADForest')]"
                    ],
                    "properties": {
                        "publisher": "Microsoft.Powershell",
                        "type": "DSC",
                        "typeHandlerVersion": "2.77",
                        "autoUpgradeMinorVersion": true,
                        "settings": {
                            "WMFVersion": "latest",
                            "configuraton": {
                            "url": "[concat(parameters('Artifacts Location'), '/dsc/CreateADBDC.zip')]",
                            "script": "CreateADBDC.ps1",
                            "function": "CreateADBDC"
                            },
                            "configurationArguments": {
                                "DomainName": "[parameters('Domain Name')]",
                                "DNSServer": "[variables('dc1ipaddress')]"
                            }
                        },
                        "protectedSettings": {
                            "configurationArguments": {
                              "adminCreds": {
                                    "UserName": "[parameters('Administrator User')]",
                                    "Password": "[parameters('Administrator Password')]"
                                    }
                                },
                            "configurationUrlSasToken": "[parameters('Artifacts Location SAS Token')]"
                        }
                    }
                }
            ]

下面是deployment_operations輸出，（我刪除了敏感信息）。 我不明白的是“請求”部分與“響應”之間的區別，“protectedsettings”中出現的任何內容都缺失，這是正常的嗎？ 

      "request": {
        "content": {
          "location": "uksouth",
          "properties": {
            "publisher": "Microsoft.Powershell",
            "type": "DSC",
            "typeHandlerVersion": "2.77",
            "autoUpgradeMinorVersion": true,
            "settings": {
              "WMFVersion": "latest",
              "configuraton": {
                "url": "https://xxxxx.blob.core.windows.net/dsc/CreateADBDC.zip",
                "script": "CreateADBDC.ps1",
                "function": "CreateADBDC"
              },
              "configurationArguments": {
                "DomainName": "domain.co.uk",
                "DNSServer": "10.x.x.250"
              }
            },
            "protectedSettings": {
              "configurationArguments": {
                "adminCreds": {
                  "UserName": "admin",
                  "Password": "password"
                }
              },
              "configurationUrlSasToken": "stuffhere"
            }
          }
        }
      },
      "response": {
        "content": {
          "properties": {
            "autoUpgradeMinorVersion": true,
            "settings": {
              "WMFVersion": "latest",
              "configuraton": {
                "url": "https://xxxxxx.blob.core.windows.net/dsc/CreateADBDC.zip",
                "script": "CreateADBDC.ps1",
                "function": "CreateADBDC"
              },
              "configurationArguments": {
                "DomainName": "domain.co.uk",
                "DNSServer": "10.x.x.250"
              }
            },
            "provisioningState": "Succeeded",
            "instanceView": {
              "name": "CreateADBDC",
              "type": "Microsoft.Powershell.DSC",
              "typeHandlerVersion": "2.77.0.0",
              "substatuses": [
                {
                  "code": "ComponentStatus/DscConfigurationLog/succeeded",
                  "level": "Info",
                  "displayStatus": "Provisioning succeeded",
                  "message": ""
                },
                {
                  "code": "ComponentStatus/DscExtensionLog/succeeded",
                  "level": "Info",
                  "displayStatus": "Provisioning succeeded",
                  "message": "[2019-03-14 20:06:49Z] Getting handler execution status HKLM:\\SOFTWARE\\Microsoft\\Azure\\DSC\\2.77.0.0\\Status ..
                },
                {
                  "code": "ComponentStatus/Metadata/succeeded",
                  "level": "Info",
                  "displayStatus": "Provisioning succeeded",
                  "message": "VMUUId=5CE28735-xxxx-xxxx-xxxx-53AA96F3A520;AgentId=BAFCAC0D-xxxx-xxxx-xxxx-0022480775AE;"
                }
              ],
              "statuses": [
                {
                  "code": "ProvisioningState/succeeded",
                  "level": "Info",
                  "displayStatus": "Provisioning succeeded",
                  "message": "PowerShell DSC has been enabled.",
                  "time": "2019-03-14T20:07:03+00:00"
                }
              ]
            },
            "publisher": "Microsoft.Powershell",
            "type": "DSC",
            "typeHandlerVersion": "2.77"
          },
          "type": "Microsoft.Compute/virtualMachines/extensions",
          "location": "uksouth",
          "id": "/subscriptions/xxxxx/resourceGroups/RG/providers/Microsoft.Compute/virtualMachines/DC2/extensions/CreateADBDC",
          "name": "CreateADBDC"
        }
      }
    }
  },

更新：

搜索DSC擴展日志我看到此錯誤： 

[ERROR] occurred while invoking events for telemetry The property 'Configuration' 
cannot be found on this object. Verify that the property exists.

還有更進一步的日志： 

A DSC configuration was not provided. PowerShell DSC has been enabled on the VM, will exit now.

這就解釋了為什么它不運行腳本，但是配置屬性在模板中。...現在非常困惑！

更新2

由DSC執行的PowerShell命令 

configuration CreateADBDC {
    Param (
        # Get deployment details
        [Parameter(Mandatory)]
        [String]$DNSServer,
        [Parameter(Mandatory)]
        [String]$DomainName,

        # Credentials
        [Parameter(Mandatory)]
        [System.Management.Automation.PSCredential]$Admincreds,

        [Int]$RetryCount = 500,
        [Int]$RetryIntervalSec = 3
    )

    Import-DscResource -ModuleName PSDesiredStateConfiguration, xStorage, xNetworking, xActiveDirectory, xPendingReboot
    $Interface = Get-NetAdapter | Where-Object { $_.Name -Like "Ethernet*" } | Select-Object -First 1
    [System.Management.Automation.PSCredential]$DomainCreds = New-Object System.Management.Automation.PSCredential ("${DomainName}\$($Admincreds.UserName)", $Admincreds.Password)
    $features = @("AD-Domain-Services", "RSAT-ADDS-Tools", "RSAT-AD-AdminCenter")

    Node localhost {
        LocalConfigurationManager {
            RebootNodeIfNeeded = $true
        }

        xWaitforDisk Disk2 {
            DiskNumber       = 2
            RetryIntervalSec = $RetryIntervalSec
            RetryCount       = $RetryCount
        }

        xDisk ADDataDisk {
            DiskNumber  = 2
            DriveLetter = "F"
            DependsOn   = "[xWaitForDisk]Disk2"
        }

        WindowsFeatureSet Prereqs {
            Name                 = $features
            Ensure               = "Present"
            IncludeAllSubFeature = $true
        } 

        xDnsServerAddress DnsServerAddress {
            Address        = $DNSServer
            InterfaceAlias = $Interface.Name
            AddressFamily  = "IPv4"
            DependsOn      = "[WindowsFeatureSet]Prereqs"
        }

        xWaitForADDomain DscForestWait {
            DomainName           = $DomainName
            DomainUserCredential = $DomainCreds
            RetryCount           = $RetryCount
            RetryIntervalSec     = $RetryIntervalSec
        }

        xADDomainController BDC {
            DomainName                    = $DomainName
            DomainAdministratorCredential = $DomainCreds
            SafemodeAdministratorPassword = $DomainCreds
            DatabasePath                  = "F:\NTDS"
            LogPath                       = "F:\NTDS"
            SysvolPath                    = "F:\SYSVOL"
            DependsOn                     = "[xWaitForADDomain]DscForestWait"
        }

        xPendingReboot RebootAfterPromotion {
            Name      = "RebootAfterDCPromotion"
            DependsOn = "[xADDomainController]BDC"
        }
    }
}

更新3

完整的DSC日志： 

VERBOSE: [2019-03-15 09:54:33Z] Extension request for sequence number 0 attempting to create lock.0 mutex
VERBOSE: [2019-03-15 09:54:33Z] Attempting to grab mutex DscExtensionHandler_Lock for sequence number 0
VERBOSE: [2019-03-15 09:54:33Z] Acquired lock for extension instance for sequence number 0
VERBOSE: [2019-03-15 09:54:33Z] Attempting to acquire extension lock
VERBOSE: [2019-03-15 09:54:33Z] Attempting to grab mutex DscExtensionHandler_Lock
VERBOSE: [2019-03-15 09:54:33Z] Acquired lock for extension
VERBOSE: [2019-03-15 09:54:33Z] lock does not exist: begin processing
VERBOSE: [2019-03-15 09:54:33Z] Starting DSC Extension ...
VERBOSE: [2019-03-15 09:54:33Z] Getting handler execution status HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status 
...
VERBOSE: [2019-03-15 09:54:33Z] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status)
VERBOSE: [2019-03-15 09:54:33Z] Transitioning to DataValidation state ...
VERBOSE: [2019-03-15 09:54:33Z] Settings handler status to 'transitioning' 
(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status)
VERBOSE: [2019-03-15 09:54:33Z] Retrieving system information ...
VERBOSE: [2019-03-15 09:54:37Z]     OS Version : 10.0
VERBOSE: [2019-03-15 09:54:37Z]     Server OS  : True
VERBOSE: [2019-03-15 09:54:37Z]     64-bit OS  : True
VERBOSE: [2019-03-15 09:54:37Z]     PS Version : 5.1.17763.316
VERBOSE: [2019-03-15 09:54:37Z] Validating user provided settings for the DSC Extension Handler ...
VERBOSE: [2019-03-15 09:54:37Z] Reading handler settings from 
C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\RuntimeSettings\0.settings
VERBOSE: [2019-03-15 09:54:37Z] Found protected settings on Azure VM. Decrypting.
VERBOSE: [2019-03-15 09:54:40Z] Updating user preference for Data Collection ......
VERBOSE: [2019-03-15 09:54:40Z] Get DSC Extension Handler install status  ...
VERBOSE: [2019-03-15 09:54:40Z]  Status: NotInstalled
VERBOSE: [2019-03-15 09:54:40Z] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status)
VERBOSE: [2019-03-15 09:54:40Z] Transitioning to DownloadHotfixes state ...
VERBOSE: [2019-03-15 09:54:40Z] Getting handler execution status HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status 
...
VERBOSE: [2019-03-15 09:54:40Z] Settings handler status to 'transitioning' 
(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status)
VERBOSE: [2019-03-15 09:54:40Z] Downloading wmf hotfixes (if any) required for the DSC Extension install ...
VERBOSE: [2019-03-15 09:54:42Z] Retrieving WMF download information (WMF_5.1-Windows_10.0-x64)...
VERBOSE: [2019-03-15 09:54:42Z] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status)
VERBOSE: [2019-03-15 09:54:42Z] Transitioning to InstallExtension state ...
VERBOSE: [2019-03-15 09:54:42Z] Getting handler execution status HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status 
...
VERBOSE: [2019-03-15 09:54:42Z] Settings handler status to 'transitioning' 
(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status)
VERBOSE: [2019-03-15 09:54:43Z] DSC Extension Install Status: NotInstalled
VERBOSE: [2019-03-15 09:54:43Z] Installing the DSC Extension...
VERBOSE: [2019-03-15 09:54:43Z] Setting install status to 'InProgress' 
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\InstallStatus)
VERBOSE: [2019-03-15 09:54:43Z] Settings handler status to 'transitioning' 
(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status)
VERBOSE: [2019-03-15 09:54:43Z] Test if WMF 5PP is installed on the machine ...
VERBOSE: [2019-03-15 09:54:45Z] Retrieving WMF download information (WMF_5.0PP-Windows_10.0-x64)...
VERBOSE: [2019-03-15 09:54:48Z] Retrieving WMF download information (WMF_5.1-Windows_10.0-x64)...
VERBOSE: [2019-03-15 09:54:48Z] Enabling WINRM listeners...
VERBOSE: [2019-03-15 09:54:50Z] Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to 
local users. 

VERBOSE: [2019-03-15 09:54:51Z] The DSC Extension was installed successfully
VERBOSE: [2019-03-15 09:54:51Z] Setting install status to 'Installed' 
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\InstallStatus)
VERBOSE: [2019-03-15 09:54:51Z] Initializing handler metadata ...
VERBOSE: [2019-03-15 09:54:53Z] AgentID is 6111F68C-4708-11E9-ACF3-000D3AXX0539 ...
VERBOSE: [2019-03-15 09:54:53Z] VMUUId is D077C845-7564-47F4-B76B-C9FAXXEA7A61 ...
VERBOSE: [2019-03-15 09:54:53Z] Azure Resource ID is  ...
VERBOSE: [2019-03-15 09:54:53Z] Loading VM agent telemetry assemblies ...
VERBOSE: [2019-03-15 09:54:54Z] [ERROR] occurred while invoking events for telemetry The property 'Configuration' 
cannot be found on this object. Verify that the property exists.
VERBOSE: [2019-03-15 09:54:54Z] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status)
VERBOSE: [2019-03-15 09:54:54Z] Transitioning to ProcessConfiguration state ...
VERBOSE: [2019-03-15 09:54:54Z] Getting handler execution status HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status 
...
VERBOSE: [2019-03-15 09:54:54Z] A DSC configuration was not provided. PowerShell DSC has been enabled on the VM, will 
exit now.
VERBOSE: [2019-03-15 09:54:54Z] Settings handler status to 'success' 
(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.77.0.0\Status\0.status)
VERBOSE: [2019-03-15 09:54:54Z] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\2.77.0.0\Status)
VERBOSE: [2019-03-15 09:54:54Z] Transitioning to Completed state ...
VERBOSE: [2019-03-15 09:54:54Z] Releasing SameSeq mutex
VERBOSE: [2019-03-15 09:54:54Z] Releasing mutex DscExtensionHandler_Lock

1 個解決方案

解決方案1
 0 已采納  2019-03-15 19:16:55

在這種情況下，錯誤是由於模板中的拼寫錯誤：configuraon而不是配置

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 Azure ARM模板-運行DSC腳本而不觸發擴展安裝？ ARM模板DSC：配置未“看到” protectedSettings.configurationArguments 從ARM模板安全地將憑據傳遞到DSC擴展 如何在powershell中獲得azure arm模板的解釋值（ex concat） 在azure FAILED上部署cloudera，JSON / ARM模板函數'copyIndex'錯誤 使用 ARM 模板和 JSON 在 Azure 中創建 VM 時出現“DiskImageNotReady”錯誤 Azure ARM 模板“VmAgentNotRunning” Azure ARM copyIndex（） Azure ARM嵌入式IF無法正常工作 從ARM模板部署新的Azure VM時，無法格式化有效的JObject for.WithParameters（）
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM