1. 首頁
  2. 問答
  3. 在自己的雲服務中創建虛擬機時出錯

在自己的雲服務中創建虛擬機時出錯

2014-12-08 109 views
0

試圖在我們中南部的中心地區和西部美國地區使用rest api創建iaas虛擬機。在自己的雲服務中創建虛擬機時出錯

該vms在他們自己的雲服務。一次創建一個虛擬機。

它已經3-4個小時，gui顯示正在進行部署。從操作ID

錯誤信息如下：

Failed409 ConflictEr ror的Windows Azure目前在該日 ployment需要獨佔訪問進行操作。

奇怪的是，使用powershell或gui我可以成功創建vms。

附加信息： 我正在使用創建VM部署API。

工作流創建VM是：

1）創建cloudservice

2）在使用中創建VM部署API上述雲服務創建VM。我正在使用生產槽。

我做了如下試驗：

1）使用蔚藍GUI創建雲服務 - 成功

2）使用curl命令來創建虛擬機。 curl的輸出具有請求標識。運行另一個curl命令，以獲得在步驟1中創建的cloudservice中創建虛擬機的狀態。

3）獲取操作狀態的curl命令顯示進行幾次，然後出現衝突錯誤。

4）此外，我檢查了gui，它已經差不多30分鐘了，沒有vm創建的跡象。雲服務顯示

C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" -H "Content-Type: application/xml" -X POST -d @makevm.xml https://m 
anagement.core.windows.net/<subscriptionid>/services/hosteds 
ervices/testvmcs/deployments 
HTTP/1.1 100 Continue 

HTTP/1.1 202 Accepted 
Cache-Control: no-cache 
Content-Length: 0 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: 997a9dadcac53e43a926b36481fc8f53 
Date: Mon, 08 Dec 2014 01:47:47 GMT 


C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" https://management.core.windows.net/04dc0d13-8d80-4781-b4b9-603708c 
e871c/operations/997a9dadcac53e43a926b36481fc8f53 
HTTP/1.1 200 OK 
Cache-Control: no-cache 
Content-Length: 197 
Content-Type: application/xml; charset=utf-8 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: 0a170e4e3f393e8aaadb8a82399d2ee3 
Date: Mon, 08 Dec 2014 01:48:07 GMT 

<Operation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www 
.w3.org/2001/XMLSchema-instance"><ID>997a9dad-cac5-3e43-a926-b36481fc8f53</ID><S 
tatus>InProgress</Status></Operation> 
C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" https://management.core.windows.net/04dc0d13-8d80-4781-b4b9-603708c 
e871c/operations/997a9dadcac53e43a926b36481fc8f53 
HTTP/1.1 200 OK 
Cache-Control: no-cache 
Content-Length: 197 
Content-Type: application/xml; charset=utf-8 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: e78866b1e3c53bfc8d5313d4078f4f5f 
Date: Mon, 08 Dec 2014 01:48:13 GMT 

<Operation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www 
.w3.org/2001/XMLSchema-instance"><ID>997a9dad-cac5-3e43-a926-b36481fc8f53</ID><S 
tatus>InProgress</Status></Operation> 
C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" https://management.core.windows.net/04dc0d13-8d80-4781-b4b9-603708c 
e871c/operations/997a9dadcac53e43a926b36481fc8f53 
HTTP/1.1 200 OK 
Cache-Control: no-cache 
Content-Length: 390 
Content-Type: application/xml; charset=utf-8 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: 8e552b9140ec34be90ab9c20e061d810 
Date: Mon, 08 Dec 2014 01:49:45 GMT 

<Operation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www 
.w3.org/2001/XMLSchema-instance"><ID>997a9dad-cac5-3e43-a926-b36481fc8f53</ID><S 
tatus>Failed</Status><HttpStatusCode>409</HttpStatusCode><Error><Code>ConflictEr 
ror</Code><Message>Windows Azure is currently performing an operation on this de 
ployment that requires exclusive access.</Message></Error></Operation> 
C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" https://management.core.windows.net/04dc0d13-8d80-4781-b4b9-603708c 
e871c/operations/997a9dadcac53e43a926b36481fc8f53 
HTTP/1.1 200 OK 
Cache-Control: no-cache 
Content-Length: 390 
Content-Type: application/xml; charset=utf-8 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: 1efb6dc33c09374484f06550cb31661b 
Date: Mon, 08 Dec 2014 01:50:03 GMT 

