Warewulf rpm install fails if /var/lib/warewulf/*
is read-only
#1208
Labels
Milestone
/var/lib/warewulf/*
is read-only
#1208
Steps to reproduce
I'm not entirely sure this is a "bug", but it does break my attempts to use a single master which replicates its
chroots
to other sites via ZFSsend
/recv
to a filesystem withreadonly=on
.I can leave
readonly=off
set on the given filesystems; futuresend
/recv
will just roll back any local changes. But that does introduce a small window for site-specific image drift to accumulate which ideally I'd like to prevent. If this failure during install could be a warning that would solve this specific problem, presumably the permissions and contexts are being set correctly when I upgrade the upstream WW master and already replicated to the local site.Note this is the lowest of low on priorities, I just wanted to note this as it's potentially going to disrupt some HA approaches that want to distribute read-only copies of the node images using ZFS
send
/recv
, an approach that I may be the only one interested in./var/lib/warewulf/chroot
read-only.Error message
Information on your system
main
General information
wwctl version
and reported the contents of/etc/os-release
The text was updated successfully, but these errors were encountered: