| *** dviroel|dr_appt is now known as dviroel | 01:16 | |
| *** dviroel is now known as dviroel|out | 01:31 | |
| *** ysandeep|out is now known as ysandeep | 02:39 | |
| opendevreview | Matthew Thode proposed openstack/openstack-ansible-ops master: gather facts for elk_metrics https://review.opendev.org/c/openstack/openstack-ansible-ops/+/859366 | 03:33 |
|---|---|---|
| *** ysandeep is now known as ysandeep|afk | 04:52 | |
| *** ysandeep|afk is now known as ysandeep | 05:35 | |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix cinder-volume AIO ceph scenario https://review.opendev.org/c/openstack/openstack-ansible/+/859263 | 07:36 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix cinder-volume AIO ceph scenario https://review.opendev.org/c/openstack/openstack-ansible/+/859263 | 08:01 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix cinder-volume AIO ceph scenario https://review.opendev.org/c/openstack/openstack-ansible/+/859263 | 08:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix cinder-volume AIO ceph scenario https://review.opendev.org/c/openstack/openstack-ansible/+/859263 | 08:52 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Extend NFS scenario to support cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859336 | 09:01 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Run test_minimum_basic_scenario test for cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859339 | 09:01 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Run test_minimum_basic_scenario test for cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859339 | 09:01 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix cinder-volume AIO ceph scenario https://review.opendev.org/c/openstack/openstack-ansible/+/859263 | 09:03 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Extend NFS scenario to support cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859336 | 09:03 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Extend NFS scenario to support cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859336 | 09:03 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Run test_minimum_basic_scenario test for cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859339 | 09:03 |
| *** dviroel|out is now known as dviroel | 11:19 | |
| ThiagoCMC | Hi folks, I'm still trying to figure out how Ironic works in OSA after a few days... I finally have the `ironic-inspector` running and container have an interface on `br-bmaas`, however, when I try to PXE, `dnsmasq-dhcp` returns "no address range available for DHCP request via eth15", any idea? | 11:51 |
| ThiagoCMC | I can see in 'inspector-dnsmasq.conf' file that its "dhcp-range" is "192.168.0.51,192.168.0.150", which isn't configured anywhere within /etc/openstack_deploy, where it comes from? | 11:52 |
| ThiagoCMC | I see that those values are hard-codeed in `os_ironic/defaults/main.yml', is it supposed to be like this? I thought that it would enable PXE on top of 'br-bmaas' network... | 11:55 |
| *** ysandeep is now known as ysandeep|afk | 11:59 | |
| noonedeadpunk | NeilHanlon: hey! I was wondering - were anybody from Rocky fixing python discovery for ansible? As I guess it was done, but I realized that discovered_interpreter_python is not set even in latest ansible-core | 12:01 |
| ThiagoCMC | Does OSA forces (hard-code) br-bmaas subnet to be 192.168.0.0/22 ? | 12:08 |
| ThiagoCMC | I also still don't know what's that "ironic_neutron_cleaning_network_name" lol =P | 12:10 |
| ThiagoCMC | I think it's werid to define this "cleaning" network in openstack_deploy, but this network won't exists unless we manually create it later on after everything is installed. | 12:11 |
| noonedeadpunk | sorry I can't answer any of this :( | 12:12 |
| ThiagoCMC | Ok, no problem! But you approved the Ironic commit LOL | 12:13 |
| ThiagoCMC | :-D | 12:13 |
| ThiagoCMC | Kidding... ^_^ | 12:13 |
| *** ysandeep|afk is now known as ysandeep|mtg | 12:33 | |
| jamesdenton | ThiagoCMC I can help here, but not at this moment. My suggestion right now is to avoid deploying inspector, as it's a bit of a mess in OSA | 12:41 |
| jamesdenton | Unless you can support multi-tenant ironic, you'll likely be faced with leveraging a single "flat" neutron network that used for provisioning (PXE), cleaning (PXE), and general network use. So, you'll want to create that network/subnet in Neutron using whatever CIDR is appropriate, then specify the name using these two vars: ironic_neutron_provisioning_network_name and ironic_neutron_cleaning_network_name. | 12:43 |
| jamesdenton | the Ironic API endpoint will need to be reachable via that neutron network. I do not use a br-bmaas bridge; instead, my provisioning network is routed like a normal neutron provider network and can hit the API via some external router/firewall | 12:45 |
| jamesdenton | There's a lot of options here, and I'm actually in the middle of documenting my environment w/ a diagram and overrides to share, just haven't circled back to it yet | 12:45 |
| ThiagoCMC | Awesome, thanks for your help! But without Inspector, where do you run the DHCP + all stuff for the PXE? | 12:49 |
| ThiagoCMC | I'm looking forward for more documentation about this! | 12:49 |
| ThiagoCMC | It's very simple to deploy MaaS, but super hard to deploy Ironic, I'll help fill the gap with examples! | 12:49 |
| jamesdenton | so, Inspector can be used in two ways: the first is sort of a legacy way that leverages it's own DHCP server (ie. not Neutron-managed) and the second uses an ironic inspection network, similiar to the cleaning and provisioning (it can be the same, too) | 12:58 |
| jamesdenton | depending on how you trigger the inspection determines which method is used. i imagine the former is a more 'standalone friendly' version than the latter | 12:58 |
| jamesdenton | since the latter relies on neutron, and the former doesn't | 12:59 |
| jamesdenton | yes, MAAS is a much simpler deployment, but once you have ironic deployed and understand the workflow it's a pretty cool setup. OSA is just weak on the docs, unfortunately. Will try to make some progress there as time allows | 13:00 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Extend NFS scenario to support cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859336 | 13:02 |
| *** ysandeep|mtg is now known as ysandeep | 13:24 | |
| ThiagoCMC | jamesdenton, thanks! Well, I'm working in a PoC, really interested in deploying Ironic, the simplest it can be now, then more elaborated next year if required. Yeah, lack of docs are a bit frustrating... =P | 13:26 |
| ThiagoCMC | I'll remove Ironic Inspector containers from this deploying and see how it behaves... | 13:27 |
| ThiagoCMC | *deployment | 13:27 |
| NeilHanlon | noonedeadpunk: I thought we fixed that with https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/bootstrap-ansible.sh#L74 | 13:35 |
| noonedeadpunk | NeilHanlon: ah. I thought it was fixed in ansible as well... As we do fail when start running ceph-ansible https://bugs.launchpad.net/openstack-ansible/+bug/1989367 | 13:43 |
| ThiagoCMC | jamesdenton, I'm still curious... Where do you run your DHCP/tftp/images/PXE stuff for Ironic (the first legacy example you mentioned)? | 13:45 |
| ThiagoCMC | I think I initially misunderstood, Inspector is needed but simpler in legacy mode (still, on this case, where the DHCP/PXE sits?)... Getting there lol | 13:46 |
| *** ysandeep is now known as ysandeep|out | 14:01 | |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Run test_minimum_basic_scenario test for cinder https://review.opendev.org/c/openstack/openstack-ansible/+/859339 | 14:25 |
| NeilHanlon | noonedeadpunk: what branch of ceph-ansible do we instlal? | 14:33 |
| noonedeadpunk | it's same on main even, but tried stable-6.0 and stable-7.0 | 14:34 |
| noonedeadpunk | but it's indeed matter of failing here https://github.com/ceph/ceph-ansible/blob/d7bf53a576465f0f25409b116ec8ca1d797ad0b7/roles/ceph-facts/tasks/facts.yml#L170 | 14:35 |
| admin1 | i would also implement ironic if the docs/playbooks are a bit more easy to follow :D | 14:42 |
| NeilHanlon | i guess i need some more coffee to understand what is happening. if I just install ansible on a rocky 8.6 node it properly detects python 3.8 via ansible_python['executable'] variable, but it seems it expects the ansible_python_interpreter explicitly set? | 14:44 |
| ThiagoCMC | admin1, right?! :-D | 14:47 |
| admin1 | (y) | 14:49 |
| admin1 | i was also exploring https://tinkerbell.org/ | 14:50 |
| ThiagoCMC | I was JUST going to replace MaaS with Tinkerbell! | 14:51 |
| ThiagoCMC | But I changed focus to Ironic for now. | 14:51 |
| admin1 | your undying love for MaaS is gone now :D ? | 14:52 |
| ThiagoCMC | LOLOL | 14:52 |
| ThiagoCMC | I'm trying! | 14:52 |
| ThiagoCMC | :-D | 14:52 |
| jrosser_ | hello o/ | 14:59 |
| admin1 | \o | 14:59 |
| ThiagoCMC | Opa! | 14:59 |
| jrosser_ | we are doing osa + ironic + ironic-inspector + lxc here | 14:59 |
| jrosser_ | and it is truly a big mess in the OSA role | 15:00 |
| admin1 | :D | 15:00 |
| admin1 | \o/ | 15:00 |
| jrosser_ | i've pushed a bunch of stuff for ironic api in LXC already | 15:00 |
| ThiagoCMC | Oh no... lol | 15:00 |
| jrosser_ | theres a ton of fixes needed for inspector in LXC | 15:00 |
| jrosser_ | and then we will document in the ironic role how to do osa + ironic + LXC | 15:00 |
| jrosser_ | but this is going to take a little bit of time to get ready | 15:01 |
| ThiagoCMC | Do you have those changes in a public branch somewhere? | 15:01 |
| ThiagoCMC | I'd like to help testing! | 15:01 |
| jrosser_ | the patches i've pushed might be enough to do ironic + lxc without inspector | 15:01 |
| noonedeadpunk | #startmeeting openstack_ansible_meeting | 15:01 |
| opendevmeet | Meeting started Tue Sep 27 15:01:57 2022 UTC and is due to finish in 60 minutes. The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| opendevmeet | The meeting name has been set to 'openstack_ansible_meeting' | 15:01 |
| noonedeadpunk | #topic rollcall | 15:02 |
| jrosser_ | o/ hello | 15:02 |
| noonedeadpunk | \o/ | 15:02 |
| damiandabrowski | hi! | 15:02 |
| ThiagoCMC | jrosser_, you mean, without Inspector containers? | 15:02 |
| ThiagoCMC | i.e., no "ironic-inspector_hosts:" declared in openstack_deploy dir...? | 15:03 |
| noonedeadpunk | #topic office hours | 15:04 |
| noonedeadpunk | So, recently I've worked a bit on improving testing for cinder volumes. Eventually, we did not test if it was working or not in aio at all | 15:05 |
| noonedeadpunk | as we never run any tempest scenario that would use bfv or jsut attach volumes | 15:05 |
| noonedeadpunk | At the same time I'm not sure how we really want to run this as we still want to check ephemerals and reduce jobs timing | 15:06 |
| noonedeadpunk | (or at least not increasing it | 15:06 |
| noonedeadpunk | I pushed couple of patches here https://review.opendev.org/q/topic:osa%252Ftest_volumes | 15:07 |
| noonedeadpunk | Next thing I looked into is ansible 2.13. We're suuuper close now, but now a bit blocked by not having infra mirrors for moder ceph | 15:07 |
| jrosser_ | how is that connected? | 15:08 |
| noonedeadpunk | By now we were installing octopus and jrosser_'s patch for pacific was never merged. | 15:08 |
| noonedeadpunk | jrosser_: well, it's connected to ceph-ansible steable-7.0 that tries to install quincy by default | 15:08 |
| noonedeadpunk | *stable-7.0 | 15:08 |
| jrosser_ | oh i see - and we need 7.0 for the newer ansible to be ok? | 15:09 |
| damiandabrowski | btw. what issues we had with bfv? I assume there's a reason why you're so motivated to cover it with tempest now :D | 15:09 |
| noonedeadpunk | and stable-7.0 does install our config_template collection rather their own fork | 15:09 |
| noonedeadpunk | damiandabrowski: it was not working?:) Denys was trying to spin up aio_ceph and cinder-volume was not starting at all because of backend naming started with rbd | 15:10 |
| NeilHanlon | i'm looking into that ansible python / rocky / ceph thing as well as getting back to my integration for rocky 9. re-downloaded the VM and hoping to get it merged this week | 15:11 |
| jrosser_ | i'm sure we came across that backend naming thing a loooong time ago for rbd | 15:11 |
| damiandabrowski | ah ok | 15:11 |
| noonedeadpunk | oh yes we did. But we never fixed aio as it never bothered us (as we didn't test it) | 15:11 |
| jrosser_ | ahha of course | 15:12 |
| noonedeadpunk | so that was motivation :) | 15:12 |
| NeilHanlon | tests?! who needs tests | 15:12 |
| NeilHanlon | tests only cause problems :D | 15:12 |
| noonedeadpunk | NeilHanlon: well, as of now I've rejected our bug, as it can be quite simply worked around (and in fact it's not our bug). But in general ansible might be worth fixing... | 15:12 |
| NeilHanlon | agreed, just not sure "what" needs fixing just yet.. in any case that one I'm taking back to rocky | 15:13 |
| noonedeadpunk | NeilHanlon: another question to you (or your team) - maybe you're also itnerested in helping out MariaDB to build/have packages and repo for CentOS/Rocky... https://jira.mariadb.org/browse/MDEV-28842 | 15:14 |
| noonedeadpunk | As when I talked to monty - they said there's no interest from ppl to have that | 15:14 |
| NeilHanlon | totally. i will comment on that issue with support and offer to help :) | 15:14 |
| noonedeadpunk | I can help out with Rocky 9 if needed - I jsut downloaded images and was about to spawn VMs to see what's wrong. | 15:16 |
| NeilHanlon | iirc from zuul, ansible in the virtualenv was unable to find libselinux to disable it | 15:16 |
| jrosser_ | this is something that was changed in recent ansibles, how selinux is handled | 15:17 |
| noonedeadpunk | I wonder that maybe it does need libselinux binary to realize that it's not needed?:) | 15:17 |
| jrosser_ | specifically how the python<>.so interface is done | 15:17 |
| noonedeadpunk | yeah, they do use c bindings now | 15:18 |
| NeilHanlon | that lib should definitely be.. available, since the package is installed on the system | 15:18 |
| noonedeadpunk | jrosser_: there was issue regardign your patch that fixed keystone bootstrap when proxy was used. It's fixed now with https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/859232 but not sure if this doesn't break anything for you (and idp stuff). | 15:18 |
| jrosser_ | ah yes i saw that | 15:18 |
| noonedeadpunk | and Andrew was not around to ask to test out. | 15:19 |
| jrosser_ | i think andrew might be back next week | 15:19 |
| noonedeadpunk | But I _think_ it should be fine | 15:19 |
| jrosser_ | i could try that easily with an AIO on our internal instance, thats behind a proxy | 15:19 |
| noonedeadpunk | NeilHanlon: maybe it also goes back to ansibles' discovery that is failing | 15:20 |
| noonedeadpunk | (and python discovery that does not happen for $reason) | 15:20 |
| jrosser_ | theres been quite some discussion of ironic recently too - we're really not in great shape there and it would be good if we can make things more working out-of-the-box for Z | 15:21 |
| noonedeadpunk | but not sure - did not have chance to check out. Though I believe we do have couple of users by now that try or do use Rocky with OSA | 15:21 |
| * noonedeadpunk still haven't got to ironic deployment so quite clueless | 15:22 | |
| jrosser_ | well, ironic itself is hugely configurable and pluggable | 15:22 |
| jrosser_ | and the existing os_ironic has one particular view about how the deployment should be (single tenant, metal deploy, some others, ......) | 15:23 |
| jrosser_ | and none of those things are documented in the role and i think jamesdenton mentioned making some docs which should cover that | 15:23 |
| jrosser_ | stuartgr has done an LXC deployment here and there is really a lot that doesnt work | 15:24 |
| noonedeadpunk | that's sad to hear :( but indeed role before did not have enough love... | 15:24 |
| jrosser_ | good news is we have it kind of working now, but there are a bunch more patches needed | 15:25 |
| noonedeadpunk | also to reming about PTG doc - here's etherpad: | 15:25 |
| noonedeadpunk | #link https://etherpad.opendev.org/p/osa-antelope-ptg | 15:25 |
| jrosser_ | including for IPMI serial consoles working in horizon | 15:25 |
| jrosser_ | i would really like to get this in better shape for Z release if there is time | 15:26 |
| noonedeadpunk | I'd love to help - but can help only with reviews now. | 15:27 |
| noonedeadpunk | If look optimistically at ours internal backlog - I'm not sure if we get to it until Antelope... Likely yes, but not 100% | 15:28 |
| noonedeadpunk | What I'd really to get progress on - internal SSLs. As a lot was already done (read - concept) but I'm not sure where and why this has stuck. | 15:29 |
| jrosser_ | well it's kind of similar here - we can work on ironic patches as we are deploying it | 15:29 |
| jrosser_ | SSL has got stuck because it was really being driven by james gibson and sadly he has moved to another job now | 15:29 |
| jrosser_ | and i don't have any replacement | 15:29 |
| noonedeadpunk | I guess we can take it and move forward if it's the only reason | 15:30 |
| opendevreview | Kevin Carter proposed openstack/openstack-ansible master: feat: Add skyline deployment capability https://review.opendev.org/c/openstack/openstack-ansible/+/859446 | 15:30 |
| jrosser_ | there is not really any technical issue other than needed to have time to work on it | 15:30 |
| prometheanfire | elk logstash container too small at 8G? | 15:30 |
| noonedeadpunk | and we're quite happy with the concept? as we haven't landed even blueprint for $reason | 15:31 |
| jrosser_ | well it is complex | 15:33 |
| jrosser_ | the transition from backends being http -> https across and upgrade is pretty difficult | 15:33 |
| noonedeadpunk | yeah, migration is quite complex indeed | 15:33 |
| jrosser_ | and understanding is needed by whoever takes it on | 15:33 |
| jrosser_ | well the code makes the transition simple for an operator | 15:34 |
| cloudnull | o/ jrosser_ I PR'd your role for skyline into the openstack-ansible repo. any thoughts on seeing that role brought into the os namespace? | 15:34 |
| jrosser_ | but the mechanism is complex | 15:34 |
| jrosser_ | cloudnull: that would be fine - just lacking time from my POV | 15:34 |
| noonedeadpunk | cloudnull: the only issue I see is that skyline is not official project yet | 15:34 |
| noonedeadpunk | not sure if that should tighten us though | 15:34 |
| cloudnull | ¯\_(ツ)_/¯ | 15:35 |
| jrosser_ | not sure they have branches or releases yet really which we'd have to be careful about | 15:35 |
| noonedeadpunk | it's still "emerging" | 15:35 |
| jrosser_ | but the velocity seems high so having it at least as "experimental" would be great | 15:35 |
| cloudnull | works i n dev 😉 | 15:35 |
| jrosser_ | personally i am stuck with horizon because of federation | 15:35 |
| jrosser_ | and i did the role to bootstrap interest from others | 15:36 |
| cloudnull | my only complaint is that all the VMs need a volume, but besides that its really nice alt to horizon | 15:36 |
| jrosser_ | cloudnull: i think CI might be interesting, because the "yarn" (?) bits needed many Gb of ram | 15:37 |
| prometheanfire | heh, tested in chrome only it seems | 15:37 |
| noonedeadpunk | I'm kind of fine bringing i as experimental | 15:37 |
| cloudnull | All of the static files are shipped with the python bits so we dont have to build the Node things. | 15:37 |
| noonedeadpunk | but I;m not sure they're following u-c and requirements yet. | 15:38 |
| noonedeadpunk | but yeah, good as experimental | 15:38 |
| noonedeadpunk | should we gain some interest during ptg/operational hours or jsut agree to add it? | 15:39 |
| cloudnull | the current skyline role doesn't do any of the node building. it probably would be a good thing to add so that we can force a rebuild of static files if required? | 15:39 |
| cloudnull | I'm in no rush to see it merged, just was committing things I have running in my environments. | 15:39 |
| cloudnull | also trying to highlight jrosser_ excellent work on that role :D | 15:40 |
| jrosser_ | i think my first patches did have the node build stuff so it should be there in the history | 15:40 |
| jrosser_ | i converted the skyline "install from source" instructions pretty verbatim into ansible iirc | 15:40 |
| cloudnull | I'm going to take another pass at trying to make it work in apache | 15:41 |
| noonedeadpunk | I'd personally hate to mess up with npm... | 15:41 |
| cloudnull | at the moment its nginx or bust | 15:41 |
| jrosser_ | yeah, i didnt dive deep enough into making the equivalent reverse proxy setup | 15:41 |
| cloudnull | I sadly cant make it work in uwsgi 😢 | 15:41 |
| noonedeadpunk | I also wonder if we should make skyline mutualy exclusive with horizon | 15:41 |
| noonedeadpunk | or we should have some acls on haproxy | 15:42 |
| cloudnull | noonedeadpunk +1 probably a good idea. in that initial pr i used 8443 for ssl and 9999 for non-ssl (9999 is their default) | 15:42 |
| noonedeadpunk | btw we have couple of backports to stable branches - so if anybody have time for reviews - super welcome | 15:44 |
| jrosser_ | cloudnull: https://github.com/jrosser/openstack-ansible-os_skyline/commit/82b1f5a5e6eff9df441c96677e0aa6d578bc8552#diff-7ae20663f88c2ee2e49e28cecf7c0eeb99efdb53ec0faf27c0a50ce3dcaf2370 | 15:45 |
| jrosser_ | i expect this would benefit from doing all the npm-ness on the repo container | 15:45 |
| jrosser_ | only wants to be done once as it's super heavyweight | 15:45 |
| cloudnull | for sure! | 15:46 |
| NeilHanlon | noonedeadpunk: any idea on how to actually get into this DIB image? I tried injecting my ssh key but I get denied lol | 15:47 |
| cloudnull | I found I didn't need to actually run that when doing the deployment as all the generated node bits are part of the skyline-console repo. however, having the option to rebuild is probably a really good thing to have. | 15:47 |
| jrosser_ | ah interesting | 15:47 |
| cloudnull | yeah for my local builds I just pip installed my way to success. | 15:48 |
| jrosser_ | i wonder if that is deliberate, or just a .gitignore accident :) | 15:48 |
| cloudnull | however, who knows how that will shape up as they get closer to an actual relesae | 15:48 |
| cloudnull | yeah exactly my thoughts too | 15:48 |
| noonedeadpunk | NeilHanlon: I think it depends on set of elements you've used to build it. As under normal conditions some cloud-init element should be explicitly included | 15:49 |
| noonedeadpunk | we can also ask infra folks to create a hold for this patch/job and they can place a key to the VM spawned by zuul | 15:49 |
| jrosser_ | do you need config-drive? | 15:50 |
| jrosser_ | iirc there is glean instead of cloud-init? | 15:50 |
| noonedeadpunk | oh. pf. yes | 15:50 |
| noonedeadpunk | though I thought it's only for latest fedora... | 15:51 |
| noonedeadpunk | But maybe it's indeed since 34... | 15:51 |
| NeilHanlon | hrm yeah I see glean in the bootup logs | 15:51 |
| NeilHanlon | ... i think the documentation on config drives is just a loop | 15:54 |
| jrosser_ | should be `openstack server create --use-config-drive ....` | 15:56 |
| NeilHanlon | yeah was trying to launch in qemu but seems I'd need to make my own ISO with the right data.. probably easier to just do in openstack | 15:57 |
| noonedeadpunk | #endmeeting | 16:00 |
| opendevmeet | Meeting ended Tue Sep 27 16:00:26 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2022/openstack_ansible_meeting.2022-09-27-15.01.html | 16:00 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2022/openstack_ansible_meeting.2022-09-27-15.01.txt | 16:00 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/openstack_ansible_meeting/2022/openstack_ansible_meeting.2022-09-27-15.01.log.html | 16:00 |
| *** dviroel is now known as dviroel|lunch | 16:01 | |
| noonedeadpunk | Btw interestingly - centos 9 repeateadly fails tempest when cinder-volume is involved | 16:07 |
| noonedeadpunk | https://zuul.opendev.org/t/openstack/build/e5d25f84966c47dc8ad27b1befc33980 | 16:07 |
| *** dviroel|lunch is now known as dviroel | 18:21 | |
| opendevreview | Merged openstack/openstack-ansible-ops master: gather facts for elk_metrics https://review.opendev.org/c/openstack/openstack-ansible-ops/+/859366 | 19:43 |
| ignacio | Hi all! Moving a conversation from #openstack here: I'm facing an issue with `openstack-ansible setup-openstack.yml` on the version 25.1.0, as part of the "TASK [openstack.osa.db_setup : Create database for service]", "module_stderr": "/bin/sh: 1: /openstack/venvs/utility-25.1.0/bin/python: not found\n". | 20:29 |
| ignacio | jrosser_ suggested that could be caused by https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html. Any idea on how can I fix the issue? | 20:30 |
| jamesdenton | you might try adding "-e ansible_python_interpreter=/usr/bin/python" to see if that gets you over the hump | 20:32 |
| *** dviroel is now known as dviroel|afk | 20:43 | |
| opendevreview | Merged openstack/openstack-ansible-os_horizon master: Add uwsgi option to horizon https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/856393 | 21:04 |
| noonedeadpunk | ignacio: are you sure that setup-infrastructure has finished without failures? As I can assume that utility container is simpy not prepared | 21:06 |
| ignacio | noonedeadpunk: Yes, I'm sure the setup finished without any problem, I actually manually stopped and destroyed the utility container, to force its re-creation. Any suggestion on how to check if it's ready? | 21:07 |
| noonedeadpunk | so utility container is missing now? | 21:08 |
| ignacio | No, its present, it was recreated, I was able to attach to it and see that it was there (lxc-ls & lxc-attach) | 21:10 |
| noonedeadpunk | ignacio: ok, have you ran playbooks/utilityinstall.yml after it's being re-created? | 21:11 |
| noonedeadpunk | or setup-infrastructure? | 21:11 |
| noonedeadpunk | * playbooks/utility-install.yml | 21:11 |
| opendevreview | Merged openstack/openstack-ansible-haproxy_server master: Allow haproxy to bind on the interface https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/852039 | 21:11 |
| ignacio | I executed `openstack-ansible setup-infrastructure.yml` | 21:11 |
| noonedeadpunk | ok. So when you do lxc-attach do you have any virtualenv in /openstack/venvs/ ? | 21:12 |
| ignacio | No, I don't event have the /openstack directory in the utility container, Should I run the playbooks/utility-install? | 21:13 |
| opendevreview | Merged openstack/openstack-ansible-os_ceilometer master: Fix wrong pathname in pre install task https://review.opendev.org/c/openstack/openstack-ansible-os_ceilometer/+/858915 | 21:14 |
| ignacio | I just executed the `openstack-ansible utility-install.yml` and the directory /openstack/venvs was created, will wait for it to finish to execute the setup command again. | 21:18 |
| noonedeadpunk | it's really weird, as if setup-infrastructure has finished without errors - it would include utility-install | 21:24 |
| ignacio | Agree, not sure what happened, it was a little frustrating at the beginning because the error was hidden. I had to modify the `/etc/ansible/ansible_collections/openstack/osa/roles/db_setup/tasks/main.yml` and set no_log=false to actually see the explicit error for the task openstack.osa.db_setup | 21:41 |
| opendevreview | Merged openstack/openstack-ansible-os_barbican stable/wallaby: Rename TLSv1.0 to TLSv1 in apache config https://review.opendev.org/c/openstack/openstack-ansible-os_barbican/+/857754 | 21:55 |
| opendevreview | Merged openstack/openstack-ansible-os_nova stable/yoga: Add new line after proxyclient_address https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/859161 | 22:04 |
| opendevreview | Merged openstack/openstack-ansible stable/wallaby: Include install_method variables for openrc https://review.opendev.org/c/openstack/openstack-ansible/+/859230 | 23:21 |
| opendevreview | Merged openstack/openstack-ansible stable/xena: Include install_method variables for openrc https://review.opendev.org/c/openstack/openstack-ansible/+/859169 | 23:46 |
| opendevreview | Merged openstack/openstack-ansible stable/yoga: Include install_method variables for openrc https://review.opendev.org/c/openstack/openstack-ansible/+/859168 | 23:46 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!