
Cinder volume attached to a terminated server ... - ask.openstack.org
I was debugging a Heat stack that (among other things) attached an existing Cinder Volume to a new instance created by the stack. The instance died, but the attachment still exists. Now I …
Why are two NICs required for OpenStack single node installation ...
As far as I understand, management network is used for establishing connectivity between OpenStack nodes in case of multi-node installation. What is a management network used for …
Openstack Flat Provider network with openvswitch
The docs mention that 2 networks are required, management and provider network. I understood the concept of management network, and my management network is a local 10.0.0.0/8 …
Can't ping floating or instance ip - Ask OpenStack: Q&A Site for ...
May 24, 2021 · The routes to my floating ip address on the system hosting the openstack installation were missing the routes to the public ip address. Since my floating ip's are not a …
ask.openstack.org
openstack-discuss mailing list. stackoverflow.com for code questions. serverfault.com for operations. The Internet Archive has archived the site.
openstack service create (HTTP 504) - Ask OpenStack: Q&A Site …
openstack service create --name keystone --description "OpenStack Identity" identity I get the following error: ERROR: openstack Gateway Timeout (HTTP 504) I am not sure whats wrong …
apt-get install memcached - Ask OpenStack: Q&A Site for …
we have issue to install memcached but successfully on apt-get install swift openssh-server rsync python-netifaces python-xattr python-memcache swift-proxy
unable to create vm instance - Ask OpenStack: Q&A Site for …
Hi, i have one controller node and compute node in my openstack setup. whenever i am trying to launch instance getting below error in horizan.
cannot create cinder volume with image - Ask OpenStack: Q&A …
The logs of /var/log/cinder/volume.log of cinder storage node is given below:
Cannot associate floating-ip - Ask OpenStack: Q&A Site for …
Bad floatingip request: Port fff4169b-191e-4b4c-9e6d-114a557986b1 is associated with a different tenant than Floating IP 1efdde72-7438-45d0-b495-2ee3352a7f58 and therefore …