Skip to content

[enterprise-4.9] Issue in file registry/configuring_registry_storage/configuring-registry-storage-osp.adoc #43053

Open

Description

@bbeaudoin

Which section(s) is the issue in?

What needs fixing?

Example is for RWO storage but does not note the rolloutStrategy needs to be set to Recreate and the replica count must be set to 1.

Activity

  1. self-assigned this
    on Mar 11, 2022
  2. maxwelldb commented on Mar 11, 2022

    @maxwelldb
    Contributor
  3. mandre commented on Mar 21, 2022

    @mandre
    Member

    Yes @maxwelldb, you're correct - since the new backend is RWO, we need to ensure the image registry runs a single replica and that the rollout strategy is Recreate. On environments where Object Storage (Swift) is not available, the cluster-image-registry-operator sets this up automatically for you, however this would be an issue if someone follows the above procedure to migrate from a Swift backend (RWX) to Cinder (RWO).

    We should add a note about the limitation when using RWO storage and change the example oc patch command to also set the replica count and rollout strategy accordingly (not tested):

    oc patch configs.imageregistry.operator.openshift.io/cluster --type 'json' -p='[{"op": "replace", "path": "/spec/storage/pvc/claim", "value": "csi-pvc-imageregistry"},{"op": "replace", "path": "/spec/replicas", "value": 1},{"op": "replace", "path": "/spec/rolloutStrategy", "value": "Recreate"}]'
    
  4. maxwelldb commented on Mar 21, 2022

    @maxwelldb
    Contributor

    @mandre Thanks!

  5. openshift-bot commented on Jun 19, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  6. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 19, 2022
  7. maxwelldb commented on Jun 19, 2022

    @maxwelldb
    Contributor

    /remove-lifecycle stale

  8. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jun 19, 2022
  9. openshift-bot commented on Sep 18, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  10. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 18, 2022
  11. maxwelldb commented on Sep 19, 2022

    @maxwelldb
    Contributor

    /remove-lifecycle stale

  12. removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 19, 2022
  13. openshift-bot commented on Dec 19, 2022

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  14. 3 remaining items

  15. openshift-bot commented on Mar 20, 2023

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  16. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Mar 20, 2023
  17. openshift-bot commented on Apr 19, 2023

    @openshift-bot

    Stale issues rot after 30d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle rotten
    /remove-lifecycle stale

  18. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 19, 2023
  19. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Apr 19, 2023
  20. openshift-bot commented on Jul 19, 2023

    @openshift-bot

    Issues go stale after 90d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle stale.
    Stale issues rot after an additional 30d of inactivity and eventually close.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle stale

  21. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jul 19, 2023
  22. openshift-bot commented on Aug 18, 2023

    @openshift-bot

    Stale issues rot after 30d of inactivity.

    Mark the issue as fresh by commenting /remove-lifecycle rotten.
    Rotten issues close after an additional 30d of inactivity.
    Exclude this issue from closing by commenting /lifecycle frozen.

    If this issue is safe to close now please do so with /close.

    /lifecycle rotten
    /remove-lifecycle stale

  23. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Aug 18, 2023
  24. bbeaudoin commented on Aug 18, 2023

    @bbeaudoin
    Author

    /remove-lifecycle stale

  25. bbeaudoin commented on Aug 18, 2023

    @bbeaudoin
    Author

    The issue with the OSP documentation being incomplete still potentially exists with 4.13: https://docs.openshift.com/container-platform/4.13/registry/configuring_registry_storage/configuring-registry-storage-osp.html

    ReadWriteOnce means the storage can only be mounted on a single node but the node spreading priority will attempt to place the registry image on different nodes. The issue with corruption seems to be limited to specific NFS implementations using Filesystem type but, if this issue doesn't exist on Cinder or CephFS then ReadWriteMany for the Filesystem type is an alternative to constraining the registry scale for multi-node access.

    The documentation is correct for bare metal given RWO storage but is also required to be RWO due to block requires special handling at https://docs.openshift.com/container-platform/4.13/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html#installation-registry-storage-block-recreate-rollout-bare-metal_configuring-registry-storage-baremetal

  26. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions