Comments
jhogarth
This update has been unpushed.
It needs karma, currently it's at +1
Feel free to test and up the karma ... I can't karma my own builds ;)
There is an upstream bug, which affects this build, which causes ansible-galaxy to break any role imported which has a file name or template.
This feels like it could break things for a lot of people so I feel a need to state no, until it's fixed upstream or a maintainer patch to fix it is added.
There is an upstream bug, which affects this build, which causes ansible-galaxy to break any role imported which has a file name or template.
This feels like it could break things for a lot of people so I feel a need to state no, until it's fixed upstream or a maintainer patch to fix it is added.
Going through the test cases...
- /tmp is correctly half my RAM
- using --tmpfs to specify /tmp gets the correct size
- confirmed /run also behaves correctly
- A rhel7 container from my rhel sub is getting subscription info from my registered fedora host correctly with yum-config-manager correctly enabling/disabling RHEL repos in the container and being able to install from extras.
Also though not linked or listed here, since it was an issue in RHEL:
- Tested mariadb (#1419040 affected rhel but not fedora) and confirm no regression, mariadb starts fine and /log is populated as expected.
I really can't replicate this at all.
I've had my instance on this build for a while now and I'm not seeing this.
What apps do you have installed?
Can you do the upgrade from the CLI and file a bug with the logs from it? Would be good to see what exactly it is changing or thinks needs changing.
Actually I suspect you meant to link this bug ... as this bug is fixed ...
This doesn't actually fix the testcase in the bug linked (see comments on bug for more detail).
It is however generally functional and fixes the critical issue preventing mariadb, httpd and similar services that expect their log directories in exist in /var/log from starting under a systemd based container.
Intel® Core™ i5-6300HQ CPU @ 2.30GHz × 4 Intel® HD Graphics 530 (Skylake GT2) / Gallium 0.4 on NV117
wifi working, tests passed, PRIME works,
my logs are being spammed with " iio-sensor-prox[951]: Could not open input accel '/dev/input/event13': Operation not permitted" but it doesn't seem to be causing noticeable problems
/sys/bus/input/devices says it is:
I: Bus=0019 Vendor=0000 Product=0000 Version=0000 N: Name="Acer BMA150 accelerometer" P: Phys=wmi/input1 S: Sysfs=/devices/virtual/input/input13 U: Uniq= H: Handlers=event13 js0 B: PROP=0 B: EV=9 B: ABS=
Using virt-install I can now install an f25 guest on an f25 host
Owncloud shows this working
A quick test looks fine
updated and working fine here
tested and wfm
tested and wfm
tested and wfm
tested with owncloud - logs no longer being spammed, all else appears to be fine
FYI the php-twig spamming logs issue has been fixed by this update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-d996c65548
Thanks that's actually a bug in php-twig that I've been meaning to file - it was picked up in the 8.2 updates where we moved to using the autoloader instead of PSR include behaviour as per the PHP SIG guidelines.
Your comment prompted me to actually do so.
This works fine in our test environment