<Operation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www 
.w3.org/2001/XMLSchema-instance"><ID>997a9dad-cac5-3e43-a926-b36481fc8f53</ID><S 
tatus>Failed</Status><HttpStatusCode>409</HttpStatusCode><Error><Code>ConflictEr 
ror</Code><Message>Windows Azure is currently performing an operation on this de 
ployment that requires exclusive access.</Message></Error></Operation> 
C:\Users\gardam\preprodmgmtcert>curl -D - -E preprodazcert.pem -H "x-ms-version: 
2014-10-01" https://management.core.windows.net/04dc0d13-8d80-4781-b4b9-603708c 
e871c/operations/997a9dadcac53e43a926b36481fc8f53 
HTTP/1.1 200 OK 
Cache-Control: no-cache 
Content-Length: 390 
Content-Type: application/xml; charset=utf-8 
Server: 1.0.6198.167 (rd_rdfe_stable.141203-1417) Microsoft-HTTPAPI/2.0 
x-ms-servedbyregion: ussouth2 
x-ms-request-id: 2d7a2cf3b043322083067519133d8e9d 
Date: Mon, 08 Dec 2014 01:50:09 GMT 

<Operation xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www 
.w3.org/2001/XMLSchema-instance"><ID>997a9dad-cac5-3e43-a926-b36481fc8f53</ID><S 
tatus>Failed</Status><HttpStatusCode>409</HttpStatusCode><Error><Code>ConflictEr 
ror</Code><Message>Windows Azure is currently performing an operation on this de 
ployment that requires exclusive access.</Message></Error></Operation>

的makevm.xml在下面給出「部署在進步」：

<?xml version="1.0"?> 
<Deployment xmlns="http://schemas.microsoft.com/windowsazure" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> 
    <Name>testmevm1</Name> 
    <DeploymentSlot>Production</DeploymentSlot> 
    <Label>dGVzdG1ldm0x</Label> 
    <RoleList> 
    <Role> 
     <RoleName>testmevm1</RoleName> 
     <RoleType>PersistentVMRole</RoleType> 
     <ConfigurationSets> 
    <ConfigurationSet i:type="LinuxProvisioningConfigurationSet"> 
    <ConfigurationSetType>LinuxProvisioningConfiguration</ConfigurationSetType> 
    <HostName>testmevm1</HostName> 
    <UserName>devuser</UserName> 
    <UserPassword>examplepassword</UserPassword> 
    <DisableSshPasswordAuthentication>false</DisableSshPasswordAuthentication> 
    </ConfigurationSet> 
    <ConfigurationSet> 
    <ConfigurationSetType>NetworkConfiguration</ConfigurationSetType> 
    <InputEndpoints> 
     <InputEndpoint> 
     <LocalPort>22</LocalPort> 
     <Name>SSH</Name> 
     <Port>2222</Port> 
     <Protocol>TCP</Protocol> 
     </InputEndpoint> 
     <InputEndpoint> 
     <LocalPort>80</LocalPort> 
     <Name>TCP-PORT-8080</Name> 
     <Port>8080</Port> 
     <Protocol>TCP</Protocol> 
     </InputEndpoint> 
     <InputEndpoint> 
     <LocalPort>3389</LocalPort> 
     <Name>TCP-PORT-3390</Name> 
     <Port>3390</Port> 
     <Protocol>TCP</Protocol> 
     </InputEndpoint> 
    </InputEndpoints> 
    <SubnetNames> 
     <SubnetName>us1-int-nb-app</SubnetName> 
    </SubnetNames> 
    </ConfigurationSet> 
</ConfigurationSets> 
     <AvailabilitySetName>us1-int-nb-app-avset1</AvailabilitySetName> 
     <OSVirtualHardDisk> 
    <HostCaching>ReadWrite</HostCaching> 
    <DiskLabel>testmevm1-osdisk</DiskLabel> 
    <DiskName>testmevm1-osdisk</DiskName> 
    <MediaLink>http://demostg5.blob.core.windows.net/osdisk/disk_2014_12_07_17_08.vhd</MediaLink> 
    <OS>Linux</OS> 
    <RemoteSourceImageLink>https://us1preprodall.blob.core.windows.net/images/central-baseimage-os-2014-11-24.vhd</RemoteSourceImageLink> 
</OSVirtualHardDisk> 
     <RoleSize>Small</RoleSize> 
    </Role> 
    </RoleList> 
    <VirtualNetworkName>us1-int</VirtualNetworkName> 
</Deployment>

我還提交了我的QS到MSDN蔚藍的論壇，但都沒有得到線索/建議，以幫助修復im面臨的問題

有人可以幫忙嗎？

關於

來源

2014-12-08 user3311402

回答

1

它看起來像你正在提供自己的形象。我相信映像和操作系統磁盤必須位於同一個存儲帳戶中，這似乎並非如此。

來源

2014-12-08 04:47:33

+0

嗨尼爾，我能夠在上週的星期三使用一箇中心位置的圖像創建虛擬現實存儲帳戶，但自從星期四以來我一直有問題。我無法理解爲什麼？謝謝 – user3311402 2014-12-08 06:04:37

+0

Hi Neil，另外我試圖從xml中指定的映像中創建一個虛擬機，但映像位於同一個存儲帳戶中，但不同的容器，並且即時看到相同的問題。 – user3311402 2014-12-08 06:47:39

相關問題

 相關問題