Service nova-network starts automatically when package gets installed on Ubuntu linux, this behaviour breaks OSTF check: Check that required services are running

Bug #1429085 reported by Igor Zinovik
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Igor Zinovik

Bug Description

Environment:
 Ubuntu as target OS
 3 controller
 vCenter enabled

Problem description:
During deploy nova-network service start automatically after its package was installed. When nova-network starts it creates a record in database with 'host' parameter. This makes OSTF tests to fail, becase nova database contains record of services
that were started with wrong host parameter.

This bug is related to https://bugs.launchpad.net/fuel/+bug/1426040

Steps to reproduce:
1. Create cluster with Ubuntu
2. Deploy 3 controller
3. Run OSTF or execute nova service-list

Expected result:
There are no services in 'down' state.

Actual result:
Several nova-network services appear with state 'down', because they are started on

Impact:
This behaviour breaks OSTF tests.

Tags: vcenter
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/162157

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/162157
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=70858545726cd011a6bf98b96c641bfc00184e08
Submitter: Jenkins
Branch: master

commit 70858545726cd011a6bf98b96c641bfc00184e08
Author: Igor Zinovik <email address hidden>
Date: Fri Mar 6 15:20:22 2015 +0300

    Do not start nova-network service on Ubuntu after package installation

    - apt-get on Ubuntu automatically run nova-network service after package
      installation, during this first run nova-network cannot be started
      with customized configuration file it leads to this: it records in
      database with nodes host name (e.g. 'node-2') and even if we start it
      with customized configuration file old record will be in database with
      state 'down'. All this leads to failed OSTF test: "Check that
      required services are running".

    Change-Id: Icc4a7006b409edfe5578ef75549186a50c3e3e89
    Closes-bug: 1429085

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Tatyana Dubyk (tdubyk) wrote :

Verified on 6.1.all (#218)

api: '1.0'
astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9
auth_required: true
build_id: 2015-03-23_15-29-20
build_number: '218'
feature_groups:
- mirantis
fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265
fuelmain_sha: a05ab877af31924585c81081f45305700961458e
nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3
ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867
production: docker
python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043
release: '6.1'
release_versions:
  2014.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9
      build_id: 2015-03-23_15-29-20
      build_number: '218'
      feature_groups:
      - mirantis
      fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265
      fuelmain_sha: a05ab877af31924585c81081f45305700961458e
      nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3
      ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867
      production: docker
      python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043
      release: '6.1'

Changed in fuel:
status: Fix Committed → Fix Released
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.