From 2b08028567f63309f8bd0931739dd9a2afc6c0d6 Mon Sep 17 00:00:00 2001 From: Howard Pritchard Date: Tue, 8 Aug 2017 16:28:12 -0600 Subject: [PATCH] mca/registry: fix problem group_component_register Turns out that supplying NULL to group_register in the mca_base_var_group_component_register is not a good idea if one wants for ompi_info to work as intended. The ugni and vader btl's both call this before registering component variables. This borks up the ompi_info works since NULL is supplied as the project name. So, now supply the project name rather than just NULL to group register. Fixes #4020. Signed-off-by: Howard Pritchard (cherry picked from commit 55774d13907ce002185bb97525faa6300e0910b5) --- opal/mca/base/mca_base_var_group.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/opal/mca/base/mca_base_var_group.c b/opal/mca/base/mca_base_var_group.c index 6fec2e21067..eb7ef326bfd 100644 --- a/opal/mca/base/mca_base_var_group.c +++ b/opal/mca/base/mca_base_var_group.c @@ -319,8 +319,7 @@ int mca_base_var_group_register (const char *project_name, const char *framework int mca_base_var_group_component_register (const mca_base_component_t *component, const char *description) { - /* 1.7 components do not store the project */ - return group_register (NULL, component->mca_type_name, + return group_register (component->mca_project_name, component->mca_type_name, component->mca_component_name, description); }