Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-07-27
03:10:35 mriedem sapd: read through https://docs.openstack.org/neutron/latest/admin/config-sriov.html and check everything in there
03:10:54 melwitt mriedem: coolness, sounds good
03:14:12 sapd mriedem: yep. I have read it. And follow the guide to config. Everything I setup is correct. Because I already launched an instance using SR-IOV successful. But It did not receive DHCP. So I launched another instance using Openvswitch then add SR-IOV port to the instance. But got above error.
03:16:57 melwitt sapd: looks like the bug has been around for awhile and still not resolved https://bugs.launchpad.net/nova/+bug/1708433 they say you can boot with the port if you pass it during server create, but that attaching port separately is broken
03:16:57 openstack Launchpad bug 1708433 in OpenStack Compute (nova) "Attaching sriov nic VM fail with keyError pci_slot" [Undecided,Expired]
03:18:17 melwitt sapd: what release of nova are you using?
03:18:32 sapd melwitt: I'm using queens version. 17.0.4
03:18:34 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Use source vifs when unplugging on source during post live migrate https://review.openstack.org/586402
03:18:35 mriedem melwitt: bzhao__: Kevin_Zheng: sean-k-mooney: ^ just needs unit tests
03:19:03 melwitt sapd: okay, I'm going to re-open that bug and mention what version you saw it in. it will need to be worked on
03:19:13 Kevin_Zheng mriedem, got it, just finish reading launchpad report
03:19:15 mriedem ask sahid to look at it
03:19:19 mriedem the sriov bug i mean
03:19:54 melwitt k
03:20:33 sean-k-mooney[m] Melwitt we used ti have an api check at one point to expresly forbid attach sriov port to existing instances.
03:20:50 melwitt hmm, interesting. I wonder what happened to that
03:21:03 sapd melwitt: I'm waiting.
03:21:12 melwitt hah
03:21:24 sean-k-mooney[m] Melwitt im guessing some of artoms changes
03:23:25 melwitt okay, I'll ask him about it
03:26:04 openstackgerrit Merged openstack/os-vif stable/rocky: Add vif_plug_noop to setup.cfg packages https://review.openstack.org/586340
03:26:20 melwitt hot dog
03:29:02 bzhao__ mriedem: So so quick.... =。=
03:31:48 melwitt I think I'm gonna give up on rechecking the r-3 patches, seems like a pretty high fail rate with the live migration thing
03:32:10 melwitt get the fix sorted in the morning and go from there
03:48:05 mriedem should have tests done pretty soon
03:56:58 openstackgerrit Matt Riedemann proposed openstack/nova master: Use source vifs when unplugging on source during post live migrate https://review.openstack.org/586402
03:57:22 mriedem alright gang there it is with a test ^
04:04:03 mriedem and now i'm going to bed
04:04:04 mriedem o/
04:04:13 melwitt gnite
04:47:28 openstackgerrit Xiaohan Zhang proposed openstack/nova master: compute node local_gb_used include swap disks https://review.openstack.org/585928
05:11:45 vishakha melwitt : Hi, waiting for your response https://review.openstack.org/#/c/580271/. Thanks
06:08:33 openstackgerrit Vishakha Agarwal proposed openstack/nova master: No change in field 'updated' in server https://review.openstack.org/586446
06:25:05 openstackgerrit Vishakha Agarwal proposed openstack/nova master: No change in field 'updated' in server https://review.openstack.org/586446
06:32:25 ileixe Hello again
06:33:11 ileixe Does any body know how to expand APIExtensionBase for pre-processing not for post-processing..?
06:47:47 openstackgerrit Xiaohan Zhang proposed openstack/nova master: compute node local_gb_used include swap disks https://review.openstack.org/585928
07:15:26 openstackgerrit Chen proposed openstack/nova master: Make nova-manage capable of syncing all cell databases https://review.openstack.org/519275
07:33:02 openstackgerrit Vishakha Agarwal proposed openstack/nova master: No change in field 'updated' in server https://review.openstack.org/586446
07:43:12 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Fix create_all() to replace_all() in comments https://review.openstack.org/586396
08:20:50 kashyap Hey folks, I'm hitting a "POST_FAILURE" state for the 'nova-live-migration' CI job; seems like a Zuul problem?
08:20:55 kashyap (For this change: https://review.openstack.org/#/c/567258/)
08:21:28 PapaOurs kashyap: nothing raised by infra AFAIK
08:21:46 PapaOurs kashyap: but maybe you should ask in #openstack-infra ?
08:21:48 kashyap Nod; in the past I've seen channel topic being changed when such errors occurreed.
08:21:56 kashyap PapaOurs: Yep, was just about to check there.
08:22:31 kashyap When I look into the log, it's the SSH failing
08:43:37 openstackgerrit Vishakha Agarwal proposed openstack/nova master: No change in field 'updated' in server https://review.openstack.org/586446
09:15:19 akki can we take lxd container snapshots and use them to launch new containers?
09:18:51 PapaOurs do folks have any idea why we stupidly set the device owner of a port to be compute:<instance_az> ?
09:18:56 openstackgerrit huanhongda proposed openstack/nova master: hypervisor-stats shows wrong disk usages with shared storage https://review.openstack.org/149878
09:29:35 MultipleCrashes Looking for further review from sometime , please have a look https://review.openstack.org/#/c/563418/
09:32:14 openstackgerrit huanhongda proposed openstack/nova master: Change the metadata re to match the unicode https://review.openstack.org/536236
10:15:09 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use placement 1.28 in scheduler report client https://review.openstack.org/583667
10:36:41 sean-k-mooney[m] kashyap: post_failure means the job failed to upload the logs/result
10:36:49 kashyap sean-k-mooney[m]: Ah, I see
10:37:09 kashyap sean-k-mooney[m]: I hit a recheck, let's see if it goes through.
10:37:31 kashyap sean-k-mooney[m]: Would you happen to have time to have a gander at this: https://review.openstack.org/#/c/567258/ ("libvirt: Remove usage of migrateToURI{2} APIs")
10:37:39 kashyap Fairly mechanical, but some churn in there.
10:38:03 kashyap (The 'recheck' is still in progress, though.)
10:38:07 kashyap It's slow as molasses.
10:38:12 sean-k-mooney[m] Am sure. I'll take a look once i ger coffee
10:39:19 sean-k-mooney[m] Its feature freeze time the gate is under a lot of load. Rechek is all you could have done in this case
10:47:16 kashyap Ah, right
10:52:42 openstackgerrit Merged openstack/nova master: doc: add missing permission for the vCenter service account https://review.openstack.org/585683
10:59:40 gilfoyle I'm trying to replicate some of nova's (the cli util) is doin. This is an old deployment of openstack. My goal is to understand how it is getting the zone-related information from the database when no zones are created
11:00:15 gilfoyle could someone help me by pointing out where in the repos should I be looking for this?
11:00:24 gilfoyle the relevant command is `nova availability-zone-list`
11:04:38 sean-k-mooney gilfoyle: what is the result you are getting and what were you expecting
11:05:00 sean-k-mooney ther are 2 default az that exist without you creating any
11:05:04 sean-k-mooney internal and nova
11:05:24 sean-k-mooney the contoler nodes will be in internal and all computes will be in nova
11:08:13 sean-k-mooney kashyap: i was going to ask why ther is a migrateToURI() migrateToURI2() and migrateToURI3() then i rembered libvirt is written in c...
11:10:41 gilfoyle sean-k-mooney: my issue is that I'm running a query against a database that's not returning me any of the coputes in the `nova` and from the nova command above I do see it thee
11:10:46 gilfoyle there even, apologies
11:11:55 sean-k-mooney gilfoyle: yes i think the api layer injects the nova az before it gets to the client
11:13:33 gilfoyle is it a case of if a compute node has been added without specifying an AZ, the reporting then returns it as being `nova`? that's how I've handled it in the past
11:15:54 sean-k-mooney gilfoyle: yes and that is still how its handeled today
11:16:35 gilfoyle or, let me restart, if the compute node has not been added to an AZ, it ends up in 'nova'? I've seen occasions where the aggregates.name came up as NULL, so I used the following shortcut in mysql `IFNULL(aggregates.name, 'nova') as zone`
11:16:43 gilfoyle s/restart/restate
11:17:43 sean-k-mooney gilfoyle: ah no if you have added a host to a host aggregate and you have set the availablity_zone metadata key on the aggregate it should not show up in nova anymore
11:18:23 gilfoyle ah, that explains my conundrum then, however, I now have a different question/ask
11:18:37 gilfoyle what's the case where aggregates.name is NULL?
11:19:16 gilfoyle if this isn't an obvious one, then I'll go back to the drawing board and try to analyse it further :)
11:19:49 sean-k-mooney gilfoyle: i belive we allow you to have host aggregate where you only set the uuid
11:20:14 sean-k-mooney i cant rember of the top of my head why however
11:22:32 gilfoyle ah, cool :)
11:24:14 sean-k-mooney gilfoyle: the name filed on the aggregate is not the availability_zone name by the way. its the host aggregate name just incase you taught they were the same
11:24:45 sean-k-mooney i mean i personally always set them the same but they dont have to be
11:25:57 gilfoyle sean-k-mooney: Oh. interesting, I've been using a query with a relationship between aggregates, aggregate_hosts, compute_nodes and services tables to try and get all nodes for all AZs
11:27:29 sean-k-mooney gilfoyle: an avlailblity zone isnet really a thing in nova. its just a host_aggregate with metadata key called availability_zone in it
11:29:17 sean-k-mooney so to get all host in an az you just find the host_aggregate with the correct metadata key then list its host.
11:29:28 sean-k-mooney the nova and internal az are special however
11:30:51 gilfoyle could you possibly eyeball this and see if you can spot any obvious assumption(s) https://paste.ubuntu.com/p/sDFRDffzpy/ ?
11:31:02 sean-k-mooney i think the nova az is calulated by taking gennerating a list of host that are not part of another az
11:34:31 gilfoyle that seems to make sense to me, so I assume it does that as a separate step/query in the `nova` cli? would you have any idea where this defined in the source?
11:34:50 sean-k-mooney gilfoyle: i think services.topic = 'compute' can be changed in the nova conf. so that might be more fragile then looking at the service.binary
11:35:30 sean-k-mooney gilfoyle: but that should list the capsity of all compute nodes ordered by the az they are in
11:36:25 gilfoyle yes, that's the goal, but for a cluster w/o any zones, I don't see the only compute node with it. Probably because it needs to be a separate query as you suggested above :)

Earlier   Later