Description of problem: sysfsutils was an optional depency of nova for fiber channel storage integration. sysfsutils and systool shoudl nolonger be used in nova directly as a result this depency shoudl nolonger be required. sysfsutils is going away in rhel 9 which will be the basis of osp 17 so we should remove it from the package list in the nova-compute container. https://opendev.org/openstack/tripleo-common/src/branch/master/container-images/tcib/base/os/nova-base/nova-compute/nova-compute.yaml#L26 Version-Release number of selected component (if applicable): How reproducible: NA Steps to Reproduce: 1. 2. 3. Actual results: sysfsutils is installed in the container Expected results: sysfsutils is not installed in the container. Additional info:
direct usage of sysfsutils/systool was removed a while ago but it is still used by fiber channel in os-brick, but os-brick does require the package correctly.
This is blocked on os-brick https://github.com/openstack/os-brick/blob/master/os_brick/initiator/linuxfc.py#L162 As noted by Lee: So to be clear we should only go ahead with this removal once os-brick has been updated to drop this direct dependency on sysfsutils and the systool binary it provides. I'm going to also follow up and ensure this is reflected in both the openstack-nova and os-brick RPM spec files. I would rise that to critical, as sysfsutils is being removed in RHEL 9, and that would block containers building pipeline until that os-brick sysfsutils dependency on resolved. Putting it back to untriaged given the revised priority and changed scope for 17.0 to address criticals/blockers.
bug 1960179 is tracking getting usage removed from os-brick, from inspection python-os-brick.spec has the right Requires Requires: sysfsutils So we should be able to drop it from tcib as an explicit entry for nova container image in tcib
OK, so this BZ is just tracking removing sysfsutils from the Nova requirements? That's easy to do, but maybe let's not do it so close to 17.0 GA, to avoid the risk of blowing up CI. Since os-brick seems to require sysfsutils regardless, seems like we'll have to package it in layered products anyways.
(In reply to Artom Lifshitz from comment #7) > OK, so this BZ is just tracking removing sysfsutils from the Nova > requirements? That's easy to do, but maybe let's not do it so close to 17.0 > GA, to avoid the risk of blowing up CI. Since os-brick seems to require > sysfsutils regardless, seems like we'll have to package it in layered > products anyways. https://review.opendev.org/c/openstack/tripleo-common/+/790070/ was abandoned. What's the next step?
this can be defered to 17.1
https://code.engineering.redhat.com/gerrit/c/python-os-brick/+/418621/ is in 17.0, so I think we're good to do our backport to wallaby and 17.x.
Can you provide the latest status for this high severity, high priority BZ?
Can you provide the latest status for this high severity, high priority BZ? https://www.marykayintouch.website/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577
This comment was flagged a spam, view the edit history to see the original text if required.
This comment was flagged as spam, view the edit history to see the original text if required.