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

Bug 2011460: UPSTREAM: <carry>: openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc. #1005

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #983

/assign dagrayvid

…ift.build.versions, etc.

For example, consider the current 4.10 RHCOS:

  $ oc image info -o json registry.ci.openshift.org/ocp/4.10:machine-os-content | jq -r '.config.config.Labels | to_entries[] | .key + ": " + .value' | grep '^io\.k8s\|^io\.openshift'
  io.k8s.description: The Universal Base Image is designed and engineered to be the base layer for all of your containerized applications, middleware and utilities. This base image is freely redistributable, but Red Hat only supports Red Hat technologies through subscriptions for Red Hat products. This image is maintained by Red Hat and updated regularly.
  io.k8s.display-name: Red Hat Universal Base Image 8
  io.openshift.build.version-display-names: machine-os=Red Hat Enterprise Linux CoreOS
  io.openshift.build.versions: machine-os=49.84.202109102026-0
  io.openshift.expose-services:
  io.openshift.tags: base rhel8

A bunch of those seem to be inherited from the UBI base image, so we
can leave them alone.  But the io.openshift.build.* entries are
RHCOS-specific, and are consumed by 'oc adm release new ...' [1,2] and
friends to answer questions like "which RHCOS is in this release?":

  $ oc adm release info -o json quay.io/openshift-release-dev/ocp-release:4.8.12-x86_64 | jq .displayVersions
  {
    "kubernetes": {
      "Version": "1.21.1",
      "DisplayName": ""
    },
    "machine-os": {
      "Version": "48.84.202109100857-0",
      "DisplayName": "Red Hat Enterprise Linux CoreOS"
    }
  }

Setting this label will avoid failures when consumers like
driver-toolkit's version consumer [3]:

  name: 0.0.1-snapshot-machine-os

bump into ci-tools-built machine-os-content images that lack the
io.openshift.build.versions declaration of machine-os version [4]:

  error: unable to create a release: unknown version reference "machine-os"

I've gone with generic testing values, so hopefully this is not
something that local maintainers need to remember to bump for each
OpenShift z stream.

[1]: https://github.com/openshift/oc/blob/f94afb52dc8a3185b3b9eacaf92ec34d80f8708d/pkg/cli/admin/release/image_mapper.go#L328-L334
[2]: https://github.com/openshift/oc/blob/f94afb52dc8a3185b3b9eacaf92ec34d80f8708d/pkg/cli/admin/release/annotations.go#L19-L28
[3]: openshift/driver-toolkit@464acca#diff-4caed9b2b966a8fa7a016ae28976634a2d3d1b635c4e820d5c038b2305d6af53R18
[4]: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_kubernetes/959/pull-ci-openshift-kubernetes-master-images/1438398678602616832#1:build-log.txt%3A97
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

@openshift-ci
Copy link

openshift-ci bot commented Oct 6, 2021

@openshift-cherrypick-robot: Bugzilla bug 2008619 has been cloned as Bugzilla bug 2011460. Retitling PR to link against new bug.
/retitle [release-4.8] [release-4.9] Bug 2011460: UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.

In response to this:

[release-4.8] [release-4.9] Bug 2008619: UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.

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.

@openshift-ci openshift-ci bot changed the title [release-4.8] [release-4.9] Bug 2008619: UPSTREAM: <carry>: openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc. [release-4.8] [release-4.9] Bug 2011460: UPSTREAM: <carry>: openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc. Oct 6, 2021
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 6, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 6, 2021

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2011460, which is invalid:

  • expected dependent Bugzilla bug 2008619 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

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

In response to this:

[release-4.8] [release-4.9] Bug 2011460: UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.

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.

@openshift-ci openshift-ci bot requested review from marun and soltysh October 6, 2021 16:05
@wking
Copy link
Member

wking commented Oct 6, 2021

/retitle Bug 2011460: UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.

No need to keep building up release-4.y markers in the title, because GitHub tracks that as structured PR-base metadata.

@openshift-ci openshift-ci bot changed the title [release-4.8] [release-4.9] Bug 2011460: UPSTREAM: <carry>: openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc. Bug 2011460: UPSTREAM: <carry>: openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc. Oct 6, 2021
@kpouget
Copy link

