gce Invalid volume ID destroying environment

Bug #1556293 reported by Seman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Invalid
High
Unassigned
1.25
Fix Released
High
Anastasia

Bug Description

While destroying GCE environment, Juju gets a "malformed volume id" error when other environments are also running

Juju version used 1.25.0 to 1,25.4 and master

Suspicious code:
https://github.com/juju/juju/blame/1.25/provider/gce/disks.go#L257
It seems the above code is trying to split the volume id using "--" as a separator but the id doesn't contain "--". Are we passing incorrect volume id?

Log:
http://reports.vapour.ws/releases/3715/job/gce-deploy-trusty-amd64/attempt/1146

2016-03-07 19:00:07 ERROR juju.cmd supercommand.go:429 environment destruction failed: destroying storage: destroying volumes: invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-1": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-1", invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-5": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-5", invalid volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-1": malformed volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-1", invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-3": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-3", invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-2": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-2", invalid volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-2": malformed volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-2", invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-0": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-0", invalid volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-4": malformed volume id "juju-1ee04202-c4aa-4137-8f6a-795f7cc1135b-machine-4", invalid volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-0": malformed volume id "juju-e6eefa0e-2906-4d5f-84dc-c5d275326508-machine-0"

How to reproduce:
Bootstrap two gce controllers or state-servers.
Destroy one controller or state-server
The error is reported because of the other disk for other server.
Juju exists with an error

Seman (sseman)
description: updated
Changed in juju-core:
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: regression
Revision history for this message
Curtis Hovey (sinzui) wrote :
Revision history for this message
Curtis Hovey (sinzui) wrote :

I don't think juju is leaking resources. I only see disks for what is being tested right now. While we get an error, the volume is deleted.

Seman (sseman)
description: updated
Revision history for this message
Curtis Hovey (sinzui) wrote :

We have found evidence of this going back to the development of 1.25.0. The code in question has not no changed since September of 2015. This issue is not visible when testing only one thing at a time in GCE.

summary: - Invalid volume ID
+ gce Invalid volume ID destroying environment
description: updated
tags: added: destroy-controller gce-provider
removed: regression test-failure
Revision history for this message
Anastasia (anastasia-macmood) wrote :
Revision history for this message
Anastasia (anastasia-macmood) wrote :

This behavior is not present on master.

Changed in juju-core:
status: Triaged → Invalid
Revision history for this message
Cheryl Jennings (cherylj) wrote :

CI shows that this problem has been seen on master branches: http://reports.vapour.ws/releases/issue/56e98a49749a5630fd107baa

Changed in juju-core:
status: Invalid → Triaged
Changed in juju-core:
status: Triaged → Invalid
Revision history for this message
Cheryl Jennings (cherylj) wrote :

The tests may be incorrect for the master branch.

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

Other bug subscribers

Remote bug watches

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