Bug 1969535
| Summary: | Topology edit icon does not link correctly when branch name contains slash | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Mohammed Saud <msaud> |
| Component: | Dev Console | Assignee: | Mohammed Saud <msaud> |
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> |
| Severity: | medium | Docs Contact: | Srivaralakshmi Ramani <srr> |
| Priority: | medium | ||
| Version: | 4.6 | CC: | aos-bugs, dsantra, gamore, hmishra, nmukherj |
| Target Milestone: | --- | Flags: | srr:
needinfo-
|
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, the topology URLs created for deployments using Bitbucket repository in the {product-title} web console did not work if they included a branch name that contained a slash character. This was due to an issue with the Bitbucket API (link:https://jira.atlassian.com/browse/BCLOUD-9969[BCLOUD-9969]). The current release mitigates this issue. If a branch name contains a slash, the topology URLs point to the default branch page for the repository. This issue will be fixed in a future release of {product-title}. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1969535[*BZ#1969535*]).
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 23:12:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1969536 | ||
|
Description
Mohammed Saud
2021-06-08 14:44:19 UTC
verified on 4.8.0-0.nightly-2021-06-09-023740 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 |