Skip to content

Conversation

@cheesesashimi
Copy link
Member

@cheesesashimi cheesesashimi commented Feb 1, 2023

- What I did

The OS release node detection was not correctly detecting RHCOS 9 OSes due to the VERSION_ID field being populated with the OCP version instead of the OS version.

- How to verify it

  1. Run the unit test suite.
  2. Deploy an OCP cluster running either RHCOS 8 or RHCOS 9 (for RHCOS 9, provision a cluster using ClusterBot pointed at Switch to rhel-coreos-9 #3485).
  3. Run the e2e test suite. The e2e test will output additional log entries indicating the node OS and, in the case of RHCOS 8 or 9, the version it is running, which should match the RHEL_VERSION field in the /etc/os-release / /usr/lib/os-release files on the node.

These logs will resemble:

go test -v -count=1 -run="TestOSDetection" .
=== RUN   TestOSDetection
=== RUN   TestOSDetection/#00
=== PAUSE TestOSDetection/#00
=== RUN   TestOSDetection/#01
=== PAUSE TestOSDetection/#01
=== RUN   TestOSDetection/#02
=== PAUSE TestOSDetection/#02
=== RUN   TestOSDetection/#03
=== PAUSE TestOSDetection/#03
=== RUN   TestOSDetection/#04
=== PAUSE TestOSDetection/#04
=== RUN   TestOSDetection/#05
=== PAUSE TestOSDetection/#05
=== CONT  TestOSDetection/#00
=== CONT  TestOSDetection/#03
=== CONT  TestOSDetection/#02
=== CONT  TestOSDetection/#04
=== CONT  TestOSDetection/#01
=== CONT  TestOSDetection/#05
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-173-134.ec2.internal with version 8.6
=== CONT  TestOSDetection/#04
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-163-214.ec2.internal with version 8.6
=== CONT  TestOSDetection/#01
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-138-110.ec2.internal with version 8.6
=== CONT  TestOSDetection/#00
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-134-197.ec2.internal with version 8.6
=== CONT  TestOSDetection/#02
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-147-135.ec2.internal with version 8.6
=== CONT  TestOSDetection/#03
    mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-152-25.ec2.internal with version 8.6
--- PASS: TestOSDetection (0.08s)
    --- PASS: TestOSDetection/#05 (0.67s)
    --- PASS: TestOSDetection/#04 (0.67s)
    --- PASS: TestOSDetection/#01 (0.70s)
    --- PASS: TestOSDetection/#00 (0.73s)
    --- PASS: TestOSDetection/#02 (0.74s)
    --- PASS: TestOSDetection/#03 (0.83s)
PASS
ok      github.com/openshift/machine-config-operator/test/e2e   1.566s

- Description for the changelog
Fixes node OS detection

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 1, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 1, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

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

/approve
/lgtm
Looks sane to me, though I'd say I think at some point we should do feature detection (e.g. rpm -q openssh) - that way it'd work automatically on Alma Linux too etc.

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

Agreed about the feature detection. I guess the big TODO there is determining which features we need and understanding how to determine whether those features are there (e.g., rpm -q openssh, rpm-ostree version, etc.).

@cheesesashimi cheesesashimi changed the title fixes node OS detection OCPBUGS-6945: Fixes node OS detection Feb 1, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 1, 2023
@openshift-ci-robot
Copy link
Contributor

@cheesesashimi: This pull request references Jira Issue OCPBUGS-6945, which is invalid:

  • expected the bug to target the "4.13.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.

Details

In response to this:

- What I did

The OS release node detection was not correctly detecting RHCOS 9 OSes due to the VERSION_ID field being populated with the OCP version instead of the OS version.

- How to verify it

  1. Deploy an OCP cluster running RHCOS 9.
  2. Run the e2e test suite.
  3. Run the unit test suite.

- Description for the changelog
Fixes node OS detection

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-robot
Copy link
Contributor

@cheesesashimi: This pull request references Jira Issue OCPBUGS-6945, which is invalid:

  • expected the bug to target the "4.13.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.

Details

In response to this:

- What I did

The OS release node detection was not correctly detecting RHCOS 9 OSes due to the VERSION_ID field being populated with the OCP version instead of the OS version.

- How to verify it

  1. Run the unit test suite.
  2. Deploy an OCP cluster running RHCOS 9 (e.g., provision a cluster using ClusterBot pointed at Switch to rhel-coreos-9 #3485).
  3. Run the e2e test suite. Depending on the underlying node OS, there will be additional entries in the MCO e2e test output log.

These logs will resemble:

go test -v -count=1 -run="TestOSDetection" .
=== RUN   TestOSDetection
=== RUN   TestOSDetection/#00
=== PAUSE TestOSDetection/#00
=== RUN   TestOSDetection/#01
=== PAUSE TestOSDetection/#01
=== RUN   TestOSDetection/#02
=== PAUSE TestOSDetection/#02
=== RUN   TestOSDetection/#03
=== PAUSE TestOSDetection/#03
=== RUN   TestOSDetection/#04
=== PAUSE TestOSDetection/#04
=== RUN   TestOSDetection/#05
=== PAUSE TestOSDetection/#05
=== CONT  TestOSDetection/#00
=== CONT  TestOSDetection/#03
=== CONT  TestOSDetection/#02
=== CONT  TestOSDetection/#04
=== CONT  TestOSDetection/#01
=== CONT  TestOSDetection/#05
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-173-134.ec2.internal with version 8.6
=== CONT  TestOSDetection/#04
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-163-214.ec2.internal with version 8.6
=== CONT  TestOSDetection/#01
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-138-110.ec2.internal with version 8.6
=== CONT  TestOSDetection/#00
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-134-197.ec2.internal with version 8.6
=== CONT  TestOSDetection/#02
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-147-135.ec2.internal with version 8.6
=== CONT  TestOSDetection/#03
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-152-25.ec2.internal with version 8.6
--- PASS: TestOSDetection (0.08s)
   --- PASS: TestOSDetection/#05 (0.67s)
   --- PASS: TestOSDetection/#04 (0.67s)
   --- PASS: TestOSDetection/#01 (0.70s)
   --- PASS: TestOSDetection/#00 (0.73s)
   --- PASS: TestOSDetection/#02 (0.74s)
   --- PASS: TestOSDetection/#03 (0.83s)
PASS
ok      github.com/openshift/machine-config-operator/test/e2e   1.566s

- Description for the changelog
Fixes node OS detection

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 removed the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2023
@cheesesashimi cheesesashimi marked this pull request as ready for review February 1, 2023 22:10
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 1, 2023
@cheesesashimi
Copy link
Member Author

/refresh jira

@openshift-ci openshift-ci bot requested review from cgwalters and jkyros February 1, 2023 22:14
Also repackages osrelease so it can be reused in e2e
@cheesesashimi cheesesashimi force-pushed the zzlotnik/OCPBUGS-6945 branch 2 times, most recently from 2d0693e to 5aa8f26 Compare February 1, 2023 22:52
@cheesesashimi
Copy link
Member Author

Now that I've fixed a few issues with the unit tests, I'd like both @cgwalters and @LorbusChris to weigh in on this PR.

@cheesesashimi
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid 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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 1, 2023
@openshift-ci-robot
Copy link
Contributor

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rioliu-rh

Details

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

@openshift-ci openshift-ci bot requested a review from rioliu-rh February 1, 2023 23:00
@openshift-ci-robot
Copy link
Contributor

@cheesesashimi: This pull request references Jira Issue OCPBUGS-6945, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.0) matches configured target version for branch (4.13.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @rioliu-rh

Details

In response to this:

- What I did

The OS release node detection was not correctly detecting RHCOS 9 OSes due to the VERSION_ID field being populated with the OCP version instead of the OS version.

- How to verify it

  1. Run the unit test suite.
  2. Deploy an OCP cluster running either RHCOS 8 or RHCOS 9 (for RHCOS 9, provision a cluster using ClusterBot pointed at Switch to rhel-coreos-9 #3485).
  3. Run the e2e test suite. The e2e test will output additional log entries indicating the node OS and, in the case of RHCOS 8 or 9, the version it is running, which should match the RHEL_VERSION field in the /etc/os-release / /usr/lib/os-release files on the node.

These logs will resemble:

go test -v -count=1 -run="TestOSDetection" .
=== RUN   TestOSDetection
=== RUN   TestOSDetection/#00
=== PAUSE TestOSDetection/#00
=== RUN   TestOSDetection/#01
=== PAUSE TestOSDetection/#01
=== RUN   TestOSDetection/#02
=== PAUSE TestOSDetection/#02
=== RUN   TestOSDetection/#03
=== PAUSE TestOSDetection/#03
=== RUN   TestOSDetection/#04
=== PAUSE TestOSDetection/#04
=== RUN   TestOSDetection/#05
=== PAUSE TestOSDetection/#05
=== CONT  TestOSDetection/#00
=== CONT  TestOSDetection/#03
=== CONT  TestOSDetection/#02
=== CONT  TestOSDetection/#04
=== CONT  TestOSDetection/#01
=== CONT  TestOSDetection/#05
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-173-134.ec2.internal with version 8.6
=== CONT  TestOSDetection/#04
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-163-214.ec2.internal with version 8.6
=== CONT  TestOSDetection/#01
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-138-110.ec2.internal with version 8.6
=== CONT  TestOSDetection/#00
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-134-197.ec2.internal with version 8.6
=== CONT  TestOSDetection/#02
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-147-135.ec2.internal with version 8.6
=== CONT  TestOSDetection/#03
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-152-25.ec2.internal with version 8.6
--- PASS: TestOSDetection (0.08s)
   --- PASS: TestOSDetection/#05 (0.67s)
   --- PASS: TestOSDetection/#04 (0.67s)
   --- PASS: TestOSDetection/#01 (0.70s)
   --- PASS: TestOSDetection/#00 (0.73s)
   --- PASS: TestOSDetection/#02 (0.74s)
   --- PASS: TestOSDetection/#03 (0.83s)
PASS
ok      github.com/openshift/machine-config-operator/test/e2e   1.566s

- Description for the changelog
Fixes node OS detection

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
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@cheesesashimi: 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/prow/okd-scos-e2e-aws-ovn 987f0a1 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-gcp-ovn-upgrade 987f0a1 link false /test okd-scos-e2e-gcp-ovn-upgrade
ci/prow/e2e-gcp-rt-op 987f0a1 link false /test e2e-gcp-rt-op
ci/prow/e2e-hypershift 987f0a1 link false /test e2e-hypershift
ci/prow/e2e-alibabacloud-ovn 987f0a1 link false /test e2e-alibabacloud-ovn

Full PR test history. Your PR dashboard.

Details

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.

@rioliu-rh
Copy link

rioliu-rh commented Feb 2, 2023

/hold
/cc @sergiordlr

@openshift-ci openshift-ci bot requested a review from sergiordlr February 2, 2023 02:51
@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2023

@rioliu-rh: GitHub didn't allow me to request PR reviews from the following users: for, qe, testing.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

/hold
/cc @sergiordlr for qe testing

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.

@rioliu-rh
Copy link

 oc debug node/ip-10-0-139-113.us-west-1.compute.internal -- chroot /host cat /etc/os-release
Temporary namespace openshift-debug-hgp9x is created for debugging node...
Starting pod/ip-10-0-139-113us-west-1computeinternal-debug ...
To use host binaries, run `chroot /host`
NAME="Red Hat Enterprise Linux CoreOS"
ID="rhcos"
ID_LIKE="rhel fedora"
VERSION="413.90.202212151724-0"
VERSION_ID="4.13"
VARIANT="CoreOS"
VARIANT_ID=coreos
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux CoreOS 413.90.202212151724-0 (Plow)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::coreos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://docs.openshift.com/container-platform/4.13/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="OpenShift Container Platform"
REDHAT_BUGZILLA_PRODUCT_VERSION="4.13"
REDHAT_SUPPORT_PRODUCT="OpenShift Container Platform"
REDHAT_SUPPORT_PRODUCT_VERSION="4.13"
OPENSHIFT_VERSION="4.13"
RHEL_VERSION="9.0"
OSTREE_VERSION="413.90.202212151724-0"

Removing debug pod ...
Temporary namespace openshift-debug-hgp9x was removed.
  • run unit test, test output is like below
go test -v -count=1 -run="TestOSDetection" .
=== RUN   TestOSDetection
=== RUN   TestOSDetection/#00
=== PAUSE TestOSDetection/#00
=== RUN   TestOSDetection/#01
=== PAUSE TestOSDetection/#01
=== RUN   TestOSDetection/#02
=== PAUSE TestOSDetection/#02
=== RUN   TestOSDetection/#03
=== PAUSE TestOSDetection/#03
=== RUN   TestOSDetection/#04
=== PAUSE TestOSDetection/#04
=== CONT  TestOSDetection/#00
=== CONT  TestOSDetection/#03
=== CONT  TestOSDetection/#04
=== CONT  TestOSDetection/#02
=== CONT  TestOSDetection/#01
=== CONT  TestOSDetection/#00
    node_os_test.go:68: Identified Red Hat Enterprise Linux CoreOS 9.0 on node ip-10-0-139-113.us-west-1.compute.internal
=== CONT  TestOSDetection/#01
    node_os_test.go:68: Identified Red Hat Enterprise Linux CoreOS 9.0 on node ip-10-0-154-69.us-west-1.compute.internal
=== CONT  TestOSDetection/#04
    node_os_test.go:68: Identified Red Hat Enterprise Linux CoreOS 9.0 on node ip-10-0-220-74.us-west-1.compute.internal
=== CONT  TestOSDetection/#03
    node_os_test.go:68: Identified Red Hat Enterprise Linux CoreOS 9.0 on node ip-10-0-183-67.us-west-1.compute.internal
=== CONT  TestOSDetection/#02
    node_os_test.go:68: Identified Red Hat Enterprise Linux CoreOS 9.0 on node ip-10-0-179-181.us-west-1.compute.internal
--- PASS: TestOSDetection (1.12s)
    --- PASS: TestOSDetection/#00 (20.86s)
    --- PASS: TestOSDetection/#01 (21.44s)
    --- PASS: TestOSDetection/#04 (21.47s)
    --- PASS: TestOSDetection/#03 (21.62s)
    --- PASS: TestOSDetection/#02 (22.63s)
PASS
ok  	github.com/openshift/machine-config-operator/test/e2e	25.005s

@rioliu-rh
Copy link

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 2, 2023
@rioliu-rh
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 2, 2023
@rioliu-rh
Copy link

@cheesesashimi @cgwalters verified with unit test, please confirm, thanks

@cheesesashimi
Copy link
Member Author

This failure in e2e-aws-ovn is related to https://issues.redhat.com/browse/TRT-819. I am reasonably confident it was not caused by the changes in this PR.

Copy link
Member

@cgwalters cgwalters left a comment

Choose a reason for hiding this comment

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

/lgtm

"path/filepath"
"strings"

"github.com/ashcrow/osrelease"
Copy link
Member

Choose a reason for hiding this comment

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

This is fine as is, but perhaps it'd make sense at some point to have this functionality move into that upstream library. We could also move it to e.g. github.com/coreos/osrelease too for more shared maintenance.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, that would be nice. I have a few ideas around some additional things we could port there such as handling paths, etc.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 3, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 3, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, cheesesashimi

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [cgwalters,cheesesashimi]

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

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 46ecd47 and 2 for PR HEAD 987f0a1 in total

@openshift-merge-robot openshift-merge-robot merged commit 944855d into openshift:master Feb 3, 2023
@openshift-ci-robot
Copy link
Contributor

@cheesesashimi: All pull requests linked via external trackers have merged:

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

Details

In response to this:

- What I did

The OS release node detection was not correctly detecting RHCOS 9 OSes due to the VERSION_ID field being populated with the OCP version instead of the OS version.

- How to verify it

  1. Run the unit test suite.
  2. Deploy an OCP cluster running either RHCOS 8 or RHCOS 9 (for RHCOS 9, provision a cluster using ClusterBot pointed at Switch to rhel-coreos-9 #3485).
  3. Run the e2e test suite. The e2e test will output additional log entries indicating the node OS and, in the case of RHCOS 8 or 9, the version it is running, which should match the RHEL_VERSION field in the /etc/os-release / /usr/lib/os-release files on the node.

These logs will resemble:

go test -v -count=1 -run="TestOSDetection" .
=== RUN   TestOSDetection
=== RUN   TestOSDetection/#00
=== PAUSE TestOSDetection/#00
=== RUN   TestOSDetection/#01
=== PAUSE TestOSDetection/#01
=== RUN   TestOSDetection/#02
=== PAUSE TestOSDetection/#02
=== RUN   TestOSDetection/#03
=== PAUSE TestOSDetection/#03
=== RUN   TestOSDetection/#04
=== PAUSE TestOSDetection/#04
=== RUN   TestOSDetection/#05
=== PAUSE TestOSDetection/#05
=== CONT  TestOSDetection/#00
=== CONT  TestOSDetection/#03
=== CONT  TestOSDetection/#02
=== CONT  TestOSDetection/#04
=== CONT  TestOSDetection/#01
=== CONT  TestOSDetection/#05
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-173-134.ec2.internal with version 8.6
=== CONT  TestOSDetection/#04
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-163-214.ec2.internal with version 8.6
=== CONT  TestOSDetection/#01
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-138-110.ec2.internal with version 8.6
=== CONT  TestOSDetection/#00
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-134-197.ec2.internal with version 8.6
=== CONT  TestOSDetection/#02
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-147-135.ec2.internal with version 8.6
=== CONT  TestOSDetection/#03
   mcd_test.go:55: Identified OS "Red Hat Enterprise Linux CoreOS" on node ip-10-0-152-25.ec2.internal with version 8.6
--- PASS: TestOSDetection (0.08s)
   --- PASS: TestOSDetection/#05 (0.67s)
   --- PASS: TestOSDetection/#04 (0.67s)
   --- PASS: TestOSDetection/#01 (0.70s)
   --- PASS: TestOSDetection/#00 (0.73s)
   --- PASS: TestOSDetection/#02 (0.74s)
   --- PASS: TestOSDetection/#03 (0.83s)
PASS
ok      github.com/openshift/machine-config-operator/test/e2e   1.566s

- Description for the changelog
Fixes node OS detection

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.

@cheesesashimi cheesesashimi deleted the zzlotnik/OCPBUGS-6945 branch March 21, 2024 14:03
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants