Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-01-10
14:52:49 dansmith eglynn: but *that* is something we could tweak in a point release for newton,
14:52:56 dansmith and if it's not gone from ocata, it needs to be,
14:53:08 dansmith so when you rolled those computes you'd be good once they're upgraded, regardless of the ordering
14:53:16 bauzas I mean https://github.com/openstack/nova/blob/180e6340a595ec047c59365465f36fed7a669ec3/nova/scheduler/client/report.py#L40-L67
14:53:37 dansmith bauzas: yeah, we have to pull most of that out for ocata anyway
14:53:40 dansmith ocata nodes *should* keep obsessing
14:53:53 bauzas dansmith: but newton computes would still stop reporting ?
14:53:58 bauzas dansmith: I mean
14:54:11 bauzas dansmith: if we say we would run the placement service before upgrading
14:54:19 bauzas and then the computes would self-heal
14:54:34 eglynn dansmith: yeah, if we could get rid of the try-once on a point release for newton, and quantify the warm-up time / downtime to populate placement data, then we could have a path forward here
14:54:35 bauzas dansmith: that wouldn't work for newton computes because of that decorator, right?
14:55:07 openstackgerrit Gábor Antal proposed openstack/nova: Transform instance.volume_detach notification https://review.openstack.org/408676
14:55:08 eglynn bauzas: IIUC dansmith was suggesting that the try-once logic is removed in a point release of newton
14:55:10 bauzas oh, if we remove that in a point release, then there is a path indeed
14:55:14 eglynn yep
14:55:44 bauzas but that would mean you couldn't upgrade from 14.0.0 straight to 15.0.1
14:55:46 bauzas oops
14:55:49 dansmith I really have to go now
14:55:50 bauzas to 15.0.0 rather
14:55:57 cdent thanks dansmith
14:56:06 bauzas you'd have to apply the point release before upgrading to Ocata
14:56:20 bauzas that's a reasonable trade-off but that requires documenting
14:56:31 bauzas dansmith: go off, we can discuss that later
14:57:42 cdent bauzas: is that only need to apply the point release prior to upgrading if you were concerned about limiting any downtime for launching new instances as much as possible? Or always ned to apply the point release?
14:58:40 bauzas cdent: if you wanna do rolling upgrade of your computes, I guess the point release upgrade is a necessary prereq
14:59:54 bauzas cdent: because if you don't apply the point release, then once you upgrade your scheduler, it won't prevent you to pick any newton node
15:00:38 cdent "won't" or "will"?
15:00:49 bauzas oh oops will
15:01:05 cdent yeah, what I'm asking is: for some people, presumably that's not a problem
15:01:16 cdent new instances would only go on upgraded nodes
15:01:27 cdent existing instances would stay wherever they happened to be
15:01:41 bauzas not only new instances
15:01:42 cdent for a small number of seconds zero nodes would available
15:01:56 bauzas if you migrate, then good luck
15:02:18 cdent good luck why?
15:02:44 bauzas the number of seconds where you have zero nodes is the duration you take for upgrading your first compute to ocata
15:32:57 markus_z lyarwood_: That's probably closed, isn't it? https://bugs.launchpad.net/openstack-gate/+bug/1646127
15:32:57 openstack Launchpad bug 1646127 in OpenStack-Gate "gate-grenade-dsvm-neutron-multinode-live-migration-nv failing on stable/newton due to devstack not supporting xenial during Mitaka" [Undecided,In progress] - Assigned to Lee Yarwood (lyarwood)
15:33:39 lyarwood_ markus_z: hey, yeah that should be closed now
15:34:29 markus_z Cool. I simply stumbled over it while looking for another thing.
15:51:44 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP] Fix failures in gate-nova-tox-db-functional-py35 https://review.openstack.org/418383
15:53:00 openstackgerrit Davanum Srinivas (dims) proposed openstack/nova: [WIP] ignore me - trying with an empty tests-functional-py3.txt https://review.openstack.org/418453
16:02:57 markus_z You worked on bug 1649586 and I was wondering what's necessary to fix that. I'm asking because https://review.openstack.org/#/c/347471/ would benefit from a vote by grenade.
16:02:57 openstack bug 1649586 in OpenStack Compute (nova) ""HTTP exception thrown: Cannot 'os-migrateLive' instance while it is in task_state migrating" in gate-grenade-dsvm-neutron-multinode-live-migration-nv" [Medium,In progress] https://launchpad.net/bugs/1649586 - Assigned to Pawel Koniszewski (pawel-koniszewski)
16:03:04 markus_z pkoniszewski: ^
16:04:07 markus_z pkoniszewski: I debugged it for some hours but I'm still clueless
16:04:31 pkoniszewski markus_z: one change is merged already https://review.openstack.org/#/c/412922/
16:04:44 pkoniszewski markus_z: but this one is also required https://review.openstack.org/#/c/413595/
16:05:43 markus_z pkoniszewski: I see, that one isn't mentioned in the bug report.
16:05:44 pkoniszewski you can run your change on top of #413595
16:06:30 markus_z pkoniszewski: I'll check the review and ask around in #openstack-qa if we can merge that quickly.
16:06:40 pkoniszewski thanks a lot
16:06:50 markus_z nah, thanks to you, you solved it :)
16:13:10 openstackgerrit Alex Szarka proposed openstack/nova: Transform instance-exists notification https://review.openstack.org/403660
16:14:59 openstackgerrit Alex Szarka proposed openstack/nova: Transform instance-exists notification https://review.openstack.org/403660
16:36:41 openstackgerrit Julian proposed openstack/nova: Removed duplicated _UNUSED enum in InstancePowerState Validation of the JSON schema fails when the enum has a duplicate https://review.openstack.org/418479
16:57:49 openstackgerrit Christopher Martin proposed openstack/nova: Stop using mox in test_compute_cells.py https://review.openstack.org/389750
16:59:15 openstackgerrit Balazs Gibizer proposed openstack/nova: Refactor InstancePayload creation https://review.openstack.org/418488
16:59:15 openstackgerrit Balazs Gibizer proposed openstack/nova: Remove **kwargs passing in payload __init__ https://review.openstack.org/418489
17:31:36 openstackgerrit Rafael Folco proposed openstack/nova: DELETE all inventory for a resource provider https://review.openstack.org/416669
17:39:16 openstackgerrit Chris Dent proposed openstack/nova: [WIP] Structure for simply managing placement-api-ref https://review.openstack.org/409340
17:39:17 openstackgerrit Chris Dent proposed openstack/nova: [placement] add api-ref for GET /resource_providers https://review.openstack.org/418503
18:24:57 openstackgerrit Ian Wells proposed openstack/nova-specs: Add the information Nova requires for a port to the port itself https://review.openstack.org/390513
18:26:22 openstackgerrit Ian Wells proposed openstack/nova-specs: VIF plugging negotiation between Nova and Neutron https://review.openstack.org/390512
18:29:37 openstackgerrit Gábor Antal proposed openstack/nova: Transform instance.volume_attach notification https://review.openstack.org/401992
18:30:58 openstackgerrit John Garbutt proposed openstack/nova: Pass objects into _validate_requested_network_ids https://review.openstack.org/418027
18:30:58 openstackgerrit John Garbutt proposed openstack/nova: Populate network data in _validate_requested_network_ids https://review.openstack.org/418511
18:30:59 openstackgerrit John Garbutt proposed openstack/nova: Pass objects into _create_ports_for_instance https://review.openstack.org/418512
18:30:59 openstackgerrit John Garbutt proposed openstack/nova: Pass objects into _update_ports_for_instance https://review.openstack.org/418513
18:49:02 openstackgerrit OpenStack Proposal Bot proposed openstack/nova: Updated from global requirements https://review.openstack.org/415978
18:50:35 openstackgerrit Gábor Antal proposed openstack/nova: Transform instance.volume_attach notification https://review.openstack.org/401992
19:14:15 satyar_ h
19:35:35 openstackgerrit Sujitha proposed openstack/nova: Adding tags field to InstancePayload https://review.openstack.org/407228
19:56:48 mguz anyone know if it's possible to tell nova to select a specific server in an ironic baremetal pool to boot?
20:18:15 cmartin Hey I am having issues with a test. The test is failing but the expected and actual calls are identical (ran the results through a diff checker) I am not really sure what to do.
20:20:35 diana_clarke cmartin: which test? can you pastebin the failure output?
20:21:26 openstackgerrit OpenStack Proposal Bot proposed openstack/nova: Updated from global requirements https://review.openstack.org/415978
20:23:12 cmartin diana_clarke: Unfortunately pastebin is blocked at work. Here is the patchset I am working on https://review.openstack.org/#/c/389750/ and it is this test '_test_delete_instance_no_cell' Here is a diff checker link for the results as well https://www.diffchecker.com/6PUmtzTm
20:26:14 diana_clarke cmartin: oh, I've seen this before. If I recall correctly, it was because I wasn't using the keyword format in the call exactly the way the actual call is constructed.
20:28:19 cmartin diana_clarke: sorry but I'm not sure how I would fix that?
20:28:39 diana_clarke cmartin: on sec, I think I know.
20:28:56 diana_clarke oops, I mean "one second"
20:29:24 cmartin diana_clarke: haha no problem
20:33:13 diana_clarke cmartin: Sadly, my hunch was wrong. The actually and expected callers are both using positional arguments, so it's not the same thing I saw recently.
20:33:56 diana_clarke (but I've recently been frustrated by something similar. I only fixed it by throwing away the code & starting again b/c my brain couldn't see the diff)
20:33:59 cmartin diana_clarke: dang it, thanks for trying though. I'm at a loss because it makes no sense lol
20:47:26 openstackgerrit Rafael Folco proposed openstack/nova: DELETE all inventory for a resource provider https://review.openstack.org/416669
20:54:42 openstackgerrit Eric Fried proposed openstack/nova: Introduce base PowerVM driver https://review.openstack.org/391288
21:00:01 openstackgerrit Dan Smith proposed openstack/nova: WIP: Test cellsv1 https://review.openstack.org/418141
21:04:22 diana_clarke cmartin: if you change the bdms parameter to mock.ANY, it gets past that error where actual looks like expected.
21:05:24 diana_clarke cmartin: I'm not entirely sure why... but note that the code you're replacing also did something special there: "mox.IsA(objects.BlockDeviceMappingList)"
21:06:10 diana_clarke cmartin: Anyhoo, I'm not necessarily saying that you should go with mock.ANY, but it's probably a clue.
21:06:42 cmartin diana_clarke: yea it gives me some direction, mox/mock testing can get super confusing sometimes lol
21:09:33 alaski equality testing doesn't necessarily work on nova objects, so even if the BlockDeviceMappingList looks the same to you python can't determine that
21:10:02 alaski that's why it was testing the type of the parameter before
21:12:41 cmartin alaski: I see, that's good to know in the future. Also setting bdms to mock.ANY worked I just fixed a few other lines and the tests pass now. Thanks for the help and explanations
21:15:45 openstackgerrit Christopher Martin proposed openstack/nova: Stop using mox in test_compute_cells.py https://review.openstack.org/389750
21:37:53 Neon`` i upgraded openstack to newton release and now when ever i boot instance it stuck at group like "inconsistent file system structure" with cirros and with windows blue screen or recovery. In centos same in grub screen. Is something changed in newton release ?
21:50:47 openstackgerrit Dan Smith proposed openstack/nova: Make placement client keep trying to connect https://review.openstack.org/418590

Earlier   Later