[Upgrade from stein to train] After upgrade, nova-compute-kvm went into hook error "cloud-compute-relation-changed"

[Celia Wang]

I recently do a upgrade for a customer following this doc: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/placement-charm-upgrade-to-train.html

After upgrade, I found I met this bug: https://bugs.launchpad.net/charm-placement/+bug/1928992
With "openstack endpoint list", placement is using nova FQDN. A while later, it automatically chagned to placement prefix FQDN for placement but with http protocol while other services are https protocol.

I've manually changed the url to https:... with "openstack endpoint set <id> --url <url>".

Also, I've manually removed left over endpoint info from ncc with:
$ juju run -a nova-cloud-controller -- relation-set -r98 placement_admin_url= \
    placement_internal_url= placement_public_url= placement_region= placement_service=

However, n-c-k are still in error with failed hook "cloud-compute-relation-changed".
Details are as below:
DNAe MODEL(openstack) jujumanage@infra-1:~$ os endpoint list | grep placement
| 27ef7b8ff64643369941e3db8e1a6e85 | uk | placement | placement | True | public | https://placement.uk.stack.dnae.com:8778 |
| a096600cd7be431486a131104eb1ea7d | uk | placement | placement | True | admin | https://placement-admin.uk.stack.dnae.com:8778 |
| d0e2876be2d64414b3bb884d9a55dda0 | uk | placement | placement | True | internal | https://placement-internal.uk.stack.dnae.com:8778 |

DNAe MODEL(openstack) jujumanage@infra-1:~$ juju run -u keystone/leader -- relation-get -r98 - nova-cloud-controller/1
egress-subnets: 172.27.83.115/32
ingress-address: 172.27.83.115
nova_admin_url: https://nova-admin.uk.stack.dnae.com:8774/v2.1
nova_internal_url: https://nova-internal.uk.stack.dnae.com:8774/v2.1
nova_public_url: https://nova.uk.stack.dnae.com:8774/v2.1
nova_region: uk
nova_service: nova
private-address: 172.27.83.115
subscribe_ep_change: neutron placement

unit-nova-compute-kvm-x.log: https://pastebin.canonical.com/p/kXDyWYqPCp/

From the log above, it's trying to connect to placement:8200 port. But the service should be at 8778 port.

[Alex Kavanagh (ajkavanagh)]

Thanks for the bug report. This bug is actually on the nova-cloud-controller charm and has been fixed in the master branch via https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1928992.

I'm marking this as a invalid, adding nova-cloud-controller and then marking as a duplicate.

@Xiyue Wang - there is a workaround for the bug if you are still having issues: https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1928992/comments/4