Earlier  
Posted Nick Remark
#openstack-nova - 2020-10-21
13:45:49 stephenfin gibi: It was something to do with o.vo namespaces. A broken test
13:46:08 stephenfin wait, no, different thing
13:47:10 stephenfin I think the older compute nodes are passing notifications back to the conductor, and the conductor can't understand those because we removed the definitions
13:47:25 stephenfin so in that change we've stopped passing them back, meaning we can remove the definitions in the next release
13:47:50 stephenfin here's we stopped passing them back, as you've seen https://review.opendev.org/#/c/749312/4/nova/compute/utils.py
13:48:22 gibi stephenfin: I don't see where we passing the o.vo via RPC
13:49:05 stephenfin Here, no? https://review.opendev.org/#/c/749312/4/nova/notifications/base.py@203
13:50:20 gibi it just emits the notification o.vo not the nova bw ovo to the message bus as notification, not as RPC message to the conductor
13:51:02 stephenfin The notification o.vo contains the bandwidth payload o.vo though
13:51:23 gibi the bandwidth payloa o.vo yes, but not he bandwidth nova o.vo
13:51:30 stephenfin ohhhhh
13:51:47 stephenfin I understand the question now :) Sec, lemme check
13:53:38 stephenfin gibi: I guess I'm just going to have to push up a DNM patch to get new grenade logs for. Will do that shortly
13:53:51 gibi stephenfin: OK, let's do that
15:17:51 markguz_ Hi. is it possible to use alternate names for the nova databases? i have a second region i'm setting up, it's in the same physical location so i wanted to colocate the dbs on the existing galera cluster.
15:18:08 markguz_ nova-manage db sync does not seem to like it however
15:20:45 gibi markguz_: the [database]/connection config option defines which database nova uses. I think you are free to use any db name you wish
15:28:49 bauzas gibi: markguz_: indeed, you're free but you need to have distinct connection strings between the api connection and each of the cell connection URLs
15:29:01 gibi bauzas: true
15:29:27 markguz_ gibi: bauzas: i have defined those distinct connection strings in nova
15:31:03 bauzas markguz_: what kind of "weird" nova-manage exception do you get when you sync ?
15:31:13 gibi from the doc https://docs.openstack.org/nova/rocky/cli/nova-manage.html#nova-database "The local database connection is determined by [database]/connection in the configuration file passed to nova-manage."
15:31:34 bauzas gibi: for a single cellv2, yep
15:31:57 bauzas gibi: but if you wanna create a second cell v2, then you need to pass a second connection URL, right?
15:32:22 gibi bauzas: our you have to run nova-manage from the node of the second cell controller
15:32:28 gibi s/our/or/
15:33:26 gibi anyhow if the correct config file is passed to nova-manage but db sync fails then it is an interesting bug to look at
15:33:44 openstackgerrit Lee Yarwood proposed openstack/nova stable/train: Add a workaround config toggle to refuse ceph image upload https://review.opendev.org/757177
15:33:48 bauzas gibi: yup, indeed
15:34:00 bauzas devstack does this by passing the connection string URL on the fly
15:34:03 bauzas but meh
15:34:11 bauzas I guess this is maybe unrelated to it
15:34:47 markguz_ bauzas: gibi: so these are the connection strings as I defined them in /etc/nova/nova.conf https://pastebin.com/e1Sb9PjF
15:36:48 gibi markguz_: could you share the error message and any stack trace that nova-manage produced?
15:38:15 markguz_ gibi: i'm just going throught the manage steps to recreate. hold on
15:39:38 openstackgerrit Merged openstack/nova stable/ussuri: Follow up for cherry-pick check for merge patch https://review.opendev.org/758463
15:45:07 markguz_ gibi: bauzas: https://pastebin.com/n9aXXKSK
15:45:14 bauzas on a meeting but looking
15:46:00 markguz_ gibi: bauzas: seems like its the cell0 db that's the sticking point.
15:46:23 bauzas markguz_: go look at the DB itself
15:46:40 markguz_ gibi: bauzas: i might have missed some config where you can define the name of the cell0 db
15:46:53 bauzas ah
15:46:54 bauzas no
15:46:56 bauzas you can't
15:47:28 bauzas ah wait
15:47:43 bauzas ok, got it
15:48:00 bauzas you are reusing the 'nova' connection string for cell0
15:48:15 bauzas but 'nova' DB is officially the API DB
15:48:20 bauzas hence the error
15:48:39 bauzas you need to pass another connection string for map_cell0
15:49:35 bauzas eg. nova-manage cell_v2 map_cell0 --database_connection my_connection_string_for_cell0
15:49:40 bauzas markguz_: ^
15:50:02 markguz_ ahhhh....dagnabbit. how did i miss that... sorry for the trouble
15:50:05 bauzas or use another conf file, or run it elsewhere, as gibi said
15:50:19 bauzas markguz_: np, this is confusing
15:50:22 markguz_ bauzas: i am using another conf gile
15:50:29 markguz_ i'm using a whole other node
15:50:38 bauzas markguz_: distinct from the API DB ? :)
15:50:47 bauzas that's not what I see from the paste
15:51:15 bauzas nova has *at least* 3 DBs
15:51:27 bauzas API DB, cell0 DB and cell1 at least
15:51:28 markguz_ the api db doesn't take it's connection string from the nova.conf ?
15:51:36 bauzas sure
15:51:38 bauzas it can
15:51:43 bauzas but that's the api db
15:51:53 bauzas cell0 db is another db
15:52:02 bauzas and you're asking to map cell0 as the api db
15:52:17 bauzas it can be on the same dbms
15:52:27 bauzas but this has to be another logical database
15:52:34 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Clean up base migration https://review.opendev.org/758155
15:52:35 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Merge in unique constraints https://review.opendev.org/758156
15:52:35 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Drop add/remove of index https://review.opendev.org/758157
15:52:36 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Icehouse database migrations https://review.opendev.org/758394
15:52:36 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Juno database migration https://review.opendev.org/758395
15:52:37 openstackgerrit Stephen Finucane proposed openstack/nova master: WIP: db: Compact Kilo database migrations https://review.opendev.org/758396
15:52:37 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Liberty database migrations https://review.opendev.org/758397
15:52:38 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Mitaka database migrations https://review.opendev.org/758398
15:52:38 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Newton database migrations https://review.opendev.org/759085
15:52:39 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Ocata database migrations https://review.opendev.org/759086
15:52:39 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Pike database migrations https://review.opendev.org/759087
15:52:40 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Queens database migrations https://review.opendev.org/759088
15:52:40 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Rocky database migrations https://review.opendev.org/759089
15:52:41 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Stein database migrations https://review.opendev.org/759090
15:52:41 openstackgerrit Stephen Finucane proposed openstack/nova master: db: Compact Train database migrations https://review.opendev.org/759091
15:52:43 bauzas that you have to create separately from the api db
15:52:58 bauzas stephenfin: you dawn paste bomber
15:53:24 markguz_ bauzas: so my connection strings are this https://pastebin.com/e1Sb9PjF
15:53:30 bauzas markguz_: eg. 'nova' can be your API DB
15:53:44 stephenfin gotta be done ~o~
15:54:08 stephenfin the kilo one is broken though. I haven't figured out why yet. Will pick up again later in the week
15:54:48 markguz_ bauzas: ok. confused. i thought from the docs that there is always nova, nova_api nova_cell0 and since rocky placement can be seperate
15:55:25 bauzas actually, that's me who's lost
15:56:11 markguz_ i think the only missing part of the puzzle is that the cell0 db has no conf options and has to be manually supplied at the cli if using something other than nova_cell0
15:56:27 markguz_ i'm a try it now
15:57:17 bauzas I'm litterally looking at the nova-manage source code
15:57:31 bauzas and we assume a _cell0 postfix if nothing was passed
15:58:27 markguz_ so nova_vsphere should be nova_vsphere_cell0 ?
15:58:31 bauzas ok, got it
15:58:52 markguz_ full disclosure.. this is rocky... so maybe it's been fixed subsequently?
15:59:26 bauzas looking at the rocky code then

Earlier   Later