Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-41488

When disabling IOP on the satellite, 'no-enable-iop' makes 'iop-ensure absent' ineffective

XMLWordPrintable

    • False
    • sat-proton
    • None
    • None
    • None
    • None

      Description of problem:
      When disabling IOP on the satellite, 'no-enable-iop' makes 'iop-ensure absent' ineffective; thus, the service and containers will remain. The customer can inadvertently run both since the options are available.
       

      How reproducible:
      100%
       

      Is this issue a regression from an earlier version:
      No
       

      Steps to Reproduce:

      1. Enable IOP on the satellite

      2. Disable IOP with 'no-enable-iop' and 'iop-ensure absent'

      Actual behavior:

      // Before enabling IOP
# foreman-installer --full-help | egrep "enable-iop|iop-ensure"
--[no-]enable-iop        Enable 'iop' puppet module (default: false)
--iop-ensure                Whether services should be present or absent (current: "present")
# podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

      // Enabling IOP - container starts
# satellite-installer --enable-iop
# foreman-installer --full-help | egrep "enable-iop|iop-ensure"
--[no-]enable-iop         Enable 'iop' puppet module (default: true)
--iop-ensure                Whether services should be present or absent (current: "present")
 
# podman ps
CONTAINER ID  IMAGE                                                             COMMAND               CREATED         STATUS         PORTS                                NAMES
9e367248085c  registry.redhat.io/amq-streams/kafka-39-rhel9:2.9.1-1             sh bin/init-start...  13 minutes ago  Up 13 minutes
 ... omit

      // Disabling the IOP with no-enable-iop, then iop-ensure absent will not change the value and container is still running  'satellite-installer --iop-ensure absent --no-enable-iop' exibited the same
# satellite-installer --no-enable-iop
# foreman-installer --full-help | egrep "enable-iop|iop-ensure"
--[no-]enable-iop           Enable 'iop' puppet module (default: false)
--iop-ensure                Whether services should be present or absent (current: "present")
 
# satellite-installer --iop-ensure absent
# foreman-installer --full-help | egrep "enable-iop|iop-ensure"
--[no-]enable-iop           Enable 'iop' puppet module (default: false)
--iop-ensure                Whether services should be present or absent (current: "present")
# podman ps
CONTAINER ID  IMAGE                                                             COMMAND               CREATED         STATUS         PORTS                                NAMES
9e367248085c  registry.redhat.io/amq-streams/kafka-39-rhel9:2.9.1-1             sh bin/init-start...  23 minutes ago  Up 23 minutes

      // You must enable IOP, then absent to disable containers: 
# satellite-installer --enable-iop --iop-ensure absent
# foreman-installer --full-help | egrep "enable-iop|iop-ensure"
--[no-]enable-iop               Enable 'iop' puppet module (default: true) 
--iop-ensure                 Whether services should be present or absent (current: "absent")
 
# podman ps
CONTAINER ID  IMAGE       COMMAND     CREATED     STATUS      PORTS       NAMES

      Expected behavior:
      https://issues.redhat.com/browse/SAT-38347 states "The no-enable-iop simply doesn't manage the IOP services anymore.", so maybe that option should not be there since the customer may intuitively use the option which makes 'iop-ensure absent' ineffective

      Business Impact / Additional info:
      It is confusing since the option is available.
       

              Unassigned Unassigned
              rhn-support-tharring Takae Harrington
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: