-opendevstatus- NOTICE: all new logins to https://review.opendev.org are currently failing. investigation is ongoing, please be patient | 08:53 | |
jrosser | good morning | 09:00 |
---|---|---|
noonedeadpunk | \o/ | 09:01 |
jrosser | noonedeadpunk: i found some things with openstack_resources | 09:14 |
jrosser | mostly small stuff but the image upload running every time is a bit of a pain | 09:15 |
jrosser | we have a similar role here, and we allow the downloaded images to persist on the ansible control node so they don't need to be downloaded each time | 09:16 |
noonedeadpunk | yeah, I've read your comment. Eventually we upload only local images (since we build them with DIB), so this path I just added from top of my head | 09:23 |
noonedeadpunk | and that's quite fair comment | 09:23 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_ironic master: Fix a typo in pxe_redfish definition https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/906353 | 09:28 |
jrosser | noonedeadpunk: you can check / upload / properties as seperate steps https://paste.opendev.org/show/bK6J7pAzt0BSJlS2Wlpk/ | 09:39 |
jrosser | ^ also handles making .raw from .qcow2 which you want for glance/cinder on RBD | 09:40 |
jrosser | in our use we have mostly upstream images for debian/ubuntu/centos/... uploaded straight to glance | 09:41 |
jrosser | but also use DIB for ironic images | 09:42 |
noonedeadpunk | ++ that's very fair suggestions | 09:42 |
jrosser | theres another task file next to that one which boots a VM with terraform and runs DIB in it | 09:42 |
jrosser | that code could be improved a bit as currently there is completely different code path depending on if image.convert_to is defined | 09:46 |
jrosser | but the tasks are basically the same | 09:46 |
gokhan | hello folks, do you recommend update and upgrade OS packages before minor and major upgrades? | 09:51 |
jrosser | gokhan: it maybe depends what you want to achieve | 10:05 |
jrosser | opesntack-ansible manages the isntallation of certain packages, and the upgrade process ensures that they are 'latest' when required, otherwise the state is set to 'present' so unexpected changes are not made | 10:06 |
jrosser | but as an example that does not keep you up to date / security patched with more general packages | 10:07 |
noonedeadpunk | just don't try to update packages when runnning against computes/net nodes, as upgrade of OVS with restart of neutron-openvswitch-agents leads to interesting race conditions | 10:09 |
noonedeadpunk | these should be done separately | 10:09 |
noonedeadpunk | or at least ovs itself | 10:09 |
gokhan | jrosser, we are trying to upgrade from victoria to antelope. so I am trying to make everything up to date but I also want to be sure it doesn't break our environment. | 10:11 |
jrosser | gokhan: let the playbooks do the updates for you | 10:13 |
jrosser | like noonedeadpunk says you make make everything very broken if you just randomly "update everything" without orchestrating those upgrades somehow | 10:13 |
gokhan | I will not update packages manually, it is the best option to let the playbooks do the updates, thanks jrosser | 10:13 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-ops master: Use only unique backends to iterate over https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906356 | 10:14 |
noonedeadpunk | gokhan: that's not actually what I said :D | 10:14 |
gokhan | also thanks noonedeadpunk :) | 10:14 |
noonedeadpunk | In fact, I'd say that upgrading packages separately from playbook might be not worth idea | 10:14 |
noonedeadpunk | *worst | 10:15 |
noonedeadpunk | at least it will avoid potential race conditions when separate services are being restarted (ones from package update and others by running handlers) | 10:16 |
noonedeadpunk | But the only weak place we found was OVS | 10:16 |
noonedeadpunk | And difference of running -e package_state=latest is dramatic in terms of environment stability | 10:16 |
jrosser | well keepalived can be fun too | 10:17 |
noonedeadpunk | Like when we've upgraded OVS manually prior to running os-neutron-install it was matter of couple of pings being lost. When we used -e package_state=latest - was almost 30min outage | 10:17 |
noonedeadpunk | Not everywhere, on some computes only, but still. | 10:18 |
gokhan | if I get correctly, you mean you can update packages except OVS (you need to update ovs seperately) before running playbooks. | 10:26 |
gokhan | noonedeadpunk ^^ | 10:27 |
jrosser | updating a package is not necessarily the same as the running software using the new stuff you just installed | 10:27 |
noonedeadpunk | this ^ | 10:30 |
jrosser | running the playbooks will update your packages where necessary, and restart services where necessary | 10:30 |
noonedeadpunk | but also - don't try to update packages while running os-neutron-install | 10:30 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-ops master: Allow to gracefully drain backends when disabled https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906358 | 10:37 |
gokhan | thank noonedeadpunk jrosser I got it :) | 10:39 |
hamburgler | Hmm, these new haproxy healthchecks just leave a bunch of non specific information as to what they are in the lxc https://paste.openstack.org/show/bF1rlzaAjkrAFM8jE2jt/ - is this intended? previously we were able to see what it was | 10:59 |
noonedeadpunk | hamburgler: there were couple of regressions covered in 28.0.1 jsut in case | 11:02 |
noonedeadpunk | like one was issuing l4 checks rather then l7 | 11:02 |
hamburgler | kk :) will check those out | 11:03 |
noonedeadpunk | and then also not using /healthcheck url | 11:03 |
hamburgler | excellent - sorry totally missed 28.0.1 | 11:03 |
noonedeadpunk | like https://opendev.org/openstack/openstack-ansible-haproxy_server/commit/baf11a22fbf66ccd1cc95d60c3ea0c60a051decb https://opendev.org/openstack/openstack-ansible/commit/8bcd9198ff00363363fa3335e25c9fb6ece41847 https://opendev.org/openstack/openstack-ansible/commit/6bb4c0f70f7343e8dda1cbdcc36c5442bc562b99 | 11:04 |
noonedeadpunk | these 3 that can lead to what you see | 11:04 |
hamburgler | ah yes :) | 11:04 |
hamburgler | wonderful ty! | 11:05 |
noonedeadpunk | specififcally I think it's one to haproxy_server | 11:05 |
noonedeadpunk | np | 11:05 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: [doc] Reffer need of haproxy backend configuration in upgrade guide https://review.opendev.org/c/openstack/openstack-ansible/+/906360 | 11:28 |
noonedeadpunk | andrewbonney: this is smth we talked back in the days about OS upgrades - seemed to work for us, but would be great if you could confirm that ^ | 11:28 |
andrewbonney | Thanks I'll take a look. Was intending to update that when we upgrade to Jammy but you've beaten me to it :) | 11:29 |
jrosser | i do wonder if we should add vrrp_track_file as a default | 11:29 |
jrosser | so that you have a persistent way on the filesystem to ensure that a node does not take the VIP | 11:30 |
noonedeadpunk | Yeah, thats also an option | 11:32 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add role to install and run sonobouy k8s validation tests https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906054 | 11:35 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add playbook to run functional test of magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906361 | 11:37 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: WIP - Add collection to deploy magnum cluster-api with vexxhost driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/901450 | 12:14 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: WIP - Bootstrapping playbook https://review.opendev.org/c/openstack/openstack-ansible-ops/+/902178 | 12:14 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add role to install and run sonobouy k8s validation tests https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906054 | 12:14 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add playbook to run functional test of magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906361 | 12:14 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add hook playbook install and test magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906363 | 12:14 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Add job to test Vexxhost cluster API driver https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 13:09 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Add job to test Vexxhost cluster API driver https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 13:16 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: DNM: Add volume type management https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/906372 | 13:17 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: DNM: Add volume type management https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/906372 | 13:21 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Add openstack_resources role skeleton https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/878794 | 13:42 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Add job to test Vexxhost cluster API driver https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 13:57 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-plugins master: Add openstack_resources role skeleton https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/878794 | 14:00 |
noonedeadpunk | ugh, regarding images part, I barely have time to work on that right now :( | 14:04 |
noonedeadpunk | potentially - just drop tempdir step? | 14:06 |
noonedeadpunk | or fetch list of images twice I guess -before and after upload | 14:07 |
noonedeadpunk | Will try to get some time for that till end of the week.... | 14:08 |
jrosser | we can always improve it | 14:09 |
noonedeadpunk | #startmeeting openstack_ansible_meeting | 15:00 |
opendevmeet | Meeting started Tue Jan 23 15:00:16 2024 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:00 |
noonedeadpunk | #topic rollcall | 15:00 |
noonedeadpunk | o/ | 15:00 |
jrosser | o/ hello | 15:00 |
NeilHanlon | o/ hiya folks | 15:02 |
mgariepy | hey | 15:02 |
noonedeadpunk | #topic office hours | 15:05 |
noonedeadpunk | Soooooo | 15:05 |
noonedeadpunk | This week I had a peek into cinder_backends stuff https://opendev.org/openstack/openstack-ansible-os_cinder/src/branch/master/tasks/cinder_backends.yml | 15:05 |
noonedeadpunk | and realized that there's no way to actually skip this thing | 15:06 |
noonedeadpunk | And there're couple of smallish issues like if you want to set public: False - this will appear in cinder.conf as well | 15:06 |
noonedeadpunk | based on what mess it is, I thought that it's worth extending openstack_resources, since some modules appeared there to cover volume types, but these modules are jsut borked.... | 15:07 |
noonedeadpunk | they're not idempotent, require weird input, etc | 15:08 |
noonedeadpunk | But now not sure if we should keep messing with what we have or try to fix modules... | 15:08 |
jrosser | even this comment is wrong https://opendev.org/openstack/openstack-ansible-os_cinder/src/branch/master/tasks/cinder_backends.yml#L28 | 15:09 |
noonedeadpunk | As at very least, I guess we should include the task conditionally based on the variable | 15:09 |
jrosser | there could be a pretty huge cleanup of that code without changing how it works | 15:10 |
noonedeadpunk | huh... it's not wrong... | 15:10 |
noonedeadpunk | As looks like we still deploying openrc to cinder_backends.... | 15:11 |
noonedeadpunk | or well, cinder_api | 15:11 |
jrosser | there is already delegation, and there is no need to run the openrc role i think | 15:11 |
noonedeadpunk | What I don't like very much, is how it's tighten to backends defenition | 15:11 |
noonedeadpunk | So I was kinda thinking of introducing the new variable, and then do some kind of default wiring to it | 15:12 |
noonedeadpunk | which basically lead me to variable structure and opensatck_resources role.... | 15:12 |
noonedeadpunk | until I realized it's a dead end as modules just don't work :( | 15:13 |
jrosser | i guess the 'right thing' to do is to fix the ansible modules :/ | 15:13 |
noonedeadpunk | but well | 15:13 |
jrosser | but that is likley work++ | 15:13 |
noonedeadpunk | potentially we can use "same" structure | 15:13 |
noonedeadpunk | What I'm afraid most, is when it will land | 15:14 |
noonedeadpunk | so we can use it | 15:14 |
jrosser | right | 15:14 |
jrosser | ultimately the modules follow pretty closely the CLI | 15:14 |
jrosser | so perhaps we can make a new datastructure that serves either, as temporary measure | 15:14 |
noonedeadpunk | volume_type jsut failed on me with `Volume Type lvm already exists.` when I ran it second time | 15:15 |
noonedeadpunk | yeah, true | 15:15 |
noonedeadpunk | How are things with capi integration? | 15:15 |
jrosser | so i think i would look at cleaning up what we have there in the ansible code as it is a huge mess | 15:15 |
jrosser | like all the path stuff is bogus, cli is in /usr/local/bin | 15:16 |
jrosser | insecure is dealt with in openrc anyway | 15:17 |
jrosser | and `environment: { OS_CLOUD: default }` is sufficient to get command or shell module to pick up and use the right bits of openrc | 15:18 |
noonedeadpunk | I was ectually thinking of providing --os-cloud default rather then sourcing openrc | 15:18 |
noonedeadpunk | or that, yes | 15:18 |
noonedeadpunk | to not repeat myself for each command, yes | 15:18 |
jrosser | i think thats what i mean about cleanup | 15:19 |
noonedeadpunk | yeah ,fair, I will look into cleanup of all that then | 15:19 |
jrosser | we could put all that in a block: and delete tons of nonsense | 15:19 |
noonedeadpunk | Was hoping a bit just to drop all that instead :D | 15:19 |
NeilHanlon | :P | 15:19 |
jrosser | ok so on capi integration | 15:20 |
jrosser | i have some pretty interesting patches | 15:20 |
jrosser | this one first https://review.opendev.org/c/openstack/openstack-ansible/+/906255 | 15:21 |
noonedeadpunk | what I'm not sure about - if it's safe to drop `public` here https://opendev.org/openstack/openstack-ansible-os_cinder/src/branch/master/templates/cinder.conf.j2#L107 | 15:21 |
jrosser | general purpose extension hook points to add new playbooks | 15:21 |
noonedeadpunk | I do like this one | 15:22 |
jrosser | this looks pretty cool as you can put in user variables `pre_setup_hosts_hook: my.collection.playbook` | 15:22 |
jrosser | and i did wonder if we want to add similar hook points to all the things in openstack-ansible/playbooks | 15:23 |
jrosser | but i make this patch first as an example | 15:23 |
noonedeadpunk | I guess it depends on how much sense to add this everywhere | 15:24 |
jrosser | then second thing is i have got a structure for a CI job that includes setup from an external collection | 15:24 |
jrosser | https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199/17/zuul.d/playbooks/bootstrap-mcapi-vexxhost.yml | 15:24 |
noonedeadpunk | As kinda service playbooks are small enough usually, so it would be close to same? | 15:24 |
noonedeadpunk | and we don't have much in pre-post tasks... | 15:24 |
jrosser | well it depends if you want to drop something in after services, but before tempest for example | 15:25 |
noonedeadpunk | but dunno. Can't think of good usecase for having same in service playbooks yet | 15:25 |
jrosser | but maybe we wait for an actual need for that | 15:25 |
noonedeadpunk | eventually.... | 15:25 |
noonedeadpunk | there was some old patch of mine, that was jsut separating tempest/rally to their own thing | 15:25 |
noonedeadpunk | or smth like that | 15:25 |
jrosser | i've got a was to have a `bootstrap-aio` playbook in an external collection that gets called in the pre job zuul playbook | 15:26 |
jrosser | *a way | 15:26 |
noonedeadpunk | like https://review.opendev.org/c/openstack/openstack-ansible/+/840685 | 15:26 |
jrosser | this keeps some things for /etc/openstack_deploy/... in the collection and drops them there before the main aio is boostrapped | 15:26 |
jrosser | currently this is a bit ugly, as there is a native way for zuul to understand that some of your repos contain roles, and to call them from your pre playbook | 15:27 |
jrosser | you would do this with `job.roles` and then use the roles as you need them | 15:27 |
jrosser | unfortunately we cannot do the same with a collection, so there is a hacky call to the playbook path on the disk instead currently | 15:28 |
jrosser | ideally i would make a `osa_ops.mcapi_vexxhost.boostrap_aio` role that we could call directly from the pre playbook | 15:28 |
noonedeadpunk | and for that bootstrap-ansible should already be done | 15:29 |
jrosser | no, this is before | 15:29 |
noonedeadpunk | um, ok. but what will execute pre-playbook then? | 15:30 |
jrosser | in the case of a CI job, zuul | 15:30 |
noonedeadpunk | like, given this pre-playbook is a hook to setup-everything (or smth like that) | 15:30 |
noonedeadpunk | (if that's was an idea) | 15:30 |
jrosser | this is separate to the hooks thing | 15:30 |
noonedeadpunk | aha, ok. | 15:31 |
noonedeadpunk | (though it could be related :D) | 15:31 |
jrosser | the hooks allow you to use an external collection to deploy whatever, like cluster_api or ELK | 15:31 |
noonedeadpunk | like provision extra stuff for openstack_deploy..... | 15:31 |
noonedeadpunk | anyway | 15:31 |
noonedeadpunk | yeah, probably you can't do that | 15:31 |
jrosser | but you need to get in *before* bootstrap-ansible to be able to use things like `user-ansible-venv-requirements.yml` | 15:32 |
noonedeadpunk | as you'd need to reload inventory | 15:32 |
noonedeadpunk | yeah, true | 15:32 |
noonedeadpunk | fair | 15:32 |
jrosser | so anyway, i think there is a route forward here for things like capi and ELK | 15:32 |
noonedeadpunk | that sounds really nice | 15:32 |
jrosser | which will be much more maintainable than what we have right now in the ops repo | 15:32 |
noonedeadpunk | yeah, that looks really nice | 15:35 |
jrosser | i have everything pretty much done to deploy magnum + out of tree capi driver, and then run sonobuoy sanity check against a deployed cluster | 15:35 |
jrosser | this works nicely locally in 8 core 32G vm | 15:35 |
jrosser | this job pulls the whole lot together https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 15:37 |
jrosser | and i am seeing now if there is any chance for it to run in 3h | 15:37 |
noonedeadpunk | fingers corssed | 15:37 |
jrosser | we can trim out heat | 15:37 |
noonedeadpunk | maybe worth disabling tempest somehow | 15:38 |
jrosser | but currently no way to do that as the auto-scenario stuff pulls it in with magnum | 15:38 |
jrosser | maybe we need a NO_SCENARIO as well :) | 15:38 |
jrosser | yes tempest is pretty spurious for this | 15:38 |
noonedeadpunk | lol | 15:38 |
noonedeadpunk | I don't have bright ideas on how to drop heat from there | 15:45 |
noonedeadpunk | rather then define all jobs from magnum independently | 15:45 |
jrosser | `tempest_install: false` looks like it will just drop tempest entirely | 15:46 |
jrosser | yeah i will think about that | 15:46 |
noonedeadpunk | yeah, tempest should be easier to drop. | 15:47 |
noonedeadpunk | ofc depending on where we keep it currently | 15:47 |
noonedeadpunk | https://opendev.org/openstack/openstack-ansible/src/branch/master/tests/roles/bootstrap-host/templates/user_variables.aio.yml.j2#L268-L270 | 15:48 |
noonedeadpunk | It's not _that_ easy | 15:48 |
jrosser | user_variables_zzzz.yml will win :) | 15:48 |
noonedeadpunk | or well, matter of condition {% if 'capi' not in bootstrap_host_scenarios %} | 15:49 |
jrosser | i was trying not to mess with the openstack-ansible repo at all | 15:49 |
jrosser | becasue i'd like to make this all general enough that it will also be suitable for ELK or whatever else | 15:49 |
jrosser | so avoiding special casing things would be good | 15:49 |
noonedeadpunk | yeah. true | 15:50 |
jrosser | hah and of course just now tempest did fail on my capi job | 15:50 |
noonedeadpunk | heh, yeah | 15:51 |
noonedeadpunk | it's doomed to fail more or less | 15:51 |
noonedeadpunk | or well. I think it's failing now jsut for regular magnum I assume | 15:51 |
jrosser | right, because tempest runs in an unconfigured magum with no driver installed | 15:51 |
jrosser | the templates and images and everything are missing at that point | 15:52 |
noonedeadpunk | ouch | 15:54 |
noonedeadpunk | ok, well, it's expected I guess though | 15:54 |
jrosser | indeed, i'll just disable it | 15:55 |
noonedeadpunk | or this all is still need for capi driver? | 15:55 |
noonedeadpunk | like cluster templates? | 15:55 |
jrosser | yes, you still need it all | 15:55 |
jrosser | but there is chicken/egg | 15:55 |
jrosser | the control plane cluster_api k8s needs to be deployed before you make the templates | 15:56 |
noonedeadpunk | aha, gotcha | 15:56 |
noonedeadpunk | And I guess here where my debt comes to introduce a playbook for creating openstack_resources | 15:56 |
jrosser | so os_magnum runs and installs the out-of-tree driver | 15:56 |
noonedeadpunk | as that can be added as post-openstack hook to create resources | 15:56 |
noonedeadpunk | or smth | 15:56 |
jrosser | then along somes the ops repo collection and puts in the rest in the post_hook | 15:57 |
jrosser | i already used openstack_resources :) https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906361/2/mcapi_vexxhost/playbooks/functional_test.yml | 15:57 |
*** jonher_ is now known as jonher | 16:06 | |
*** jonher_ is now known as jonher | 16:08 | |
noonedeadpunk | #endmeeting | 16:09 |
opendevmeet | Meeting ended Tue Jan 23 16:09:06 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:09 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-01-23-15.00.html | 16:09 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-01-23-15.00.txt | 16:09 |
opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-01-23-15.00.log.html | 16:09 |
noonedeadpunk | yeah, structure of the role kinda common to writing task itself I guess.... | 16:10 |
noonedeadpunk | in terms that it's huge | 16:10 |
noonedeadpunk | *structure of vars for the role | 16:10 |
jrosser | I like it | 16:12 |
jrosser | the code/tasks stay small and obvious | 16:12 |
jrosser | and everything else is data | 16:12 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: WIP - Bootstrapping playbook https://review.opendev.org/c/openstack/openstack-ansible-ops/+/902178 | 16:22 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add role to install and run sonobouy k8s validation tests https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906054 | 16:22 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add playbook to run functional test of magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906361 | 16:22 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add hook playbook install and test magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906363 | 16:22 |
noonedeadpunk | seems rocky is unhappy with `nothing provides openssl-libs(x86-64) = 1:3.0.7-24.el9 needed by openssl-devel-1:3.0.7-24.el9.x86_64 from appstream` | 16:25 |
noonedeadpunk | https://zuul.opendev.org/t/openstack/build/093dbc671bcb4f9da034bf72aa8ed9a6 | 16:25 |
noonedeadpunk | more then 2 jobs failed with that | 16:25 |
jrosser | is that familiar thing | 16:27 |
jrosser | perhaps it was ovs or something last time | 16:27 |
noonedeadpunk | nah, dunno. sounds like repo being desynced.... | 16:31 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible master: Add SCENARIO_EXCLUDE environment variable to limit expansion of SCENARIO https://review.opendev.org/c/openstack/openstack-ansible/+/906388 | 16:53 |
jrosser | noonedeadpunk: you can probably think of things this breaks :/ not sure im liking messing with the parameters of gate-check-commit script | 16:54 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-os_magnum master: Add job to test Vexxhost cluster API driver https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/905199 | 19:26 |
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily for a restart, in order to attempt to restore OpenID login functionality | 19:35 | |
-opendevstatus- NOTICE: OpenID logins for the Gerrit WebUI on review.opendev.org should be working normally again since the recent service restart | 20:02 | |
hamburgler | Hey all :) was wondering if it was possible to get python-openstackclient bumped to 6.4.0 over 6.3.0 for bobcat - https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/default-security-group-rule.html | 22:42 |
jrosser | hamburgler: unfortunately that is not something openstack-ansible has direct control over https://github.com/openstack/requirements/blob/stable/2023.2/upper-constraints.txt#L479 | 22:46 |
hamburgler | oh shoot :D | 22:46 |
hamburgler | okay no worries :) | 22:46 |
jrosser | however, there are enough hooks / places to override that you would be able to manipulate upper-constraints in your deployment | 22:47 |
jrosser | totally untested though :) | 22:47 |
hamburgler | :) - honestly don't even really need it for the utility container, just more of a nice to have, will just install on our deployment container and add any custom rules to default security group | 22:48 |
jrosser | yeah the risk is that all the playbooks use ansible modules that use python-openstackclient as defined in u-c | 22:49 |
jrosser | so if you change that in the utility container there might be side effects | 22:50 |
hamburgler | definitely, will leave it for now :) | 22:51 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: WIP - Bootstrapping playbook https://review.opendev.org/c/openstack/openstack-ansible-ops/+/902178 | 22:57 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add role to install and run sonobouy k8s validation tests https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906054 | 22:57 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add playbook to run functional test of magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906361 | 22:58 |
opendevreview | Jonathan Rosser proposed openstack/openstack-ansible-ops master: Add hook playbook install and test magnum capi driver https://review.opendev.org/c/openstack/openstack-ansible-ops/+/906363 | 22:58 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!