Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prefer podman authentication file locations #37726

Merged

Conversation

atiratree
Copy link
Member

@atiratree atiratree commented Mar 27, 2023

we want to remove preference for docker auth files in favor of podman ones in openshift/oc#1376. Since openshift/release depends on the cli (oc) to obtain and manipulate images and releases, we need to first merge the changes in openshift/ci-tools#3345 and then here before the changes in oc can be merged. This change was announced in 4.10 and a proper warning was shown when using oc commands that work with registries since then.

  • podman ~/.docker/config.json is deprecated in favor of podman authentication file locations (default is ${XDG_RUNTIME_DIR}/containers/auth.json)
  • oc registry login will try to write to this location so XDG_RUNTIME_DIR environment variable must be present and the XDG_RUNTIME_DIR directory created/accessible. Places that need to manipulate with ~/.docker/config.json for backwards compatibility reasons need to specify --to or --registry-config
  • other oc commands that lookup credentials from registry authentication files will first try the podman locations and if the credentials are not found, oc will fallback and check ~/.docker/config.json

@openshift-ci-robot
Copy link
Contributor

@atiratree: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-azure-disk-csi-driver-release-4.9-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-master-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.15-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.14-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.13-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.12-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.11-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.10-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.9-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.8-e2e-azure openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-master-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.15-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.14-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.13-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.12-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.11-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.10-e2e-azure-csi openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.10-e2e-azure-csi-migration openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-disk-csi-driver-release-4.9-e2e-azure-csi-migration openshift/azure-disk-csi-driver presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.10-e2e-azure-file-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.9-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-master-e2e-azure-ovn openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.15-e2e-azure-ovn openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.14-e2e-azure-ovn openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.13-e2e-azure-ovn openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.12-e2e-azure-ovn openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.11-e2e-azure openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.10-e2e-azure openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.9-e2e-azure openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.8-e2e-azure openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-master-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.15-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.14-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.13-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed
pull-ci-openshift-cluster-storage-operator-release-4.12-e2e-azure-csi openshift/cluster-storage-operator presubmit Registry content changed

A total of 2459 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse refresh to get an updated list of affected jobs (useful if you have new pushes to the branch)

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

echo "ERROR Registry config file not found: $REGISTRY_TOKEN_FILE"
echo " Is the docker/config.json in a different location?"
echo "ERROR Registry authentication file not found: $REGISTRY_TOKEN_FILE"
echo " Is the auth.json in a different location?"
exit 1
fi
oc registry login
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this PR changes only places that depend on ~/.docker/config.json, eg. plain oc registry login. Other invocations of oc registry login that write to a different file were not changed in this PR as they are not required to be updated to comply with openshift/oc#1376.

There are still many mention of docker/config.json and we can update these in a followup as these will be mostly cosmetic changes.

@@ -18,6 +18,10 @@ fi
MIRROR_REGISTRY_HOST=`head -n 1 "${SHARED_DIR}/mirror_registry_url"`
echo "MIRROR_REGISTRY_HOST: $MIRROR_REGISTRY_HOST"

export HOME="${HOME:-/tmp/home}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if HOME variable is always exposed in all of these so I am adding it to make sure we always have it.

@@ -167,6 +167,11 @@ objects:
value: /tmp/artifacts
- name: HOME
value: /tmp/home
- name: XDG_RUNTIME_DIR
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these changes should be identical to changes here openshift/ci-tools#3345

@@ -64,16 +66,16 @@ echo "INFO Image tag is $IMAGE_TAG"
# Setup registry credentials
REGISTRY_TOKEN_FILE="$SECRETS_PATH/$REGISTRY_SECRET/$REGISTRY_SECRET_FILE"

config_file="$HOME/.docker/config.json"
config_file="${XDG_RUNTIME_DIR}/containers/auth.json"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assisted-baremetal-images-publish, assisted-baremetal-operator-publish, opendatahub-io-ci-image-mirror and red-hat-data-services-ci-image-mirror seem to be used only up to 4.10 so these should be okay to change


