I did the following to check behaviour on a "golden image", where /etc/machine-id is expected to be recreated on boot, thus testing the underlying "systemctl preset-all" behaviour more directly. I think this is close enough to testing a future ISO built from this new package for the fresh installation case.
wget https://cloud-images.ubuntu.com/oracular/current/oracular-server-cloudimg-amd64.img cp oracular-server-cloudimg-amd64.{,mod.}img sudo -s http_proxy=http://<REDACTED>:3128/ https_proxy=http://<REDACTED>:3128/ mount-image-callback oracular-server-cloudimg-amd64.mod.img -- mchroot sh -c 'add-apt-repository -y ppa:racb/experimental3 && apt install -y sysstat' exit uvt-kvm create --backing-image-file=oracular-server-cloudimg-amd64.img rbasak-sysstat-o uvt-kvm wait rbasak-sysstat-o uvt-kvm ssh rbasak-sysstat-o 'cat /etc/default/sysstat; systemctl status sysstat-collect.timer' # ENABLED="false" yet sysstat-collect.timer is enabled and active uvt-kvm destroy rbasak-sysstat-o uvt-kvm create --backing-image-file=oracular-server-cloudimg-amd64.mod.img rbasak-sysstat-o uvt-kvm wait rbasak-sysstat-o uvt-kvm ssh rbasak-sysstat-o 'cat /etc/default/sysstat; systemctl status sysstat-collect.timer' # ENABLED="true" and sysstat-collect.timer is enabled and active uvt-kvm ssh rbasak-sysstat-o 'sudo systemctl restart sysstat-collect.service; systemctl show --property=ConditionResult sysstat-collect.service' # ConditionResult=yes uvt-kvm destroy rbasak-sysstat-o -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073284 Title: sysstat service enablement state mismatches debconf and /etc/default/sysstat setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/2073284/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
