diff options
Diffstat (limited to 'docs/sections/release_notes/release-notes-frankfurt.rst')
| -rw-r--r-- | docs/sections/release_notes/release-notes-frankfurt.rst | 48 |
1 files changed, 24 insertions, 24 deletions
diff --git a/docs/sections/release_notes/release-notes-frankfurt.rst b/docs/sections/release_notes/release-notes-frankfurt.rst index c0374a6dd8..db515dc480 100644 --- a/docs/sections/release_notes/release-notes-frankfurt.rst +++ b/docs/sections/release_notes/release-notes-frankfurt.rst @@ -55,36 +55,36 @@ New features **Bug fixes** A list of issues resolved in this release can be found here: -https://jira.onap.org/projects/OOM/versions/10826 +https://lf-onap.atlassian.net/projects/OOM/versions/10826 **Known Issues** -- `OOM-1237 <https://jira.onap.org/browse/OOM-1237>`_ Source Helm Charts from +- `OOM-1237 <https://lf-onap.atlassian.net/browse/OOM-1237>`_ Source Helm Charts from ONAP Repo. Having helm charts repo is not possible for Frankfurt release. -- `OOM-1720 <https://jira.onap.org/browse/OOM-1237>`_ galera container is +- `OOM-1720 <https://lf-onap.atlassian.net/browse/OOM-1237>`_ galera container is outdated. containers used for mariadb are outdated and not supported anymore. -- `OOM-1817 <https://jira.onap.org/browse/OOM-1817>`_ Use of global.repository +- `OOM-1817 <https://lf-onap.atlassian.net/browse/OOM-1817>`_ Use of global.repository inconsistent across Helm Charts. it's then may be hard to retrieve some containers when deploying in constrained environment. -- `OOM-2075 <https://jira.onap.org/browse/OOM-2075>`_ Invalid MTU for Canal CNI +- `OOM-2075 <https://lf-onap.atlassian.net/browse/OOM-2075>`_ Invalid MTU for Canal CNI interfaces -- `OOM-2227 <https://jira.onap.org/browse/OOM-2227>`_ Cassandra Backup Mechanism +- `OOM-2227 <https://lf-onap.atlassian.net/browse/OOM-2227>`_ Cassandra Backup Mechanism works only on "static PV" mode. -- `OOM-2230 <https://jira.onap.org/browse/OOM-2230>`_ Missing requests/limits +- `OOM-2230 <https://lf-onap.atlassian.net/browse/OOM-2230>`_ Missing requests/limits for some PODS. This can lead to "memory bombing" so cautious monitoring of Kubernetes resources usage must be set up. -- `OOM-2279 <https://jira.onap.org/browse/OOM-2279>`_ OOM El Alto and master +- `OOM-2279 <https://lf-onap.atlassian.net/browse/OOM-2279>`_ OOM El Alto and master clamp mariadb resources doesn't match chart. -- `OOM-2285 <https://jira.onap.org/browse/OOM-2285>`_ deploy.sh does not work +- `OOM-2285 <https://lf-onap.atlassian.net/browse/OOM-2285>`_ deploy.sh does not work for mariadb-galera. deploy script doesn't behave well with "-" in the component name. -- `OOM-2369 <https://jira.onap.org/browse/OOM-2369>`_ DMAAP Helm install takes +- `OOM-2369 <https://lf-onap.atlassian.net/browse/OOM-2369>`_ DMAAP Helm install takes too long and often fails. -- `OOM-2418 <https://jira.onap.org/browse/OOM-2418>`_ Readiness-check 2.0.2 not +- `OOM-2418 <https://lf-onap.atlassian.net/browse/OOM-2418>`_ Readiness-check 2.0.2 not working properly for stateful set. -- `OOM-2421 <https://jira.onap.org/browse/OOM-2421>`_ OOM NBI chart deployment +- `OOM-2421 <https://lf-onap.atlassian.net/browse/OOM-2421>`_ OOM NBI chart deployment error. In some case, NBI deployment fails. -- `OOM-2422 <https://jira.onap.org/browse/OOM-2422>`_ Portal App is unreachable +- `OOM-2422 <https://lf-onap.atlassian.net/browse/OOM-2422>`_ Portal App is unreachable when deploying without HTTPs @@ -107,21 +107,21 @@ Known Vulnerabilities Workarounds ----------- -- `OOM-1237 <https://jira.onap.org/browse/OOM-1237>`_ Workaround is to generate +- `OOM-1237 <https://lf-onap.atlassian.net/browse/OOM-1237>`_ Workaround is to generate them as explained in documentation. -- `OOM-1817 <https://jira.onap.org/browse/OOM-1817>`_ Workaround is to use +- `OOM-1817 <https://lf-onap.atlassian.net/browse/OOM-1817>`_ Workaround is to use offline installer if needed. -- `OOM-2227 <https://jira.onap.org/browse/OOM-2227>`_ Workaround is to stick to +- `OOM-2227 <https://lf-onap.atlassian.net/browse/OOM-2227>`_ Workaround is to stick to "static PV" (so, not using storage class) if backup is needed. -- `OOM-2285 <https://jira.onap.org/browse/OOM-2285>`_ Workaround is to use +- `OOM-2285 <https://lf-onap.atlassian.net/browse/OOM-2285>`_ Workaround is to use directly helm upgrade if needed. -- `OOM-2369 <https://jira.onap.org/browse/OOM-2369>`_ Workaround is to play +- `OOM-2369 <https://lf-onap.atlassian.net/browse/OOM-2369>`_ Workaround is to play postinstall jobs by hand. -- `OOM-2418 <https://jira.onap.org/browse/OOM-2418>`_ Workaround is to use +- `OOM-2418 <https://lf-onap.atlassian.net/browse/OOM-2418>`_ Workaround is to use version 2.2.2 in global part of override file if the new check is needed. -- `OOM-2421 <https://jira.onap.org/browse/OOM-2421>`_ Workaround is to +- `OOM-2421 <https://lf-onap.atlassian.net/browse/OOM-2421>`_ Workaround is to undeploy/redeploy NBI. -- `OOM-2422 <https://jira.onap.org/browse/OOM-2422>`_ Workaround is to create +- `OOM-2422 <https://lf-onap.atlassian.net/browse/OOM-2422>`_ Workaround is to create first portal app service with service type Cluster IP then changing it to NodePort or LoadBalancer so all the port are available. @@ -131,9 +131,9 @@ Security Notes **Fixed Security Issues** - In default deployment OOM (consul-server-ui) exposes HTTP port 30270 outside - of cluster. [`OJSI-134 <https://jira.onap.org/browse/OJSI-134>`_] + of cluster. [`OJSI-134 <https://lf-onap.atlassian.net/browse/OJSI-134>`_] - CVE-2019-12127 - OOM exposes unprotected API/UI on port 30270 - [`OJSI-202 <https://jira.onap.org/browse/OJSI-202>`_] + [`OJSI-202 <https://lf-onap.atlassian.net/browse/OJSI-202>`_] References ========== @@ -147,6 +147,6 @@ For more information on the ONAP Frankfurt release, please see: .. _`ONAP Home Page`: https://www.onap.org -.. _`ONAP Wiki Page`: https://wiki.onap.org +.. _`ONAP Wiki Page`: https://lf-onap.atlassian.net/wiki .. _`ONAP Documentation`: https://docs.onap.org .. _`ONAP Release Downloads`: https://git.onap.org |