ERROR PUT request failed: BadRequest - XML Schema validation error in network configuration at line 54,18. (http code 400: Bad Request)

Bug #1304778 reported by Juan Carlos Bauza Ogazón
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Andrew Wilkins

Bug Description

Followed configuration steps here: https://juju.ubuntu.com/docs/config-azure.html but I encountered two issues:

1) When using a storage account that is part of an affinity group I get:
ERROR POST request failed: BadRequest - The affinity group name is empty or was not specified. (http code 400: Bad Request)

2) When using a stand alone storage account I get:
ERROR PUT request failed: BadRequest - XML Schema validation error in network configuration at line 54,18. (http code 400: Bad Request)

when using the Windows version instead of the Ubuntu one I get:

Microsoft Windows [Versión 6.3.9600]

C:\Program Files (x86)\Juju>juju bootstrap
WARNING unknown config field "public-storage-account-name"
WARNING unknown config field "public-storage-container-name"
Bootstrap failed, destroying environment
ERROR Bootstrap failed, and the environment could not be destroyed: cannot get i
nstances: crypto/tls: failed to parse key: ASN.1 structure error: tags don't mat
ch (2 vs {class:0 tag:16 length:1113 isCompound:true}) {optional:false explicit:
false application:false defaultValue:<nil> tag:<nil> stringType:0 set:false omit
Empty:false} int @4
ERROR crypto/tls: failed to parse key: ASN.1 structure error: tags don't match (
2 vs {class:0 tag:16 length:1113 isCompound:true}) {optional:false explicit:fals
e application:false defaultValue:<nil> tag:<nil> stringType:0 set:false omitEmpt
y:false} int @4

Any help would be greatly appreciated. Let me know if you need any additional information.
Thanks!

Curtis Hovey (sinzui)
tags: added: azure-provider
Revision history for this message
Curtis Hovey (sinzui) wrote :

I haven't seen an error like this before, but I see lots of intermittent errors with azure.

1. Check that the jenv file was not left behind an early attempt because juju will use it instead of environments.yaml.
    rm ~/.juju/environments/azure.jenv
2. The only differerence between my config and the one from the docs is that I specify where to find the tools
     tools-metadata-url: https://jujutools.blob.core.windows.net/juju-tools/tools
3. The location must be
    location: West US
    I have never gotten juju to work with a different location

Revision history for this message
Curtis Hovey (sinzui) wrote :

If config changes do not help, please run
    juju --debug bootstrap
and attach the long log to this bug report.

Changed in juju-core:
status: New → Incomplete
Revision history for this message
Juan Carlos Bauza Ogazón (jcbauza) wrote :

I made changes as indicated but I still get the same error message. Below is the log you requested:

2014-04-09 13:39:57 INFO juju.cmd supercommand.go:297 running juju-1.18.0-saucy-amd64 [gc]
2014-04-09 13:39:57 DEBUG juju.environs.configstore disk.go:64 Making /home/lokikun/.juju/environments
2014-04-09 13:39:57 DEBUG juju.provider.azure environprovider.go:28 opening environment "azure".
2014-04-09 13:40:33 INFO juju.environs.bootstrap bootstrap.go:46 bootstrapping environment "azure"
2014-04-09 13:40:45 INFO juju.cmd cmd.go:113 Bootstrap failed, destroying environment
2014-04-09 13:40:45 DEBUG juju.provider.azure environ.go:680 destroying environment "azure"
2014-04-09 13:40:56 ERROR juju.cmd supercommand.go:300 PUT request failed: BadRequest - XML Schema validation error in network configuration at line 54,18. (http code 400: Bad Request)

Thanks!

Curtis Hovey (sinzui)
Changed in juju-core:
status: Incomplete → Triaged
importance: Undecided → High
tags: added: bootstrap
Changed in juju-core:
milestone: none → 1.19.1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.19.1 → 1.20.0
Changed in juju-core:
milestone: 1.20.0 → next-stable
Revision history for this message
Andrew Wilkins (axwalk) wrote :

I believe the XML Schema Validation errors no longer occur on trunk. I do not have a working Windows machine at the moment, so if anyone is able to test with trunk to see if the Windows issue persists, that would be very helpful.

Revision history for this message
Ian Booth (wallyworld) wrote :

Marking as fix committed since various Azure fixes were done to address this and other issues. Please re-open if problem still occurs on 1.19.4 or later releases.

Changed in juju-core:
assignee: nobody → Andrew Wilkins (axwalk)
milestone: next-stable → 1.20.0
status: Triaged → Fix Committed
Ian Booth (wallyworld)
Changed in juju-core:
milestone: 1.20.0 → none
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.