cannot obtain provisioning script

Bug #1559299 reported by Aaron Bentley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Unassigned
juju-core
Fix Released
High
Anastasia
1.25
Fix Released
High
Anastasia

Bug Description

Bootstrap fails because juju cannot obtain a provisioning script. Seen only on manual-provider so far.

As seen here:
http://reports.vapour.ws/releases/issue/56ec65fa749a564cbca944bf

Aaron Bentley (abentley)
Changed in juju-core:
status: New → Incomplete
Revision history for this message
Ian Booth (wallyworld) wrote :

I can't reproduce this so far.
I set up an LXD machine, 10.0.1.19

$ juju bootstrap --debug --upload-tools ian manual/10.0.1.19
...
...
2016-03-20 11:49:48 INFO cmd cmd.go:129 Bootstrap complete, local.ian now available.
2016-03-20 11:49:48 INFO cmd supercommand.go:454 command finished
$
$ juju list-models
NAME OWNER LAST CONNECTION
admin admin@local never connected
default* admin@local 5 seconds ago
$

All works as expected.

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

I then added a new manual machine and installed some charms. Wordpress I installed to machine 0 and mysql to machine 1. mysql installed fine. wordpress failed because it tries to download the charm from the controller ip for some reason. Not sure why. But there's no error about not getting a provisioning script.

juju status
[Services]
NAME STATUS EXPOSED CHARM
mysql unknown false cs:trusty/mysql-36
wordpress unknown false cs:trusty/wordpress-4

[Relations]
SERVICE1 SERVICE2 RELATION TYPE
mysql mysql cluster peer
wordpress wordpress loadbalancer peer

[Units]
ID WORKLOAD-STATUS JUJU-STATUS VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
mysql/0 unknown idle 2.0-delta1.1 1 3306/tcp 10.0.1.86
wordpress/0 unknown allocating 2.0-delta1.1 0 10.0.1.19 Waiting for agent initialization to finish

[Machines]
ID STATE DNS INS-ID SERIES AZ
0 started 10.0.1.19 manual: trusty
1 started 10.0.1.86 manual:10.0.1.86 trusty

...

unit-wordpress-0: 2016-03-20 12:06:30 DEBUG juju.worker.dependency engine.go:465 "uniter" manifold worker stopped: preparing operation "install cs:trusty/wordpress-4": failed to download charm "cs:trusty/wordpress-4" from ["https://10.0.1.19:17070/model/784af577-73ca-459f-8d90-95f43f9eb965/charms?file=%2A&url=cs%3Atrusty%2Fwordpress-4"]: cannot download "https://10.0.1.19:17070/model/784af577-73ca-459f-8d90-95f43f9eb965/charms?file=%2A&url=cs%3Atrusty%2Fwordpress-4": bad http response: 400 Bad Request

Revision history for this message
Andrew Wilkins (axwalk) wrote :

There's a problem with the manual and lxd providers, which I'll fix separately. I've proposed a simplification of the provisioning script code that avoids the issues for now: https://github.com/juju/juju/pull/4816

Curtis Hovey (sinzui)
Changed in juju-core:
status: Incomplete → Invalid
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue is now in juju 1.25.

Changed in juju-core:
status: Invalid → Incomplete
tags: added: blocker regression xenial
Revision history for this message
Anastasia (anastasia-macmood) wrote :
tags: removed: blocker
Changed in juju-core:
status: Incomplete → Invalid
Revision history for this message
Aaron Bentley (abentley) wrote :

This is actually our top issue in master (excluding things that are already fixed). I don't see a rationale for marking it invalid.

http://reports.vapour.ws/releases/issue/56ec65fa749a564cbca944bf

Changed in juju-core:
status: Invalid → Triaged
importance: Undecided → High
affects: juju-core → juju
Changed in juju:
milestone: none → 2.0.0
Changed in juju-core:
assignee: nobody → Anastasia (anastasia-macmood)
importance: Undecided → High
status: New → Fix Released
Revision history for this message
Richard Harding (rharding) wrote :

Not seen since July 29, marking as fix released.

Changed in juju:
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.