Skip to content

Conversation

@bergerhoffer
Copy link
Contributor

@bergerhoffer bergerhoffer commented Sep 10, 2024

Version(s):
4.17

Issue:
https://issues.redhat.com/browse/OSDOCS-11308

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Note to peer reviewers: These files are automatically generated. I can't fix anything manually here, but if you see any issues, we can fix it in the appropriate eng repo.

@bergerhoffer bergerhoffer added this to the Planned for 4.17 GA milestone Sep 10, 2024
@openshift-ci openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 10, 2024
@bergerhoffer
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Sep 10, 2024
@bergerhoffer
Copy link
Contributor Author

@zhouying7780 Can you please QE review?

oc adm node-image monitor --ip-addresses 192.168.111.83
# Monitor multiple nodes being added to a cluster by separating each
IP address with a comma
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Note that I've submitted a fix for this line (should be commented out) here: openshift/oc#1872

@ShaunaDiaz ShaunaDiaz added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Sep 10, 2024
@ShaunaDiaz
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 10, 2024
[source,bash,options="nowrap"]
----
# Create the ISO image and download it in the current folder
oc adm node-image create

Choose a reason for hiding this comment

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

error: stat nodes-config.yaml: no such file or directory```
command failed. 

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@zhouying7780 if I look at the help for oc adm node-image create, it does say this:

A nodes-config.yaml config file must be created to provide the required initial configuration for the selected nodes.

So I think this means that this file must exist (either in the current folder for this command, or in the /tmp/assets/ folder for the next command) for these commands to work.

Choose a reason for hiding this comment

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

That's correct. If the --dir option is not configured (and no single node flag is used), by default the asset is equal to the current working directory

oc adm node-image create
# Use a different assets folder
oc adm node-image create --dir=/tmp/assets

Choose a reason for hiding this comment

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

same here : ./oc adm node-image create --dir=/tmp/assets error: stat nodes-config.yaml: no such file or directory

Choose a reason for hiding this comment

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

In this example the nodes-config.yaml it's expected to be in the /tmp/assets folder

oc adm node-image create --dir=/tmp/assets
# Specify a custom image name
oc adm node-image create --o=my-node.iso

Choose a reason for hiding this comment

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

error: unknown flag: --o
See 'oc adm node-image create --help' for usage```

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this is supposed to be

Suggested change
oc adm node-image create --o=my-node.iso
oc adm node-image create -o=my-node.iso

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll submit a PR to fix this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Submitted openshift/oc#1874 to fix this in the oc repo for next time. Also manually fixed it here in this PR

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 16, 2024
@openshift-ci
Copy link

openshift-ci bot commented Sep 16, 2024

New changes are detected. LGTM label has been removed.

@openshift-ci
Copy link

openshift-ci bot commented Sep 16, 2024

@bergerhoffer: 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.

@zhouying7780
Copy link

/lgtm

@bergerhoffer bergerhoffer merged commit 6db26c4 into openshift:main Sep 24, 2024
@bergerhoffer
Copy link
Contributor Author

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@bergerhoffer: new pull request created: #82345

In response to this:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.17 peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants