Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2020-08-12
14:20:29 sean-k-mooney so it pretty safe
14:21:01 sean-k-mooney kklimonda: what did you need for your usecase
14:21:05 gmann yeah, chance of changing request body is very less. addition is there
14:21:11 gmann also scope control and new defaults, can solve the problem at most extend.
14:27:31 kklimonda sean-k-mooney: it's a billing issue - we want to have two types of VMs: pay-as-you-go and prepaid (attached to a contract). I need to limit `compute:create:*` API calls based on whether user has credits, or contract with a open slots for a given flavor type. Also, have a way to return a customized error message back to the user would be nice.
14:29:02 sean-k-mooney kklimonda: that is not really a policy function
14:29:58 sean-k-mooney kklimonda: that feels more like a use case for keystone middelware or quotas
14:30:36 kklimonda keystone middleware as in custom middleware for keystone?
14:31:07 gmann yeah, we cannot control these with policy
14:31:11 sean-k-mooney as in custom mideelware for the nova api
14:31:32 sean-k-mooney sorry not keystone middelware oslo.middleware
14:31:52 sean-k-mooney we have keystone middelware that uses that to handel all our auth
14:32:02 sean-k-mooney so its the example of api middelware that comes to mind
14:32:06 kklimonda can I still add custom middleware to nova? keystone have removed that feature around stein iirc
14:32:18 sean-k-mooney you can do it with paste
14:32:19 sean-k-mooney but yes
14:32:55 gmann here https://github.com/openstack/nova/blob/master/etc/nova/api-paste.ini
14:34:37 kklimonda makes sense, for some reason I've completely blacked out on middleware - derp
14:35:13 sean-k-mooney anyway im not that familar with how that all works but you can still add custom middleware and then intercept any request and do whatever you want provided you are also happy to support it yourself :)
14:56:03 alex_xu efried: sean-k-mooney, for the user add their own custom trait manually through placement, that should be the case we want to ignore the conflict trait from provider config?
14:56:47 alex_xu efried: sean-k-mooney, compare to modify inventory, the user adds custom trait is more normal case I guess
14:59:47 sean-k-mooney so CUSTOM_ traits we shoudl ignore i think
15:00:14 sean-k-mooney but standard tratis should only be set via virt driver or provider.yaml
15:00:40 sean-k-mooney i have to join a meething now however so havnt fully tought through that answer
15:02:59 alex_xu sean-k-mooney: yea
15:32:07 efried alex_xu: What does it mean to have a trait conflict? The provider config is intended to allow you to override things. If it contains a CUSTOM_ trait that's not already on the provider, we should add it. If there's a trait -- CUSTOM or otherwise -- on the provider but not in the config, we should leave it alone. Right?
17:48:11 eandersson I know Rocky patches are not a priority, but if someone has time could you look at getting this patch series merged? https://review.opendev.org/#/c/703117/
#openstack-nova - 2020-08-13
02:22:51 openstackgerrit renminmin proposed openstack/nova master: Fix instance booted with snapshot image and bdms https://review.opendev.org/745821
02:50:01 openstackgerrit Merged openstack/nova master: Detach is broken for multi-attached fs-based volumes https://review.opendev.org/741712
04:53:53 openstackgerrit Harshavardhan Metla proposed openstack/nova master: Raising a failure in case of 403 https://review.opendev.org/735068
08:07:11 openstackgerrit Alexandre Arents proposed openstack/nova master: Rebase qcow2 images when unshelving an instance https://review.opendev.org/696084
08:27:20 openstackgerrit Jie Li proposed openstack/nova master: fix revert resize failed https://review.opendev.org/746020
12:35:06 openstackgerrit Merged openstack/nova master: [Trivial] Remove wrong format_message() conversion https://review.opendev.org/744280
12:53:58 openstackgerrit Mark Goddard proposed openstack/nova master: docs: fix aggregate weight multiplier property names https://review.opendev.org/746128
14:28:25 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add new default roles in baremetal nodes policies https://review.opendev.org/741716
14:28:59 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Pass the actual target in baremetal nodes policy https://review.opendev.org/741717
14:31:30 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add new default roles in networks policies https://review.opendev.org/742566
14:31:52 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Pass the actual target in networks policy https://review.opendev.org/742568
14:34:32 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add scope and new default roles in extensions policies https://review.opendev.org/743046
14:36:30 artom Is logstash... working?
14:36:42 artom I'm trying to understand if "Multiple possible networks found, use a Network ID to be more specific" in the nova-next job is a recurring thing
14:55:44 sean-k-mooney artom: its a few days delayed
14:56:02 sean-k-mooney i think 3-5 days
14:57:19 sean-k-mooney artom: http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Multiple%20possible%20networks%20found,%20use%20a%20Network%5C%22
14:57:26 sean-k-mooney set it to 30days and you get hits
14:58:08 artom Ah yes, indeed. I feel like we've hit this before, for a different job
14:58:12 artom gmann ^^ sound familiar?
14:58:17 sean-k-mooney we have hit this many times
14:58:21 sean-k-mooney its a tempest bug
14:58:41 sean-k-mooney the tests are not wrtten correctly
14:59:07 artom I kinda figured that already :P
14:59:28 artom I was looking for a previous fix that I could plagiarize to avoid having to think about this ;)
14:59:38 artom Or to straight up "delegate" to someone else :P
15:01:11 sean-k-mooney the first failure was in this requiremnt update to neutron libs https://review.opendev.org/#/c/745237
15:02:00 sean-k-mooney that may or may not be related to the cause
15:12:33 gmann artom: sean-k-mooney yeah, we fixed this issue while we see error.
15:15:50 artom gmann, do you remember what the fix was? Do we need to redo it somewhere else?
15:16:36 gmann by default, tempest tests does not pass the dedicated network while creating server so we go test by test and request for unique network to be created for test
15:16:39 gmann artom: yeah
15:17:29 gmann artom: https://review.opendev.org/#/c/721767/
15:17:42 gmann which test failing?
15:18:29 artom gmann, looks like we're hitting it in tempest.scenario.test_server_advanced_ops.TestServerAdvancedOps.test_server_sequence_suspend_resume
15:18:59 artom And something else, but I can't figure out the test from the kibana info
15:19:52 gmann artom: ah that is scenario test which always has the unique network, let me confirm
15:20:09 sean-k-mooney there are a number of test failing
15:22:01 sean-k-mooney tempest-AttachInterfacesTestJSON tempest-test_creds-1679784040
15:22:36 gmann for API tests, root cause is same and we can fix it in Tempest side
15:23:23 sean-k-mooney actully i need to filter out passing jobs
15:23:35 sean-k-mooney apparently we have some tests that try to create that error
15:24:12 artom sean-k-mooney, ah, it would explain why https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_1a8/744280/6/check/nova-next/1a8a26e/controller/logs/screen-n-api.txt is from a passing job
15:24:30 artom I guess start by fixing test_server_sequence_suspend_resume then?
15:25:13 sean-k-mooney oh so 212 hits instead of ~500
15:26:23 sean-k-mooney and some of those have failure that are not related to this
15:26:45 sean-k-mooney this will be annoying to fine a query for
15:26:54 gmann test_server_sequence_suspend_resume does not explicit create the network and test try to get one from neutron - https://github.com/openstack/tempest/blob/master/tempest/scenario/manager.py#L257
15:27:58 gmann artom: the fix i mentioned will not help for test_server_sequence_suspend_resume , we need to do either create the network explicitly or add some common logic in scenario manager also like we do in API test
15:28:34 lyarwood I'm supposed to be running the meeting at the top of the hour but I've ended up home alone with my 10 week old who is wide awake and causing chaos, would anyone mind stepping in and running it this week?
15:29:45 gmann this query -http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22HTTP%20exception%20thrown:%20Multiple%20possible%20networks%20found,%20use%20a%20Network%20ID%20to%20be%20more%20specific.%5C%22%20AND%20NOT%20message:%5C%22AttachInterfacesTestJSON%5C%22%20AND%20tags:%5C%22screen-n-api.txt%5C%22&from=7d
15:32:59 admin0 when i run nova-manage --debug db sync .. it says ERROR: Could not access cell0. .. i check the username and password and the user (nova_api) can acess nova_cell0 database .. what could be wrong ?
15:34:17 admin0 or does nova_api need access to nova database also ?
15:34:47 sean-k-mooney this is the query i came up with http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Multiple%20possible%20networks%20found,%20use%20a%20Network%5C%22%20AND%20NOT%20message:%5C%22AttachInterfacesTestJSON%5C%22%20AND%20NOT%20message:%5C%22tempest-test_creds%5C%22%20%20AND%20NOT%20build_status:%5C%22SUCCESS%5C%22&from=30d
15:36:37 sean-k-mooney admin0: nova manage gets the db creds from the nova.conf
15:36:54 admin0 i have validated it and it is correct
15:37:01 admin0 is there a way to debug what actually it is using
15:37:02 gmann yeah, AttachInterfacesTestJSON is most in failing
15:37:11 admin0 --debug does not seem to produce that much of a log
15:37:49 sean-k-mooney gmann: right but none of those builds failed
15:38:07 lyarwood AttributeError: module 'libvirt' has no attribute 'VIR_ERR_DEVICE_MISSING' - whops, my bad.
15:38:13 sean-k-mooney well wehn the failed that was nto the issue
15:38:29 gmann yeah
15:39:19 admin0 sean-k-mooney, i did a grep mysql /etc/nova.conf .. then installed mysql-client .. and then when i do mysql -h (hostname as in the conf) -u username -p ( copy paste of the password) .. it works just fine i can login and select the database
15:39:51 gmann artom: sean-k-mooney do you have link where test_server_sequence_suspend_resume failing ?
15:40:29 admin0 i did a create table and drop table ( the same test table) to validate that the login is rw
15:41:17 sean-k-mooney admin0: odd im not certin what the issue is off the top of my head
15:41:51 admin0 is there a way to get more verbose/debug steps in nova-manage db sync ?
15:44:25 admin0 nova-manage --debug api_db sync and nova-manage --debug cell_v2 map_cell0 worked fine .. only in db sync its giving issues
15:48:46 artom gmann, https://zuul.opendev.org/t/openstack/build/0c87381c639e4d629fa2bd48ea2da4f2
15:49:56 gmann artom: thanks, i can try to build logic of creating unique network in scenario test too but may be during weekend or tomorrow.
15:50:25 gmann failing scenario tests on this should be less-frequent than API tests or rare
15:55:43 lyarwood I'm supposed to be running the meeting at the top of the hour but I've ended up home alone with my 10 week old who is wide awake and causing chaos, would anyone mind stepping in and running it this week?

Earlier   Later