Hello Christian, thanks for your quick response. True, it is quite unfortunate that this problem is just a waiting game, and not a game-ending issue. And I definitely agree that some end game here might not be good for a [5] type of result.
Regarding [3], yes I saw that yesterday while searching around. Had not seen [4] yet, but I can see why they wanted to find a better solution for the "large hammer" approach. Now, regarding [2], that sounds like a very interesting possibility. I will say that while running Ubuntu 17.10 for a short time, we did experience quite noticeable instability on Xeon-based servers, as well as hard system resets on AMD-based servers. (This required us to go back to 16.04.3 on all hardware last weekend.) Do you think that those issues have anything to do with libvirt, or with other parts of the system? Also for [2], do you think there would be any harm in updating all packages that are newer from xenial-pike? Or what do you think the best approach here would be? I wasn't exactly aware of this option, and definitely don't know much about it safely going into datacenter production. But depending on how reliable/stable all of these versions are on 16.04.3, I'd definitely be willing to go this route. After our 17.10 disaster though, I just need to be cautious. :) Very interested to hear more. Thanks again, Christian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738864 Title: libvirt updates all iSCSI targets from host each time a pool is started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1738864/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
