Canonical Juju

Fails to add unit after origin controller destroyed

Bug #1668469 reported by Christopher Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

As seen at: http://reports.vapour.ws/releases/issue/58b4d876749a560fcddefeb4

On GCE when attempting to add a unit to a model that has been migrated and after the origin controller has been destroyed an error is raised with the text like:

ERROR ('2', 'sending new instance request: GCE operation "operation-1488232260102-5498a1334e770-7e42e157-19314605" failed')

Possibly related to LP:1668471

See original description
Christopher Lee (veebers)
description: updated
Anastasia (anastasia-macmood)
tags: added: gce-provider intermittent-failure race-condition regression
Changed in juju:
importance: High → Medium
status: Confirmed → Triaged
Revision history for this message
Tim Penhey (thumper) wrote :

I think this is just better provisioning retries and provisioning awareness.

tags: added: provisioner
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Since this report has been filed, we have added a functionality to re-direct users to a new location (controller/model) after a migration. I wonder if this failure has been addressed as part of that work.

I would have expected this failure to be non-provider specific.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
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.