Skip to content

Bug Fixes for ODC 4.7 #30299

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.

Sign up for GitHub

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

Merged
Preeticp merged 1 commit into from
Mar 18, 2021
Merged

Bug Fixes for ODC 4.7 #30299

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions release_notes/ocp-4-7-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1258,6 +1258,10 @@ If you are using the option `--keep-manifest-list=true`, the only valid value fo

* Previously, monitoring alerts with severity levels such as `critical` and `warning` were treated as `info` level alerts. As a result, the *Monitoring Alert* icon was not displayed on the workload in the *Topology* view for these alerts. This issue is now fixed; alerts like `critical` are treated as `warning` level alerts and a *Monitoring Alert* icon is displayed. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1925200[*BZ#1925200*])

* Previously, in the *YAML view* of the Helm installation form only the YAML code was shown. Now a *Schema* viewer is added in the YAML editor to show the schema and its description. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1886861[*BZ#1886861*])

* Previously, all Pods were failing with the `ErrImagePull` and `ImagePullBackOff` errors, even after an Image Pull Secret was added to access the external private image container registry. This is because the image download failed as it had no permissions for the external image registry and the cluster tried to load the container image directly from the external URL without the provided secret. As a result, the deployment was stuck until the service account or deployment was updated manually. Now, the issue is fixed and new deployments can start pods from the internal private container registry and import a container image from an external private container registry without any additional changes to the service account or deployment. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1924955[*BZ#1924955*])

*DNS*

* Previously, a cluster might experience intermittent DNS resolution errors because the `/etc/hosts` file on some nodes included invalid entries. With this release, DNS resolution no longer fails because of an `/etc/hosts` file with invalid entries. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1882485[*BZ#1882485*])
Expand Down