-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS#11308: Generating CLI docs for 4.17 #81546
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
Conversation
|
/label peer-review-needed |
|
@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 |
There was a problem hiding this comment.
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
|
/lgtm |
| [source,bash,options="nowrap"] | ||
| ---- | ||
| # Create the ISO image and download it in the current folder | ||
| oc adm node-image create |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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```
There was a problem hiding this comment.
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
| oc adm node-image create --o=my-node.iso | |
| oc adm node-image create -o=my-node.iso |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
2950284 to
b4a5203
Compare
|
New changes are detected. LGTM label has been removed. |
|
@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. |
|
/lgtm |
|
/cherrypick enterprise-4.17 |
|
@bergerhoffer: new pull request created: #82345 In response to this:
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. |
Version(s):
4.17
Issue:
https://issues.redhat.com/browse/OSDOCS-11308
Link to docs preview:
QE review:
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.