How to Install OpenStack on CentOS 8 with Packstack

Openstack is a free and open-source private cloud software through which we can manage compute, network and storage resources of our data center with an ease using a single dashboard and via openstack cli commands. In this article we will demonstrate on how to install Openstack on a CentOS 8 system with packstack. Packstack is a command line utility which deploy different components of openstack using puppet modules.

Openstack deployment with packstack is generally used for POC (proof of concept) purpose, so it is not recommended to use packstack for production deployment. Use TripleO method to deploy openstack in production environment.

Minimum System requirements for OpenStack

  • Minimal CentOS 8
  • Dual core Processor
  • 8 GB RAM
  • 40 GB free disk space
  • Stable Internet Connection
  • At least one nic card

My Lab setup details:

  • Hostname – openstack.example.com
  • IP – 192.168.1.8
  • Flat Network – 192.168.1.0/24

Let’s deep dive into the openstack installation steps,

Step 1) Set the hostname and update /etc/hosts file

Open the terminal and set the hostname using the following hostnamectl command,

[[email protected] ~]# hostnamectl set-hostname "openstack.example.com"
[[email protected] ~]# exec bash

Run below echo command to append hostname entry in /etc/hosts file.

[[email protected] ~]# echo -e "192.168.1.8\topenstack.example.com" >> /etc/hosts

Step 2) Disable Network Manager and Configure Network using network-scripts

Network-Manager is the default tool in CentOS 8 to manager networks but for Openstack we must disable it because openstack networking will not work properly with network-manager. In place of network manager, we must install native network-scripts.

To disable network-manager run the following commands,

[[email protected] ~]# systemctl disable NetworkManager
[[email protected] ~]# systemctl stop NetworkManager

Run following dnf command to install native network-scripts

[[email protected] ~]# dnf install network-scripts -y

Once the network-scripts package is installed then we can manage networking (ifcfg-* files) using native network.service

Now let’s configure IP address in ifcfg-enp0s3 file and start network service

[email protected] ~]# vi /etc/sysconfig/network-scripts/ifcfg-enp0s3

network-file-ifcfg-enp0s3-centos8

Save and exit the file and then start network service using following command,

[[email protected] ~]# systemctl start network
[[email protected] ~]# systemctl enable network

Now verify whether IP is assigned to NIC (enp0s3) using ip command,

[[email protected] ~]# ip a s enp0s3

ifcfg-enp0s3-ip-command-linux

Step 3) Enable OpenStack repositories and install packstack utility

At time of writing this article, ussuri openstack was available, so run the following command to configure its repositories

[[email protected] ~]# dnf config-manager --enable PowerTools
[[email protected] ~]# dnf install -y centos-release-openstack-ussuri

Now installed all the available updates and reboot your system,

[[email protected] ~]# dnf update -y
[[email protected] ~]# reboot

Once the system is available after the reboot, execute following dnf command to install packstack utility

[[email protected] ~]# dnf install -y openstack-packstack

Step 4) Generate answer file and install openstack using packstack

Use packstack command to generate the answer file,

[[email protected] ~]# packstack --gen-answer-file /root/openstack-answer.txt

Once the answer file is generated, edit the following parameters using vi editor,

[[email protected] ~]# vi /root/openstack-answer.txt
..............
CONFIG_HEAT_INSTALL=y
CONFIG_PROVISION_DEMO=n
[email protected]
CONFIG_NEUTRON_OVN_BRIDGE_IFACES=br-ex:enp0s3
..............

Save and exit the file.

Replace the interface name (enp0s3) as per your setup.

Note: Default Tenant network type drive is set as “geneve” and default neutron type driver is set as “geneve and flat”. If wish to change these default parameters, then update following lines in answer file. In this demonstration i am not going to update these parameters.

CONFIG_NEUTRON_ML2_TYPE_DRIVERS=geneve,flat
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=geneve

Run the following command to initiate the openstack deployment using answer file.

[[email protected] ~]# packstack --answer-file /root/openstack-answer.txt

Deployment will take around 20 to 30 minutes depending on your system’s hardware and internet speed. Once it is installed successfully, we will get the following:

Openstack-Successfull-Installation-Screen

