Can't launch instance after adding disk space to /var/log/nova/instances

asked 2017-01-22 22:29:30 -0500

Don75080 gravatar image

I had an issue when I was launching instances due to free space in /var/log/nova/instances and I had a free drive available on the compute nodes. So, I formatted and mounted /dev/sdb1 under /var/log/nova/instances. This fixed the error I was having starting large instances ("no node available") but now all launches fail when opening "console.log". What I found is that all files under /var/log/nova/instances are not owned by user id nova, group id nova but are also owned by qemu. The qemu files are the ones failing (console.log). I have checked other openstack installs I have done and the permissions appear exactly the same. Any help setting permissions correctly would be appreciated. I could reinstall but I do not see the need to do so for something as simple as this.

"/var/lib/nova/instances/d9ca9e6e-57cd-4127-b1e4-0edc4fa46160/console.log: Permission denied"

| fault                                | {"message": "Exceeded maximum number of retries. Exceeded max scheduling attempts 3 for instance d9ca9e6e-57cd-4127-b1e4-0edc4fa46160. Last exception: Unable to open file: /var/lib/nova/instances/d9ca9e6e-57cd-4127-b1e4-0edc4fa46160/console.log: Permission denied", "code": 500, "details": "  File \"/usr/lib/python2.7/site-packages/nova/conductor/manager.py\", line 400, in build_instances |
|                                      |     filter_properties, instances[0].uuid)                                                                                                                                                                                                                                                                                                                                                                   |
|                                      |   File \"/usr/lib/python2.7/site-packages/nova/scheduler/utils.py\", line 186, in populate_retry

Taken from a working system below:

[root@overcloud-compute-2 instances]# ls -l
total 4
drwxr-xr-x. 2 nova nova 54 Dec 27 22:50 _base
-rw-r--r--. 1 nova nova 53 Jan 22 20:12 compute_nodes
drwxr-xr-x. 2 nova nova 54 Dec 27 22:50 d64a8a5e-101b-482e-9a71-34883d03564c
drwxr-xr-x. 2 nova nova 93 Dec 27 22:50 locks
[root@overcloud-compute-2 instances]# ls -lR
.:
total 4
drwxr-xr-x. 2 nova nova 54 Dec 27 22:50 _base
-rw-r--r--. 1 nova nova 53 Jan 22 20:12 compute_nodes
drwxr-xr-x. 2 nova nova 54 Dec 27 22:50 d64a8a5e-101b-482e-9a71-34883d03564c
drwxr-xr-x. 2 nova nova 93 Dec 27 22:50 locks

./_base:
total 2600188
-rw-r--r--. 1 qemu qemu 21474836480 Jan 22 20:12 034a6a49970faf6570537aa2af972eb2ce33d417

./d64a8a5e-101b-482e-9a71-34883d03564c:
total 12143264
-rw-r--r--. 1 qemu qemu       53343 Dec 27 22:55 console.log
-rw-r--r--. 1 qemu qemu 12434538496 Jan 22 20:19 disk
-rw-r--r--. 1 nova nova          79 Dec 27 22:50 disk.info

./locks:
total 0
-rw-r--r--. 1 nova nova 0 Dec 27 22:50 nova-034a6a49970faf6570537aa2af972eb2ce33d417
-rw-r--r--. 1 nova nova 0 Dec 17 00:08 nova-storage-registry-lock

Not Working compute node:

[root@overcloud-compute-6 nova]# ls -lR
.:
total 0
drwxr-xr-x. 2 nova nova   6 Nov 16 17:21 buckets
drwxr-xr-x. 8 nova nova 152 Nov 30 14:17 CA
drwxrwxrwx. 4 nova nova  53 Jan 21 22:31 instances
drwxr-xr-x. 2 nova nova   6 Nov 16 17:21 keys
drwxr-xr-x. 2 nova nova   6 Nov 16 17:21 networks
drwxr-xr-x. 2 nova nova   6 Nov 16 17:21 tmp

./buckets:
total 0

./CA:
total 12
drwxr-xr-x. 2 nova nova    6 Nov 16 17:21 certs
drwxr-xr-x. 2 nova nova    6 Nov 16 17:21 crl
-rwxr-xr-x. 1 nova nova 1787 Oct 10 13:20 geninter.sh
-rwxr-xr-x. 1 nova nova ...
(more)
edit retag flag offensive close merge delete

Comments

Check if SELinux is enabled (in case of RHEL based Linux)

Moorthy gravatar imageMoorthy ( 2017-01-25 03:43:24 -0500 )edit