Ask Your Question

toddleish's profile - activity

2020-09-02 14:25:08 -0500 received badge  Notable Question (source)
2020-09-02 13:33:31 -0500 received badge  Popular Question (source)
2020-08-10 09:56:59 -0500 commented question Have a huge file in the ROOT directory called "data". Any idea what this file could be for?

Okay, thanks Bernd. Do you think it's safe to delete?

2020-08-07 20:13:23 -0500 commented question Have a huge file in the ROOT directory called "data". Any idea what this file could be for?

Thank you for responding. losetup -a doesn't return anything, but the file command returns:

file data

data: QEMU QCOW Image (v3), 214748364800 bytes

2020-08-07 17:34:11 -0500 asked a question Have a huge file in the ROOT directory called "data". Any idea what this file could be for?

On my master node (horizon, etc) I have a huge file in the ROOT directory called "data". It is 40GB and has filled up the hard drive. I installed Rocky with RDO Packstack. Any idea what this file could be for?

2020-07-06 15:58:46 -0500 received badge  Famous Question (source)
2020-03-01 02:04:25 -0500 received badge  Notable Question (source)
2020-02-28 16:28:05 -0500 commented question instance snapshot fails to complete

I have not checked keystone, but will do that next. Good tip.

2020-02-28 15:37:43 -0500 commented question instance snapshot fails to complete

Okay... No, the NVMe drive has over 1TB remaining.

2020-02-28 15:17:49 -0500 received badge  Popular Question (source)
2020-02-28 13:32:29 -0500 commented question instance snapshot fails to complete

For glance, I have it mapped to a NAS shared directory... Again, It has worked on all snapshots, but this one... For nova, instances / tmp snapshots are stored on a local NVMe drive.

2020-02-28 10:53:04 -0500 commented question instance snapshot fails to complete

Yes, I had done debug mode on those control node logs as well, but no issues could be seen... Could you step me through the process Snapshot uses to create/move/store the snapshot?

2020-02-28 07:04:30 -0500 commented question instance snapshot fails to complete

Hi... Yes, that was run with debug logs on, and that was the only thing I saw related to the snapshot process -- for hours... Should I post the entire log?

2020-02-27 17:41:49 -0500 asked a question instance snapshot fails to complete

I have several instances on one compute node. I can successfully "Create Snapshot" for all but one instance. The instance that fails to complete is much larger than the others, but at 99GB, there should still be plenty of disk space to create the temporary snapshot file. The temp snapshot file never gets bigger than 176KB.

The compute node is using a local NVMe drive for instance storage.

I have watched the local nova log and the glance log, but there are no errors. The process never gets past

2020-02-27 14:39:16.166 31638 INFO nova.virt.libvirt.driver [req-45708b6c-d892-4a87-ab82-2e68bfb8deb7 d63af2d376de4f68af54f1afdea41f8c d82194f0fc3a440faf5e73aae5337b61 - default default] [instance: 4a4fed08-ab95-4291-9841-c5a00a8cd7f5] Beginning cold snapshot process

I get the same result whether I run this via the Horizon interface or via the CLI. Is there anywhere else I can look to see why this snapshot is not processing? I am running OpenStack Stein (RDO Packstack with 6 compute nodes)

2019-10-29 02:49:20 -0500 received badge  Famous Question (source)
2019-09-19 17:32:28 -0500 asked a question compute host showing twice with different hostname

Hello, I have a small OpenStack cluster with 6 compute nodes. One of the nodes, node 3, is showing in Horizon's Compute Host list twice -- Once as vmc-03-vm and once as vmc-03-man. One shows the State as UP and vmc-03-man shows the state as DOWN. On the Hypervisor list, only vmc-03-man is listed. In the Host Aggregates list, they are both listed, and vmc-03-man shows (Services Down).

I only noticed this because I could see in the Hypervisor list that all of the other compute hosts have a large number of instances running on them, while this one host has ZERO instances running on it.

The physical hosts have multiple network cards and related hostnames, so something must have gotten mixed up when I installed... How can I fix this compute host so it will be properly recognized by openstack -- with only one hostname?

2019-07-31 04:54:57 -0500 received badge  Popular Question (source)
2019-07-31 04:54:57 -0500 received badge  Notable Question (source)
2019-07-30 17:01:35 -0500 answered a question Neutron fails to bind port when launching VM

I was able to fix this with the help of @eblock. OVS was pulling the server hostname from a different source than I had it configured (the CentOS host file)... To fix the problem I set the hostname for each server in /etc/sysconfig/network. OVS now picks up the correct hostname and does not use localhost. I should have done this before. Thank you for the great ideas!

