MOS 7.0 MU1 kvm+vmware environment fails to deploy with custom hostname for node

Bug #1534851 reported by Ihor Stehantsev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Igor Zinovik
7.0.x
Won't Fix
High
Igor Zinovik
8.0.x
Fix Released
High
Igor Zinovik

Bug Description

Problem:
nova-compute service configuration file does not get configured by puppet
manifests. Nailgun provides incorrect value in target node field, when
user changes hostname of a compute-vmware node on the Nodes tab.

Expected result:
cluster deploys without errors.

Actual result:
manifests do not configure nova-compute properly, after that vcenter_hooks.py
script is not able to add hypervisors (vSphere clusters in this case) to
availability zone.

Steps to reproduce:
1. Create cluster with vCenter
2. Add 1 controller
3. Add 1 compute-vmware node
4. Configure nova-compute (VCDriver) service on the VMware tab to use that
   node (set "Target node")
5. Switch to the Nodes tab
6. Rename hostname of compute-vmware node (click gear icon cogwheel)
7. Change "Hostname" (click pencil icon) parameter in popup window

Reproducable: 100%

Affected Fuel version: 7.0
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "301"
  build_id: "301"
  nailgun_sha: "4162b0c15adb425b37608c787944d1983f543aa8"
  python-fuelclient_sha: "486bde57cda1badb68f915f66c61b544108606f3"
  fuel-agent_sha: "50e90af6e3d560e9085ff71d2950cfbcca91af67"
  fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
  astute_sha: "6c5b73f93e24cc781c809db9159927655ced5012"
  fuel-library_sha: "5d50055aeca1dd0dc53b43825dc4c8f7780be9dd"
  fuel-ostf_sha: "2cd967dccd66cfc3a0abd6af9f31e5b4d150a11c"
  fuelmain_sha: "a65d453215edb0284a2e4761be7a156bb5627677"

tags: added: vmware
description: updated
Revision history for this message
Maciej Relewicz (rlu) wrote :

Hi, thank you for your report, but please provide diagnostic snapshot from the failed environment if it is possible.

tags: added: area-partners
Changed in fuel:
importance: Undecided → Medium
assignee: nobody → Fuel Partner Core (fuel-partner-core)
milestone: none → 7.0-updates
Maciej Relewicz (rlu)
Changed in fuel:
status: New → Incomplete
Changed in fuel:
assignee: Fuel Partner Core (fuel-partner-core) → Partner Centric Engineering (fuel-partner-engineering)
Revision history for this message
Ihor Stehantsev (istegantsev) wrote :

I can not provide a snapshot, as far as it happened on a customer env, and I do not have access to it.

Changed in fuel:
status: Incomplete → Triaged
Revision history for this message
Andrian Noga (anoga) wrote :

Colleagues,

to fix this bug, we need to get a snapshot.

Andrian Noga (anoga)
Changed in fuel:
importance: Medium → High
importance: High → Medium
Revision history for this message
Alexander Arzhanov (aarzhanov) wrote :

Possible causes:
1. MOS 7.0 GA OpenStack integration requires a vCenter service account with the following minimum permissions (see point about "VMware vCenter service account"):
http://docs.openstack.org/kilo/config-reference/content/vmware.html
Please check your vCenter account permissions. Most likely, you are missing, at least, "Register extension" permissions.
2. Double check data on VMware tab (vCenter host, vCenter username, vCenter password, vSphere cluster,etc)
3. Check network connectivity to vCenter. Can you ping vCenter IP or vCenter dns name from compute-vmware node?

Igor Zinovik (izinovik)
tags: added: customer-found
Igor Zinovik (izinovik)
description: updated
Changed in fuel:
milestone: 7.0-updates → 9.0
status: Triaged → Confirmed
Changed in fuel:
assignee: Partner Centric Engineering (fuel-partner-engineering) → Igor Zinovik (izinovik)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/273041

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Alexander Arzhanov (aarzhanov) wrote : Re: MOS 7.0 MU1 kvm+vmware environment fails to deploy

I raise the Importance to High, because it's customer-found bug and it is very important for Wells Fargo.

Changed in fuel:
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/8.0)

Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/273046

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/273041
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=49c5a4870fbcd9791c3f6525313a736be97a4159
Submitter: Jenkins
Branch: master

commit 49c5a4870fbcd9791c3f6525313a736be97a4159
Author: Igor Zinovik <email address hidden>
Date: Wed Jan 27 16:25:17 2016 +0300

    Fix manifest behaviour on hostname change

    Manifest relies on fact that 'target_node' value that is provided by
    Nailgun will always match pattern 'node-[0-9]', but backend provides
    hostname that can be changed by user.

    Closes-bug: #1534851
    Change-Id: I4a9984d683bd741785e1f9f70476ed74fcc0c478

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (stable/7.0)

Fix proposed to branch: stable/7.0
Review: https://review.openstack.org/273488

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (stable/8.0)

Reviewed: https://review.openstack.org/273046
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=c90c2bae420a8c7f0e2b1e622ae9fc459b900834
Submitter: Jenkins
Branch: stable/8.0

commit c90c2bae420a8c7f0e2b1e622ae9fc459b900834
Author: Igor Zinovik <email address hidden>
Date: Wed Jan 27 16:25:17 2016 +0300

    Fix manifest behaviour on hostname change

    Manifest relies on fact that 'target_node' value that is provided by
    Nailgun will always match pattern 'node-[0-9]', but backend provides
    hostname that can be changed by user.

    Closes-bug: #1534851
    Cherry-picked from 49c5a48
    Change-Id: I4a9984d683bd741785e1f9f70476ed74fcc0c478

tags: added: area-pce-vcenter
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote : Re: MOS 7.0 MU1 kvm+vmware environment fails to deploy

Was tested with Fuel 8.0 #512

summary: - MOS 7.0 MU1 kvm+vmware environment fails to deploy
+ MOS 7.0 MU1 kvm+vmware environment fails to deploy with custom hostname
+ for node
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Verified on Fuel 9.0 mos-iso#495 (RC2) with DVS 3.0.0 build 705

Changed in fuel:
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (stable/7.0)

Change abandoned by Igor Zinovik (<email address hidden>) on branch: stable/7.0
Review: https://review.openstack.org/273488

Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

fix abandoned by the author

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.