split-stack: can't upgrade from newton and use get-occ-config.sh since local collector was disabled

[James Slagle]

When trying to backport https://review.openstack.org/Ibde9e6bf360277d4ff64f66d637a5c7f0360e754 to ocata, the multinode-upgrades job is failing as in:

http://logs.openstack.org/41/454341/1/check/gate-tripleo-ci-centos-7-multinode-upgrades/8e8e5c6/

It's due to the fact that in the job, newton is initially deployed and get-occ-config.sh from newton is used to configure the subnodes. We were using the "heat" collector then, and also disabling all other collectors, including the local collector.

The patch being backported attempts to inject local data for the local collector so the subnodes can get their new metadata from the updated stack during the upgrade. However, since the local collector was previously disabled, their os-collect-config agents never act on the new data, and the stack update just hangs.

[Emilien Macchi (emilienm)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Ben Nemec (bnemec)]

I see the patch referenced in this bug got abandoned. Are we not going to fix this then?

[James Slagle (james-slagle)]

i need to investigate a different method, assuming we'll still care about this in queens. i'll move it to queens-1.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE