On 03/24/2017 11:01 AM, Harald Dunkel wrote: > On 03/23/17 19:49, Christian Seiler wrote: >> >> The issue has now been fixed upstream: >> >> https://github.com/open-iscsi/targetcli-fb/commit/8011ea6a741d494c145b4906f7a7865c8b74c6a7 >> > > I highly appreciate your fast response and fix on this > problem.
My question now would be: you also reported #858434 in targetcli, which I can't reproduce. I now have two option: - I could either upload a new version now with the fix for #858459 (this bug). - I could wait until we've zeroed in on the second issue and upload a package with both fixes. Since the release team has to manually review each change at this point in the freeze, I'd prefer not ask twice. On the other hand, if you are yourself having trouble figuring out how to reproduce the second problem and this could take a while, perhaps it's better to fix the backup issue first to get that out of the way. > Do you think that #858533 should be linked to this report? No, that's a separate issue (separate package), but thanks for making me aware of it, I'll take a look. (You could link the report to the package targetcli-fb though, see [1].) > I have no idea why rtslib-fb-targetctl is managed by the > Openstack maintainers. Because OpenStack uses LIO to export volumes to VM instances, and they use rtslib-fb internally. Plus, the OpenStack team was first to package the rtslib-fb package. (The non-fb rtslib package was packaged by Ritesh earlier, but we decided to switch away from the non-fb LIO branch only after OpenStack already had that package in Debian.) There were some discussions recently about rtslib-fb changing maintenance to the LIO team, but that hasn't happened yet, and it definitely won't happen officially for Stretch. That said: I'll be happy to take a look at that other bug report. Regards, Christian [1] https://www.debian.org/Bugs/server-control#affects
