Bug 1396172 - RHV VMs cannot be live migrated, Error "undefined method `auth_key_configured?' for nil:NilClass" [NEEDINFO]
Summary: RHV VMs cannot be live migrated, Error "undefined method `auth_key_configured...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Oved Ourfali
QA Contact: Ilanit Stein
URL:
Whiteboard: rhev
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-17 16:44 UTC by Prasad Mukhedkar
Modified: 2017-02-15 05:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-10 07:26:55 UTC
Category: ---
Cloudforms Team: RHEVM
Target Upstream Version:
oourfali: needinfo? (pmukhedk)

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

Description Prasad Mukhedkar 2016-11-17 16:44:21 UTC 
Description of problem:

There is 'Migrate this VM' option for rhv virtul machines
under 'vm/lifecycle' menu.

When I click on the live migration button, It takes me to "Migrate Virtual Machine" dialog to take  environment details. Select hosts to migrate the virtual machine. After filling the information when I clicked
"submit" button it thrown error "undefined method `auth_key_configured?' for nil:NilClass"


Version-Release number of selected component (if applicable):
Version 5.7.0.10-beta3.20161109111947_9a61b18

How reproducible:
always

Steps to Reproduce:

- Select a virtual machine, Go to 'vm/lifecycle'
  and click on "Migrate this VM"

- Enter the migration information.
- Submit.


Actual results:
Error in migration : 
undefined method `auth_key_configured?' for nil:NilClass"

Expected results:
successful migration 

Additional info:
Comment 2 Oved Ourfali 2016-11-17 18:24:32 UTC 
Seems like a duplicate of bug 1389303. 
What's your region number? 

CC-ing also Nick.
Note You need to log in before you can comment on or make changes to this bug.