** Attachment added: "juju-crashdump-openstack-2018-10-11-13.29.52.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1651497/+attachment/5200440/+files/juju-crashdump-openstack-2018-10-11-13.29.52.tar.gz
** Changed in: open-iscsi (Ubuntu)
Status: Incomplete => Confirmed
Just saw this one again after a while.
--
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 dist-
upgrade later on
To manage
If we were to change the behavior of open-iscsi to be socket activated,
then that should happen under bug 1755858.
** Description changed:
I am getting a transient error installing open-iscsi in a xenial lxd
container. Sometimes it works fine, but occasionally, it fails like
this (apt-get
2016-12-20 12:33:55 INFO install Job for iscsid.service failed because a
configured resource limit was exceeded. See "systemctl status
^ if that is the source of the issue, then this is "working as
designed". If the container had some memory or other constraints and
open-iscsi failed to restart a
I also cannot repro this failure. I can trigger the upgrade, and use a
script similar to what smoser had, but each time, the upgrade works
fine. I went through 250 iterations of the script without failure.
Could someone please attach a reproducer, or give access to a live
system that has just sh
I cannot seem to re-create this, so I'm not really interested in SRU'ing
a fix that we think might solve the problem without the ability to
verify that.
Here is what I'm doing to attempt to recreate
http://paste.ubuntu.com/p/STVg62nGPb/
I'm through 432 containers 10 at a time right now on my sys
@Jason,
I'm guessing that you ran some script to collect the logs that you collected
(open-iscsi-errors.tar.gz). There is a lot of good information there, thank
you.
Please add collection of /etc/cloud/build.info to the script that
collects.
--
You received this bug notification because you a
I had hoped to reproduce this so that I could be sure that I actually fixed it.
What I did to attempt that was
- download the 20180816 xenial daily build that had
2.0.873+git0.3b4b4500-14ubuntu3.4.
- add to lxc
lxc image import xenial-server-cloudimg-amd64-lxd.tar.xz
xenial-server-cloudimg-a
Fixing this properly should mean that open-iscsi is socket-activated in
stable releases the same as it currently is in cosmic. This should
resolve the problems including on package upgrade since the postinst
will no longer be trying to start the daemon that shouldn't be started.
--
You received
** Changed in: open-iscsi (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
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, result
10 matches
Mail list logo
