New Charmed Openstack deployment results to blocked services

Bug #2025048 reported by Panos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Expired
Undecided
Unassigned

Bug Description

I have a maas environment (version 3.3.4) and used this file https://pastebin.ubuntu.com/p/qPFSHJvk9H/ to deploy Openstack. After juju (version 2.9.43-ubuntu-amd64) completes deployment
nova-cloud-controller unit reports Services not running that should be: nova-scheduler and,
nova-compute hosts report Services not running that should be: nova-compute

```

Revision history for this message
Panos (leijona) wrote :
Revision history for this message
Harry Pidcock (hpidcock) wrote :

This doesn't look to be a bug with juju. Please reach out on https://discourse.charmhub.io/ so you can get the attention of the OpenStack charm developers.

Changed in juju:
status: New → Incomplete
Revision history for this message
Panos (leijona) wrote :

Hello Harry,
I have gone via the charmhub route before (https://discourse.charmhub.io/t/zed-openstack-new-deployment-with-blocked-cloud-controller-and-nova-compute/10954) and it was suggested to me to open a bug.

Revision history for this message
Peter Matulis (petermatulis) wrote (last edit ):

I changed the bug task to the nova-cloud-controller charm.

For guidance in submitting software bugs to the OpenStack Charms project please see:

https://docs.openstack.org/charm-guide/latest/community/software-bug.html

affects: juju → charm-nova-cloud-controller
Changed in charm-nova-cloud-controller:
status: Incomplete → New
Revision history for this message
Billy Olsen (billy-olsen) wrote :

We'll need the logs from the nova cloud controller unit in order to determine what's going on here. Can you please collect the various logs from under the /var/log/juju and /var/log/nova directories?

Changed in charm-nova-cloud-controller:
status: New → Incomplete
Revision history for this message
Panos (leijona) wrote :

Hello Billy,
I had a feeling this behaviour is related to the use of os-admin-hostname and os-internal-hostname in the deployment file. I destroyed and re-deployed only with commented out the above options and seems to NOT experience the same.

I can destroy again and uncomment the options and deploy again to verify but can this be related?

Revision history for this message
Panos (leijona) wrote :

Hello Billy, just commenting out the os-admin-hostname and os-internal-hostname the deployment does not report nova-scheduler and nova-compute charms as blocked.

Is this expected ?

Revision history for this message
Panos (leijona) wrote :

Hello,
Have you tried replicating the behaviour ?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Nova Cloud Controller Charm because there has been no activity for 60 days.]

Changed in charm-nova-cloud-controller:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.