Deploy has failed with 'Could not evaluate: Primitive 'p_vrouter' was not found in CIB!' errors on slave controller nodes

Bug #1449523 reported by Vadim Rovachev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Vadim Rovachev

Bug Description

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "357"
  build_id: "2015-04-27_22-54-38"
  nailgun_sha: "5e52637d9944c2f4170012560d15ecf89a691af6"
  python-fuelclient_sha: "8cd6cf575d3c101dee1032abb6877dfa8487e077"
  astute_sha: "c1793f982fda7e3fc7b937ccaa613c649be6a144"
  fuel-library_sha: "0e5b82d24853304befb22145ac4aaf3545d295e1"
  fuel-ostf_sha: "b38602c841deaa03ddffc95c02f319360462cbe3"
  fuelmain_sha: "1ec588d364b9b97f124f6d602dbcc4aa13327218"

Env parameters:
nodes:
   [controller + mongo] x3 KVM
   [compute + ceph_osd] x1 Supermicro
virt_type=kvm
config_mode=ha_compact
release_name=centos
net_provider=neutron
net_segment_type=vlan

Deploy env has failed with error message:
Deployment has failed. Method granular_deploy. Deployment failed on nodes 4.
Inspect Astute logs for the details

errors on controller nodes:
http://paste.openstack.org/show/210061/

Revision history for this message
Vadim Rovachev (vrovachev) wrote :
Changed in fuel:
milestone: none → 6.1
summary: - Environment has failed with 'Could not evaluate: Primitive 'p_vrouter'
- was not found in CIB!' errors on slave controller nodes
+ Deploy has failed with 'Could not evaluate: Primitive 'p_vrouter' was
+ not found in CIB!' errors on slave controller nodes
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
importance: Undecided → High
Changed in fuel:
status: New → In Progress
assignee: Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov)
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

There were no cluster for corosync created:

What network driver you were using? Was it e1000?

Nonealex@alex-B85M-DS3H:/tmp/fuel-snapshot-2015-04-28_11-36-13$ cat ./node-3.domain.tld/commands/pcs_status.txt
===== COMMAND =====: pcs status
===== RETURN CODE =====: 0
===== STDOUT =====:
[node-3.domain.tld] out: Cluster name:
[node-3.domain.tld] out: Last updated: Tue Apr 28 11:36:14 2015
[node-3.domain.tld] out: Last change: Tue Apr 28 10:54:51 2015
[node-3.domain.tld] out: Stack: corosync
[node-3.domain.tld] out: Current DC: node-3.domain.tld (3) - partition WITHOUT quorum
[node-3.domain.tld] out: Version: 1.1.11-97629de
[node-3.domain.tld] out: 1 Nodes configured
[node-3.domain.tld] out: 0 Resources configured
[node-3.domain.tld] out:
[node-3.domain.tld] out:
[node-3.domain.tld] out: Online: [ node-3.domain.tld ]
[node-3.domain.tld] out:
[node-3.domain.tld] out: Full list of resources:
[node-3.domain.tld] out:
[node-3.domain.tld] out:
[node-3.domain.tld] out:

Changed in fuel:
status: In Progress → Incomplete
assignee: Oleksiy Molchanov (omolchanov) → Vadim Rovachev (vrovachev)
Revision history for this message
Vadim Rovachev (vrovachev) wrote :

No, on KVM nodes uses virtio driver

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Our network in Centos doesn't work with virtio =( Use e1000 instead

Changed in fuel:
status: Incomplete → Invalid
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.