Comment 3 for bug 2002653

Well, var-www-repo.mount does require network-online as by default it's glusterfs, that does require networking. But if it has been overwritten for some local filesystem, that will cause faulty mount to be configured. Same will happen if systemd_mount role was leveraged to mount any other local filesystem, that doesn't require networking. As we've seen exact same behavior where systemd_mount was part of it, as it was conflicting with local-fs.target and going to loop because of that.

But I will take a deeper look specifically on mariadbcheck.socket now.