We're actually seeing iscsi errors show up as soon as the container starts; I guess the iscsid service never starts properly and so when the charm does an apt-get install of some unrelated packages, something is trying to set up that iscsi service and it's failing again.
I've attached logs from a container where this happened. Excerpt from syslog: http://paste.ubuntu.com/p/vwqmRkGzdP/ ** Attachment added: "open-iscsi-errors.tgz" https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1651497/+attachment/5182210/+files/open-iscsi-errors.tgz ** Summary changed: - install Job for iscsid.service failed because a configured resource limit was exceeded + iscsid.service fails to start in container, results in failed apt-get install later on -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651497 Title: iscsid.service fails to start in container, results in failed apt-get install later on To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot-log-analyser/+bug/1651497/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
