Cinder HTTP 503 : Keystone unavailable

asked 2020-07-21 17:07:33 -0500

updated 2020-07-22 11:45:08 -0500

This is the Rocky release that I'm working with. After installing MariaDB, Glance, Nova, etc. Had no problems connecting these services to the horizon dashboard apache2.

Ran into problems with cinder. I can create volumes and groups on cinder command line, and the disks show up when using fdisk command. I'm feeling like I screwed up on something related to the cinder.conf

Smooth sailing only working on the controller node, but the compute node made me face more problems. I also have two separate storage nodes. And cinder has giving problems with devstack and I felt maybe by installing the services and conf files, then it would be easier off.

root@compute:~#
--- Volume group ---
  VG Name               cinder-volumes
  System ID
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  4
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               0
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               19.99 GiB
  PE Size               4.00 MiB
  Total PE              5118
  Alloc PE / Size       4872 / 19.03 GiB
  Free  PE / Size       246 / 984.00 MiB
  VG UUID               a1mu4X-fhl7-imqJ-5iO6-bBNN-cTxF-S7JK56



root@compute:~#
--- Physical volume ---
  PV Name               /dev/sdb
  VG Name               cinder-volumes
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               246
  Allocated PE          2313
  PV UUID               12NGCr-aGFX-jA3x-jh8I-eE1t-We2w-yvkICb

  --- Physical volume ---
  PV Name               /dev/sdc
  VG Name               cinder-volumes
  PV Size               10.00 GiB / not usable 4.00 MiB
  Allocatable           yes (but full)
  PE Size               4.00 MiB
  Total PE              2559
  Free PE               0
  Allocated PE          2559
  PV UUID               Nx3SZn-SrEU-Zw98-15tL-Ggc9-883z-rzFsYx



root@compute:~# fdisk -l
Disk /dev/loop0: 96.5 MiB, 101191680 bytes, 197640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 89.1 MiB, 93417472 bytes, 182456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EA66441F-E2D2-4DAB-A909-CC695259B244

Device     Start      End  Sectors Size Type
/dev/sda1   2048     4095     2048   1M BIOS boot
/dev/sda2   4096 20969471 20965376  10G Linux filesystem


Disk /dev/sdb: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdc: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

ITS GETTING THE VOLUMES TO SHOW UP IN DASHBOARD THATS CAUSING PROBLEMS

root@controller:~ nano /etc/cinder/cinder.conf
[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper = tgtadm
volume_name_template = volume-%s ...
(more)
edit retag flag offensive close merge delete

Comments

I'd check the Cinder API and Keystone logs for more information.

Your description is a bit confusing. You mention problems with the compute node without elaborating. You mention two storage nodes but cinder-vol seems to be installed on the compute node. And what's wrong with Devstack?

Bernd Bausch gravatar imageBernd Bausch ( 2020-07-21 19:27:31 -0500 )edit

Can you run other commands, such as openstack project list or openstack server list? What about Cinder services - check them with openstack volume service list.

Bernd Bausch gravatar imageBernd Bausch ( 2020-07-21 19:28:48 -0500 )edit

Also, it's unclear why you need an RC file on the compute node. Do you log on to the compute node and run openstack commands there? The compute node is not meant to be used like this.

Bernd Bausch gravatar imageBernd Bausch ( 2020-07-21 19:29:43 -0500 )edit

openstack project list works

stack@controller:~$ openstack server list Nothing comes up

stack@controller:~$ openstack volume service list The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503)

Ryan.McFarland.Bauer gravatar imageRyan.McFarland.Bauer ( 2020-07-22 11:51:09 -0500 )edit

should i uninstall the cinder-volume off the compute node and install it on my store1 and store2 nodes?

Ryan.McFarland.Bauer gravatar imageRyan.McFarland.Bauer ( 2020-07-22 11:52:47 -0500 )edit