{"id":5917,"date":"2021-10-18T17:00:20","date_gmt":"2021-10-18T15:00:20","guid":{"rendered":"https:\/\/nil.uniza.sk\/?p=5917"},"modified":"2022-02-16T00:08:02","modified_gmt":"2022-02-15T23:08:02","slug":"how-to-install-microstack-on-virtualbox-ubuntu","status":"publish","type":"post","link":"https:\/\/nil.uniza.sk\/en\/how-to-install-microstack-on-virtualbox-ubuntu\/","title":{"rendered":"How to install Microstack on Virtualbox with Ubuntu guest OS"},"content":{"rendered":"<p>MicroStack is an OpenStack distribution for Ubuntu, which is suitable for the deployment of fully functional OpenStack on a single machine. Installation is quite straightforward.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"my-environment\"><strong>My environment<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>Host system: Win 10 Pro 64bit<\/li><li>VirtualBox 6.1.25r 64bit<\/li><li>Guest System: <ul><li>clear server install of Ubuntu 20.04.3 :LTS with bridged networking<\/li><li>4GB of RAM<\/li><li>4 vPCU<\/li><li>100GB of HDD (the size is officially recommended, but mainly is used for hosting virtual VMs)<\/li><\/ul><\/li><\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"single-node-installation-steps-using-snap\"><strong>Single node installation steps using snap<\/strong><\/h2>\n\n\n\n<p>Official guides use the snap system, where all applications are packaged with all their dependencies. All the microstack installation is relatively fast, taking no more than 15 minutes.<\/p>\n\n\n\n<p>Installation steps:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Update and upgrade system packages\n<strong>sudo apt update\nsudo apt upgrade<\/strong><\/pre>\n\n\n\n<p>Snap should be already installed and available for use on the majority of the latest Ubuntu distributions. If you have any issues regarding Snap, we recommend installing it by using the command below. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Install snapd \n<strong>sudo apt install snapd<\/strong><\/pre>\n\n\n\n<p>We recommend checking if open-vm-tools.service is disabled on your guest OS. In normal conditions, this tool should be enabled only on guest operating systems running under VMware. To check the status please enter the command below. You should see similar output. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Check open-vm-tools status \n<strong>sudo systemctl status open-vm-tools.service<\/strong>\n\n open-vm-tools.service\n     Loaded: masked (Reason: Unit open-vm-tools.service is masked.)\n     Active: inactive (dead)<\/pre>\n\n\n\n<p>If the status is active, you need to disable open-vm-tools.service by using the command below and reboot the system for changes to apply.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Disable open-vm-tools\n<strong>sudo systemctl disable open-vm-tools.service<\/strong>\n\n# Reboot system\n<strong>sudo reboot now<\/strong><\/pre>\n\n\n\n<p>Now we can finally proceed to the actual installation of the Microstack. Official documentation recommends using installation channel beta with dev mode for now. There are many channels and options to be used for installation. To list all of them with descriptions use the command below.  <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all channels and available options\n<strong>sudo snap install microstack --help<\/strong>\n\n# Install microstack\n<strong>sudo snap install microstack --devmode --beta<\/strong>\n\nEnsure prerequisites for \"microstack\" are available\nFetch and check assertions for snap \"microstack\" (233)\nMount snap \"microstack\" (233)\nCopy snap \"microstack\" data\nSetup snap \"microstack\" (233) security profiles\nConnect microstack:network-bind to core:network-bind\nSetup snap \"microstack\" (233) security profiles for auto-connections\nRun install hook of \"microstack\" snap if present\nStart snap \"microstack\" (233) services\nRun configure hook of \"microstack\" snap if present\nRun health check of \"microstack\" snap\nmicrostack (beta) ussuri from Canonical\u2713 installed\n\n# Verification \n<strong>sudo<\/strong> <strong>snap list microstack\n<\/strong>\nName       Version  Rev   Tracking     Publisher    Notes\nmicrostack ussuri   233   latest\/beta  canonical\u2713  devmode<\/pre>\n\n\n\n<p>After the installation, it is necessary to initialize the Microstack. There are a few options available when initializing. We used the one mentioned and recommended in the official documentation. To list all available options please see the command below. <\/p>\n\n\n\n<p><strong>Important!<\/strong> Make sure that your VM will have the same IP address as was assigned during the initialization process. Once the IP address changes (e.g. after reboot) you may encounter problems. We recommend setting up the IP address statically to avoid issues. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all options with descriptions\n<strong>sudo microstack init --help<\/strong>\n<strong>\n<\/strong># Setup the microstack\n<strong>sudo microstack init --auto --control<\/strong>\n\n2021-10-18 11:51:24,089 - microstack_init - INFO - Configuring clustering \u2026\n2021-10-18 11:51:24,231 - microstack_init - INFO - Setting up as a control node.\n2021-10-18 11:51:28,830 - microstack_init - INFO - Configuring networking \u2026\n2021-10-18 11:51:39,566 - microstack_init - INFO - Opening horizon dashboard up to *\n2021-10-18 11:51:41,301 - microstack_init - INFO - Waiting for RabbitMQ to start \u2026\nWaiting for 192.168.10.216:5672\n2021-10-18 11:51:50,177 - microstack_init - INFO - RabbitMQ started!\n2021-10-18 11:51:50,177 - microstack_init - INFO - Configuring RabbitMQ \u2026\n2021-10-18 11:51:51,752 - microstack_init - INFO - RabbitMQ Configured!\n2021-10-18 11:51:51,792 - microstack_init - INFO - Waiting for MySQL server to start \u2026\nWaiting for 192.168.10.216:3306\n2021-10-18 11:52:06,797 - microstack_init - INFO - Mysql server started! Creating databases \u2026\n2021-10-18 11:52:10,051 - microstack_init - INFO - Configuring Keystone Fernet Keys \u2026\n2021-10-18 11:52:42,964 - microstack_init - INFO - Bootstrapping Keystone \u2026\n2021-10-18 11:53:00,660 - microstack_init - INFO - Creating service project \u2026\n2021-10-18 11:53:10,592 - microstack_init - INFO - Keystone configured!\n2021-10-18 11:53:10,630 - microstack_init - INFO - Configuring the Placement service\u2026\n2021-10-18 11:53:46,582 - microstack_init - INFO - Running Placement DB migrations\u2026\n2021-10-18 11:53:53,485 - microstack_init - INFO - Configuring nova control plane services \u2026\n2021-10-18 11:54:14,139 - microstack_init - INFO - Running Nova API DB migrations (this may take a lot of time)\u2026\n2021-10-18 11:55:02,675 - microstack_init - INFO - Running Nova DB migrations (this may take a lot of time)\u2026\nWaiting for 192.168.10.216:8774\n2021-10-18 11:56:59,458 - microstack_init - INFO - Creating default flavors\u2026\n2021-10-18 11:57:44,607 - microstack_init - INFO - Configuring nova compute hypervisor \u2026\n2021-10-18 11:57:44,608 - microstack_init - INFO - Checking virtualization extensions presence on the host\n2021-10-18 11:57:44,651 - microstack_init - WARNING - Unable to determine hardware virtualization support by CPU vendor id \"GenuineIntel\": assuming it is not supported.\n2021-10-18 11:57:44,652 - microstack_init - WARNING - Hardware virtualization is not supported - software emulation will be used for Nova instances\n2021-10-18 11:57:49,067 - microstack_init - INFO - Configuring the Spice HTML5 console service\u2026\n2021-10-18 11:57:50,087 - microstack_init - INFO - Configuring Neutron\nWaiting for 192.168.10.216:9696\n2021-10-18 12:00:29,445 - microstack_init - INFO - Configuring Glance \u2026\nWaiting for 192.168.10.216:9292\n2021-10-18 12:01:42,117 - microstack_init - INFO - Adding cirros image \u2026\n2021-10-18 12:01:49,036 - microstack_init - INFO - Creating security group rules \u2026\n2021-10-18 12:02:08,167 - microstack_init - INFO - Configuring the Cinder services\u2026\n2021-10-18 12:03:49,646 - microstack_init - INFO - Running Cinder DB migrations\u2026\n2021-10-18 12:04:26,458 - microstack_init - INFO - restarting libvirt and virtlogd \u2026\n2021-10-18 12:05:09,660 - microstack_init - INFO - Complete. Marked microstack as initialized!<\/pre>\n\n\n\n<p>You can verify the initialization by using these commands.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all available images\n<strong>microstack.openstack image list<\/strong>\n\n+--------------------------------------+--------+--------+\n| ID                                   | Name   | Status |\n+--------------------------------------+--------+--------+\n| 2a61f2e6-ea86-4161-8ea1-17d0955c0717 | cirros | active |\n+--------------------------------------+--------+--------+\n\n# List default flavors\n<strong>microstack.openstack flavor list<\/strong>\n\n+----+-----------+-------+------+-----------+-------+-----------+\n| ID | Name      |   RAM | Disk | Ephemeral | VCPUs | Is Public |\n+----+-----------+-------+------+-----------+-------+-----------+\n| 1  | m1.tiny   |   512 |    1 |         0 |     1 | True      |\n| 2  | m1.small  |  2048 |   20 |         0 |     1 | True      |\n| 3  | m1.medium |  4096 |   20 |         0 |     2 | True      |\n| 4  | m1.large  |  8192 |   20 |         0 |     4 | True      |\n| 5  | m1.xlarge | 16384 |   20 |         0 |     8 | True      |\n+----+-----------+-------+------+-----------+-------+-----------+<\/pre>\n\n\n\n<p id=\"block-11ad25cb-7f41-4c5a-ae44-c9f31a895605\">If you got similar outputs as mentioned above, we can move on and create a VM instance. By default the only OS available for use is cirros. If not specified, a tiny flavor will be used when creating an instance. The command below will launch a VM with the name test, cirros OS, one CPU core, 1 GB HDD and 512 MB RAM (see m1.tiny flavor).  <\/p>\n\n\n\n<pre id=\"block-99e9cf5e-259f-4477-85c1-faa4bab4c3cc\" class=\"wp-block-preformatted\"># List all launch options with descriptions\n<strong>microstack launch --help<\/strong>\n<strong>\n<\/strong># Launch a VM\n<strong>microstack launch cirros --name test<\/strong>\n<strong>\n<\/strong>Creating local \"microstack\" ssh key at \/home\/root\/snap\/microstack\/common\/.ssh\/id_microstack\nLaunching server \u2026\nAllocating floating ip \u2026\nServer test launched! (status is BUILD)\n\nAccess it with <code>ssh -i \/home\/root\/snap\/microstack\/common\/.ssh\/id_microstack cirros@<\/code>192.168.10.216\nYou can also visit the OpenStack dashboard at http:\/\/192.168.10.216:80<\/pre>\n\n\n\n<p>Finally, we should be able to verify if the Microstack installation is running performing some CLI query<\/p>\n\n\n\n<pre id=\"block-bc5bd64b-e143-40b0-8cfe-45e8568cebf5\" class=\"wp-block-preformatted\"><strong>sudo microstack.openstack keypair list<\/strong>\n+------------+-------------------------------------------------+\n| Name | Fingerprint |\n+------------+-------------------------------------------------+\n| microstack | ba:19:fc:70:92:92:56:92:6e:d5:72:2e:42:7e:4b:1b |\n+------------+-------------------------------------------------+<\/pre>\n\n\n\n<p>There are two ways on how to access the created VM. The first way is with the use of SSH, second is with the use of the WEB dashboard. All information needed to access the VM using SSH are provided when you create the instance. In our case, the command is shown below. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Access VM using SSH\n<strong>ssh -i \/home\/user\/snap\/microstack\/common\/.ssh\/id_microstack cirros@192.168.10.216<\/strong><\/pre>\n\n\n\n<p>To list every created instance and its corresponding status execute the following command. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List all instances\n<strong>microstack.openstack server list<\/strong>\n\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+\n| ID                                   | Name     | Status | Networks                          | Image  | Flavor  |\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+\n| 79bd75d0-24be-4ebb-99d1-6a9d2da613c7 | firstTry | ACTIVE | test=192.168.222.195, 10.20.20.34 | cirros | m1.tiny |\n+--------------------------------------+----------+--------+-----------------------------------+--------+---------+<\/pre>\n\n\n\n<p>If you need more information on OpenStack commands try the command below. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># List OpenStack commands and help<strong>\nmicrostack.openstack --help<\/strong><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"web-access\"><strong>WEB access<\/strong><\/h2>\n\n\n\n<p>The Microstack installation supports also the web login using the HTTP URI in the form http:\/\/VM_IP_address<\/p>\n\n\n\n<p>Then we need to specify a username and a password. The username is \u2018<strong>admin<\/strong>\u2019 and the password must be obtained in this way:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>sudo snap get microstack config.credentials.keystone-password<\/strong><\/pre>\n\n\n\n<p>What will return a password, for example:<\/p>\n\n\n\n<pre id=\"block-c52b34ba-6f47-4863-addd-2e488d897d8c\" class=\"wp-block-preformatted\"><strong>1jv2r3RH0NwenKRtUttXyBqMHbwFUX9J<\/strong><\/pre>\n\n\n\n<p>then open a browser and access the microstack using the HTTPS URI, in my case http:\/\/192.168.10.216 where the login page is displayed. Using mentioned credentials we are admitted enter to the dashboard.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img alt=\"\" decoding=\"async\" width=\"605\" height=\"504\" src=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image.png\" class=\"wp-image-5919\" srcset=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image.png 605w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image-300x250.png 300w\" sizes=\"(max-width: 605px) 100vw, 605px\" \/><\/figure>\n\n\n\n<p>Well. it works!<\/p>\n\n\n\n<p>The space consumed by the installation is about 8GB:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">root@psserver:~# df -h\nroot@psserver:~# df -h\nFilesystem                         Size  Used Avail Use% Mounted on\nudev                               1.9G     0  1.9G   0% \/dev\ntmpfs                              394M  1.5M  393M   1% \/run\n\/dev\/mapper\/ubuntu--vg-ubuntu--lv   49G  7.1G   39G  16% \/\ntmpfs                              2.0G     0  2.0G   0% \/dev\/shm\ntmpfs                              5.0M     0  5.0M   0% \/run\/lock\ntmpfs                              2.0G     0  2.0G   0% \/sys\/fs\/cgroup\n\/dev\/loop4                          33M   33M     0 100% \/snap\/snapd\/12704\n\/dev\/loop1                          56M   56M     0 100% \/snap\/core18\/2128\n\/dev\/loop2                          71M   71M     0 100% \/snap\/lxd\/21029\n\/dev\/loop0                          62M   62M     0 100% \/snap\/core20\/1169\n\/dev\/sda2                          976M  107M  803M  12% \/boot\n\/dev\/loop5                          33M   33M     0 100% \/snap\/snapd\/13270\n\/dev\/loop6                          68M   68M     0 100% \/snap\/lxd\/21545\ntmpfs                              394M     0  394M   0% \/run\/user\/1000\n\/dev\/loop3                         387M  387M     0 100% \/snap\/microstack\/233\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"problems\"><strong>Problems<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"1\"><strong>1::<\/strong><\/h3>\n\n\n\n<p id=\"block-5270adba-3f9e-4919-8240-c66548288c3d\">The command used in several guides :<\/p>\n\n\n\n<pre id=\"block-5270adba-3f9e-4919-8240-c66548288c3d\" class=\"wp-block-preformatted\"><strong>sudo snap install microstack --beta<\/strong><\/pre>\n\n\n\n<p>does not work and after a few steps ends with an error. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">2021-10-18 11:36:51,655 - microstack_init - INFO - Configuring clustering ...\n2021-10-18 11:36:51,797 - microstack_init - INFO - Setting up as a control node.\n2021-10-18 11:36:56,667 - microstack_init - INFO - Configuring networking ...\nTraceback (most recent call last):\n  File \"\/snap\/microstack\/233\/bin\/microstack\", line 11, in &lt;module&gt;\n    load_entry_point('microstack==0.0.1', 'console_scripts', 'microstack')()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/microstack\/main.py\", line 44, in main\n    cmd()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 60, in wrapper\n    return func(*args, **kwargs)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 227, in init\n    question.ask()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/question.py\", line 210, in ask\n    self.yes(awr)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/__init__.py\", line 189, in yes\n    enable('ovs-vswitchd')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 162, in enable\n    check('snapctl', 'start', 'microstack.{}'.format(service), '--enable')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 69, in check\n    raise subprocess.CalledProcessError(proc.returncode, \" \".join(args))\ns<span style=\"background-color:#fcb900\" class=\"background-color\">ubprocess.CalledProcessError: Command 'snapctl start microstack.ovs-vswitchd --enable' returned non-zero exit status 1.<\/span>\n<\/pre>\n\n\n\n<p><strong>Solution<\/strong>: Remove the snap installation using <\/p>\n\n\n\n<pre id=\"block-5270adba-3f9e-4919-8240-c66548288c3d\" class=\"wp-block-preformatted\"><strong>snap remove microstack<\/strong><\/pre>\n\n\n\n<p>and try the install process mentioned above again.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"2-the-ip-address-of-guest-system-has-hanged\"><strong>2:: The IP address of guest system has hanged<\/strong><\/h3>\n\n\n\n<p>One cause of problems is that the DHCP has a very short lease time where after the reboot or a time as it was shut down VM will obtain a different IP address. For example, after reboot, I have obtained 192.168.10.208, but Microstack was installed when I had 192.168.10.230. Then you may receive an error message:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">palo@psserver:~$ sudo microstack.openstack keypair list\n\nFailed to discover available identity versions when contacting http:\/\/192.168.10.230:5000. Attempting to parse version from URL.\nCould not find versioned identity endpoints when attempting to authenticate. Please check that your auth_url is correct. Unable to establish connection to http:\/\/<span style=\"background-color:#fcb900\" class=\"background-color\">192.168.10.230<\/span>:5000: HTTPConnectionPool(host='192.168.10.230', port=5000): Max retries exceeded with url: \/ (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 113] No route to host'))<\/pre>\n\n\n\n<p>The web GUI shows login page, but the login does not work and the web server returns 504 Error message<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized is-style-default\"><img alt=\"\" decoding=\"async\" src=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image-7.png\" class=\"wp-image-5967\" width=\"436\" height=\"125\" srcset=\"https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image-7.png 584w, https:\/\/nil.uniza.sk\/wp-content\/uploads\/2021\/10\/image-7-300x86.png 300w\" sizes=\"(max-width: 436px) 100vw, 436px\" \/><\/figure>\n\n\n\n<p><strong>Solution<\/strong>: <\/p>\n\n\n\n<ol class=\"wp-block-list\"><li>Remove the snap installation and try the install process mentioned above again.<\/li><li>Set the IP address statically<\/li><\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"3-open-vm-tools-is-not-disabled\"><strong>3:: open-vm-tools is not disabled<\/strong><\/h3>\n\n\n\n<p>You should disable open-vm-tools.service if you are trying to install Microstack. <\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Start snap \"microstack\" (233) services                                         |\nerror: cannot perform the following tasks:\n<span style=\"background-color:#fcb900\" class=\"background-color\">- Start snap \"microstack\" (233) services (systemctl command [start snap.microstack.load-modules.service] failed with exit status 1: Job for snap.microstack.load-modules.service failed because the control process exited with error code.<\/span>\nSee \"systemctl status snap.microstack.load-modules.service\" and \"journalctl -xe\" for details.\n)<\/pre>\n\n\n\n<p>Debugging:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>systemctl status snap.microstack.load-modules.service<\/strong>\n\nsnap.microstack.load-modules.service\n     Loaded: not-found (Reason: Unit snap.microstack.load-modules.service not found.)\n     Active: failed (Result: exit-code) since Thu 2021-10-21 09:10:41 UTC; 3min 4s ago\n   Main PID: 4408 (code=exited, status=1\/FAILURE)\n\nOct 21 09:10:40 ubuntu systemd[1]: Starting Service for snap application microstack.load-modules...\nOct 21 09:10:40 ubuntu microstack.load-modules[4484]: ++ systemd-detect-virt --container\nOct 21 09:10:40 ubuntu microstack.load-modules[4408]: + [[ none == \\n\\o\\n\\e ]]\nOct 21 09:10:40 ubuntu microstack.load-modules[4408]: + modprobe -a vhost vhost-net vhost-scsi vhost-vsock vfio nbd dm-mod dm-thin-pool dm-snapshot iscsi-tcp target-core-mod\n<span style=\"background-color:#fcb900\" class=\"background-color\">Oct 21 09:10:41 ubuntu microstack.load-modules[4486]: modprobe: ERROR: could not insert 'vhost_vsock': Device or resource busy<\/span>\nOct 21 09:10:41 ubuntu systemd[1]: snap.microstack.load-modules.service: Main process exited, code=exited, status=1\/FAILURE\nOct 21 09:10:41 ubuntu systemd[1]: snap.microstack.load-modules.service: Failed with result 'exit-code'.\nOct 21 09:10:41 ubuntu systemd[1]: Failed to start Service for snap application microstack.load-modules.<\/pre>\n\n\n\n<p> <strong>Solution: <\/strong>Remove the snap installation using<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Remove microstack installation\n<strong>sudo snap remove microstack<\/strong><\/pre>\n\n\n\n<p>and install Microstack using the guide above.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"4-nginx\"><strong>4:: NGINX<\/strong><\/h3>\n\n\n\n<p>If your host OS is running NGINX you may encounter an error during initialization.<\/p>\n\n\n\n<p>Error message:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">2021-10-25 20:00:20,658 - microstack_init - INFO - Mysql server started! Creating databases ...\nTraceback (most recent call last):\n  File \"\/snap\/microstack\/233\/bin\/microstack\", line 11, in &lt;module&gt;\n    load_entry_point('microstack==0.0.1', 'console_scripts', 'microstack')()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/microstack\/main.py\", line 44, in main\n    cmd()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 60, in wrapper\n    return func(*args, **kwargs)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/main.py\", line 227, in init\n    question.ask()\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/question.py\", line 210, in ask\n    self.yes(awr)\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/questions\/__init__.py\", line 388, in yes\n    enable('nginx')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 162, in enable\n    check('snapctl', 'start', 'microstack.{}'.format(service), '--enable')\n  File \"\/snap\/microstack\/233\/lib\/python3.8\/site-packages\/init\/shell.py\", line 69, in check\n    raise subprocess.CalledProcessError(proc.returncode, \" \".join(args))\nsubprocess.CalledProcessError: <span style=\"background-color:#fcb900\" class=\"background-color\">Command 'snapctl start microstack.nginx --enable' returned non-zero exit status 1.<\/span><\/pre>\n\n\n\n<p><strong>Solution:<\/strong><\/p>\n\n\n\n<p>Uninstall Nginx with<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>sudo apt-get remove nginx<\/strong>\n<strong>sudo apt-get autoremove<\/strong><\/pre>\n\n\n\n<p>and retry the initialization process.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"some-links\"><strong>Some links<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><a href=\"https:\/\/microstack.run\/\">https:\/\/microstack.run\/<\/a><\/li><li><a href=\"https:\/\/ubuntu.com\/openstack\/install\">https:\/\/ubuntu.com\/openstack\/install<\/a><\/li><\/ul>\n\n\n\n<p><\/p>","protected":false},"excerpt":{"rendered":"<p>MicroStack is an OpenStack distribution for Ubuntu, which is suitable for the deployment of fully functional OpenStack on a single machine. Installation is quite straightforward. My environment Host system: Win 10 Pro 64bit VirtualBox 6.1.25r 64bit Guest System: clear server install of Ubuntu 20.04.3 :LTS with bridged networking 4GB of RAM 4 vPCU 100GB of&#8230;<\/p>","protected":false},"author":9,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_robots_primary_cat":"","_seopress_titles_title":"","_seopress_titles_desc":"","_seopress_robots_index":"","_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"footnotes":""},"categories":[637,1479],"tags":[],"class_list":["post-5917","post","type-post","status-publish","format-standard","hentry","category-cloud-en","category-cloud-microstack"],"taxonomy_info":{"category":[{"value":637,"label":"Cloud"},{"value":1479,"label":"MicroStack"}]},"featured_image_src_large":false,"author_info":{"display_name":"palo73","author_link":"https:\/\/nil.uniza.sk\/en\/author\/palo73\/"},"comment_info":7,"category_info":[{"term_id":637,"name":"Cloud","slug":"cloud-en","term_group":0,"term_taxonomy_id":635,"taxonomy":"category","description":"","parent":0,"count":2,"filter":"raw","cat_ID":637,"category_count":2,"category_description":"","cat_name":"Cloud","category_nicename":"cloud-en","category_parent":0},{"term_id":1479,"name":"MicroStack","slug":"cloud-microstack","term_group":0,"term_taxonomy_id":1477,"taxonomy":"category","description":"","parent":637,"count":2,"filter":"raw","cat_ID":1479,"category_count":2,"category_description":"","cat_name":"MicroStack","category_nicename":"cloud-microstack","category_parent":637}],"tag_info":false,"_links":{"self":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/5917","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/comments?post=5917"}],"version-history":[{"count":0,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/posts\/5917\/revisions"}],"wp:attachment":[{"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/media?parent=5917"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/categories?post=5917"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nil.uniza.sk\/en\/wp-json\/wp\/v2\/tags?post=5917"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}