Comments

79 Comments
karma

Found some minor issues (reported upstream), but generally seems OK.

Successfully used flatpak to update the org.gnome.Platform and org.gnome.gedit.

Installed org.gnome.Weather.

Successfully ran both gedit and weather

Successfully composed an F24 tree

pkg-add works well!

pkg-add works nicely

Used ostree admin unlock to install this version.

Ran the following commands as unprivileged user:

rpm-ostree status
rpm-ostree db diff
rpm-ostree db list
rpm-ostree db version

And successfully used the following as privileged user:

rpm-ostree deploy
rpm-ostree rollback
rpm-ostree rebase
karma

Used new ostree admin unlock with great success!

Also performed basic ostree log, ostree pull, ostree refs, and ostree admin status commands.

Works fine here

karma

Using a F23 Atomic Host, I rebased to a custom ostree compose that included the latest package.

I used the reproducer above to verify the changes and noted the permissions were correct:

-bash-4.3# stat /sysroot/tmp/
  File: ‘/sysroot/tmp/’
  Size: 145             Blocks: 0          IO Block: 4096   directory
Device: fd00h/64768d    Inode: 101         Links: 7
Access: (1777/drwxrwxrwt)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:tmp_t:s0
Access: 2015-11-18 16:24:11.636000000 +0000
Modify: 2015-11-18 19:32:10.337000000 +0000
Change: 2015-11-18 19:32:10.337000000 +0000
Birth: -
-bash-4.3# stat /tmp
  File: ‘/tmp’ -> ‘sysroot/tmp’
  Size: 11              Blocks: 0          IO Block: 4096   symbolic link
Device: fd00h/64768d    Inode: 5394866     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Context: system_u:object_r:tmp_t:s0
Access: 2015-11-18 19:26:09.546000000 +0000
Modify: 2015-11-18 19:24:46.338000000 +0000
Change: 2015-11-18 19:24:46.339000000 +0000
 Birth: -

And the systemd unit file was fired off

# systemctl status ostree-remount.service
● ostree-remount.service - OSTree Remount OS/ bind mounts
   Loaded: loaded (/usr/lib/systemd/system/ostree-remount.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Wed 2015-11-18 19:26:09 UTC; 2min 23s ago
  Process: 571 ExecStart=/usr/sbin/ostree-remount (code=exited, status=0/SUCCESS)
 Main PID: 571 (code=exited, status=0/SUCCESS)

Nov 18 19:26:08 rhel-atomic-test-0.localdomain systemd[1]: Starting OSTree Remount OS/ bind mounts...
Nov 18 19:26:09 rhel-atomic-test-0.localdomain systemd[1]: Started OSTree Remount OS/ bind mounts.
BZ#1276775 [f23 - atomic] 755 perms on /tmp directory (symlink to /sysroot/tmp)
karma

Booted F23 cloud image and installed this build.

Followed these instructions to get up and running:

https://fedoraproject.org/wiki/Changes/CockpitManagementConsole#How_To_Test

Was able to successfully login on port 9090, started a docker container, pulled down a new docker image, used the terminal.

Booted F23 cloud image, installed docker, upgraded to this build.

Ran through a number of docker build, docker run, and docker stop tasks without error.

Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.

Ran a number of docker build and docker run tasks without error.

Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.

Ran a number of 'docker build' and 'docker run' tasks without error.

Booted the F23 Cloud Image, installed latest docker, then upgraded to this build.

Ran a number of docker build and docker run tasks without error.

Booted F23 cloud image, installed docker, then upgraded to this build.

I ran a number of docker build, docker run, and docker stop tasks without error

Booted F23 cloud image, installed latest docker, and then upgraded to this build.

Ran a few docker build, docker run, and docker stop operations without error.