[release-4.16] OCPBUGS-36147: Bump fedora-coreos-config

[coreosbot-releng]

Created by GitHub workflow (source).

Jonathan Lebon (2):
      growfs: set PKNAME and partnum in multipath path
      growfs: workaround sfdisk + LUKS incompatibility on 512e disks

[openshift-ci-robot]

@coreosbot-releng: This pull request references Jira Issue OCPBUGS-35410, which is invalid:

• expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.17.0" instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected Jira Issue OCPBUGS-35410 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Created by GitHub workflow (source).

Jonathan Lebon (2):
     growfs: set PKNAME and partnum in multipath path
     growfs: workaround sfdisk + LUKS incompatibility on 512e disks

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.

[travier]

/lgtm
/label backport-risk-assessed
/label cherry-pick-approved

[travier]

/retest

[travier]

/retitle OCPBUGS-36147: Bump fedora-coreos-config

[openshift-ci-robot]

@coreosbot-releng: This pull request references Jira Issue OCPBUGS-36147, which is invalid:

• expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.17.0" instead
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected Jira Issue OCPBUGS-36147 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Created by GitHub workflow (source).

Jonathan Lebon (2):
     growfs: set PKNAME and partnum in multipath path
     growfs: workaround sfdisk + LUKS incompatibility on 512e disks

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.

[travier]

/retitle [release-4.16] OCPBUGS-36147: Bump fedora-coreos-config

[travier]

/jira refresh

[openshift-ci-robot]

@travier: This pull request references Jira Issue OCPBUGS-36147, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected Jira Issue OCPBUGS-36147 to depend on a bug targeting a version in 4.17.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

/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.

[travier]

/jira refresh

[openshift-ci-robot]

@travier: This pull request references Jira Issue OCPBUGS-36147, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
• expected dependent Jira Issue OCPBUGS-35410 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

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.

[travier]

Error: Parsing metadata from src/config/tests/kola/shared/root-reprovision/luks/512e/test.sh: yaml: unmarshal errors:
  line 25: field primaryDisk not found in type kola.externalTestMeta
2024-06-25T09:37:52Z cli: Parsing metadata from src/config/tests/kola/shared/root-reprovision/luks/512e/test.sh: yaml: unmarshal errors:
  line 25: field primaryDisk not found in type kola.externalTestMeta
failed to execute cmd-kola: exit status 1

Needs a backport of coreos/coreos-assembler#3822

[jlebon]

/retest

[jlebon]

/jira refresh

[openshift-ci-robot]

@jlebon: This pull request references Jira Issue OCPBUGS-36147, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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.

[jlebon]

/jira refresh

[openshift-ci-robot]

@jlebon: This pull request references Jira Issue OCPBUGS-36147, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-35410 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-35410 targets the "4.17.0" version, which is one of the valid target versions: 4.17.0
• bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

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.

[sdodson]

/label staff-eng-approved

[jlebon]

/test images
/test rhcos-9-build-test-qemu

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 4729d1f and 2 for PR HEAD 9c8420c in total

[jlebon]

Hmm weird, still seems to be using a stale 4.16 cosa.

[travier]

/test images

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: coreosbot-releng, marmijo, travier

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 [marmijo,travier]

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

[jlebon]

/retest

[jlebon]

Logs for ci/prow/images shows

FROM image-registry.openshift-image-registry.svc:5000/ci-op-0yq7b11x/pipeline@sha256:45edfa461413c22e52c9094f7220250512c43d753a21bde72964661350ff097b

which matches

$ skopeo inspect --no-tags docker://quay.io/coreos-assembler/coreos-assembler:rhcos-4.16 | jq .Digest
"sha256:45edfa461413c22e52c9094f7220250512c43d753a21bde72964661350ff097b"

So rhcos-9-build-test-qemu should pass now.

I'm honestly confused by the mess in openshift/release related to the coreos-assembler image. There's references there and in the logs here that there's a :4.16 tag in the coreos/coreos-assembler imagestream, but I don't see that in either https://console.build02.ci.openshift.org/k8s/ns/coreos/imagestreams/coreos-assembler or https://console-openshift-console.apps.ci.l2s4.p1.openshiftapps.com/k8s/ns/coreos/imagestreams/coreos-assembler.

[openshift-ci]

@coreosbot-releng: all tests passed!

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

[openshift-ci-robot]

@coreosbot-releng: Jira Issue OCPBUGS-36147: All pull requests linked via external trackers have merged:

• openshift/os#1538

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

In response to this:

Created by GitHub workflow (source).

Jonathan Lebon (2):
     growfs: set PKNAME and partnum in multipath path
     growfs: workaround sfdisk + LUKS incompatibility on 512e disks

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.