Comment 7 for bug 1582599

Revision history for this message
Aleksandr Didenko (adidenko) wrote :

Root cause is missing fuel_pkgs/fuel_pkgs.pp task.

On primary controller tests made stop deployment on fuel_pkgs/setup_repositories.pp and then continued deployment on roles/allocate_hugepages.pp task. So fuel_pkgs/fuel_pkgs.pp task is missing. This is why corosync/pacemaker resources were not able to start:

2016-05-17T00:27:54.732628+00:00 warning: warning: Cannot execute '/usr/lib/ocf/resource.d/fuel/ns_vrouter': No such file or directory (2)
2016-05-17T00:27:54.732628+00:00 err: error: Failed to retrieve meta-data for ocf:fuel:ns_vrouter
2016-05-17T00:27:54.732628+00:00 warning: warning: No metadata found for ns_vrouter::ocf:fuel: Input/output error (-5)
2016-05-17T00:27:54.732628+00:00 err: error: No metadata for fuel::ocf:ns_vrouter
2016-05-17T00:27:54.732628+00:00 err: error: Operation p_vrouter_monitor_0 (node=node-3.test.domain.local, call=6, status=7, cib-update=39, confirmed=true) Not installed