2019-07-30 10:15:08 -0500 commented question Neutron fails to bind port when launching VM

You are absolutely right... The compute hostname is shp-vmc-05-man, but ovs-vsctl list open_vswitch shows external_ids : {hostname=localhost, ... Same thing happening on all hosts. Do you know a quick way to edit this OVS setting? Is this a bug?

2019-07-29 17:11:57 -0500 commented question Neutron fails to bind port when launching VM

Adding more neutron server.log info from DEBUG mode into the original post...

2019-07-29 10:57:37 -0500 received badge  Editor (source)
2019-07-29 09:39:57 -0500 commented question Neutron fails to bind port when launching VM

Thank you for responding. I am not running Cinder (just using local LVM storage for instances in this experiment), so openstack volume service list returns public endpoint for volumev2 service in RegionOne region not found. I will post the other lists in the edited post.

2019-07-29 09:39:48 -0500 commented question Neutron fails to bind port when launching VM

Note that neutron-dhcp-agent shows its STATE ad UP, but its ALIVE as XXX.

2019-07-29 09:34:39 -0500 received badge  Commentator
2019-07-26 23:53:59 -0500 asked a question Neutron fails to bind port when launching VM

I have been running a small Packstack Stein setup with 1 Controller/Network node and 6 Compute nodes. Everything was working fine for a week or so, and then I rebooted the Controller node. After that reboot, none of the VMs I had created will bind to their DHCP addresses. Also, when I try to create a new VM, Horizon gives this error:

Error: Failed to perform requested operation on instance "demo-ubuntu-1", the instance has an error status: Please try again later [Error: Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance a69324fb-6d8f-48db-879e-3ef7eb662e72. Last exception: Binding failed for port d5b75470-312f-43b2-9227-b7d9addd58ed, please check neutron logs for more information.].

The Neutron server.log shows this corresponding error:

2019-07-26 20:22:25.053 6556 ERROR neutron.plugins.ml2.managers [req-b95bda3

d-b022-464e-a0c9-90d8030e5141 66c1ccba9ff34e05bc28e503c3058f3d 4ab1c3975b3e4

6fba252f1fe38fd067d - default default] Failed to bind port d5b75470-312f-43b

2-9227-b7d9addd58ed on host shp-vmc-06-man for vnic_

type normal using segments [{'network_id': '64d106db-376b-4736-9e38-f820a9fc

87e3', 'segmentation_id': 50, 'physical_network': None, 'id': 'efe44ba5-d98f

-44d3-ac40-8b33d06fe6f3', 'network_type':

More Neutron server.log info from DEBUG mode:

2019-07-29 11:34:08.910 6536 DEBUG neutron.plugins.ml2.managers [req-07fc39e0-b191-4b8a-83e0-b7c2c8599498 66c1ccba9ff34e05bc28e503c3058f3d 4ab1c3975b3e46fba252f1fe38fd067d - default default] Attempting to bind port caa7070a-8e71-482c-87d9-a0e9deac5106 on host shp-vmc-06-man for vnic_type normal with profile  bind_port /usr/lib/python2.7/site-packages/neutron/plugins/ml2/managers.py:765
2019-07-29 11:34:08.911 6536 DEBUG neutron.plugins.ml2.managers [req-07fc39e0-b191-4b8a-83e0-b7c2c8599498 66c1ccba9ff34e05bc28e503c3058f3d 4ab1c3975b3e46fba252f1fe38fd067d - default default] Attempting to bind port caa7070a-8e71-482c-87d9-a0e9deac5106 by drivers ovn on host shp-vmc-06-man at level 0 using segments [{'network_id': '64d106db-376b-4736-9e38-f820a9fc87e3', 'segmentation_id': 50, 'physical_network': None, 'id': 'efe44ba5-d98f-44d3-ac40-8b33d06fe6f3', 'network_type': u'geneve'}] _bind_port_level /usr/lib/python2.7/site-packages/neutron/plugins/ml2/managers.py:792
2019-07-29 11:34:08.912 6536 DEBUG networking_ovn.ml2.mech_driver [req-07fc39e0-b191-4b8a-83e0-b7c2c8599498 66c1ccba9ff34e05bc28e503c3058f3d 4ab1c3975b3e46fba252f1fe38fd067d - default default] Refusing to bind port caa7070a-8e71-482c-87d9-a0e9deac5106 due to no OVN chassis for host: shp-vmc-06-man bind_port /usr/lib/python2.7/site-packages/networking_ovn/ml2/mech_driver.py:634

Again, the DHCP binding was working fine until I rebooted... Any ideas on what could be wrong, or where I could start looking?

I am not running Cinder in this experiment.

Here is the output of openstack compute service list:

[root@shp-vmc-00-man ~]# openstack compute service list
+----+------------------+----------------+----------+---------+-------+----------------------------+
| ID | Binary           | Host           | Zone     | Status  | State | Updated At                 |
+----+------------------+----------------+----------+---------+-------+----------------------------+
| 10 | nova-conductor   | shp-vmc-00-man | internal | enabled | up    | 2019-07-29T14:14:59.000000 |
| 21 | nova-scheduler   | shp-vmc-00-man | internal | enabled | up    | 2019-07-29T14:14:59.000000 |
| 31 | nova-consoleauth | shp-vmc-00-man | internal | enabled | up    | 2019-07-29T14:14:58.000000 |
| 32 | nova-compute     | shp-vmc-01-man | nova     | enabled | up    | 2019-07-29T14:15:00.000000 |
| 33 | nova-compute     | shp-vmc-02-man | nova     | enabled | up    | 2019-07-29T14:14:57.000000 |
| 34 | nova-compute     | shp-vmc-04-man | nova     | enabled | up    | 2019-07-29T14:14:57.000000 |
| 35 | nova-compute     | shp-vmc-05-man | nova     | enabled | up    | 2019-07-29T14:14:57.000000 |
| 36 | nova-compute     | shp-vmc-06-man | nova     | enabled | up    | 2019-07-29T14:15:00.000000 |
| 37 | nova-compute     | shp-vmc-03-vm  | nova     | enabled | up    | 2019-07-29T14:15:00.000000 |
+----+------------------+----------------+----------+---------+-------+----------------------------+

Here is the output of openstack network agent list:

[root@shp-vmc-00-man ~]# openstack network agent list

+--------------------------------------+----------------------+----------------+-------------------+-------+-------+-------------------------------+
| ID                                   | Agent Type           | Host           | Availability Zone | Alive | State | Binary                        |
+--------------------------------------+----------------------+----------------+-------------------+-------+-------+-------------------------------+
| 13b83a90-acd9-4c77-84ed-1f7caa2e2a5e | DHCP agent           | shp-vmc-00-man | nova              | XXX   | UP    | neutron-dhcp-agent            |
| dbf1018e-4178-48d0-a360-b315790897ef | OVN Controller agent | localhost      | n/a               | :-)   | UP    | ovn-controller                |
| 40dad5f7-b8d4-4c67-8376-2ba6672cf1fa | OVN Metadata agent   | localhost      | n/a               | :-)   | UP    | networking-ovn-metadata-agent |
| 37564b7a-8ea7-47e1-a2d3-dbd692728f05 ...
(more)
2019-07-16 10:20:49 -0500 received badge  Enthusiast
2019-07-12 16:53:37 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

Nevermind about that last comment... I had inserted the interface name into the wrong field in this new answer-file... I fixed it and this node also gets the same error as the previous node: ERROR : "Couldn't detect ipaddress of interface ens2f1 on node 10.57.38.122"

2019-07-12 16:53:37 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

ens2f1 (file: /var/tmp/packstack/07134f0190f947268d531377829727bd/modules/packstack/manifests/firewall.pp, line: 43)

2019-07-12 16:53:37 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

ERROR : Error appeared during Puppet run: 10.57.38.122_network.pp Error: Parameter source failed on Firewall[001 neutron tunnel port incoming neutron_tunnel_10.57.38.122_ens2f1]: Munging failed for value "ens2f1" in class source: host_to_ip failed for ens2f1, exception Failed to resolve hostname

2019-07-12 16:53:37 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

Thanks Bernd... I ran Packstack on a different server -- first as allinone, and then tried to add a compute node and that same OVN tunnel config. This time I got a different error, but also related to that interface:

2019-07-11 17:45:10 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

I ran packstack again after modifying my answer-file to use openvswitch instead of OVN, and I got the same result: ERROR : "Couldn't detect ipaddress of interface ens2f1 on node 10.57.38.123"

2019-07-11 08:49:41 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

Thank you Bernd. Do you have a link to the source code? I've done some searching and found a few different possibilities, but it's not clear which is the actual source code.

2019-07-10 23:02:04 -0500 received badge  Famous Question (source)
2019-07-10 16:53:56 -0500 commented question Packstack Stein - Cannot Detect Tunnel Interface

Thank you for your reply. I removed VXLAN and used Geneve as the driver, but I still got the same result when I re-ran Packstack: ERROR : "Couldn't detect ipaddress of interface ens2f1 on node 10.57.38.123" Do you think this could be a bug?

2019-07-10 04:23:19 -0500 received badge  Notable Question (source)
2019-07-09 22:19:25 -0500 received badge  Popular Question (source)
2019-07-09 17:42:14 -0500 received badge  Popular Question (source)
2019-07-09 09:15:35 -0500 commented question Error detecting ipaddress of OVN Tunnel interface

For some reason, I can't edit the post. I will delete and re-post.

2019-07-09 09:15:31 -0500 asked a question Packstack Stein - Cannot Detect Tunnel Interface

Hello, I am attempting to use Packstack with an answer file to install Openstack on two nodes -- a controller/network node and a compute node. I installed Packstack for Stein new today.

When I run packstack with the answer file, it gets to the step: "Preparing Neutron API entries" and then errors out. The error reads: ERROR : "Couldn't detect ipaddress of interface ens2f1 on node 10.57.38.123"

The controller node management IP is 10.57.38.123 (on bond0). I am trying to use ens2f1 for the OVN tunnel. It's IP address is 10.57.37.123 (verified on the server).

I will post the networking part of the answer file and the setup log with failure below. The entire answer file won't post correctly.


# Password to use for OpenStack Networking (neutron) to authenticate
# with the Identity service.
CONFIG_NEUTRON_KS_PW=##

# The password to use for OpenStack Networking to access the
# database.
CONFIG_NEUTRON_DB_PW=##

# The name of the Open vSwitch bridge (or empty for linuxbridge) for
# the OpenStack Networking L3 agent to use for external  traffic.
# Specify 'provider' if you intend to use a provider network to handle
# external traffic.
CONFIG_NEUTRON_L3_EXT_BRIDGE=br-ex

# Password for the OpenStack Networking metadata agent.
CONFIG_NEUTRON_METADATA_PW=91f9fac7af944e61

# Specify 'y' to install OpenStack Networking's Load-Balancing-
# as-a-Service (LBaaS). ['y', 'n']
CONFIG_LBAAS_INSTALL=n

# Specify 'y' to install OpenStack Networking's L3 Metering agent
# ['y', 'n']
CONFIG_NEUTRON_METERING_AGENT_INSTALL=y

# Specify 'y' to configure OpenStack Networking's Firewall-
# as-a-Service (FWaaS). ['y', 'n']
CONFIG_NEUTRON_FWAAS=n

# Specify 'y' to configure OpenStack Networking's VPN-as-a-Service
# (VPNaaS). ['y', 'n']
CONFIG_NEUTRON_VPNAAS=n

# Comma-separated list of network-type driver entry points to be
# loaded from the neutron.ml2.type_drivers namespace. ['local',
# 'flat', 'vlan', 'gre', 'vxlan', 'geneve']
CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,flat,geneve

# Comma-separated, ordered list of network types to allocate as
# tenant networks. The 'local' value is only useful for single-box
# testing and provides no connectivity between hosts. ['local',
# 'vlan', 'gre', 'vxlan', 'geneve']
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vxlan,geneve

# Comma-separated ordered list of networking mechanism driver entry
# points to be loaded from the neutron.ml2.mechanism_drivers
# namespace. ['logger', 'test', 'linuxbridge', 'openvswitch',
# 'hyperv', 'ncs', 'arista', 'cisco_nexus', 'mlnx', 'l2population',
# 'sriovnicswitch', 'ovn']
CONFIG_NEUTRON_ML2_MECHANISM_DRIVERS=ovn

# Comma-separated list of physical_network names with which flat
# networks can be created. Use * to allow flat networks with arbitrary
# physical_network names.
CONFIG_NEUTRON_ML2_FLAT_NETWORKS=*

# Comma-separated list of <physical_network>:<vlan_min>:<vlan_max> or
# <physical_network> specifying physical_network names usable for VLAN
# provider and tenant networks, as well as ranges of VLAN tags on each
# available for allocation to tenant networks.
CONFIG_NEUTRON_ML2_VLAN_RANGES=

# Comma-separated list of <tun_min>:<tun_max> tuples enumerating
# ranges of GRE tunnel IDs that are available for tenant-network
# allocation. A tuple must be an array with tun_max +1 - tun_min >
# 1000000.
CONFIG_NEUTRON_ML2_TUNNEL_ID_RANGES=

# Comma-separated list of addresses for VXLAN multicast group. If
# left empty, disables VXLAN from sending allocate broadcast traffic
# (disables multicast VXLAN mode). Should be a Multicast IP (v4 or v6)
# address.
CONFIG_NEUTRON_ML2_VXLAN_GROUP=

# Comma-separated list of <vni_min>:<vni_max> tuples enumerating
# ranges of VXLAN VNI IDs that are available for tenant network
# allocation. Minimum value is 0 and maximum value is 16777215.
CONFIG_NEUTRON_ML2_VNI_RANGES=10:100

# Name ...
(more)
2019-07-08 22:31:12 -0500 asked a question Error detecting ipaddress of OVN Tunnel interface

Hello, I am attempting to use Packstack with an answer file to install Openstack on two nodes -- a controller/network node and a compute node. I installed Packstack for Stein new today.

When I run packstack with the answer file, it gets to the step: "Preparing Neutron API entries" and then errors out. The error reads: ERROR : "Couldn't detect ipaddress of interface ens2f1 on node 10.57.38.123"

The controller node management IP is 10.57.38.123 (on bond0). I am trying to use ens2f1 for the OVN tunnel. It's IP address is 10.57.37.123 (verified on the server).

Below are my answer file and the setup log with failure.

Any ideas on what could be wrong?

AnswerFile: [general]

Path to a public key to install on servers. If a usable key has not

been installed on the remote servers, the user is prompted for a

password and this key is installed so the password will not be

required again.

CONFIG_SSH_KEY=/root/.ssh/id_rsa.pub

Default password to be used everywhere (overridden by passwords set

for individual services or users).

CONFIG_DEFAULT_PASSWORD=abc#

The amount of service workers/threads to use for each service.

Useful to tweak when you have memory constraints. Defaults to the

amount of cores on the system.

CONFIG_SERVICE_WORKERS=%{::processorcount}

Specify 'y' to install MariaDB. ['y', 'n']

CONFIG_MARIADB_INSTALL=y

Specify 'y' to install OpenStack Image Service (glance). ['y', 'n']

CONFIG_GLANCE_INSTALL=y

Specify 'y' to install OpenStack Block Storage (cinder). ['y', 'n']

CONFIG_CINDER_INSTALL=n

Specify 'y' to install OpenStack Shared File System (manila). ['y',

'n']

CONFIG_MANILA_INSTALL=n

Specify 'y' to install OpenStack Compute (nova). ['y', 'n']

CONFIG_NOVA_INSTALL=y

Specify 'y' to install OpenStack Networking (neutron) ['y']

CONFIG_NEUTRON_INSTALL=y

Specify 'y' to install OpenStack Dashboard (horizon). ['y', 'n']

CONFIG_HORIZON_INSTALL=y

Specify 'y' to install OpenStack Object Storage (swift). ['y', 'n']

CONFIG_SWIFT_INSTALL=n

Specify 'y' to install OpenStack Metering (ceilometer). Note this

will also automatically install gnocchi service and configures it as

the metrics backend. ['y', 'n']

CONFIG_CEILOMETER_INSTALL=n

Specify 'y' to install OpenStack Telemetry Alarming (Aodh). Note

Aodh requires Ceilometer to be installed as well. ['y', 'n']

CONFIG_AODH_INSTALL=n

Specify 'y' to install OpenStack Events Service (panko). ['y', 'n']

CONFIG_PANKO_INSTALL=n

Specify 'y' to install OpenStack Data Processing (sahara). In case

of sahara installation packstack also installs heat.['y', 'n']

CONFIG_SAHARA_INSTALL=n

Specify 'y' to install OpenStack Orchestration (heat). ['y', 'n']

CONFIG_HEAT_INSTALL=n

Specify 'y' to install OpenStack Container Infrastructure

Management Service (magnum). ['y', 'n']

CONFIG_MAGNUM_INSTALL=n

Specify 'y' to install OpenStack Database (trove) ['y', 'n']

CONFIG_TROVE_INSTALL=n

Specify 'y' to install OpenStack Bare Metal Provisioning (ironic).

['y', 'n']

CONFIG_IRONIC_INSTALL=n

Specify 'y' to install the OpenStack Client packages (command-line

tools). An admin "rc" file will also be installed. ['y', 'n']

CONFIG_CLIENT_INSTALL=y

Comma-separated list of NTP servers. Leave plain if Packstack

should not install ntpd on instances.

CONFIG_NTP_SERVERS=

Comma-separated list of servers to be excluded from the

installation. This is helpful if you are running Packstack a second

time with the same answer ...

(more)