juju-core

munna/juju2 is too slow to deploy windows images

Bug #1605777 reported by Curtis Hovey
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-ci-tools
Triaged
Critical
Unassigned
juju-core
Triaged
Critical
Christian Muirhead
juju-core 2.0-beta14

Bug Description

As seen in
    http://reports.vapour.ws/releases/issue/5789759d749a5616aa83b491

munna with juju2 to now too slow to deploy windows images. Tests/Juju timeout waiting for machines to start.

We can see though that 1.25 can reliably pass the same test on the same host. Juju2 might be slow or broken. Munna is also very slow and may be a factor

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

The QA team is working a a windows test run in azure for Juju2. This might identify if the substrate is a factor

Changed in juju-core:
status: New → Triaged
importance: Undecided → Critical
tags: added: maas-provider regression windows
removed: reg
Tim Penhey (thumper)
Changed in juju-core:
milestone: none → 2.0-beta14
Anastasia (anastasia-macmood)
Changed in juju-core:
assignee: nobody → Christian Muirhead (2-xtian)
Revision history for this message
Christian Muirhead (2-xtian) wrote :

Example successful run with Juju 1.25 here:
http://reports.vapour.ws/releases/4150/job/maas-1-9-deploy-win2012hvr2-amd64/attempt/652

Can we get access to this environment to run a deploy manually? Is there any way to get the cloudbase-init logs off the machines that aren't coming up?

There have been pretty extensive changes to the user data we use when starting a Windows instance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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