[vCenter] It is not possible to get metadata and internal / external network from VMs

Bug #1488563 reported by Timur Nurlygayanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
Critical
Fuel Partner Integration Team

Bug Description

MOS 7.0 ISO #154.

Lab:
3 controllers, Ubuntu, vCenter for compute nodes, 2 Ceph OSD nodes, VMDK images for VMs.

VMDK image with debian: http://files.linachan.ru/images/debian/debian-agent.vmdk

Please contact to MOS QA team to get the access to the lab.

Steps To Reproduce:
1. Install cloud with 3 controllers, 2 Ceph OSD nodes, vCenter for compute
2. Upload VMDK image to Glance and add required options:
root@node-1:~# glance image-show dagent | grep vmware
| Property 'hypervisor_type' | vmware |
| Property 'vmware_adaptertype' | lsilogic |
| Property 'vmware_disktype' | sparse

3. Boot VM

Expected Result:
Status of VM is active, VM can access metadata and can ping 8.8.8.8

Observed Result:
Status of VM is active, VM can't get metadata and can't access internal / external network.

We still debug the issue on the lab, we will add some details when the root of the issue will be found.

Tags: vcenter
Changed in fuel:
assignee: nobody → Fuel Partner Integration Team (fuel-partner)
importance: Undecided → Critical
milestone: none → 7.0
status: New → Confirmed
Revision history for this message
Victor Ryzhenkin (vryzhenkin) wrote :

Screenshot from VM, which will launched in vCenter

Revision history for this message
Victor Ryzhenkin (vryzhenkin) wrote :
tags: added: vcenter
description: updated
description: updated
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.