RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 858652 - vdsm: migration of vm fails with FQDN error in vdsm 4.9-113.3 but succeeds with vdsm 4.9.6-32.0
Summary: vdsm: migration of vm fails with FQDN error in vdsm 4.9-113.3 but succeeds wi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Michal Skrivanek
QA Contact: Haim
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 10:26 UTC by Dafna Ron
Modified: 2014-01-13 00:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-20 21:35:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
vdsm log (864.08 KB, application/x-xz)
2012-09-19 10:26 UTC, Dafna Ron
no flags Details

Description Dafna Ron 2012-09-19 10:26:36 UTC
Created attachment 614303 [details]
vdsm log

Description of problem:

I have a host which is added with correct FQDN but the host name in the host still appears as localhost. 
when I have vdsm 4.9-113.3 I fail to migrate vm's to the host with the below error: 

libvirtError: internal error hostname on destination resolved to localhost, but migration requires an FQDN

but in vdsm  vdsm 4.9-32.0 I succeed to migrate. 

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

vdsm 4.9-113.3
vdsm 4.9-32.0
si18

How reproducible:

100%

Steps to Reproduce:
1. have two hosts both registered in DHCP with correct host name 
2.  1host should still be called localhost (local). 
3. install hosts in a 3.0 cluster with vdsm 4.9-113.3 using FQDN name and not IP
4. create and run vm's -> try to migrate vm's to the host which is called localhost 
  
Actual results:

we fail migration in vdsm 4.9-113.3
after upgrading vdsm to vdsm 4.9-32.0 we are able to migrate the vm. 

Expected results:

we should be able to migrate the vms in both vdsm versions. 


Additional info: vdsm log with both failed migration and success. 


succeeds: 

Thread-1470::DEBUG::2012-09-19 11:52:24,350::BindingXMLRPC::864::vds::(wrapper) client [10.35.97.65]::call vmMigrate with ({'src': 'gold-vdsd.qa.lab.tlv.redhat.com', 'dst': 'gold-vdsc.qa.lab.tlv.redhat.com:54321', 'vmId': 'ecbfaeed-0b8f
-4639-82a6-021f4239f975', 'method': 'online'},) {} flowID [6c5a60ae]
Thread-1470::DEBUG::2012-09-19 11:52:24,351::API::421::vds::(migrate) {'src': 'gold-vdsd.qa.lab.tlv.redhat.com', 'dst': 'gold-vdsc.qa.lab.tlv.redhat.com:54321', 'vmId': 'ecbfaeed-0b8f-4639-82a6-021f4239f975', 'method': 'online'}
Thread-1470::DEBUG::2012-09-19 11:52:24,354::BindingXMLRPC::870::vds::(wrapper) return vmMigrate with {'status': {'message': 'Migration process starting', 'code': 0}}


failed: 

Thread-1850::DEBUG::2012-09-19 10:47:20,010::clientIF::54::vds::(wrapper) [10.35.97.65]::call migrate with ({'src': 'gold-vdsd.qa.lab.tlv.redhat.com', 'dst': 'gold-vdsc.qa.lab.tlv.redhat.com:54321', 'vmId': 'ecbfaeed-0b8f-4639-82a6-021f
4239f975', 'method': 'online'},) {}
Thread-1850::DEBUG::2012-09-19 10:47:20,013::clientIF::357::vds::(migrate) {'src': 'gold-vdsd.qa.lab.tlv.redhat.com', 'dst': 'gold-vdsc.qa.lab.tlv.redhat.com:54321', 'vmId': 'ecbfaeed-0b8f-4639-82a6-021f4239f975', 'method': 'online'}
Thread-1850::DEBUG::2012-09-19 10:47:20,018::clientIF::59::vds::(wrapper) return migrate with {'status': {'message': 'Migration process starting', 'code': 0}}

Comment 3 Itamar Heim 2012-09-20 21:35:55 UTC
3.0 doesn't support migration without full fqdn.
3.1 does and removed the specific error log. no change in behavior of live migratoin itself in 3.0 mode)


Note You need to log in before you can comment on or make changes to this bug.