So, I've reproduced it and it actually happens from the upgrade of bionic-queens (distro) -> bionic-rocky. It does move from its "own" api executable to being run under wsgi in apache2. The fix (as Drew reported) is to migrate the check to validating the wsgi service. An interim is to simply rely on the fact that the apache2 check "means" that the api is running at bionic and remove the defunct nova-api-os-compute check altogether.
I'll investigate the difficulty on the former, but put a patch in to clean up the defunct check at bionic+.
So, I've reproduced it and it actually happens from the upgrade of bionic-queens (distro) -> bionic-rocky. It does move from its "own" api executable to being run under wsgi in apache2. The fix (as Drew reported) is to migrate the check to validating the wsgi service. An interim is to simply rely on the fact that the apache2 check "means" that the api is running at bionic and remove the defunct nova-api-os-compute check altogether.
I'll investigate the difficulty on the former, but put a patch in to clean up the defunct check at bionic+.