Now verify whether IP from enp03 interface is assigned to bridge br-ex and also confirm whether interface enp0s3 is added as a port in ovs-bridge.

Run the following commands:

[[email protected] ~]# ip a s enp0s3
[[email protected] ~]# ip a s br-ex
[[email protected] ~]# ovs-vsctl show

ovs-vsctl-command-centos8

Perfect, above output confirms that installation was successful, and networking is also configured as per the answer file.

Step 5) Access Horizon Dashboard

Now try to login to Horizon dashboard. URL is already specified in the above output, in my case url is http://192.168.1.8/dashboard , Use the user name as admin and password that we specify in answer file.

We also refer the file “keystonerc_admin” for credentials

OpenStack-Horizon-Dashboard-CentOS8

Instance-Overview-OpenStack-Dashboard

Now, let’s test this openstack deployment by launching an instance.

Step 6) Test and verify OpenStack installation by launching an instance

Before launching an instance in openstack, first we must create networks and router and glance image. So, let’s first create external network in admin tenant using following neutron commands,

[[email protected] ~]# source keystonerc_admin
[[email protected] ~(keystone_admin)]# neutron net-create external_network --provider:network_type flat --provider:physical_network extnet --router:external

Now add a subnet of your flat network to external network by running following neutron command.

[[email protected] ~(keystone_admin)]# neutron subnet-create --name public_subnet --enable_dhcp=True --allocation-pool=start=192.168.1.210,end=192.168.1.230 --gateway=192.168.1.1 external_network 192.168.1.0/24

Create a router by executing the following neutron command and set its gateway using external network

[[email protected] ~(keystone_admin)]# neutron router-create dev-router
[[email protected] ~(keystone_admin)]# neutron router-gateway-set dev-router external_network

Create private network and attach a subnet to it. Run the following neutron command,

[[email protected] ~(keystone_admin)]# neutron net-create pvt_net
[[email protected] ~(keystone_admin)]# neutron subnet-create --name pvt_subnet pvt_net 10.20.1.0/24

Add pvt_net interface to router “dev_router” using beneath neutron command,

[[email protected] ~(keystone_admin)]# neutron router-interface-add dev-router  pvt_subnet

Now Download Cirros image and then upload it to glance

[[email protected] ~(keystone_admin)]# wget http://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img
[[email protected] ~(keystone_admin)]# openstack image create --disk-format qcow2 --container-format bare --public --file cirros-0.5.1-x86_64-disk.img  cirros

Now head back to horizon dashboard and verify the network topology

Network-Topology-OpenStack-Dashboard

Perfect, above confirms that private and external network have been setup correctly along with the router.

One final step before creating a vm, update the default security group, add icmp and ssh ingress rules, click on “Security Groups” under the network Tab, Click on Manage Rules and then click on “Add rule

Manage-Security-Group-Rules-ICMP-OpenStack

Similarly add rule for ssh

Manage-Security-Group Rules-ssh-OpenStack

Click on Add

Now all the requirements for launching an openstack instance are fullfilled. Click on Compute Tab and then Choose Instances option and click on “Launch Instance

VM-Creation-OpenStack

Once VM is launched successfully then we will get something like below,

Instances-Status-OpenStack-Dashboard

Now Associate floating IP to instance (demo_vm), Under the “Actions” Tab, Choose “Associate Floating IP

Associate-Floating-IP-Option-Openstack

Now Choose IP or Click on + sign to get floating IP from external network and then associate it

Choose-IP-Associate-Port-OpenStack

Once IP is associated to the VM then floating IP will be displayed for under ‘IP Address‘ option, example is shown below

Floating-IP-Address-Openstack-VM

Now try to access this demo_vm using the floating ip, use cirros as a user and ‘gocubsgo’ as password

Access-VM-using-floating-ip-openstack

Great, above output confirms that we can access our instance via floating ip. This concludes the article; I hope this tutorial helps to deploy openstack on CentOS 8 system. Please don’t hesitate to share your feedback and comments.

Also Read: How to Create an Instance in OpenStack via Command Line

