rm notifications from Python group

Notes about this published at https://www.dereckson.be/blog/2017/05/24/upgrade-beyond-docker-1-12-on-centos-7/

I've documented we use sha256 hashes at https://agora.nasqueron.org/Code_conventions#Salt

Download docker-ce.repo

I was writing it prints @modules as is instead to expand it when I've figured we only cleared the config and the compiled caches, not the view cache.

In https://social.nasqueron.org/@Kumkum/398092 that works too.

Looks good to me now — https://social.nasqueron.org/@Dereckson/398055

It's easier than that: in most recent Mastodon version, the process runs under a Mastodon user, so it now needs to own the /mastodon/public directory.

I switched the SELinux configuration to Permissive, so we'll get logs, and we'll be apply to apply sand_virt_t SELinux policy to the directories to manage by the container.

Could be a SELinux issue, as the same time in the main logs:

[ Decreasing priority as it's done. ]

Upgrade done.

Whitelines after import

PEP 8

Wrong instance

Wrong instance

Currently testable on https://tools51.nasqueron.org/wikimedia/write/sourcetemplatesgenerator

A side issue: ntpd wasn't running, and a drift existed. That has been resolved at 12:28:49.

Server consolidation done.

To give a little idea about how this process is slow:

Snapshot consolidation started, that will take a long time. During this operation, I/O perfs will be degraded.

Hypervisor happy, server running again.

Tests successfully done on Docker we can delete the files from the hypervisor.

Remove the volume

Remove the volume group

Disable the volume group

Currently, the disk isn't even mounted on Dwellers, /etc/fstab line is commented out.

Ysul is in snapshot mode, that explains the growing.

I'll attach a VSphere client to the server to see what happens. ETA 22:30.