Canonical Juju

Deploying a bundle to aws returns VPCResourceNotSpecified error

Bug #1616578 reported by Jeff Pihach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
High
Unassigned

Bug Description

When deploying this bundle: https://jujucharms.com/realtime-syslog-analytics/ to AWS using Juju 2 tip reporting as 2.0-beta16-trusty-amd64 a number of the machines do not get allocated because AWS returns an error:

'cannot run instances: The specified instance type can only be used
in a VPC. A subnet ID or network interface ID is required to carry out the
request. (VPCResourceNotSpecified)'

I can reproduce this simply by deploying this bundle at any time to AWS so it's not spurious.

See original description
Tags: 2.0
Alexis Bruemmer (alexis-bruemmer)
Changed in juju:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Richard Harding (rharding)
tags: added: 2.0
Jeff Pihach (hatch)
description: updated
Anastasia (anastasia-macmood)
Changed in juju:
milestone: none → 2.1.0
Anastasia (anastasia-macmood)
Changed in juju:
assignee: Richard Harding (rharding) → nobody
Revision history for this message
Anastasia (anastasia-macmood) wrote :

I cannot re-produce with 2.1 tip.

I've bootstrapped on AWS.

Deployed bundle: https://pastebin.canonical.com/179285/

Status after dust settled: https://pastebin.canonical.com/179286/

Changed in juju:
status: Triaged → Incomplete
milestone: 2.1.0 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
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.