22 Responses

  1. marian says:

    when issuing command “dnf config-manager –enable PowerTools” it throws an error “No such command: config-manager. Please use /usr/bin/dnf –help

    [[email protected] ~]# dnf config-manager –enable PowerTools
    No such command: config-manager. Please use /usr/bin/dnf –help
    It could be a DNF plugin command, try: “dnf install ‘dnf-command(config-manager)'”
    [[email protected] ~]#

    • Pradeep Kumar says:

      Hi Marian,

      Run the following dnf command to fix the above said issue:

      $ sudo dnf install ‘dnf-command(config-manager)’

  2. Manusia says:

    Hi Sir,
    I get an issue below :

    ERROR : Failed to run remote script, stdout: skipping creation of hiera.yaml symlink

    stderr: Warning: Permanently added ‘10.10.69.100’ (ECDSA) to the list of known hosts.
    + trap t ERR
    + [[ -f /etc/hiera.yaml ]]
    + echo ‘skipping creation of hiera.yaml symlink’
    ++ puppet config print hiera_config
    + sed -i ‘s;:datadir:.*;:datadir: /var/tmp/packstack/d7eabbcf57df47b6b283fc89caeb47be/hieradata;g’ /etc/puppet/hiera.yaml
    sed: can’t read /etc/puppet/hiera.yaml: No such file or directory
    ++ t
    ++ exit 2

    How to solve it?

  3. yoichi says:

    Hi Sir,
    I was able to access this demo_vm using cirros as user with floating IP.
    But from demo_vm, the following fails.
    $ ping 8.8.8.8
    How to solve it?

  4. Pradeep Kumar says:

    Add the DNS Sever IP while creating the external network subnet.

  5. yoichi says:

    Thank you
    I added a DNS server to the external network subnet, but it doesn’t work.
    Other conditions are as follows.
    Ping from demo_vm
    to: FloatingIP -> Success
    to: GestOS IP -> Success
    (Use VirtualBox and bridge connection)
    to: Host Default GW IP -> Failure
    How to solve it?

  6. claus_tuxi says:

    @Manusia:
    I had the same error and now i found the issue
    There is a problem with epel and the hiera package (hiera-3.6.0-2.el8)
    The centos-openstack-ussuri repo provides hiera-3.6.0-1.el8

    A look at the filelist in rpm shows that hiera-3.6.0-2.el8 didn’t include:
    /etc/puppet
    /etc/puppet/hiera.yaml

    So remove hiera, disable epel and reinstall openstack-packstack:
    dnf remove hiera -y
    dnf config-manager –disable epel
    dnf install -y openstack-packstack

  7. Bhartendu says:

    First of all, this is a great reference document for Openstack installation on CentOS. I followed every step in the document and was successful. However, ran into some issue during last few steps.

    Can you please help me with some trigger or suggestion to solve this issue? Thanks a lot in advance.

    Copying Puppet modules and manifests [ DONE ]
    Applying 192.168.0.3_controller.pp
    192.168.0.3_controller.pp: [ ERROR ]
    Applying Puppet manifests [ ERROR ]

    ERROR : Error appeared during Puppet run: 192.168.0.3_controller.pp
    Error: Facter: error while resolving custom fact “rabbitmq_nodename”: undefined method `[]’ for nil:NilClass
    You will find full trace in log /var/tmp/packstack/20200723-225316-7yvkznxa/manifests/192.168.0.3_controller.pp.log
    Please check log file /var/tmp/packstack/20200723-225316-7yvkznxa/openstack-setup.log for more information
    Additional information:
    * Parameter CONFIG_NEUTRON_L2_AGENT: You have chosen OVN Neutron backend. Note that this backend does not support the VPNaaS or FWaaS services. Geneve will be used as the encapsulation method for tenant networks
    * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
    * File /root/keystonerc_admin has been created on OpenStack client host 192.168.0.3. To use the command line tools you need to source the file.
    * To access the OpenStack Dashboard browse to http://192.168.0.3/dashboard .
    Please, find your login credentials stored in the keystonerc_admin in your home directory.
    [[email protected] ~]$

    • Pradeep Kumar says:

      Hi,

      Please check controller.pp.log and openstack-setup.log, You might get the clue there. I would suggest give a try one more time.

  8. Bhartendu says:

    Hi All.

    Thanks a lot for helping me for previous query. Earlier problem fixed, now I am able to create VM instance successfully, but I can’t connect from Virtual box machine (CentOS machine) and outside network.

    Furthermore, there are no route 172.24.1.0/24 on my Virtual box machine (CentOS machine).

    Is Virtual box IP address and External Network should be on same subnet? I tried that and that still not worked.

    It seems Neutron not properly configured.

    Please suggest me how to fix this (Using same commands provided in the document).

    Virtual box IP address: 192.168.0.104 (Subnet = 192.168.0.0/24)
    Private Network: 10.20.1.0/24
    External Network: 172.24.1.0/24

    ================
    CLI Commands:
    ================
    source keystonerc_admin
    neutron net-create external_network –provider:network_type flat –provider:physical_network extnet –router:external
    neutron subnet-create –name public_subnet –enable_dhcp=True –allocation-pool=start=172.24.1.210,end=172.24.1.230 –gateway=172.24.1.1 external_network 172.24.1.0/24
    neutron router-create dev-router
    neutron router-gateway-set dev-router external_network
    neutron net-create pvt_net
    neutron subnet-create –name pvt_subnet pvt_net 10.20.1.0/24
    neutron router-interface-add dev-router pvt_subnet

    [[email protected] ~(keystone_admin)]# ifconfig -a
    br-ex: flags=4163 mtu 1500
    inet 192.168.0.104 netmask 255.255.255.0 broadcast 192.168.0.255
    inet6 fe80::a00:27ff:fe8a:a9cd prefixlen 64 scopeid 0x20
    ether 08:00:27:8a:a9:cd txqueuelen 1000 (Ethernet)
    RX packets 33024 bytes 27440713 (26.1 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 29794 bytes 17763062 (16.9 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    br-int: flags=4098 mtu 1500
    ether 86:09:c0:60:00:4e txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    docker0: flags=4099 mtu 1500
    inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
    ether 02:42:49:2d:fa:d2 txqueuelen 0 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    enp0s3: flags=4163 mtu 1500
    inet6 fe80::a00:27ff:fe8a:a9cd prefixlen 64 scopeid 0x20
    ether 08:00:27:8a:a9:cd txqueuelen 1000 (Ethernet)
    RX packets 38913 bytes 28292425 (26.9 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 38573 bytes 21086877 (20.1 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73 mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10
    loop txqueuelen 1000 (Local Loopback)
    RX packets 2708229 bytes 2168061258 (2.0 GiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 2708229 bytes 2168061258 (2.0 GiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    ovs-system: flags=4098 mtu 1500
    ether 22:df:63:8b:31:35 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    [[email protected] ~(keystone_admin)]# ip route show
    default via 192.168.0.1 dev br-ex
    169.254.0.0/16 dev enp0s3 scope link metric 1002
    169.254.0.0/16 dev br-ex scope link metric 1004
    172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
    192.168.0.0/24 dev br-ex proto kernel scope link src 192.168.0.104
    [[email protected] ~(keystone_admin)]#

    Thanks & Regards

  9. Robert Brown says:

    I have a running instance of Openstack after following your instructions. I do have a problem, though: I created an instance and associated it with a floating IP address, but when I try to ping that address I get “Host unreachable” failures.

    What would cause this problem, and how do I fix it? Is it some openstack configuration problem?

  10. kart says:

    Thanks am able to install sucessfully but whenever i click on anything through GUI or ISSUE ANY OPENSTACK CLI COMMANDS am getting error “Unable to retreieve” in GUI and HTTP 500 error as below

    [[email protected] nova(keystone_admin)]# nova hypervisor-list
    ERROR (ClientException): Unknown Error (HTTP 500

    If i restart service restart httpd, it will go away , then comes back one i start issuing commands. Anyway to solve this ? Struck for 2 days on same issue, i reinstalled the OS two times already. same issue i am struck at.

  11. kart says:

    neutron net-create external_network –provider:network_type flat –provider:physical_network extnet –router:external
    neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.

    Am getting timedout error. Anyway to fix this common issue on my set up.

    VNClientQosExtension
    2020-08-19 01:05:13.332 52079 INFO neutron.db.ovn_revision_numbers_db [req-b54badc4-d7a9-4bb8-9c2a-b6ac2bc1228b – – – – -] Successfully bumped revision number for resource ce1326ba-a831-4111-866b-0f10c7e20063 (type: security_groups) to 1
    2020-08-19 01:05:13.333 52079 INFO neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.maintenance [req-b54badc4-d7a9-4bb8-9c2a-b6ac2bc1228b – – – – -] Maintenance task: Synchronization finished (took 0.06 seconds)
    2020-08-19 01:06:31.225 51836 ERROR neutron_lib.callbacks.manager [req-856ded2d-08ee-420b-9bef-5b42d6688fbf 953d2f61e4ae485190d3ded583c92b41 246c8ce7566d42918867484d84604013 – default default] Error during notification for neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver.OVNMechanismDriver._create_security_group-4177769 security_group, after_create: ovsdbapp.exceptions.TimeoutException: Commands [, , , , ] exceeded timeout 180 seconds

  12. Shafaq Zia says:

    Hi All,

    I am looking for some suggestion on how to solve an “ERROR: Failed handling answer file: Given host does not listen on port 22: fe80::190a:4da5:6e3d:fd1a.” This error popped out right after the command “packstack –gen-answer-file=/root/answers.txt.” I tried the following commands to add port 22 but did not resolve the issue.

    firewall -cmd –add-port=22/tcp
    firewall -cmd –add-port=22/tcp –permenant
    systemctl start ssh
    systemctl enable sshd

    [[email protected] ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s3
    192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
    [[email protected] ~]# ifconfig
    enp0s3: flags=4163 mtu 1500
    inet 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 2600:1700:3d00:7940:8f42:999a:4299:f5c2 prefixlen 64 scopeid 0x0
    inet6 2600:1700:3d00:7940::48 prefixlen 128 scopeid 0x0
    inet6 fe80::190a:4da5:6e3d:fd1a prefixlen 64 scopeid 0x20
    ether 08:00:27:ff:ae:9b txqueuelen 1000 (Ethernet)
    RX packets 27422 bytes 2490306 (2.3 MiB)
    RX errors 0 dropped 4647 overruns 0 frame 0
    TX packets 207 bytes 31619 (30.8 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73 mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10
    loop txqueuelen 1000 (Local Loopback)
    RX packets 58 bytes 4734 (4.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 58 bytes 4734 (4.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    virbr0: flags=4099 mtu 1500
    inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
    ether 52:54:00:c0:d3:75 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    I would really appreciate if someone can assist. I am not so savvy in Linux so still in learning phase.

  13. Shafaq Zia says:

    Hi All,

    I am looking for some suggestion on how to solve an “ERROR: Failed handling answer file: Given host does not listen on port 22: fe80::190a:4da5:6e3d:fd1a.” This error popped out right after the command “packstack –gen-answer-file=/root/answers.txt.” I tried the following commands to add port 22 but did not resolve the issue.

    firewall -cmd –add-port=22/tcp
    firewall -cmd –add-port=22/tcp –permenant
    systemctl start ssh
    systemctl enable sshd

    [[email protected] ~]# route -n
    Kernel IP routing table
    Destination Gateway Genmask Flags Metric Ref Use Iface
    192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp0s3
    192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
    [[email protected] ~]# ifconfig
    enp0s3: flags=4163 mtu 1500
    inet 192.168.1.0 netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 2600:1700:3d00:7940:8f42:999a:4299:f5c2 prefixlen 64 scopeid 0x0
    inet6 2600:1700:3d00:7940::48 prefixlen 128 scopeid 0x0
    inet6 fe80::190a:4da5:6e3d:fd1a prefixlen 64 scopeid 0x20
    ether 08:00:27:ff:ae:9b txqueuelen 1000 (Ethernet)
    RX packets 27422 bytes 2490306 (2.3 MiB)
    RX errors 0 dropped 4647 overruns 0 frame 0
    TX packets 207 bytes 31619 (30.8 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73 mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    inet6 ::1 prefixlen 128 scopeid 0x10
    loop txqueuelen 1000 (Local Loopback)
    RX packets 58 bytes 4734 (4.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 58 bytes 4734 (4.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    virbr0: flags=4099 mtu 1500
    inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
    ether 52:54:00:c0:d3:75 txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    I would really appreciate if someone can assist. I am not so savvy in Linux so still in learning phase.

  14. Hugo Gayosso says:

    Thanks for posting this article it provided me with ideas.
    I have created automation to set up OpenStack (Packstack) on free VMware ESXi using Terraform and Ansible.

    ‘https://github.com/TribalNightOwl/openstack-packstack-esxi’

  15. dz says:

    Hi….Im not able to ping from VM instance to external network (lan/home routergw//internet)…vm can only ping up to openstack router GW.
    From external network I can ping those VM. Running openstack over virtualbox. I have gone through so many solution and yet none resolve the issue. Appreciate if someone that face the same problem and have found the solution to share with me….have tried for more than 2 weeks without luck….thank you

  16. KV Suresha says:

    Hi Pradeep Kumar,
    it very helpful to us.

    everything is working fine but sometimes we got as below mentioned error in the dashboard.

    Error: Unable to retrieve usage information.

    can you please suggest could be the issue and please explain Network part deeply.

  17. Balkrishna Savalia says:

    Hi Pradeep Kumar,

    I have install openstack successfully but while launching instance i am getting error

    ————

    Message
    No valid host was found.
    Code
    500
    Details
    Traceback (most recent call last): File “/usr/lib/python3.6/site-packages/nova/conductor/manager.py”, line 1463, in schedule_and_build_instances instance_uuids, return_alternates=True) File “/usr/lib/python3.6/site-packages/nova/conductor/manager.py”, line 870, in _schedule_instances return_alternates=return_alternates) File “/usr/lib/python3.6/site-packages/nova/scheduler/client/query.py”, line 42, in select_destinations instance_uuids, return_objects, return_alternates) File “/usr/lib/python3.6/site-packages/nova/scheduler/rpcapi.py”, line 160, in select_destinations return cctxt.call(ctxt, ‘select_destinations’, **msg_args) File “/usr/lib/python3.6/site-packages/oslo_messaging/rpc/client.py”, line 181, in call transport_options=self.transport_options) File “/usr/lib/python3.6/site-packages/oslo_messaging/transport.py”, line 129, in _send transport_options=transport_options) File “/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py”, line 654, in send transport_options=transport_options) File “/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py”, line 644, in _send raise result nova.exception_Remote.NoValidHost_Remote: No valid host was found. Traceback (most recent call last): File “/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py”, line 241, in inner return func(*args, **kwargs) File “/usr/lib/python3.6/site-packages/nova/scheduler/manager.py”, line 200, in select_destinations raise exception.NoValidHost(reason=””) nova.exception.NoValidHost: No valid host was found.
    Created
    Sept. 14, 2020, 10:35 p.m.

    —-
    Please help to resolve the same
    Thanks,
    Balkrishna

  18. kelvin says:

    i have this problem

    [[email protected] ~(keystone_admin)]# nova list
    ERROR (ClientException): Unknown Error (HTTP 500)
    [[email protected] ~(keystone_admin)]# nova list
    +————————————–+———–+——–+————+————-+————————————-+
    | ID | Name | Status | Task State | Power State | Networks |
    +————————————–+———–+——–+————+————-+————————————-+
    | ddeb8bbd-52d3-4e01-bb03-07f667f99d67 | Ubuntu 20 | ACTIVE | – | Running | RED1=10.9.9.13; private=10.1.1.163 |
    +————————————–+———–+——–+————+————-+————————————-+
    [[email protected] ~(keystone_admin)]# nova list
    ERROR (ClientException): Unknown Error (HTTP 500)
    [[email protected] ~(keystone_admin)]# nova list
    ERROR (ClientException): Unknown Error (HTTP 500)
    [[email protected] ~(keystone_admin)]# nova list
    +————————————–+———–+——–+————+————-+————————————-+
    | ID | Name | Status | Task State | Power State | Networks |
    +————————————–+———–+——–+————+————-+————————————-+
    | ddeb8bbd-52d3-4e01-bb03-07f667f99d67 | Ubuntu 20 | ACTIVE | – | Running | RED1=10.9.9.13; private=10.1.1.163 |
    +————————————–+———–+——–+————+————-+————————————-+
    [[email protected] ~(keystone_admin)]#

Leave a Reply

Your email address will not be published. Required fields are marked *

Pin It on Pinterest