/srv/irclogs.ubuntu.com/2022/07/27/#ubuntu-server.txt

cc111 Hi. Does anyone have an example of an autoinstall yaml that includes a disk path: "*sdb" to choose an installl disk by chance? The installer keeps selecting a different disk.03:25
fooNginx question (I realize there is an nginx channel, too): Getting this error:  [error] 23619#23619: *136 client intended to send too large body: 761038926 bytes ... am I missing something, shouldn't client_max_body_size 1500M solve that?04:55
fooMight be that nginx is the best place for that, in which case, please disregard :) stumped on this.04:55
=== BOWnbERTHA2 is now known as BOWnbERTHA
Walex"Context: http, server, location", you may have to specify it in some or all contexts, depending on your configuration.11:37
=== SuperL4g is now known as SuperLag
cc111Is there an example of the autoinstall that includes matching a disk like path: "*sdb" to choose an install disk? The installer keeps selecting a different disk.13:51
RoyKcc111: what makes it even more interesting, is that device naming isn't very stable in linux ;)15:03
cc111I am fine with matching the pcipath like in /dev/disk/by-path/15:57
RoyKcc111: that's probably better, but then, I don't know much about autoinstall, so please excuse me there - others may know more16:00
cc111is there any way  i could tell why it's ignoring the parameters? and if i could restart the installer with a new user-data file without rebooting?16:08
RoyKcc111: personally, I don't know, but again, others may know16:19
blackboxswathos: for ubuntu server future support of ansible: are we looking at whether ansible-core (minimal package) is a viable install target as opposed? cloud-init may opt to install the minimal ansible-core instead of ansible, but I notice ansible-core deb can't install on kinetic. 21:22
blackboxswfiling a bug against ansible-core for reference21:23
blackboxswmaybe it's this bug https://bugs.launchpad.net/ubuntu/+source/ansible-core/+bug/1969917 digging in21:24
ubottuLaunchpad bug 1969917 in ansible-core (Ubuntu) "package ansible-core 2.12.0-1 failed to install/upgrade: installed ansible-core package post-installation script subprocess returned error exit status 1" [Undecided, Confirmed]21:24
blackboxswhere's the full symptom athos https://bugs.launchpad.net/ubuntu/+source/ansible-core/+bug/1969917/comments/5 broken symlink due to deb package putting release.py in unversioned /usr/lib/python3 vs versioned /usr/lib/python3.10 and py3compile not tying the links together properly I think21:40
ubottuLaunchpad bug 1969917 in ansible-core (Ubuntu) "package ansible-core 2.12.0-1 failed to install/upgrade: installed ansible-core package post-installation script subprocess returned error exit status 1" [Undecided, Confirmed]21:40
blahdeblahblackboxsw: Out of curiosity, how did we get into the situation where ansible & ansible-core are different versions?  I was just building myself a dev environment container for it and realised that the version numbering is a bit weird.23:38
blackboxswwow blahdeblah that is strange and from the looks of ansible:debian/control  it doesn't generate the ansible-core module as I would have expected.23:39
blackboxswI didn't realize they were generated from separate source packages until just now.23:40
blahdeblahWas there perhaps an upstream Debian package maintainer dispute?23:42
blackboxswseems like we'd want to make sure we are syncing the right compatible versions. I see a couple breaks/replaces in control files that need sorting I think23:42
blahdeblahThere's also the ansible PPA, which seems to more closely follow upstream ansible.23:42
blackboxswansible-core: Breaks: ansible (<< 4.6.0-1~), ansible-base                                     23:42
blackboxswReplaces: ansible (<< 4.6.0-1~), ansible-base                                   23:43
blackboxswso yeah a bit muddy to sort I think23:43
* blackboxsw has to run for dinner. will check in later23:43
blackboxswttfn23:43
=== blackro0t is now known as blackroot

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!