Closed naved001 closed 1 year ago
@naved001 Do we know if Yatharth is planning on migrating to the NERC environment? If so, then maybe we don't care about these issues as long as Cinder is operating correctly (because then it's just a volume migration issue).
Hmm, except that volume list
is also failing with a 503 error, so there goes that idea.
@larsks I don't know what their plan is, but they will be affected by this because we can't retrieve any volumes either
I'll take a closer look.
@naved001 I think the problem is that you have disabled the service
project, which all the services use for authentication:
$ openstack project show service
+-------------+-----------------------------------+
| Field | Value |
+-------------+-----------------------------------+
| description | Tenant for the openstack services |
| domain_id | default |
| enabled | False |
| id | da2e40428b7e4083a65131b090efa896 |
| is_domain | False |
| name | service |
| parent_id | default |
| tags | [] |
+-------------+-----------------------------------+
I've enabled the project:
openstack project set --enable service
And now things seem to work:
$ openstack hypervisor list
+----+-----------------------------+-----------------+--------------+-------+
| ID | Hypervisor Hostname | Hypervisor Type | Host IP | State |
+----+-----------------------------+-----------------+--------------+-------+
| 2 | neu-3-35-stackcomp.kzn.moc | QEMU | 172.16.32.16 | up |
| 5 | neu-3-37-stackcomp.kzn.moc | QEMU | 172.16.32.12 | up |
| 8 | neu-5-36-stackcomp.kzn.moc | QEMU | 172.16.32.24 | up |
| 11 | neu-5-38-stackcomp.kzn.moc | QEMU | 172.16.32.13 | down |
| 14 | neu-15-34-stackcomp.kzn.moc | QEMU | 172.16.32.31 | up |
| 17 | neu-5-34-stackcomp.kzn.moc | QEMU | 172.16.32.25 | up |
| 20 | neu-15-38-stackcomp.kzn.moc | QEMU | 172.16.32.35 | up |
| 23 | neu-5-35-stackcomp.kzn.moc | QEMU | 172.16.32.15 | up |
| 26 | neu-3-38-stackcomp.kzn.moc | QEMU | 172.16.32.17 | up |
| 29 | neu-3-34-stackcomp.kzn.moc | QEMU | 172.16.32.18 | up |
| 32 | neu-5-37-stackcomp.kzn.moc | QEMU | 172.16.32.34 | up |
| 35 | neu-15-36-stackcomp.kzn.moc | QEMU | 172.16.32.33 | down |
| 38 | neu-15-37-stackcomp.kzn.moc | QEMU | 172.16.32.43 | up |
| 41 | neu-3-36-stackcomp.kzn.moc | QEMU | 172.16.32.20 | up |
| 44 | neu-15-35-stackcomp.kzn.moc | QEMU | 172.16.32.40 | down |
| 48 | neu-15-12-gcomp.kzn.moc | QEMU | 172.16.32.23 | up |
| 50 | neu-17-2-stackcomp.kzn.moc | QEMU | 172.16.32.21 | up |
| 53 | neu-17-1-stackcomp.kzn.moc | QEMU | 172.16.32.14 | up |
| 59 | neu-19-1-stackcomp.kzn.moc | QEMU | 172.16.32.32 | up |
| 62 | neu-19-3-stackcomp.kzn.moc | QEMU | 172.16.32.37 | up |
| 65 | neu-19-5-stackcomp.kzn.moc | QEMU | 172.16.32.39 | up |
| 71 | neu-17-4-stackcomp.kzn.moc | QEMU | 172.16.32.26 | up |
| 74 | neu-17-3-stackcomp.kzn.moc | QEMU | 172.16.32.22 | up |
| 77 | neu-19-2-stackcomp.kzn.moc | QEMU | 172.16.32.36 | up |
| 80 | neu-19-4-stackcomp.kzn.moc | QEMU | 172.16.32.38 | up |
| 86 | neu-19-12-gcomp.kzn.moc | QEMU | 172.16.32.42 | up |
+----+-----------------------------+-----------------+--------------+-------+
@larsks great, thanks!
To address osticket #001222, I enabled the project but I couldn't list any servers in that project. Then I realized I cannot run lots of other openstack commands.
I can't launch any new instance on my project (which is enabled) because it says I have exceeded the quota.
I can still run project related commands like,
openstack project show
,openstack project list
etc.I don't know if that has anything to do with me disabling most projects, I am sure the
admin
project is enabled` if that matters. I will look at the logs next.@knikolla @larsks any thoughts?