| 2019-01-25 14:23:58 |
F.B. |
bug |
|
|
added bug |
| 2019-01-25 14:25:32 |
F.B. |
description |
jujud versions : 2.4.7, 2.5.0
Fault location : provider/vsphere/internal/vsphereclient/client.go, function extendDisk
when called upon root-disk constraint, taskWaiter.waitTask(ctx, task, "extending disk") never gives up and prevents furthers actions (powering on, ...).
If bypassed by a simple time.Sleep giving enough time to the disk extension, everything's fine, the VM starts and is correctly deployed.
That's the problem described in https://bugs.launchpad.net/juju/+bug/1790183 |
jujud versions : 2.4.7, 2.5.0
Fault location : provider/vsphere/internal/vsphereclient/client.go, function extendDisk
when called upon root-disk constraint, taskWaiter.waitTask(ctx, task, "extending disk") never gives up and prevents further actions (powering on, ...).
If bypassed by a simple time.Sleep giving enough time to the disk extension, everything's fine, the VM starts and is correctly deployed.
That's the problem described in https://bugs.launchpad.net/juju/+bug/1790183 |
|
| 2019-01-25 14:26:20 |
F.B. |
tags |
|
vsphere-provider |
|
| 2019-01-25 14:26:43 |
F.B. |
description |
jujud versions : 2.4.7, 2.5.0
Fault location : provider/vsphere/internal/vsphereclient/client.go, function extendDisk
when called upon root-disk constraint, taskWaiter.waitTask(ctx, task, "extending disk") never gives up and prevents further actions (powering on, ...).
If bypassed by a simple time.Sleep giving enough time to the disk extension, everything's fine, the VM starts and is correctly deployed.
That's the problem described in https://bugs.launchpad.net/juju/+bug/1790183 |
jujud versions : 2.4.7, 2.5.0
Fault location : provider/vsphere/internal/vsphereclient/client.go, function extendDisk
when called upon root-disk constraint, taskWaiter.waitTask(ctx, task, "extending disk") never gives up and prevents further actions (powering on, ...).
If bypassed by a simple time.Sleep giving enough time for the disk extension, everything's fine, the VM starts and is correctly deployed.
That's the problem described in https://bugs.launchpad.net/juju/+bug/1790183 |
|
| 2019-01-25 21:31:10 |
Ian Booth |
juju: milestone |
|
2.5.1 |
|
| 2019-01-25 21:31:20 |
Ian Booth |
juju: assignee |
|
Christian Muirhead (2-xtian) |
|
| 2019-01-25 21:31:26 |
Ian Booth |
juju: status |
New |
Triaged |
|
| 2019-01-25 21:31:30 |
Ian Booth |
juju: importance |
Undecided |
High |
|
| 2019-01-28 22:07:45 |
Ian Booth |
juju: milestone |
2.5.1 |
2.5.2 |
|
| 2019-03-11 23:01:55 |
Canonical Juju QA Bot |
juju: milestone |
2.5.2 |
2.5.3 |
|
| 2019-03-26 02:09:16 |
Canonical Juju QA Bot |
juju: milestone |
2.5.3 |
2.5.4 |
|
| 2019-04-02 01:46:38 |
Canonical Juju QA Bot |
juju: milestone |
2.5.4 |
2.5.5 |
|
| 2019-05-14 06:23:17 |
Anastasia |
juju: milestone |
2.5.6 |
2.5.8 |
|
| 2019-06-28 02:03:46 |
Canonical Juju QA Bot |
juju: milestone |
2.5.8 |
2.5.9 |
|
| 2019-10-31 03:44:38 |
Anastasia |
juju: milestone |
2.5.9 |
|
|
| 2022-11-03 15:22:03 |
Canonical Juju QA Bot |
juju: importance |
High |
Low |
|
| 2022-11-03 15:22:04 |
Canonical Juju QA Bot |
tags |
vsphere-provider |
expirebugs-bot vsphere-provider |
|
