Tag Archives: OpenStack

[Solved] nova-compute.log Error: Instance failed block device setup

Project scenario:

Openstack private cloud failed to create a virtual machine

nvoa-compute.log prompt:
instance failed block device setup
multipathd is not running exit code 1

Problem description

Create a new virtual machine, select the corresponding image, network, storage, etc., and the creation fails. The host status is error

Cause analysis:

If the cloud host creation fails, you need to first determine the node that the cloud host was scheduled to, then go to that node and check the nova-compute logs and search for that log record by UUID. It is better to determine the request ID, req-id, that created that task and go to the error log, as shown in the figure showing that the node is not running the multipath service causing the volume creation to fail.

Solution:

Start the corresponding node multipath service, and check whether the multipath service of all nodes is running normally.

systemctl restart multipathd.service
systemctl status multipathd.service

Then re-create the virtual machine.

[Solved] Failed to connect to server(code:1006)

Generally, the VNC configuration of the/etc/Nova/nova.conf configuration file is improper

Open, replace with

2. Modify novncproxy_base_URL, try to use IP address instead of domain name

For server_proxyclient_Address if you use a domain name, you need to modify the resolution in the local host file

Add a line: IP addresses Domain name

After modification Systemctl restart openstack-nova-compute.service restart the service

Problem solving

Fuel9.0 deployment openstack error: Deployment has failed,All nodes are finishedFailed task:Task[netconfig/1]

Fuel9.0 deployment openstack error:

When deploying a node in fuel9.0, click “deploy changes” and the following error occurs when deploying the node halfway:

Deployment has failed,All nodes are finishedFailed task:Task[netconfig/4] Stopping the deployment process!

solution: turn off 360 and firewall before deployment to avoid this error.

Attributeerror encountered when using ceilometer and gnocchi to execute commands related to gnocchi metric list: _Environ instance has no attribute ‘

AttributeError encountered when executing gnocchi metric list related commands using ceilometer and gnocchi: _Environ instance has no attribute ‘。
Control node execution: gnocchi metric list
Traceback (most recent call last):
File “/usr/bin/gnocchi”, line 10, in
sys.exit(main())
File “/usr/lib/python2.7/site-packages/gnocchiclient/shell.py”, line 252, in main
return GnocchiShell().run(args)
File “/usr/lib/python2.7/site-packages/gnocchiclient/shell.py”, line 99, in init
deferred_help=True,
File “/usr/lib/python2.7/site-packages/cliff/app.py”, line 79, in init
self.parser = self.build_option_parser(description, version)
File “/usr/lib/python2.7/site-packages/gnocchiclient/shell.py”, line 130, in build_option_parser
os.environ.set(“OS_AUTH_TYPE”, “password”)
AttributeError: _Environ instance has no attribute ‘set’

Solution:
vi keystonerc_admin
Modify
unset OS_SERVICE_TOKEN
export OS_USERNAME=admin
export OS_PASSWORD=‘openstack password’
export OS_REGION_NAME=RegionOne
export OS_AUTH_URL=http://x.x.x.x:5000/v3
export PS1=’[\u@\h \W(keystone_admin)]$ ’
export OS_PROJECT_NAME=admin
export OS_USER_DOMAIN_NAME=Default
export OS_PROJECT_DOMAIN_NAME=Default
export OS_IDENTITY_API_VERSION=3
export OS_PLACEMENT_API_VERSION=1.17
export OS_AUTH_TYPE=password
At this point the following command can be used in the terminal:

source ~/keystonerc_admin
gnocchi metric list
gnocchi metric list | grep cpu
gnocchi resource list
gnocchi resource list  --type image
gnocchi measures show 839afa02-1668-4922-a33e-6b6ea7780715

After openstack neutron is installed, the Linux bridge starts and the error is resolved

After openstack neutron is installed, the Linux bridge starts and the error is resolved

After the Linux bridge service is started, check the operation log and report errors. For possible solutions, refer to the blog

After the Linux bridge service is started, check the operation log and report an error

    after installing and configuring the neutron computing node component, start the linuxbridge service, which can be started, but check the operation log and find an error. The main error contents are:
Oslo_ Privsep.daemon.failedtodropprivileges: privsep helper command exited non zero (1)

    at this time, check dhcp-agent.log and find the same error. After reading several blogs on Baidu, the positioning problem is the permission problem.

Possible solutions

1. First, close SELinux. It is possible that SELinux has access control over privsep helper programs. Modify/ etc/SELinux/config file:
change SELinux = enforcing to SELinux = disabled
restart the system: reboot
check whether the problem is solved

2. If the above methods cannot be solved, it may also be that neutron privsep needs sudo permission, but the default environment is not configured after installation. Therefore, add sudoer permission
modify the VIM/etc/neutron/neutron.conf file, and modify the following contents:

[privsep]
user = neutron
helper_command = sudo privsep-helper

Modify the VIM/etc/sudoers. D/neutron file, add the following contents, and then force save and exit

neutron ALL = (root) NOPASSWD: ALL

customer service

[1] https://www.cnblogs.com/dyd168/p/14466744.html

A solution to the refusal of rdesktop connection to windows host

1. On the Windows host to be connected, right click ‘My Computer’ -& GT; Attribute “- & gt; “Advanced System Settings” – & GT; Remote setting “-& GT; In the Remote Desktop option, select the connection that allows you to run any version of the remote desktop. 2. Check whether the Linux host and the Windows host to be connected can ping each other; 3. Check whether the IP address appended to rdesktop is correct; 4. Create passwords for users on Windows hosts. Sometimes rdesktop cannot support password-less remote connections. 5. Close the firewall on the Windows host.
in general, rdesktop can connect to remote Windows hosts after the above five steps.

Failed to start Remote desktop service (VNC)

problem: after setting up the VNC, restart has been failed 

[root@gaia system]# systemctl status vncserver@:1.service
● vncserver@:1.service - Remote desktop service (VNC)
   Loaded: loaded (/usr/lib/systemd/system/vncserver@:1.service; disabled; vendor preset: disabled)
   Active: failed (Result: resources) since Fri 2020-03-27 16:27:34 CST; 14s ago
  Process: 12500 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS)
  Process: 12496 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS)

Mar 27 16:27:30 gaia systemd[1]: Starting Remote desktop service (VNC)...
Mar 27 16:27:34 gaia systemd[1]: PID file /root/.vnc/gaia:1.pid not readable (yet?) after start.
Mar 27 16:27:34 gaia systemd[1]: Failed to start Remote desktop service (VNC).
Mar 27 16:27:34 gaia systemd[1]: Unit vncserver@:1.service entered failed state.
Mar 27 16:27:34 gaia systemd[1]: vncserver@:1.service failed.


address:
rm - rf/TMP /. * X 

[root@gaia data]# systemctl daemon-reload
[root@gaia data]# systemctl restart vncserver@:1.service
[root@gaia data]# systemctl status vncserver@:1.service