Dusty Mabe

kola: AWS/GCP platforms getting afterburn SSH key when running the coreos.ignition.ssh.key test

15

If I look at the the logs for the kola AWS and GCP runs for the [coreos.ignition.ssh.key test](https://github.com/coreos/coreos-assembler/blob/3f2100c836a681d7b7c8947d6a08029e851827f3/mantle/kola/tests/ignition/ssh.go#L22-L35) I see in the console output: ``` ens4: 10.128.0.13 fe80::4001:aff:fe80:d Ignition: user...

rethink build specification in container.yml

12

There are a few issues I'd like to discuss. - Being more explicit about what is going on in ansible-container - allowing for users to specify what playbook file to...

# Bug # If I don't pass an ssh key when starting an instance I get this error from afterburn: ``` [core@fcos-s390x-builder ~]$ journalctl -u [email protected] Jun 01 01:06:40 fcos-s390x-builder...

## Bug # When booting a Fedora CoreOS instance on azure there is a 30 second delay: ``` Dec 09 21:25:31 localhost.localdomain systemd[1]: sysroot-ostree-deploy-fedora\x2dcoreos-deploy-92d58206bcc345f7ede4a2385e64addc26e4714e4c2333b5e36ec84d524f6411.0.mount: Deactivated successfully. Dec 09 21:25:59 localhost.localdomain...

New release request

2

Can we get a new release? I had to use master to get around an [issue I was having](https://github.com/strukturag/libheif/issues/56#issuecomment-450523876). We need a new release so the distros can pick it...

possible memory overuse when pruning

6

Discussed this with @jlebon and we decided to open an issue here to further investigate. I'm working on pruning our large Fedora OSTree repositories. Currently I'm running test runs and...

Install from boot.iso doesn't work for aarch64

2

oz will try to do a direct boot by downloading the kernel and initrd, if that fails then it will try to boot from a boot.iso in the install tree....

RFE: warn users when secret data is not base64 encoded

8

It might be nice to add a feature to warn a user when secret data that is being passed in is obviously not base64 encoded. For example, if I have...

how to use image stream with generated deployment

6

if there happens to be an imagestream that already exists and I want to use it for a container that is part of my kedge.yaml file how do I do...

should setting `CONTAINER_ROOT_LV_MOUNT_PATH` also update docker to not point at `/var/lib/docker` ?

4

I set: ``` STORAGE_DRIVER=overlay2 GROWPART=true ROOT_SIZE=15G CONTAINER_ROOT_LV_SIZE=100%FREE CONTAINER_ROOT_LV_NAME="container-root-lv" CONTAINER_ROOT_LV_MOUNT_PATH="/var/lib/containers/container-runtime" ``` I want `/var/lib/containers/container-runtime` to be used by docker. Should container-storage-setup do this for me?