Regarding the error in puppet repos, it turned out that one repo(puppet-openstack-integration)
has no deliverables for Pike and Ocata and because of that its stable/ocata and stable/pike
have not yet been EOLed.
(These two stable branches were EOLed in the other puppet repos)

I've raised this in #openstack-release channel and will ask some help from the release team
to move these two branches in p-o-i repo to EOL.

On Sat, Jun 26, 2021 at 2:28 PM Takashi Kajinami <tkajinam@redhat.com> wrote:
The EOL tags for stable/ocata and pike for puppet-openstack were created a while ago[1]
and these two branches are no longer maintained.
Because eol tag was already created, we can remove the stable/ocata branch
and the stable/pike branch from git repo and gerrit.
I'll ask the Release Management team to delete these two branches, then I expect
the current errors will be solved.
(Sorry but it seems I forgot to ask the deletion when I proposed EOL)

[1] https://review.opendev.org/c/openstack/releases/+/726392/


On Sat, Jun 26, 2021 at 1:57 AM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2021-06-25 10:39:25 -0600 (-0600), Alex Schultz wrote:
[...]
> It looks like puppet-openstack-integration stable/ocata and
> stable/pike needs to be cleaned up/removed. I don't see it as
> deliverables in the releases repo so these might have been
> manually created before moving under the release umbrella. I
> believe we've EOL'd pike and ocata for the regular modules. What
> would be the best course of action to clean up these branches?
[...]

The OpenStack Release Managers have branch deletion access via the
Gerrit WebUI and REST API, and have been performing scripted batch
deletions of EOL branches for a little while now. These may already
be slated for removal, but it can't hurt to confirm.
--
Jeremy Stanley