Bootstrapping azure causes memory to fill
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
juju-core (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
When running 'juju bootstrap -e azure' my memory is completely filling up (16GB +8GB swap) within about 1-2 minutes, leaving me with an unusable system. I have also tried using the package in the ppa which I experienced the same issue.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
juju-core:
Installed: 1.16.0-0ubuntu1
Candidate: 1.16.0-0ubuntu1
Version table:
*** 1.16.0-0ubuntu1 0
500 http://
500 http://
100 /var/lib/
Is there any specific logs you need with this bug report?? If so i will get those to you asap.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: juju 1.16.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 11 09:28:09 2013
Dependencies:
gcc-4.8-base 4.8.1-10ubuntu8
juju-core 1.16.0-0ubuntu1
libc6 2.17-93ubuntu4
libgcc1 1:4.8.1-10ubuntu8
multiarch-support 2.17-93ubuntu4
InstallationDate: Installed on 2013-10-28 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitec
SourcePackage: juju-core
UpgradeStatus: Upgraded to saucy on 2013-11-10 (0 days ago)
FIX:
The problem is caused by using the *.cer. Azure wants the *.pem file. The azure documentation from MS is vague. Users of the SDKs also make this mistake.
The juju azure-provider could check if the file is a pem and raise an error early.
Changed in juju-core: | |
status: | Incomplete → Triaged |
importance: | Undecided → High |
milestone: | none → 1.17.1 |
Changed in juju-core: | |
milestone: | 1.17.1 → 1.18.0 |
Changed in juju-core (Ubuntu): | |
importance: | Undecided → High |
Changed in juju-core: | |
milestone: | 1.20.0 → next-stable |
tags: | added: azure-provider |
description: | updated |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
milestone: | next-stable → 1.19.4 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Confirmed → Fix Released |
We have never seen this in automated or manual testing, both of which use machines with 2-4Gs of memory. Does this happen with 1.16.5?