if [[ -n "${INSTALL_INITIAL_RELEASE}" && -n "${RELEASE_IMAGE_INITIAL}" ]]; then
echo "Installing from initial release ${RELEASE_IMAGE_INITIAL}"
OPENSHIFT_INSTALL_RELEASE_IMAGE_OVERRIDE="${RELEASE_IMAGE_INITIAL}"
elif [[ "${CLUSTER_VARIANT}" =~ "mirror" ]]; then
# mirror the release image and override the release image to point to the mirrored one
mkdir /tmp/.docker && cp /etc/openshift-installer/pull-secret /tmp/.docker/config.json
mkdir "${XDG_RUNTIME_DIR}/containers" && cp /etc/openshift-installer/pull-secret "${XDG_RUNTIME_DIR}/containers/auth.json"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm, this seems it might brake eg. release-openshift-ocp-installer-e2e-aws-csi-4.9. Need to test and we probably have to support the ~docker/config.json for the old releases

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have reverted these and using .docker/config.js to ensure it works for older versions

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-ocp-installer-e2e-aws-csi-4.9 pull-ci-openshift-assisted-service-master-push-pr-image periodic-ci-red-hat-data-services-notebooks-release-2023a-notebook-jupyter-pytorch-ubi9-python-3-9-image-mirror-weekly

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-ocp-installer-e2e-aws-csi-4.9

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): release-openshift-ocp-installer-e2e-aws-csi-4.9 either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree
Copy link
Member Author

/pj-rehearse pull-ci-openshift-assisted-service-master-push-pr-image

@atiratree
Copy link
Member Author

/pj-rehearse periodic-ci-red-hat-data-services-notebooks-release-2023a-notebook-jupyter-pytorch-ubi9-python-3-9-image-mirror-weekly

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-origin-installer-e2e-aws-shared-vpc-4.9

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): release-openshift-origin-installer-e2e-aws-shared-vpc-4.9 either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-origin-installer-e2e-azure-shared-vpc-4.9

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-origin-installer-e2e-aws-disruptive-4.9

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): release-openshift-origin-installer-e2e-azure-shared-vpc-4.9 either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree
Copy link
Member Author

/pj-rehearse release-openshift-ocp-installer-e2e-aws-mirrors-4.9

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): release-openshift-origin-installer-e2e-aws-disruptive-4.9 either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree
Copy link
Member Author

/pj-rehearse periodic-ci-openshift-cluster-autoscaler-operator-e2e-aws-master

@openshift-ci-robot
Copy link
Contributor

@atiratree: job(s): periodic-ci-openshift-cluster-autoscaler-operator-e2e-aws-master either don't exist or were not found to be affected, and cannot be rehearsed

@atiratree atiratree force-pushed the prefer-podman-auth branch 2 times, most recently from 6690f43 to bcc8c5d Compare March 28, 2023 12:39
- podman ~/.docker/config.json is deprecated in favor of podman
  authentication file locations (default is
  ${XDG_RUNTIME_DIR}/containers/auth.json)
- oc registry login will try to write to this location so
  XDG_RUNTIME_DIR environment variable must be present and the XDG_RUNTIME_DIR
  directory created/accessible. Places that need to manipulate with
  ~/.docker/config.json for backwards compatibility reasons should specify
  --to or --registry-config
- other oc commands that lookup credentials from registry authentication files
  will first try the podman locations and if the credentials are not found,
  oc will fallback and check ~/.docker/config.json
@atiratree
Copy link
Member Author

/pj-rehearse refresh

@openshift-ci-robot
Copy link
Contributor

@atiratree: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-azure-file-csi-driver-release-4.10-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.10-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-master-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.15-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.14-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.13-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.12-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.11-e2e-azure-file-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-master-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.15-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.14-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.13-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.12-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-azure-file-csi-driver-release-4.11-e2e-azure-file-nfs-csi openshift/azure-file-csi-driver presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-master-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.15-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.14-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.13-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.12-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.11-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.10-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.9-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.8-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.7-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.6-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.5-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.4-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.3-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-cluster-api-actuator-pkg-release-4.2-e2e-azure-operator openshift/cluster-api-actuator-pkg presubmit Registry content changed
pull-ci-openshift-image-registry-master-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed
pull-ci-openshift-image-registry-release-4.15-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed
pull-ci-openshift-image-registry-release-4.14-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed
pull-ci-openshift-image-registry-release-4.13-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed
pull-ci-openshift-image-registry-release-4.12-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed
pull-ci-openshift-image-registry-release-4.11-e2e-agnostic-image-registry openshift/image-registry presubmit Registry content changed

A total of 2462 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 jobs.

A full list of affected jobs can be found here

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse refresh to get an updated list of affected jobs (useful if you have new pushes to the branch)

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@atiratree
Copy link
Member Author

/pj-rehearse

@atiratree
Copy link
Member Author

the rehearse failures do not seem to be connected to these changes

@atiratree
Copy link
Member Author

/pj-rehearse

@atiratree
Copy link
Member Author

the additional rehearse failures do not seem to be relevant as well

@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d 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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2023
@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d 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

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 2, 2023
@atiratree
Copy link
Member Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 5, 2023
Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2023
@atiratree
Copy link
Member Author

/pj-rehearse max

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2023

