| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-11-09 | |||
| 12:48:08 | sean-k-mooney | ya | |
| 12:48:24 | sean-k-mooney | so bauzas gibi correct me if im wrong be we have had customer do that right^ | |
| 12:48:57 | sean-k-mooney | use the updated contaienr with this command ot repair old dbs when connection infor is out of date | |
| 12:49:34 | sean-k-mooney | admin1: i think we have a downstream backport of this by the way to some release which is why im not 100% sure how we used this downstream with train | |
| 12:51:45 | sean-k-mooney | admin1: ya so we have it backported downstream to train in our 16.2 product | |
| 12:52:15 | sean-k-mooney | and i think we have had custoemr use the 16.2 contaienr to fix this on queens/osp 13 | |
| 12:52:19 | admin1 | i am on osa tag 23.1.2 | |
| 12:53:25 | admin1 | wallaby | |
| 12:54:00 | sean-k-mooney | we cannot backport db/object/rpc change even downstream so the fact it works on train implies this is very self contaiend meanign you should be able to use it with wallaby | |
| 12:54:47 | admin1 | : invalid choice: 'volume_attachment' on this | |
| 12:54:56 | admin1 | i have to boot a new container, point to the existing one and try from there | |
| 12:55:21 | sean-k-mooney | yep | |
| 13:46:02 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: Adds a repoducer for post live migration fail https://review.opendev.org/c/openstack/nova/+/863806 | |
| 13:46:03 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/864055 | |
| 13:55:54 | dvo-plv | Hello, everyone, Could tou please review our comments on the next blueprint: https://review.opendev.org/c/openstack/nova-specs/+/859290 | |
| 14:19:50 | admin1 | sean-k-mooney,is this a libvirt-secrets-gone thing or a ceph thing ? https://gist.githubusercontent.com/a1git/67cc7dab45f9bff536296670ab6ce65d/raw/450a2e31125e01826a90b1f133bc9b4821f807e8/gistfile1.txt | |
| 14:20:15 | admin1 | my mons were deleted completely .. i recreated those from osds | |
| 14:20:25 | admin1 | and cinder client was added with the same keys | |
| 14:20:33 | admin1 | most vms started, a few come with this error | |
| 14:22:46 | sean-k-mooney | did the mon ips change | |
| 14:23:18 | sean-k-mooney | presumable the secret is the same | |
| 14:23:50 | sean-k-mooney | but ya it could be that either the secret is msisign or the user aut info changed | |
| 14:23:59 | sean-k-mooney | the sechre has the ceph keyring inside | |
| 14:24:33 | sean-k-mooney | i dont have a ceph deployment to check but i belive that is tied a a spcific pool/user uuid | |
| 14:24:55 | sean-k-mooney | im not really shoudl how you recover on teh cecph side form all mons going away | |
| 14:25:24 | sean-k-mooney | but if any of the uuid chaged then you might need to get new keyrings and update the secret | |
| 14:26:03 | sean-k-mooney | changing the mon ips is not supproted in an openstack env since it requried bd surgery to fix | |
| 14:26:07 | admin1 | the mons were gone totally, but the ips did not change | |
| 14:26:13 | admin1 | all 3 mons are back in qorum | |
| 14:26:21 | admin1 | ceph is healthy and most of the vms started OK | |
| 14:26:29 | sean-k-mooney | ok the ips are cluster uuid and secrete are teh main things | |
| 14:26:30 | admin1 | there are 2 i know of that show this behaviour | |
| 14:26:32 | admin1 | there is no lock | |
| 14:27:00 | sean-k-mooney | so if the ips are the same no need to update the nova db unless the cluster id changed | |
| 14:27:15 | admin1 | cluster name /fsid all is same | |
| 14:27:23 | sean-k-mooney | ya fsid was what i ment | |
| 14:27:29 | admin1 | fsid is the same | |
| 14:27:52 | sean-k-mooney | so if that the same then provide the keyring in the secret is still valid you are porably ok | |
| 14:28:18 | sean-k-mooney | have you tried using that to list the volumes on the pool | |
| 14:32:03 | admin1 | got it | |
| 15:50:26 | clarkb | melwitt: thanks. It does look like bfv is tested, but it does also appear that the image used for rescuing is modified to set its bus and device types? I wonder if that is what we are missing here. The rescue command itself doesn't appear to take those arguments so these would need to be specified before hand on a special image? I guess that lends more weight to having | |
| 15:50:28 | clarkb | dedicated images as a required part of the rescue process? | |
| 16:07:41 | melwitt | clarkb: can be image properties or expressed as extra specs in the flavor. I can test out a change that would add a flavor create setting bus and device types in the test | |
| 16:09:02 | clarkb | melwitt: either way it is something that the cloud or cloud user would need to be aware of. Currently the default rescue behavior is to reuse the same image the rescued node booted off of. This is problematic because of the label specifier collisions, but also because if the image itself is broken you'd still be broken in a rescue. That leads users to using another image, but | |
| 16:09:04 | clarkb | there isn't any clear indication to me as a user that I need to use a special image. | |
| 16:10:15 | opendevreview | Dan Smith proposed openstack/nova master: Test ceph-multistore with a real image https://review.opendev.org/c/openstack/nova/+/860864 | |
| 16:11:05 | clarkb | I suspect the solution here is to make it clear to cloud operators that rescue has requirements x y z (I don't know what they all are yet) and that they should provide an image that meets those requirements | |
| 16:11:57 | melwitt | clarkb: hm yeah you are probably right it's only image properties, this section doesn't mention using a flavor to do it https://docs.openstack.org/nova/latest/user/rescue.html#stable-device-instance-rescue | |
| 16:12:42 | clarkb | also I wonder if nova should drop the default behavior or reusing the running image and instead force people to explicitly provide one | |
| 16:13:07 | clarkb | I suspect there are scenarios where reusing the image would work, but in the vast majority it seems unlikely | |
| 16:13:24 | clarkb | and that would help provide signal that something different is required here | |
| 16:16:46 | melwitt | I think we could do that in a new API microversion to avoid breaking anyone who is using it the old way and succeeding ... but the fact that openstackclient defaults to lowest microversion makes it more difficult to signal imho | |
| 16:18:27 | clarkb | ya and I think users could manually specify the same image if they really did need/want that | |
| 16:18:38 | clarkb | it just wouldn't be provided as a dfeault (which I think users expect to work) | |
| 16:19:27 | melwitt | yeah, I think that makes sense | |
| 17:19:55 | opendevreview | Merged openstack/nova stable/yoga: [compute] always set instance.host in post_livemigration https://review.opendev.org/c/openstack/nova/+/861872 | |
| 17:31:39 | opendevreview | Amit Uniyal proposed openstack/nova stable/ussuri: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/862603 | |
| 17:31:40 | opendevreview | Amit Uniyal proposed openstack/nova stable/ussuri: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/862604 | |
| 18:45:28 | opendevreview | melanie witt proposed openstack/nova-specs master: Re-propose spec for ephemeral storage encryption https://review.opendev.org/c/openstack/nova-specs/+/864138 | |
| 19:29:37 | darkhorse | Hi team | |
| 19:29:40 | darkhorse | class NovaSession(): | |
| 19:29:40 | darkhorse | def __init__(self): | |
| 19:29:40 | darkhorse | self.auth = v3.Password(KEYSTONE_URL, username=OPENSTACK_ADMIN, password=OPENSTACK_ADMIN_PASS, project_name=ADMIN_PROJECT, user_domain_id=DOMAIN_ID, | |
| 19:29:40 | darkhorse | project_domain_id=PROJECT_DOMAIN_ID) | |
| 19:29:40 | darkhorse | self.sess = session.Session(self.auth) | |
| 19:29:42 | darkhorse | self.nova2 = nova_client.Client(2, session=self.sess) | |
| 19:31:16 | darkhorse | I use this code to create nova session. I want to use internal IP address since my app runs on controller. I set KEYSTONE_URL to internal keystone endpoint address but the client still send requests to nova public ip address. | |
| 19:31:39 | darkhorse | Is there a setting that I can tell the client to use internal address? | |
| 19:34:12 | opendevreview | Dan Smith proposed openstack/nova master: Test ceph-multistore with a real image https://review.opendev.org/c/openstack/nova/+/860864 | |
| 19:57:05 | melwitt | darkhorse: you might try the 'interface' kwarg to Client (interface=$the_name_of_your_internal_endpoint_in_the_service_catalog) which will get passed to the keystone adapter https://docs.openstack.org/keystoneauth/latest/api/keystoneauth1.adapter.html | |
| 19:58:52 | melwitt | there's also endpoint_override to provide the full url but the interface discovery is nicer I think if it works | |
| 20:02:10 | darkhorse | melwitt: thank you i ended up using nova_client.Client(2, session=self.sess, endpoint_type='internal') | |
| 20:02:22 | darkhorse | interface kwarg seems to be deprecated. | |
| 20:03:50 | melwitt | darkhorse: ok cool. it's the other way around I think, endpoint_type is an old name now used as an alias | |
| 20:04:41 | darkhorse | ok thank you. | |
| 22:30:18 | opendevreview | melanie witt proposed openstack/nova-specs master: Re-propose spec for ephemeral encryption for libvirt https://review.opendev.org/c/openstack/nova-specs/+/864147 | |
| 23:44:44 | opendevreview | melanie witt proposed openstack/nova-specs master: Re-propose per process healthchecks https://review.opendev.org/c/openstack/nova-specs/+/864150 | |
| #openstack-nova - 2022-11-10 | |||
| 01:52:34 | opendevreview | Nobuhiro MIKI proposed openstack/nova master: libvirt: add maxphysaddr support https://review.opendev.org/c/openstack/nova/+/864091 | |
| 04:28:37 | opendevreview | melanie witt proposed openstack/nova master: DNM test ephemeral encryption + resize: qcow2, raw https://review.opendev.org/c/openstack/nova/+/862416 | |
| 04:33:24 | opendevreview | melanie witt proposed openstack/nova master: DNM test ephemeral encryption + resize: qcow2, raw https://review.opendev.org/c/openstack/nova/+/862416 | |
| 07:05:13 | opendevreview | melanie witt proposed openstack/nova master: DNM test ephemeral encryption + resize: qcow2, raw https://review.opendev.org/c/openstack/nova/+/862416 | |
| 08:22:41 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/864168 | |
| 08:22:42 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/864169 | |
| 08:53:50 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/864168 | |
| 08:53:51 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/864169 | |
| 10:22:57 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/864168 | |
| 10:22:58 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/864169 | |
| 10:53:00 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/864168 | |
| 10:53:01 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/864169 | |
| 11:36:49 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: add regression test case for bug 1978983 https://review.opendev.org/c/openstack/nova/+/864168 | |
| 11:36:50 | opendevreview | Amit Uniyal proposed openstack/nova stable/train: For evacuation, ignore if task_state is not None https://review.opendev.org/c/openstack/nova/+/864169 | |
| 13:59:34 | fungi | bauzas: when you have time, can you recommend some updates for https://launchpad.net/~nova-coresec/+members and the nova entry at https://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management ? i get the distinct impression those are extremely stale | |
| 14:01:03 | sean-k-mooney | yes, dan is still about and john says hi form time to time but it would likely be better to 1 include the current ptl and 2 conisder if others on the core team should be there | |
| 14:01:30 | fungi | that's what i was thinking as well | |
| 14:03:07 | fungi | certainly if bauzas wants to be included in nova-coresec then i can set him as an administrator for it and he can make any further adjustments he likes | |
| 14:04:31 | sean-k-mooney | what i was kind of thinking is adding this to the ptl guide to do a reveiw each release and make adding the next ptl be part fo the hand over process | |
| 14:05:07 | opendevreview | ribaudr proposed openstack/nova-specs master: Re-propose "Allow Manila shares to be directly attached to an instance when using libvirt" https://review.opendev.org/c/openstack/nova-specs/+/864206 | |
| 14:05:31 | sean-k-mooney | i dont think i have access to check the audit log for that group but i do suspect its been updated in a while | |
| 14:08:59 | opendevreview | ribaudr proposed openstack/nova-specs master: Re-propose "Allow Manila shares to be directly attached to an instance when using libvirt" https://review.opendev.org/c/openstack/nova-specs/+/864206 | |
| 14:12:04 | fungi | sean-k-mooney: the only administrators in that group haven't been active in the projects for years, so i can guarantee it's not been updated for quite a long while | |