No missing expected images.
Failed openQA tests: 1/2 (x86_64)
New failures (same test did not fail in 28-20180518.0):
ID: 239211 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/239211
Passed openQA tests: 1/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
No missing expected images.
Failed openQA tests: 1/2 (x86_64)
New failures (same test did not fail in 27-20180518.0):
ID: 239209 Test: x86_64 Atomic-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/239209
Passed openQA tests: 1/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Started the CentOS Atomic Host vagrant box I have lying around on my system. It was the `7.1711` version. It starts fine but after I upgrade docker service doesn't come up. I see two issues:
- docker-storage-setup fails
```
-bash-4.2# systemctl status docker-storage-setup -o cat | tee
● docker-storage-setup.service - Docker Storage Setup
Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-05-16 01:30:26 UTC; 10min ago
Process: 719 ExecStart=/usr/bin/container-storage-setup (code=exited, status=1/FAILURE)
Main PID: 719 (code=exited, status=1/FAILURE)
Starting Docker Storage Setup...
ERROR: Storage is already configured with devicemapper driver. Can't configure it with overlay2 driver. To override, remove /etc/sysconfig/docker-storage and retry.
docker-storage-setup.service: main process exited, code=exited, status=1/FAILURE
Failed to start Docker Storage Setup.
Unit docker-storage-setup.service entered failed state.
docker-storage-setup.service failed.
```
- docker service itself doesn't come up
```
-bash-4.2# systemctl status docker -o cat | tee
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/docker.service.d
└─flannel.conf
Active: failed (Result: exit-code) since Wed 2018-05-16 01:30:27 UTC; 9min ago
Docs: http://docs.docker.com
Process: 795 ExecStart=/usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --seccomp-profile=/etc/docker/seccomp.json $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES (code=exited, status=1/FAILURE)
Main PID: 795 (code=exited, status=1/FAILURE)
Starting Docker Application Container Engine...
time="2018-05-16T01:30:26.496375725Z" level=warning msg="could not change group /var/run/docker.sock to docker: group docker not found"
time="2018-05-16T01:30:26.499243981Z" level=info msg="libcontainerd: new containerd process, pid: 925"
Error starting daemon: error initializing graphdriver: devicemapper: Non existing device atomicos-docker--pool
docker.service: main process exited, code=exited, status=1/FAILURE
Failed to start Docker Application Container Engine.
Unit docker.service entered failed state.
docker.service failed.
```
We probably need to address these issues.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/498
cverna reported a new issue against the project: `atomic-wg` that you are following:
``
The label `BZComponent` is apparently case sensitive.
```FAILED: BuildError: Required LABELs haven't been found in Dockerfile: com.redhat.component (or BZComponent).```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/500
miabbott reported a new issue against the project: `atomic-wg` that you are following:
``
If you start a Fedora 28 container image from `registry.fedorproject.org` and do a `dnf` operation, you'll see that the 'test updates' repo is enabled by default.
This is different from the Fedora 27 container image from the same registry.
```
$ sudo podman run -it registry.fedoraproject.org/fedora:28
[root@3cf1fc993791 /]# dnf install wget
Fedora 28 - x86_64 - Test Updates 389 kB/s | 16 MB 00:43
Fedora 28 - x86_64 - Updates 1.1 MB/s | 8.3 MB 00:07
Fedora 28 - x86_64 2.2 MB/s | 60 MB 00:27
Last metadata expiration check: 0:00:06 ago on Thu May 17 14:33:43 2018.
Dependencies resolved.
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
wget x86_64 1.19.5-1.fc28 updates 719 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 719 k
Installed size: 2.8 M
Is this ok [y/N]: n
Operation aborted.
# cat /etc/yum.repos.d/fedora-updates-testing.repo
[updates-testing]
name=Fedora $releasever - $basearch - Test Updates
failovermethod=priority
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/testing/$releasever/Everything/$basearch/os/
metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f$…
enabled=1
repo_gpgcheck=0
type=rpm
gpgcheck=1
metadata_expire=6h
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch
skip_if_unavailable=False
...
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/499