Bug 1376865 - Azure power start vm only starts first vm when multiple vms are selected.
Summary: Azure power start vm only starts first vm when multiple vms are selected.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 5.7.0
Assignee: Greg Blomquist
QA Contact: Jeff Teehan
URL:
Whiteboard: provider:azure:power
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 16:27 UTC by Jeff Teehan
Modified: 2016-09-19 01:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-16 16:55:40 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jeff Teehan 2016-09-16 16:27:33 UTC 
Description of problem:
At the Instances page I selected two VMs by checkbox and then selected Start from the Power menu.  The flash message asked if I wanted to start both VMs, but when I went to Azure only the first vm in the list was powered on.  I checked the second vm Audit log to see if an attempt was made, but there was no reference.

Version-Release number of selected component (if applicable):
5.6.2.0.20160913114355_70e9086

How reproducible:
Always on 10.16.6.182

Steps to Reproduce:
1.  Compute:cloud:instances
2.  Select two or more vms.
3.  Select start from the power menu.
4.  Click ok to confirm

Actual results:
Only the first VM powered on.

Expected results:
Both vms to power on.

Additional info:
That appliance should be running for a week or two.
Comment 2 Jeff Teehan 2016-09-16 16:34:11 UTC 
Added Polarion test case - https://polarion.engineering.redhat.com/polarion/#/project/RHCF3/workitem?id=RHCF3-11959
Comment 3 Jeff Teehan 2016-09-16 16:55:40 UTC 
Argh rabbit skins.  Azure finally updated the audit log and in fact the vm I select is missing a resource.  Tried with another regions vms and it worked fine. 
jt--
Note You need to log in before you can comment on or make changes to this bug.