| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-06-25 | |||
| 06:07:27 | cf__ | The thing is, the person that started a bunch of instances did it with config_drive enabled which is kinda destroying the idea of a flexible environment, by making it extremely hard to live migrate running instances | |
| 06:08:48 | cf__ | Yeah, that's what i'm trying to find, however as pasted above, it dosnt show.. This is a test instance I made with delete_on_termination true, but I wanted to check if I was able to see it anywhere because for my production instances, i cannot risk to lose my volumes when i'm forced to delete the running instances and create new ones with the existing volumes in order to get rid of config_drive | |
| 06:10:04 | cf__ | for a random production instance i get: | |
| 06:10:04 | cf__ | stack@j3499-cp1-c1-m1-mgmt:~$ nova show f0c664e6-f161-41ac-93bd-cc2500644583 |grep volume | |
| 06:10:05 | cf__ | | image | Attempt to boot from volume - no image supplied | | |
| 06:10:05 | cf__ | | os-extended-volumes:volumes_attached | [{"id": "d86ea1ef-1b31-435d-8d3c-f106b61501ec"}, {"id": "d6fc7a5b-2cc0-4764-9a47-8cc89a609e0f"}, {"id": "9ff316b7-ff6d-4f63-a3fe-97dde0ba8803"}] | | |
| 06:11:08 | cf__ | ofcause this one, I do not know if delete_on_termination was set uppon creation - however it is on the first one I pasted, which was made only to check if I was able to find the info about delete_on_termination | |
| 06:12:01 | brinzhang__ | cf__: I think you can check it in block_device_mapping table, is that the delete_on_termination was set? | |
| 06:12:35 | cf__ | brinzhang__: so check the database? or is there a way to check it from cli? | |
| 06:13:14 | brinzhang__ | Because there is no scene for you, you can’t be sure that the problem exists. | |
| 06:13:45 | cf__ | Yeah, i just want to make sure not to lose data when I delete the running instances :) | |
| 06:15:40 | brinzhang__ | Currently, the delete_on_termination can only set when the server boot, there are two specs want to support config and reconfig that change, but not start working ... | |
| 06:16:39 | cf__ | It make sense.. maybe I should just create some backup before testing this :P | |
| 06:17:46 | brinzhang__ | Thanks, you can try test this, and report a but on launchpad https://bugs.launchpad.net/nova | |
| 06:18:16 | brinzhang__ | If ensure that issue exist :P | |
| 06:19:01 | cf__ | Will do, thanks :) | |
| 06:19:44 | cf__ | Oh btw, it's worth mentioning that this is a rather old instance of openstack since we're currently running Newton, but I guess that shouldnt do much of a difference | |
| 06:24:49 | brinzhang__ | Oh.. good luck. | |
| 06:33:14 | openstackgerrit | Yongli He proposed openstack/nova master: Clean up orphan instances virt driver https://review.opendev.org/648912 | |
| 06:33:15 | openstackgerrit | Yongli He proposed openstack/nova master: clean up orphan instances https://review.opendev.org/627765 | |
| 06:54:27 | cf__ | brinzhang__: I found it! Turns out that the easiest way was to check it in the nova database... | |
| 06:54:40 | cf__ | mysql> select delete_on_termination from block_device_mapping where instance_uuid = '83fcdb58-045a-4475-b4eb-5b9287daebcc'; | |
| 06:54:40 | cf__ | | delete_on_termination | | |
| 06:54:40 | cf__ | +-----------------------+ | |
| 06:54:40 | cf__ | | 1 | | |
| 06:54:41 | cf__ | +-----------------------+ | |
| 07:01:20 | brinzhang__ | cf__:So, next, you should to check that 'nova show' why not return this attribute, is there some error? Or some useful log? | |
| 07:02:51 | brinzhang__ | I am sorry, I am not have the newton environment to support more help :P | |
| 07:59:32 | openstackgerrit | zhaixiaojun proposed openstack/python-novaclient master: Modify the url of upper_constraints_file https://review.opendev.org/665934 | |
| 09:02:15 | openstackgerrit | Rui Zang proposed openstack/nova-specs master: support virtual persistent memory https://review.opendev.org/601596 | |
| 09:06:13 | openstackgerrit | Arnaud Morin proposed openstack/nova master: Do not refresh deleted instance info cache https://review.opendev.org/667294 | |
| 09:53:13 | openstackgerrit | huichen proposed openstack/nova master: Support pagination for sever groups by sql https://review.opendev.org/667259 | |
| 10:00:39 | openstackgerrit | huichen proposed openstack/nova master: Support pagination for sever groups by sql https://review.opendev.org/667259 | |
| 10:06:57 | openstackgerrit | Boxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server https://review.opendev.org/645520 | |
| 10:34:26 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-status: Remove consoleauth workaround check https://review.opendev.org/652968 | |
| 10:34:26 | openstackgerrit | Stephen Finucane proposed openstack/nova master: Remove nova-consoleauth https://review.opendev.org/652969 | |
| 10:34:27 | openstackgerrit | Stephen Finucane proposed openstack/nova master: objects: Remove ConsoleAuthToken.to_dict https://review.opendev.org/652970 | |
| 10:34:27 | openstackgerrit | Stephen Finucane proposed openstack/nova master: docs: Rework nova console diagram https://review.opendev.org/660147 | |
| 10:34:28 | openstackgerrit | Stephen Finucane proposed openstack/nova master: docs: Integrate 'sphinx.ext.imgconverter' https://review.opendev.org/665693 | |
| 11:24:52 | openstackgerrit | Balazs Gibizer proposed openstack/nova stable/stein: Remove redundant group host setup https://review.opendev.org/667334 | |
| 11:50:43 | openstackgerrit | Arnaud Morin proposed openstack/nova stable/stein: Always Set dhcp_server in network_info https://review.opendev.org/667340 | |
| 12:04:41 | openstackgerrit | Lee Yarwood proposed openstack/nova master: libvirt: flatten rbd images when unshelving an instance https://review.opendev.org/457886 | |
| 12:05:10 | lyarwood | mdbooth / dansmith ; ^ rebased and touched up slightly, should be ready for review again. | |
| 12:07:58 | mdbooth | lyarwood: Hehe, I managed to avoid the external_events conflict with my patch by out-waiting it :) | |
| 12:08:50 | mdbooth | Ah, you didn't conflict with it. Lucky. | |
| 12:16:21 | mdbooth | artom|gmtplus3 sean-k-mooney: Do you expect your fixed hybrid vif plugged patch to land soon? | |
| 12:17:16 | sean-k-mooney | am i hope so but that depend on stealing review time from peole to land it | |
| 12:19:25 | sean-k-mooney | it looks like artom has some concerns | |
| 12:20:05 | sean-k-mooney | so maybe not right away | |
| 12:20:17 | sean-k-mooney | mdbooth: are you asking for you patch that is in merge conflict | |
| 12:20:56 | mdbooth | sean-k-mooney: Well it was in merge conflict while the patch was landed, but is now no longer conflicting but I need to rebase anyway because it seems gerrit can't tell that. | |
| 12:21:26 | sean-k-mooney | ah well you might as well rebase | |
| 12:21:58 | mdbooth | sean-k-mooney: https://youtu.be/N0BkjvUOtX4?t=29 | |
| 12:22:06 | sean-k-mooney | have you got any review on it lately | |
| 12:22:29 | mdbooth | sean-k-mooney: Yeah, a bit. | |
| 12:23:44 | sean-k-mooney | hum i havent seen fifth element in a while | |
| 12:24:19 | mdbooth | Me neither, but I love that film. Your comment just reminded me of the 'I have a doubt' scene :) | |
| 12:46:15 | openstackgerrit | Stephen Finucane proposed openstack/nova stable/stein: Ignore hw_vif_type for direct, direct-physical vNIC types https://review.opendev.org/667354 | |
| 12:46:50 | openstackgerrit | Stephen Finucane proposed openstack/nova stable/rocky: Ignore hw_vif_type for direct, direct-physical vNIC types https://review.opendev.org/667355 | |
| 12:47:39 | stephenfin | lyarwood: Could you take a look at those two ^ Clean backports, both of them | |
| 12:49:36 | lyarwood | stephenfin: ack sure | |
| 12:57:08 | artom|gmtplus3 | mdbooth, if I'm right it's not as simple as we thought | |
| 12:57:27 | artom|gmtplus3 | I'll let sean-k-mooney respond | |
| 13:03:26 | sean-k-mooney | artom|gmtplus3: well i dont know why we would recive plug time event for same host resize of hybrid plug | |
| 13:03:39 | sean-k-mooney | the vif is already plugged and the binding host does not change | |
| 13:03:45 | artom|gmtplus3 | sean-k-mooney, I don't either, but it looks like we do | |
| 13:06:08 | sean-k-mooney | for what its worth the patch i have up passed the same host reszie test in tempest | |
| 13:06:31 | mriedem | mgoddard: johnthetubaguy: i have a few questions in https://bugs.launchpad.net/nova/+bug/1833542 for what you want to see | |
| 13:06:32 | sean-k-mooney | it was tested by the neutron iptables hybird job | |
| 13:06:32 | openstack | Launchpad bug 1833542 in OpenStack Compute (nova) "No mechanism to wait for computes to update service version before restarting to remove RPC version cap after upgrade" [Wishlist,Triaged] | |
| 13:06:50 | mgoddard | mriedem: fire away | |
| 13:06:53 | sean-k-mooney | i have not had time to go through your comment properly and read the logs however | |
| 13:08:13 | artom|gmtplus3 | sean-k-mooney, it would, because I think it just don't wait for any events in case of same host resize | |
| 13:08:51 | sean-k-mooney | right it wont be considerd a plug time event so we wont wait | |
| 13:09:07 | sean-k-mooney | we would wait for plug time events | |
| 13:09:44 | mriedem | mgoddard: they are in the bug report, answer when you have time | |
| 13:09:55 | mriedem | mgoddard: mostly asking about what interface you need | |
| 13:10:00 | artom|gmtplus3 | sean-k-mooney, in fact, I don't think tests would pick it up at all - even migrate revert guest connectivity tests would succeed eventually, assuming everything went well | |
| 13:10:32 | artom|gmtplus3 | There'd just be a few seconds (dozens of seconds?) between instance boot and network connectivity being established | |
| 13:11:25 | mgoddard | mriedem: ah, got it. Have to head out soon but will respond | |
| 13:12:31 | mriedem | mgoddard: feel free to post to the ML for other ops to weigh in if they need something like this | |
| 13:16:45 | bauzas | mriedem: efried: I'm working on https://bugs.launchpad.net/nova/+bug/1793569 | |
| 13:16:47 | openstack | Launchpad bug 1793569 in OpenStack Compute (nova) "Add placement audit commands" [Wishlist,Confirmed] - Assigned to Sylvain Bauza (sylvain-bauza) | |
| 13:17:30 | bauzas | mriedem: efried: should we use the reportclient or just calling the placement API directly? | |
| 13:17:51 | efried | bauzas: looking... | |
| 13:17:53 | mriedem | i'm pretty sure the other nova-manage placement commands use the reportclient | |
| 13:17:58 | bauzas | they do, yet | |
| 13:18:02 | bauzas | yes* | |
| 13:18:08 | mriedem | so yeah just use that | |
| 13:18:12 | bauzas | ok | |
| 13:18:28 | efried | bauzas: agree | |
| 13:19:08 | bauzas | I was about to do this, but I wonder whether the placement folks would prefer to just use other clients | |
| 13:19:57 | efried | bauzas: All nova code should go through SchedulerReportClient to talk to Placement. | |
| 13:20:16 | efried | SchedulerReportClient should really be called PlacementClient or similar | |
| 13:20:16 | bauzas | k | |
| 13:20:46 | mriedem | right...nova doesn't have any other placement client | |
| 13:20:51 | mriedem | nor is there a python-placementclient | |
| 13:20:57 | mriedem | only the sdk | |
| 13:21:28 | mriedem | keep in mind that if this is something you think your customers on older branches might want, you're best to not introduce a bunch of new dependencies here | |
| 13:21:51 | mriedem | unrelated, doesn't suse and red hat have docs writers that could verify the install guide issue mentioned here https://bugs.launchpad.net/nova/+bug/1833650 ? | |