Comments

82 Comments
karma

This osbuild-composer release seems to crash on startup. The issue has been reported upstream:

https://github.com/osbuild/osbuild-composer/issues/685

User Icon stefw commented & provided feedback on cockpit-220-1.fc32 4 days ago
karma

Smoke tested. Logged in, did a software upgrade. Works.

karma

Tested again. Works for creating image. Tested with VMDK images. System remains functional.

BZ#1636644 File conflicts: /usr/bin/composer
karma

Successfully used lorax and lorax-composer. Verified that composer-cli is now the command:

[root@m6 ~]# composer-cli compose status
25e3e1d4-8228-4894-8172-70c678437ed7 FINISHED Tue Oct  9 14:10:07 2018 example-http-server 0.0.1 qcow2            1317797888
[root@m6 ~]# 
[root@m6 ~]# 
[root@m6 ~]# 
[root@m6 ~]# composer
bash: composer: command not found
BZ#1636644 File conflicts: /usr/bin/composer
karma

I've tested lorax-composer here. It fixes a number of bugs I ran into with the version in Fedora 28 updates, including incorrect permissions on files.

Upstream changes to bots to push Cockpit into F27: https://github.com/cockpit-project/cockpit/pull/7726 as well ... addressing a couple test failures on automated test tab.

karma

Some fixes for automated tests going upstream: https://github.com/cockpit-project/cockpit/pull/7725

karma

Upgraded, did general smoke tests. Accessed VMs, Kubernetes cluster, and timers.

BZ#1472815 oci-kvm-hook Doesn't work on RHEL7 docker

Better commands:

$ koji download-build --arch=noarch --arch=x86_64 cockpit-133-1.fc25
$ sudo yum install *.rpm
$ systemctl start cockpit
$ sudo firewall-cmd --add-service=cockpit
karma

Tested with:

$ koji download-build --arch=noarch --arch=x86_64 863657
$ sudo yum install *.rpm
$ systemctl start cockpit
$ sudo firewall-cmd --add-service=cockpit
karma

Installed and this works.

Regressions are bad either way. But https://bugzilla.redhat.com/show_bug.cgi?id=1414096 has a workaround.

https://bugzilla.redhat.com/show_bug.cgi?id=1413997 does not have a workaround.

karma

This regressed the 'atomic storage reset' command https://bugzilla.redhat.com/show_bug.cgi?id=1413862

This update also broke the Atomic DBus API for VulnerabilityInfo: https://bugzilla.redhat.com/show_bug.cgi?id=1414010

karma

This update also broke the Atomic DBus API for VulnerabilityInfo: https://bugzilla.redhat.com/show_bug.cgi?id=1414010

karma

This regressed the 'atomic storage reset' command https://bugzilla.redhat.com/show_bug.cgi?id=1413862

karma

The regressions noted in the Cockpit integration tests are gone after this update. This can be seen here: https://github.com/cockpit-project/cockpit/pull/5391

One other unrelated storaged issue remains.

BZ#1393379 partitions can't be created nor removed in gnome-disks, cockpit