juju - OpenStack Charms Deployment Guide - "ERROR... failed to bootstrap model" | pressku.com

Trending 3 months ago

Any assistance would beryllium overmuch appreciated; I searched done galore posts and person recovered nary answers yet.

I person been pursuing this guide: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/2023.2/index.html

I person tried aggregate methods utilizing beingness and virtual deployments pinch aforesaid correction erstwhile moving nan pursuing bid nether nan "Install Juju" section: juju bootstrap --bootstrap-series=jammy --constraints tags=juju maas-one maas-controller

23:57:50 DEBUG juju.provider.maas environ.go:685 attempting to get node successful area "default" 23:57:50 ERROR juju.cmd.juju.commands bootstrap.go:969 grounded to bootstrap model: cannot commencement bootstrap lawsuit successful readiness area "default": grounded to get node: No disposable instrumentality matches constraints: [('agent_name', ['ba18b361-58d8-41e8-8f6c-a72faa0493a9']), ('mem', ['3584']), ('tags', ['juju']), ('zone', ['default'])] (resolved to "mem=3584.0 tags=juju zone=default") 23:57:50 DEBUG juju.cmd.juju.commands bootstrap.go:970 (error details: [{github.com/juju/juju/cmd/juju/commands.(*bootstrapCommand).Run:1068: grounded to bootstrap model} {github.com/juju/juju/environs/bootstrap.Bootstrap:748: } {github.com/juju/juju/environs/bootstrap.bootstrapIAAS:600: } {github.com/juju/juju/provider/common.BootstrapInstance:309: cannot commencement bootstrap lawsuit successful readiness area "default"} {github.com/juju/juju/provider/maas.(*maasEnviron).StartInstance:716: } {github.com/juju/juju/provider/maas.(*maasEnviron).StartInstance:711: grounded to get node} {No disposable instrumentality matches constraints: [('agent_name', ['ba18b361-58d8-41e8-8f6c-a72faa0493a9']), ('mem', ['3584']), ('tags', ['juju']), ('zone', ['default'])] (resolved to "mem=3584.0 tags=juju zone=default")}])

I person verified nan following:

  • memory of juju controller exceeds constraint and has 4096M of memory
  • all nodes are successful "default" zone
  • juju controller deployed via MAAS and moving 22.04 LTS
  • juju controller has tag "juju" configured
  • both MAAS and juju systems are capable to pass to each other

I person attached output of nan supra bid beneath pinch --debug set

More
close