您的位置: 首页  >  技术问答  >  在自己的云服务中创建虚拟机时出错

在自己的云服务中创建虚拟机时出错

分类: 技术问答 • 2022-09-19 00:29:33
问题描述：

试图在我们中南部的中心地区和西部美国地区使用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面临的问题

有人可以帮忙吗？

关于

答

它看起来像你正在提供自己的形象。我相信映像和操作系统磁盘必须位于同一个存储帐户中，这似乎并非如此。

+0

嗨尼尔，我能够在上周的星期三使用一个中心位置的图像创建虚拟现实存储帐户，但自从星期四以来我一直有问题。我无法理解为什么？谢谢 – user3311402 2014-12-08 06:04:37

+0

Hi Neil，另外我试图从xml中指定的映像中创建一个虚拟机，但映像位于同一个存储帐户中，但不同的容器，并且即时看到相同的问题。 – user3311402 2014-12-08 06:47:39

相关推荐