Earlier  
Posted Nick Remark
#openstack-nova - 2021-09-10
18:01:57 dansmith right,
18:02:17 dansmith but 807014 is breaking lots of *other* gates, so we want that in the queue ASAP
18:03:20 gmann ohk.
18:03:47 gmann or try re/another +w can trigger gate pipeline directly ?
18:05:03 gmann but it might do check also. yeah rebase is more safer to put it queue asap
18:05:06 melwitt gmann: it's this if you want to try https://review.opendev.org/c/openstack/placement/+/807014
18:05:12 melwitt ok, will do then
18:05:24 dansmith I think rebasing is better,
18:05:34 dansmith because if they get kicked out, we want them to stay in the right order for the next trip
18:05:46 gmann ok
18:06:25 opendevreview melanie witt proposed openstack/placement master: Narrow scope of set allocations database transaction https://review.opendev.org/c/openstack/placement/+/807014
18:06:53 dansmith melwitt: got it
18:07:09 melwitt thanks!
19:00:05 opendevreview Merged openstack/placement master: Call Engine.execute() in func tests for oslo.db 11.0.0 https://review.opendev.org/c/openstack/placement/+/808477
19:58:08 admin1 hi all .. is this s known error ? is this a known error coming up when launching new instances "Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-17bb244e-46c6-4f2f-a213-3a1ae786afc2)" ?
20:03:32 melwitt admin1: that means an unhandled exception bubbled up to the api. need to check the nova-api.log to see what happened
21:09:25 opendevreview Merged openstack/placement master: Narrow scope of set allocations database transaction https://review.opendev.org/c/openstack/placement/+/807014
23:35:27 opendevreview Merged openstack/nova master: [doc] port-resource-request-groups not landed in Xena https://review.opendev.org/c/openstack/nova/+/807564
#openstack-nova - 2021-09-11
02:57:06 opendevreview melanie witt proposed openstack/placement master: Commonize code for updating and creating allocations https://review.opendev.org/c/openstack/placement/+/808535
05:59:03 gibi melwitt: thank you.
09:15:54 opendevreview Merged openstack/nova master: hardware: Add TODO to remove '(un)pin_cpu_with_siblings' https://review.opendev.org/c/openstack/nova/+/705666
10:04:41 opendevreview Merged openstack/python-novaclient master: Update master for stable/xena https://review.opendev.org/c/openstack/python-novaclient/+/808461
11:10:05 opendevreview Merged openstack/python-novaclient master: Add Python3 yoga unit tests https://review.opendev.org/c/openstack/python-novaclient/+/808462
13:34:50 opendevreview xiaoxin yang proposed openstack/nova master: Secure boot requires SMM feature enabled https://review.opendev.org/c/openstack/nova/+/808126
14:12:22 opendevreview Merged openstack/nova stable/queens: [neutron] Get only ID and name of the SGs from Neutron https://review.opendev.org/c/openstack/nova/+/791421
#openstack-nova - 2021-09-12
13:08:20 opendevreview Takashi Natsume proposed openstack/osc-placement master: Add Python3 yoga unit tests https://review.opendev.org/c/openstack/osc-placement/+/808565
#openstack-nova - 2021-09-13
08:57:16 gibi good morning
09:03:14 lyarwood Morning all \o
09:13:03 gibi lyarwood: there is a fairly easy bug repro and fix for placement that I'd like to land before RC1. melwitt already +2d it. So if you have time I would appreciate some review https://review.opendev.org/q/topic:story-2009167
09:13:20 lyarwood ack I'll look this morning
09:15:32 gibi thanks
09:39:21 gibi it is just my devstack or we broke $nova-manage db version ?
09:40:50 sean-k-mooney it now uses alembic
09:40:58 sean-k-mooney so its proably changed
09:41:42 gibi https://paste.opendev.org/show/809276/
09:42:29 sean-k-mooney that is not what i was expecting
09:42:33 gibi yeah
09:42:40 gibi me neither
09:42:57 lyarwood oh fun
09:43:10 sean-k-mooney Engine' object has no attribute 'get_main_option'
09:43:16 sean-k-mooney that should be a config object
09:43:21 sean-k-mooney not an engine right
09:43:37 sean-k-mooney oh its from alembic_version = alembic_api.current(engine)
09:43:50 sean-k-mooney not script_location = config.get_main_option("script_location")
09:44:09 sean-k-mooney are we passing things in the wrong order
09:45:32 sean-k-mooney https://alembic.sqlalchemy.org/en/latest/api/commands.html?highlight=current#alembic.command.current
09:45:50 sean-k-mooney i think ya we are passing the engine insteasd of the config
09:46:54 sean-k-mooney here https://github.com/openstack/nova/blob/master/nova/db/migration.py#L172-L173
09:48:13 sean-k-mooney we should probaly factor this out into a function https://github.com/openstack/nova/blob/master/nova/db/migration.py#L127-L139
09:49:04 gibi sean-k-mooney: thanks for the quick check, I will try it in devstack
09:49:24 sean-k-mooney cool i was going to hack something quickly and push it
09:50:57 gibi your suggestion seem to work
09:50:58 gibi https://paste.opendev.org/show/809277/
09:52:09 opendevreview Merged openstack/os-vif stable/xena: Update .gitreview for stable/xena https://review.opendev.org/c/openstack/os-vif/+/808452
09:52:11 opendevreview Merged openstack/os-vif stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena https://review.opendev.org/c/openstack/os-vif/+/808453
09:52:58 gibi sean-k-mooney: is it OK to you if I file a bug and push a fix?
09:53:53 sean-k-mooney sure
09:54:34 gibi OK, working on it
09:54:59 sean-k-mooney this is what i had
09:55:00 opendevreview sean mooney proposed openstack/nova master: [WIP] db version fix https://review.opendev.org/c/openstack/nova/+/808712
09:55:14 sean-k-mooney feel free to reuse or ignore
09:55:21 gibi sean-k-mooney: OK, thanks
10:01:27 gibi reported a critical bug for it as it affects the execution of db sync as well https://bugs.launchpad.net/nova/+bug/1943436
10:03:01 sean-k-mooney ah presumable because db sync checks the version first
10:03:25 sean-k-mooney do we know why this happens now
10:03:39 sean-k-mooney looking at git blame this has not changed for 3 months
10:04:07 gibi I think this is changed when we switched to alembic. was it 3 months ago?
10:04:18 sean-k-mooney yep
10:04:26 gibi I think we don't have test coverage on this path
10:04:26 sean-k-mooney well that is thet commit date
10:04:44 sean-k-mooney we should for sync however right
10:04:55 gibi as it only happens if the db is migrated to alembic control and then you wan to migrate it futher
10:05:18 sean-k-mooney ah
10:05:23 gibi so grenade will only hit it after we have Xena -> Yoga run
10:05:29 sean-k-mooney and since we have no migrations since then we would not see it
10:06:03 sean-k-mooney i was wondering if it was related to the alembic version bump 12 days ago
10:06:09 sean-k-mooney form 1.6.5 to 1.7.1
10:06:26 sean-k-mooney e.g. if the engine was previously valid and nolonger is
10:06:44 gibi I did not see any job failing do to this. I just noticed this problem when run the CLI manually this morning
10:10:54 gibi hm I was mistaken, the db sync part is not affected
10:16:26 sean-k-mooney its still a regerssion in either case
10:16:52 gibi yepp
10:17:02 gibi trying to add repro / test coverage
10:24:20 opendevreview Merged openstack/os-vif master: Update master for stable/xena https://review.opendev.org/c/openstack/os-vif/+/808454
10:42:47 opendevreview Merged openstack/placement master: Reproduce 404 when allocation queried with 1.38 https://review.opendev.org/c/openstack/placement/+/807154
10:57:31 gibi sean-k-mooney: alembic_api.current does not return the version alembic_script.ScriptDirectory.from_config( self.config)
10:57:34 gibi sorry
10:57:36 gibi wrong buffer
10:57:43 gibi so here https://github.com/openstack/nova/blob/master/nova/db/migration.py#L173
10:57:55 gibi the alembic_api.current does not return anything
10:58:02 gibi that function actually prints to stdout
11:02:29 sean-k-mooney hehe lovely
11:02:31 sean-k-mooney so 2 bugs
11:03:18 sean-k-mooney https://alembic.sqlalchemy.org/en/latest/api/commands.html#alembic.command.current right Display the current revision for a database.
11:04:02 sean-k-mooney we likely dont want to call the function form the command module
11:04:17 sean-k-mooney we likely want to get the saem from the engin or similar
11:10:12 gibi yepp
11:10:19 gibi https://alembic.sqlalchemy.org/en/latest/api/runtime.html#alembic.runtime.migration.MigrationContext
11:10:23 gibi I think that is the right way
11:10:40 gibi there is get_current_revision() on the MigrationContext object

Earlier   Later