Various documentation updates and fixes #492
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci-robot
added
needs-rebase
FAQ.md
Outdated
| There is currently an issue with using Fedora CoreOS 33 for UPI installations. Please use the FCOS 32 image. After installation, the nodes will have rebooted and updated to the latest stable FCOS 33. | ||
| ======= | ||
| There is currently an issue with using Fedora CoreOS 33 for UPI installations. Please use the FCOS 32 image. After installation, the nodes will have rebooted and updated to the latest stable FCOS 33. For example, you can use the [FCOS 32 .ova image](https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/32.20201104.3.0/x86_64/fedora-coreos-32.20201104.3.0-vmware.x86_64.ova) for vSphere installations. | ||
| >>>>>>> 0cbed72... Various documentation updates and fixes |
There was a problem hiding this comment.
Please fix this rebase conflict
KNOWN_ISSUES.md
Outdated
| **Description:** Cluster upgrades will fail due to incorrect image signatures. | ||
| **Workaround:** Perform the upgrade in the terminal using the --force flag | ||
| ```bash | ||
| oc adm upgrade --to-latest=true --force=true |
There was a problem hiding this comment.
If you already tried to upgrade above command won't be enough.
Output will be like:
oc adm upgrade --to-latest=true --force=true
error: already upgrading.
Reason: ImageVerificationFailed
Message: Unable to apply 4.6.0-0.okd-2021-01-23-132511: the image may not be safe to use
If you want to upgrade anyway, use --allow-upgrade-with-warnings.
There was a problem hiding this comment.
And then:
# oc adm upgrade --to-latest=true --force=true --allow-upgrade-with-warnings
warning: --allow-upgrade-with-warnings is bypassing: already upgrading.
Reason: ImageVerificationFailed
Message: Unable to apply 4.6.0-0.okd-2021-01-23-132511: the image may not be safe to use
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to latest version 4.6.0-0.okd-2021-01-23-132511
There was a problem hiding this comment.
Right, we should add oc adm upgrade --reset && oc adm update .. instead
There was a problem hiding this comment.
Added --reset before forced upgrade and use of --allow-upgrade-with-warnings for forced upgrade.
vrutkovs
reviewed
Jan 29, 2021
FAQ.md
Outdated
| @@ -121,8 +121,7 @@ accessible and user workloads would be evicted and rescheduled as nodes are upda | |||
|
|
|||
| ## Should I use Fedora CoreOS 32 or 33 for installing on User Provisioned Infrastructure? | |||
|
|
|||
| There is currently an issue with using Fedora CoreOS 33 for UPI installations. Please use the FCOS 32 image. After installation, the nodes will have rebooted and updated to the latest stable FCOS 33. | |||
|
|
|||
| There is currently an issue with using Fedora CoreOS 33 for UPI installations. Please use the FCOS 32 image. After installation, the nodes will have rebooted and updated to the latest stable FCOS 33. For example, you can use the [FCOS 32 .ova image](https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/32.20201104.3.0/x86_64/fedora-coreos-32.20201104.3.0-vmware.x86_64.ova) for vSphere installations. | |||
There was a problem hiding this comment.
I don't think its still actual. F33 as a base should work fine.
Lets remove this and then re-add if folks complain?
Add link to Known Issues adding reset and --allow-upgrade-with-warnings flag fix merge remove question on FCOS versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates to the FAQ, Known Issues, README.