Erroneous Juju user data on Windows for Juju version 1.23

Bug #1451626 reported by Adrian Vladu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Unassigned
1.24
Fix Released
High
Gabriel Samfira

Bug Description

On Windows 2012 R2 with Juju tools 1.23, MAAS user data fails to execute due to an erroneous echo redirect.
This is the PowerShell user data line that fails in my case:
    echo 'Starting Juju machine agent (jujud-machine-1)' >&9

I have attached the cloudbase-init log.

Due to this issue, all the Juju 1.23.x versions are not working with Windows supported versions.

Revision history for this message
Adrian Vladu (avladu) wrote :
description: updated
description: updated
description: updated
Curtis Hovey (sinzui)
tags: added: windows
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.24-alpha1
milestone: 1.24-alpha1 → 1.25.0
Revision history for this message
Gabriel Samfira (gabriel-samfira) wrote :

There are a couple of branches in review that will fix windows userdata. Those will probably have to be backported to 1.23.

Revision history for this message
Gabriel Samfira (gabriel-samfira) wrote :

The following PRs will restore Windows functionality in master branch.

http://reviews.vapour.ws/r/1609/
http://reviews.vapour.ws/r/1608/

Larry Michel (lmic)
tags: added: oil
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue is confirmed to be in 1.23.3
    https://pastebin.canonical.com/131541/

tags: added: blocker regression
Revision history for this message
Eric Snow (ericsnowcurrently) wrote :

It isn't clear why fixing this requires Go 1.4. Could someone elaborate?

My suspicion is that we have some dependency that needs to be updated and the updated revision requires Go 1.4. If that is the case then in the meantime I'd recommend forking that dependency, fixing it in your fork, and then updating juju to use your fork. Once we move to Go 1.4 we can drop the fork.

Changed in juju-core:
status: Triaged → 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.