WARN: Could not disable basic service for Pacemaker primitive 'vip__management' using 'upstart' provider
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Dmitry Ilyin | ||
6.0.x |
Won't Fix
|
Medium
|
Dmitry Ilyin | ||
7.0.x |
Won't Fix
|
Medium
|
Dmitry Ilyin |
Bug Description
"build_id": "2014-11-
"ostf_sha": "8be702d5cafcb7
"build_number": "122",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "e4c59607c852f1
"production": "docker",
"fuelmain_sha": "3a6833b3e5223c
"astute_sha": "46d23177f9c0e5
"feature_groups": ["mirantis"],
"release": "6.0",
"release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-11-
"fuellib_sha": "666c40d0f5c0bb
1. Create new environment (Ubuntu, HA mode)
2. Choose nova-network, flat
3. Choose Sahara
4. Add 3 controllers, 1 compute, 1 cinder
5. Start deployment. It was successful
6. There are warnings on all of controllers (node-20, 21, 9)
2014-11-21 16:12:06 WARNING
Could not disable basic service for Pacemaker primitive 'vip__management' using 'upstart' provider: Could not find init script or upstart conf file for 'vip__management'
2014-11-21 16:11:57 WARNING
Could not disable basic service for Pacemaker primitive 'ping_vip__public' using 'upstart' provider: Could not find init script or upstart conf file for 'ping_vip__public'
2014-11-21 16:11:39 WARNING
Could not disable basic service for Pacemaker primitive 'vip__public' using 'upstart' provider: Could not find init script or upstart conf file for 'vip__public'
Logs are here: https:/
Changed in fuel: | |
status: | New → Invalid |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Dmitry Ilyin (idv1985) |
Changed in fuel: | |
status: | Won't Fix → Confirmed |
Changed in fuel: | |
importance: | Medium → Low |
Changed in fuel: | |
milestone: | 6.1-updates → 8.0 |
tags: | added: area-library |
tags: | added: wontfix-feature |
That is expexcted behavior for those pacemaker services. Lowering priority to medium.
Maybe we should switch this type of messages from Puppet.warning to Puppet.info?