juju destroy-environment >=256 nodes fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
juju-core (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
maas (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
juju destroy-environment in a large maas deployment (~256 servers) fails with:
ERROR destroying environment: gomaasapi: got error back from server: 414 Request-URI Too Long (<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>414 Request-URI Too Long</title>
</head><body>
<h1>Request-URI Too Long</h1>
<p>The requested URL's length exceeds the capacity
limit for this server.<br />
</p>
<hr>
<address>
</body></html>
)
Using the --force option worked around this.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.5+bzr2252-
ProcVersionSign
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
Date: Mon May 5 12:04:35 2014
InstallationDate: Installed on 2014-04-18 (17 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitec
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
Related branches
- Juju Engineering: Pending requested
-
Diff: 1305 lines (+232/-257)38 files modifiedcontainer/interface.go (+7/-3)
container/kvm/kvm.go (+2/-2)
container/kvm/kvm_test.go (+1/-1)
container/kvm/live_test.go (+1/-1)
container/lxc/lxc.go (+2/-2)
container/lxc/lxc_test.go (+5/-5)
dependencies.tsv (+1/-1)
environs/broker.go (+3/-2)
environs/jujutest/livetests.go (+6/-6)
environs/jujutest/tests.go (+1/-1)
provider/azure/environ.go (+17/-16)
provider/azure/environ_test.go (+11/-12)
provider/common/bootstrap.go (+1/-1)
provider/common/bootstrap_test.go (+7/-7)
provider/common/destroy.go (+6/-1)
provider/common/destroy_test.go (+11/-11)
provider/common/mock_test.go (+3/-3)
provider/dummy/environs.go (+7/-7)
provider/ec2/ec2.go (+1/-5)
provider/ec2/live_test.go (+5/-5)
provider/joyent/environ_instance.go (+39/-6)
provider/joyent/instance.go (+0/-41)
provider/joyent/local_test.go (+3/-3)
provider/local/environ.go (+5/-5)
provider/maas/environ.go (+11/-25)
provider/maas/environ_whitebox_test.go (+17/-13)
provider/maas/util.go (+3/-3)
provider/maas/util_test.go (+1/-1)
provider/manual/environ.go (+1/-1)
provider/openstack/local_test.go (+8/-8)
provider/openstack/provider.go (+23/-19)
state/apiserver/client/destroy.go (+1/-22)
worker/provisioner/kvm-broker.go (+4/-4)
worker/provisioner/kvm-broker_test.go (+3/-3)
worker/provisioner/lxc-broker.go (+4/-4)
worker/provisioner/lxc-broker_test.go (+3/-3)
worker/provisioner/provisioner_task.go (+6/-2)
worker/provisioner/provisioner_test.go (+2/-2)
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.19.2 |
tags: | added: destroy-environment maas-provider |
Changed in juju-core: | |
milestone: | 1.19.2 → 1.19.3 |
Changed in juju-core (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in juju-core: | |
assignee: | nobody → Andrew Wilkins (axwalk) |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | Triaged → Confirmed |
Changed in juju-core (Ubuntu): | |
status: | Confirmed → Fix Released |
It looks like that error came from Apache, so I'm going to invalidate the maas task. If you think I'm wrong, please open it again and tell me why, I won't be offended.