@atiratree: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/azure-file-csi-driver-operator/release-4.15/e2e-azure-file-csi 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-azure-file-csi-driver-operator-release-4.15-e2e-azure-file-csi
ci/rehearse/openshift/oauth-server/release-4.14/e2e-agnostic-upgrade 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-oauth-server-release-4.14-e2e-agnostic-upgrade
ci/rehearse/openshift/machine-api-provider-nutanix/main/e2e-nutanix-operator 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-main-e2e-nutanix-operator
ci/rehearse/openshift/origin/release-4.15/e2e-agnostic-ovn-cmd 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-origin-release-4.15-e2e-agnostic-ovn-cmd
ci/rehearse/periodic-ci-kata-containers-kata-containers-main-e2e-tests 5cb6c26 link unknown /pj-rehearse periodic-ci-kata-containers-kata-containers-main-e2e-tests
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.14/e2e-nutanix-operator 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.14-e2e-nutanix-operator
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.13/e2e-nutanix 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.13-e2e-nutanix
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.12/e2e-nutanix-operator 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.12-e2e-nutanix-operator
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.14/e2e-nutanix 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.14-e2e-nutanix
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.15/e2e-nutanix 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.15-e2e-nutanix
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.15/e2e-nutanix-operator 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.15-e2e-nutanix-operator
ci/rehearse/openshift/machine-api-provider-nutanix/main/e2e-nutanix 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-main-e2e-nutanix
ci/rehearse/openshift/origin/release-4.15/e2e-azure 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-origin-release-4.15-e2e-azure
ci/rehearse/openshift/cluster-etcd-operator/release-4.3/e2e-aws-disruptive 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-cluster-etcd-operator-release-4.3-e2e-aws-disruptive
ci/rehearse/openshift/machine-api-provider-nutanix/release-4.12/e2e-nutanix 5cb6c26 link unknown /pj-rehearse pull-ci-openshift-machine-api-provider-nutanix-release-4.12-e2e-nutanix
ci/rehearse/periodic-ci-kata-containers-kata-containers-main-4.11-e2e-tests 5cb6c26 link unknown /pj-rehearse periodic-ci-kata-containers-kata-containers-main-4.11-e2e-tests

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@bear-redhat
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: atiratree, bear-redhat, soltysh

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2023
@atiratree
Copy link
Member Author

/pj-rehearse ack

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jun 8, 2023
@openshift-merge-robot openshift-merge-robot merged commit 1122e12 into openshift:master Jun 8, 2023
39 of 54 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2023

@atiratree: Updated the following 24 configmaps:

  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster build03 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster vsphere using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build01 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster build02 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster build01 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster build02 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster build05 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster vsphere using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster build01 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build02 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster build03 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster multi01 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster app.ci using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster build04 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster multi01 using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build04 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster multi01 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster app.ci using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster build04 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-custom-test-image configmap in namespace ci at cluster app.ci using the following files:
    • key cluster-launch-installer-custom-test-image.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-custom-test-image.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build03 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster build05 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster build05 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster vsphere using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml

In response to this:

we want to remove preference for docker auth files in favor of podman ones in openshift/oc#1376. Since openshift/release depends on the cli (oc) to obtain and manipulate images and releases, we need to first merge the changes in openshift/ci-tools#3345 and then here before the changes in oc can be merged. This change was announced in 4.10 and a proper warning was shown when using oc commands that work with registries since then.

  • podman ~/.docker/config.json is deprecated in favor of podman authentication file locations (default is ${XDG_RUNTIME_DIR}/containers/auth.json)
  • oc registry login will try to write to this location so XDG_RUNTIME_DIR environment variable must be present and the XDG_RUNTIME_DIR directory created/accessible. Places that need to manipulate with ~/.docker/config.json for backwards compatibility reasons need to specify --to or --registry-config
  • other oc commands that lookup credentials from registry authentication files will first try the podman locations and if the credentials are not found, oc will fallback and check ~/.docker/config.json

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/test-infra repository.

jtaleric pushed a commit to jtaleric/release that referenced this pull request Jun 9, 2023
- podman ~/.docker/config.json is deprecated in favor of podman
  authentication file locations (default is
  ${XDG_RUNTIME_DIR}/containers/auth.json)
- oc registry login will try to write to this location so
  XDG_RUNTIME_DIR environment variable must be present and the XDG_RUNTIME_DIR
  directory created/accessible. Places that need to manipulate with
  ~/.docker/config.json for backwards compatibility reasons should specify
  --to or --registry-config
- other oc commands that lookup credentials from registry authentication files
  will first try the podman locations and if the credentials are not found,
  oc will fallback and check ~/.docker/config.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
6 participants