kpouget commented Oct 8, 2021

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 8, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 8, 2021

@kpouget: This pull request references Bugzilla bug 2011460, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.z) matches configured target release for branch (4.8.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2008619 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2008619 targets the "4.9.0" release, which is one of the valid target releases: 4.9.0
  • bug has dependents

Requesting review from QA contact:
/cc @wabouhamad

In response to this:

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

@openshift-ci openshift-ci bot requested a review from wabouhamad October 8, 2021 07:16
@openshift-ci
Copy link

openshift-ci bot commented Oct 8, 2021

@dagrayvid: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

  • /test configmap-scale
  • /test e2e-agnostic-cmd
  • /test e2e-aws
  • /test e2e-aws-csi
  • /test e2e-aws-downgrade
  • /test e2e-aws-fips
  • /test e2e-aws-jenkins
  • /test e2e-aws-multitenant
  • /test e2e-aws-ovn
  • /test e2e-aws-serial
  • /test e2e-aws-upgrade
  • /test e2e-azure
  • /test e2e-azure-upgrade
  • /test e2e-gcp
  • /test e2e-gcp-upgrade
  • /test e2e-metal-ipi
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere
  • /test images
  • /test integration
  • /test k8s-e2e-conformance-aws
  • /test k8s-e2e-gcp
  • /test k8s-e2e-gcp-serial
  • /test unit
  • /test verify
  • /test verify-commits

The following commands are available to trigger optional jobs:

  • /test e2e-aws-csi-migration
  • /test e2e-aws-disruptive
  • /test e2e-aws-single-node

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-kubernetes-release-4.8-configmap-scale
  • pull-ci-openshift-kubernetes-release-4.8-e2e-agnostic-cmd
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-csi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-downgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-fips
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-jenkins
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-multitenant
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-ovn
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-serial
  • pull-ci-openshift-kubernetes-release-4.8-e2e-aws-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure
  • pull-ci-openshift-kubernetes-release-4.8-e2e-azure-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-e2e-gcp-upgrade
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-kubernetes-release-4.8-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-kubernetes-release-4.8-e2e-vsphere
  • pull-ci-openshift-kubernetes-release-4.8-images
  • pull-ci-openshift-kubernetes-release-4.8-integration
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-conformance-aws
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp
  • pull-ci-openshift-kubernetes-release-4.8-k8s-e2e-gcp-serial
  • pull-ci-openshift-kubernetes-release-4.8-unit
  • pull-ci-openshift-kubernetes-release-4.8-verify
  • pull-ci-openshift-kubernetes-release-4.8-verify-commits

In response to this:

/retest required

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.

@dagrayvid
Copy link

/retest-required

1 similar comment
@kpouget
Copy link

kpouget commented Oct 9, 2021

/retest-required

@kpouget
Copy link

kpouget commented Oct 9, 2021

/retest

@kpouget
Copy link

kpouget commented Oct 9, 2021 via email

Copy link

@wabouhamad wabouhamad 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 Oct 11, 2021
@dagrayvid
Copy link

/cc @sttts
/assign @soltysh

@kpouget
Copy link

kpouget commented Oct 14, 2021

ping @sttts, we need this PR for merging the DriverToolkit imagestream in 4.8
[this PR prevents a breakage of openshift/kubernetes presubmit testing that we observed with 4.10 after merging the DriverToolkit PR]

@sttts
Copy link

sttts commented Oct 14, 2021

/approve

@sttts sttts removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 14, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 14, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sttts, wabouhamad

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 Oct 14, 2021
@kpouget
Copy link

kpouget commented Oct 15, 2021

@sttts I'm not sure who to ask for backport-risk-assessed label, z-stream approvers are missing from https://github.com/openshift/release/blob/master/core-services/prow/02_config/openshift/kubernetes/_pluginconfig.yaml

@sdodson sdodson added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Oct 15, 2021
@openshift-merge-robot openshift-merge-robot merged commit 6438632 into openshift:release-4.8 Oct 15, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 15, 2021

@openshift-cherrypick-robot: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 2011460 has not been moved to the MODIFIED state.

In response to this:

Bug 2011460: UPSTREAM: : openshift-hack/images/os/Dockerfile: Add io.openshift.build.versions, etc.

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

10 participants