OCPBUGS-44995: Update the storage.conf configuration file template

[kwilczynski]

- What I did

Updated current storage.conf configuration file template to reflect changes made over time to the upstream dependencies such as containers/storage package, etc. The changes include:

• Move the size attribute from the storage table into the specific file system driver table
• Update the runroot property from the storage table to reflect changes to the temporary directory default location
• Mention the storage.options table Remap-User/Group settings precedence over Remap-UIDs/GIDs when both are set
• Remove the storage.options.thinpool table entirely, as the support for DeviceMapper driver has been removed
• Disable the partial container image downloads as it is still considered an experimental feature that should be opt-in
• Add use_hard_links and ostree_repos properties to storage.options.pull_options table with their default values

Related:

• Move storage options to driver specific entries containers/storage#432
• Switch references of /var/run -> /run containers/storage#790
• options: enable Remap-User/Group setting containers/storage#1620
• Remove devicemapper storage driver containers/storage#1622
• Disable partial pulls (zstd:chunked) by default containers/storage#2156
• podman + latest c-storage: thinpool throws a warning containers/podman#22473

- How to verify it

Run a test OpenShift cluster using ClusterBot that references this Pull Request, or manually apply configuration file changes against a running CRI-O instance and reload the configuration file or restart the service itself.

- Description for the changelog

Update the storage.conf configuration file template to reflect changes made over time to the upstream dependencies.

[kwilczynski]

/assign kwilczynski

[kwilczynski]

@giuseppe and @mtrmac, please have a look. Thank you!

[kwilczynski]

@haircommander, please have a look when you have a moment. Thank you!

[haircommander]

/approve

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[kwilczynski]

/retest

[LorbusChris]

/approve

[LorbusChris]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: haircommander, kwilczynski, LorbusChris

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [LorbusChris]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[LorbusChris]

/label acknowledge-critical-fixes-only

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-44995, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

- What I did

Updated current storage.conf configuration file template to reflect changes made over time to the upstream dependencies such as containers/storage package, etc. The changes include:

• Move the size attribute from the storage table into the specific file system driver table
• Update the runroot property from the storage table to reflect changes to the temporary directory default location
• Mention the storage.options table Remap-User/Group settings precedence over Remap-UIDs/GIDs when both are set
• Remove the storage.options.thinpool table entirely, as the support for DeviceMapper driver has been removed
• Disable the partial container image downloads as it is still considered an experimental feature that should be opt-in
• Add use_hard_links and ostree_repos properties to storage.options.pull_options table with their default values

Related:

• Move storage options to driver specific entries containers/storage#432
• Switch references of /var/run -> /run containers/storage#790
• options: enable Remap-User/Group setting containers/storage#1620
• Remove devicemapper storage driver containers/storage#1622
• Disable partial pulls (zstd:chunked) by default containers/storage#2156
• podman + latest c-storage: thinpool throws a warning containers/podman#22473

- How to verify it

Run a test OpenShift cluster using ClusterBot that references this Pull Request, or manually apply configuration file changes against a running CRI-O instance and reload the configuration file or restart the service itself.

- Description for the changelog

Update the storage.conf configuration file template to reflect changes made over time to the upstream dependencies.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-44995, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-44995, which is invalid:

• expected the bug to target only the "4.19.0" version, but multiple target versions were set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kwilczynski]

/jira refresh

[openshift-ci-robot]

@kwilczynski: This pull request references Jira Issue OCPBUGS-44995, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 7ba69ba and 2 for PR HEAD 18a0dc6 in total

[openshift-ci-robot]

@kwilczynski: Jira Issue OCPBUGS-44995: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#4681

Jira Issue OCPBUGS-44995 has been moved to the MODIFIED state.

In response to this:

- What I did

Updated current storage.conf configuration file template to reflect changes made over time to the upstream dependencies such as containers/storage package, etc. The changes include:

• Move the size attribute from the storage table into the specific file system driver table
• Update the runroot property from the storage table to reflect changes to the temporary directory default location
• Mention the storage.options table Remap-User/Group settings precedence over Remap-UIDs/GIDs when both are set
• Remove the storage.options.thinpool table entirely, as the support for DeviceMapper driver has been removed
• Disable the partial container image downloads as it is still considered an experimental feature that should be opt-in
• Add use_hard_links and ostree_repos properties to storage.options.pull_options table with their default values

Related:

• Move storage options to driver specific entries containers/storage#432
• Switch references of /var/run -> /run containers/storage#790
• options: enable Remap-User/Group setting containers/storage#1620
• Remove devicemapper storage driver containers/storage#1622
• Disable partial pulls (zstd:chunked) by default containers/storage#2156
• podman + latest c-storage: thinpool throws a warning containers/podman#22473

- How to verify it

Run a test OpenShift cluster using ClusterBot that references this Pull Request, or manually apply configuration file changes against a running CRI-O instance and reload the configuration file or restart the service itself.

- Description for the changelog

Update the storage.conf configuration file template to reflect changes made over time to the upstream dependencies.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[kwilczynski]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@kwilczynski: new pull request created: #4719

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

/cherry-pick release-4.16

[openshift-cherrypick-robot]

@kwilczynski: new pull request created: #4720

In response to this:

/cherry-pick release-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@kwilczynski: new pull request created: #4721

In response to this:

/cherry-pick release-4.15

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

/cherry-pick release-4.14

[openshift-cherrypick-robot]

@kwilczynski: new pull request created: #4722

In response to this:

/cherry-pick release-4.14

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kwilczynski]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@kwilczynski: new pull request created: #4751

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.