Thursday, 2021-12-16

opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Change haproxy variable used to set security headers to haproxy_frontend_raw  https://review.opendev.org/c/openstack/openstack-ansible/+/82181403:41
noonedeadpunkdamiandabrowski[m]: there're some problems, yes... And pretty huge ML thread regarding them becoming offical project due to this03:47
noonedeadpunkAs they didn't want to use like oslo and invented their own way of doing things03:48
noonedeadpunkBut I guess they agreed to adapt some things at the end03:51
noonedeadpunkWill see03:51
jrosser_we really are very unlucky with the 'start Y cycle' patch07:44
jrosser_it's failing already again07:44
noonedeadpunkdamn07:45
* jrosser_ wonders where the ara report has gone07:50
noonedeadpunkit crashed while generating07:50
jrosser_yes https://paste.opendev.org/show/811714/07:51
noonedeadpunkoh and it fails everywhere now07:51
noonedeadpunkdmsimard: anything known? ^07:51
jrosser_is this subject to u-c?07:52
jrosser_maybe something important is bumped and breaks it07:52
noonedeadpunkwell i sounds like dynaconf ut it's not constrained07:53
noonedeadpunk(which is even worse)07:53
noonedeadpunkand released a week ago :D07:54
noonedeadpunkand they even dropped previous version from pypi...07:54
noonedeadpunkthere's no 3.1.6 https://pypi.org/project/dynaconf/#history07:55
jrosser_nice07:55
jrosser_looking in the ara release notes same kind of thing has happened before07:55
BraceProbably not the right place to ask, but does anyone know Openstack (Victoria) is vulnerable to log4j?09:06
jrosser_openstack itself is python, not java09:08
jrosser_if you surround your openstack with other external tools, like an ELK stack for log collection for example, then you'd defiantly need to address that.09:10
Bracejrosser_: that's kinda what I thought, thank you for confirming09:37
*** sshnaidm|afk is now known as sshnaidm10:54
*** dviroel|out is now known as dviroel|rover11:26
dmsimardnoonedeadpunk: not aware of an issue but I've also been a bit out of the loop, it wouldnt be the first time dynaconf breaks ara12:09
dmsimardI'm not fully awake yet, could I ask you to create an issue on github ? I will look today12:09
noonedeadpunksure12:23
jamesdentongood morning, all13:31
damiandabrowski[m]hey!13:32
dmsimardnoonedeadpunk, jrosser_: I have other stuff I need to look at but I glanced briefly at the issue and I don't see a recent release of dynaconf ? Looks like last version dates back to september13:43
noonedeadpunkfacepalm13:44
noonedeadpunkyes, sorry... I read september as december13:45
noonedeadpunkhm, which means it's smth different....13:45
noonedeadpunkSorry, was pretty busy, will make up bug report a bit later13:45
dmsimardnp, not saying there is no bug but I was wondering if I was missing something obvious13:46
dmsimardI will take another look later13:46
jrosser_noonedeadpunk: dmsimard its perhaps this https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L44814:28
jrosser_we've run jobs today on stable/xena which install django 2.2.24 and generate a report ok, but from master we pick up the master version of upper-constraints and get 3.2.1014:30
noonedeadpunkwell https://github.com/ansible-community/ara/blob/master/setup.cfg#L6414:31
noonedeadpunkWe should somehow avoid u-c for ara I guess14:32
dmsimardoh yeah, ara isn't tested with django 3.2 yet14:32
noonedeadpunkfor some reason I thought they're not used even...14:32
dmsimardara is meant to use the 2.2 LTS for now but there is an issue to upgrade to django 3.2 which is the next LTS14:33
dmsimardgood catch14:33
jrosser_should it be respecting setup.cfg when we install?14:33
jrosser_if it were i'd expect it to conflict with whats in u-c and fail14:34
noonedeadpunkso that's how we install it https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/scripts-library.sh#L204-L21014:34
noonedeadpunkquestion is what's in PIP_OPTS14:34
jrosser_ahh i see14:34
dmsimardthat pin on dynaconf can also go away14:34
dmsimardit was to avoid 3.1.3 but it's since been excluded from ara: https://github.com/ansible-community/ara/blob/master/setup.cfg#L7014:35
noonedeadpunkI guess we add u-c here https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/scripts-library.sh#L7114:36
jrosser_ /opt/ansible-runtime/bin/pip install --isolated --index-url http://mirror.bhs1.ovh.opendev.org/pypi/simple --trusted-host mirror.bhs1.ovh.opendev.org --extra-index-url http://mirror.bhs1.ovh.opendev.org/wheel/ubuntu-20.04-x86_64 --constraint global-requirement-pins.txt --constraint file:///opt/ansible-runtime-constraints-f5dcb1d64534feb5720400c81089bd2b0765e2c3.txt 'ara[server]' 'dynaconf<3.1.3'14:38
jrosser_for example14:38
jrosser_feels like the issue is that we install ansible-runtime according to u-c (maybe unnecessary now?)14:39
jrosser_so then coming along later to install ara without u-c might change a bunch of stuff14:39
dmsimardif django is the only issue maybe you can pin it to https://github.com/ansible-community/ara/blob/f366c9f9f2a06311dd67449f1124dca0674563c2/setup.cfg#L64 like you did with dynaconf14:40
dmsimardI don't suspect you'd install django for another reason than ara in the runtime venv -- I guess the u-c on it is for horizon14:40
jrosser_it was ok for dynaconf as that doesnt appear in u-c14:41
noonedeadpunkI'd expect to see pip conflicting because of that...14:41
jrosser_tbh really all we put in ansible-runtime venv is ansible now14:41
jrosser_there used to be the openstack client and stuff but not any more14:42
jrosser_so maybe this is just legacy and we'd be better sticking with our own global-pins here14:42
dmsimardnoonedeadpunk: ah, my u-c is rusty :)14:42
jrosser_with older pip it would have been ok14:42
noonedeadpunkThen I wonder if we should put ansible dependencies like jinja inside our pins14:42
jrosser_but now with the new resolver if you have two differing constraints for the same thing it fails14:43
noonedeadpunkas nasty htings might happen when new jinja lands for same osa for instance14:43
noonedeadpunkand I think it's not only thing that we might want to lock14:44
jrosser_right - and then we are in the same problem as jinja2 is also in u-c14:44
jrosser_it amost says that we want our own controlled constraints file for the ansible-runtime venv14:44
jrosser_as it's not really a co-installable openstack thing, just internal to OSA14:44
noonedeadpunkwell, I guess while it's unctrained in u-c we might be fine not having it locally?14:45
noonedeadpunk*while it's constrained14:45
noonedeadpunkWhat I meant is that we likely want to have ansible dependencies constrained somehow anyway14:45
jrosser_well, if we want to constrain the django version then we can't use u-c14:46
noonedeadpunkand it's more matter if we want to maintain that or not14:46
jrosser_without a bunch of filtering mess in boostrap-ansible to remove some things14:46
noonedeadpunkor we can just drop U-C when installing ara... Yeah, that could bring us some mess in venv in CI though14:47
jrosser_jinja2 in u-c -> good / django in u-c -> bad from ansible-runtime POV, we're a little stuck14:47
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Do not add u-c to PIP_OPTS  https://review.opendev.org/c/openstack/openstack-ansible/+/82198814:50
noonedeadpunkjrosser_: wdyt? ^14:50
noonedeadpunkdoh....14:51
jrosser_it would be possible to use global-pins and a new ansible-runtime-pins for that14:51
jrosser_so that we have the same setuptools / virtualenv / .... everywhere from global-pins14:51
jrosser_then specifically we can put the jinja2 version (and anything else just for the runtime venv) in ansible-runtime-pins14:52
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Do not add u-c to PIP_OPTS  https://review.opendev.org/c/openstack/openstack-ansible/+/82198814:52
noonedeadpunkI didn't really understood but sounds interesting :)14:53
jrosser_:)14:53
jrosser_you were concerned about the jinja2 version being unconstrained14:53
noonedeadpunkjust in case setuptools are now in u-c14:53
jrosser_and i agree there that there is a risk of wierdness for stable branches14:54
noonedeadpunkwell it wasnt only about jinja...14:54
noonedeadpunkPyYAML is also constrained for example14:55
noonedeadpunkand cryptography14:55
noonedeadpunkhttps://github.com/ansible/ansible/blob/devel/requirements.txt is quite small though:)14:55
jrosser_hah i was just looking at exactly the same file14:55
noonedeadpunkand packaging btw in u-c as well. so the only unconstrained thing now is resolvelib14:56
noonedeadpunkand I kind of wonder if collections do install required modules to venv as well....14:56
jrosser_well idk - do we use some horrible grep to pull the necessary lines out of u-c? we have the file in /opt now14:57
jrosser_but it does make me wonder why this all doesnt break more often - i'm forever making a new venv and pip install ansible into it14:58
noonedeadpunkI believe that collections do not install modules they need...14:59
*** dviroel|rover is now known as dviroel|rover|lunch15:51
opendevreviewMerged openstack/openstack-ansible master: Start Yoga development cycle  https://review.opendev.org/c/openstack/openstack-ansible/+/82147616:29
noonedeadpunkfinally....16:30
*** dviroel|rover|lunch is now known as dviroel|rover16:42
opendevreviewMerged openstack/openstack-ansible master: Change haproxy variable used to set security headers to haproxy_frontend_raw  https://review.opendev.org/c/openstack/openstack-ansible/+/82181418:55
opendevreviewMerged openstack/openstack-ansible master: [doc] Add Xena compatible OS  https://review.opendev.org/c/openstack/openstack-ansible/+/82167618:55
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: [doc] Add Xena compatible OS  https://review.opendev.org/c/openstack/openstack-ansible/+/82202018:58
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: Change haproxy variable used to set security headers to haproxy_frontend_raw  https://review.opendev.org/c/openstack/openstack-ansible/+/82202118:59
noonedeadpunkwould be great if we could fast merge these backports ^18:59
noonedeadpunkregarding ara - this works https://review.opendev.org/c/openstack/openstack-ansible/+/821988 but I didn't catch alternative. Maybe you can pus patch jrosser_ with what you was suggsting?19:00
jrosser_oh well basically an extra pins file just for the runtime venv19:01
jrosser_so it gets global_pins + ansibl_pins19:01
spateljamesdenton around?19:31
opendevreviewMerged openstack/openstack-ansible stable/xena: Add documentation of security improvements made to Openstack Ansible  https://review.opendev.org/c/openstack/openstack-ansible/+/82152919:47
opendevreviewMerged openstack/openstack-ansible stable/xena: [doc] Add Xena compatible OS  https://review.opendev.org/c/openstack/openstack-ansible/+/82202019:47
*** dviroel|rover is now known as dviroel|out21:21

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!