Chapter 5. Fixed issues
Chapter 5. Fixed issues This section lists issues fixed in Red Hat Developer Hub 1.3. 5.1. Fixed issues in 1.3.5 5.1.1. In the Helm chart, dynamic plugins PVC Storage class and Access mode are not configurable In the versions of the Developer Hub Helm Chart, it was not possible to configure the storage class and access mode to use in the dynamic plugins PVC created by the Chart. This could cause the Developer Hub Deployment to remain stuck forever in clusters without a default storage class or where the default storage class cannot be used. This issue has been fixed by making the whole dynamic plugins PVC specification configurable. This way, it is possible to configure various aspects of the PVC, like the storage class or the access mode. The following fields are now exposed in the Helm Chart: dynamicPlugins: cache: # -- Spec of the dynamic plugins root volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: null Additional resources RHIDP-5835 5.1.2. In the Helm chart, test-connection pod Image is hardcoded, which can be an issue in air-gapped environments In the versions of the Developer Hub Helm Chart, it was not possible to configure the image for the test-connection pod, which could be a problem for air-gapped environments. The test-connection pod is a Pod created by the Helm Chart when a user runs the helm test command to test a deployed Release. This issue has been fixed by making the image configurable and also allowing disabling the test-connection pod creation altogether. The following fields are now exposed in the Helm Chart: # -- Test pod parameters test: # -- Whether to enable the test-connection pod used for testing the Release using `helm test`. enabled: true image: # -- Test connection pod image registry registry: quay.io # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it. repository: curl/curl # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it. tag: latest Additional resources RHIDP-5837 5.1.3. In the Helm chart, the audit log PVC Storage class and Access mode are not configurable In the versions of the Developer Hub Helm Chart, it was not possible to configure the storage class and access mode to use in the audit log PVC created by the Chart. This could cause the Developer Hub Deployment to remain stuck forever in clusters without a default storage class or where the default storage class cannot be used. This issue has been fixed in this version by making the whole audit log PVC specification configurable. This way, it is possible to configure various aspects of the PVC, like the storage class or the access mode. Please note that the audit log PVC has been removed in 1.4. The following fields are now exposed in this release of the Helm Chart: auditLog: # -- Spec of the audit log volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi storageClassName: null Additional resources RHIDP-5839 5.2. Fixed issues in 1.3.4 5.2.1. GitLab Org plugin throws MODULE_NOT_FOUND error In the version of Developer Hub, the gitlab org catalog backend plugin would fail to load when configured with a MODULE_NOT_FOUND error. This has been fixed by embedding the missing dependencies in the dynamic plugins. See similar issue https://issues.redhat.com/browse/RHIDP-5308 Additional resources RHIDP-5477 5.3. Fixed issues in 1.3.3 5.3.1. Opting out of using Redis sets does not work Before this update, configuring the useRedisSets: false option resulted in the useRedisSets: true behaviour. With this update, you can now opt out of using Redis sets. It is recommended to clear your cache in order to remove any invalid keys. Additional resources RHIDP-5180 5.4. Fixed issues in 1.3.2 5.4.1. Impossible to report a documentation issue from selected documentation content Previously, the feature to report a documentation (techdoc) issue didn't work. When the user selected a text in the documentation, it showed a huge icon rather than a tooltip button. With this update, the user can select content in the documentation, and click the tooltip button to report a documentation issue. Additional resources RHIDP-5121 5.5. Fixed issues in 1.3.1 5.5.1. Conditional alias USDownerRefs does not work Before this update, a conditional alias that uses USDownerRefs did not work. With this update, a conditional alias can use USDownerRefs . Additional resources RHIDP-4069 5.6. Fixed issues in 1.3.0 5.6.1. Removed unnecessary pull secret from the Red Hat Developer Hub Helm Chart With this update, the Red Hat Developer Hub Helm Chart does not contain a pull secret that is no longer needed. Additional resources RHIDP-1334 5.6.2. Filtering for permissions policies that do not exist leads to an error being thrown Before this update, permission checks by the permission framework would throw an error if a matching permission policy was not previously defined. Therefore, Developer Hub denied the request with an error. With this update, Developer Hub denies the request without throwing an error. Additional resources RHIDP-2139 5.6.3. HTTP error code 431 when an user is member of many groups Before this update, Developer Hub API became unresponsive when a user was member of a high number of groups (more than 150) with aggregated relations. Therefore, the user might have failed to authenticate. Also, Developer Hub might have shown an error when opening the user entity in the UI. With this update, Developer Hub can handle a user member of a high number of groups (more than 150) with aggregated relations. Additional resources RHIDP-2412 5.6.4. OCM calls are not scoped to the OCM page Before this update, when the OCM plugin is installed, navigating to non-OCM pages triggered unnecessary failed OCM API calls. With this update, Developer Hub restricts OCM API calls to OCM-related pages. Additional resources RHIDP-2438 5.6.5. When login using azure entra sso, it will use id to match the user entity, which will fail to match with user entity imported by msgraph. Before this update, Developer Hub failed to resolve user entities with Azure authentication provider to entities ingested by the MsGraph catalog provider. Therefore, a user authentication with Microsoft Azure could not open a session in Developer Hub. With this update, Developer Hub resolves user entities with Azure authentication provider to entities ingested by the MsGraph catalog provider. Therefore, a user authentication with Microsoft Azure can open a session in Developer Hub. Additional resources RHIDP-2529 5.6.6. Replaced the deprecated backend.auth.keys field in the default configuration Before this update, in a Developer Hub deployment with the default configuration, the application logs displayed the deprecation warning. With this update, the default upstream.backstage.appConfig configuration uses the backend.auth.externalAccess field rather than the deprecated backend.auth.keys field. Additional resources RHIDP-2716 5.6.7. Handle PII logging in Application Logs With this update, Developer Hub does not include user IP addresses in the application logs. Additional resources RHIDP-2728 5.6.8. The last ~10 GitHub Pull Requests are missing from the list Before this update, Developer Hub ignored GitHub search API restrictions to list pull requests. Therefore, Developer Hub might have not displayed all pull requests. With this update, Developer Hub limits paging to max 1000 results to respect GitHub search API restrictions. Developer Hub show users when additional results are available, suggesting in a tooltip that they can refine their query to retrieve more specific results. Additional resources RHIDP-3159 5.6.9. rhtap installation always failed at RHDH due to Migration table is already locked Before this update, after updating a config map or a secret, when pods where restarting to apply the changes, they might have tried to simultaneous lock the database. The situation ended with a dead lock. With this update, Developer Hub handles simultaneous pod refreshing without a dead lock. Additional resources RHIDP-3217 5.6.10. Renamed optional secret dynamic-plugins-npmrc in helm chart Before this update, the Helm Chart was using an unversioned name for the dynamic-plugins-npmrc secret. Therefore subsequent Helm deployments of the RHDH Helm Chart version 1.2.1 failed after the first deployment with an error that a secret named dynamic-plugins-npmrc exists and is not owned by the current release. With this update, the Helm Chart creates and uses a dynamic-plugins-npmrc secret that is named in line with the other resources managed by the Helm Chart: <release-name> -dynamic-plugins-npmrc . As a result, the Helm Chart does not fail on the error. Additional resources RHIDP-3260 5.6.11. Backstage Specific Metrics no longer appear in /metrics endpoint Before this update, Developer Hub stopped displaying some metrics such as catalog metrics in the <RHDH_URL> /metrics endpoint. With this update, Developer Hub displays expected metrics in the /metrics endpoint. Additional resources RHIDP-3458 5.6.12. Theme issues with plugins using material 5 Before this update, Developer Hub had theme issues with plugins using Material UI (MUI) 5. With this update, Developer Hub includes additional MUI 5 related packages, added to the application shell as shared modules. Therefore, dynamic plugins that use MUI 5 components and tss-react can properly load the currently selected theme. This ensures that MUI 5 components have the correct colors and styling applied to them. While not strictly a requirement, if a dynamic plugin relies on MUI 5 components with a class name prefix, that behavior can be added to a frontend dynamic plugin by adding the following code to the plugin's index.ts: This update requires using a version of the @janus-idp/cli package > 1.13.1. Additional resources RHIDP-3471 5.6.13. Creating RBAC role with name that contains ':' or '/' creates a role that does nothing and cannot be deleted Before this update, creating an RBAC role with name that contains ':' or '/' through the REST API (or RBAC admin panel in the UI) created a role that did nothing and could not be deleted. Although the name of the role showed up in full as written in the POST request, when clicked on for more information about the role it showed only the part of the name written before the first ':' or '/'. Also while the list of RBAC roles did list how many policies were added to the role, when clicking on the role for more information it displayed no users or policies. With this udpate, Developer Hub validates more strictly role and namespace names in accordance with backstage validation: Developer Hub invalidates role names that do not conform with the format: Strings of length at least 1, and at most 63. Must consist of sequences of [a-z0-9A-Z] possibly separated by one of [-_.] . Developer Hub invalidates namespaces that do not conform with the format: Strings of length at least 1, and at most 63. Must be sequences of [a-zA-Z0-9] , possibly separated by - . Additional resources RHIDP-3580 5.6.14. Update contitional policies and policies loaded from files when these files are deleted Before this update, conditional policies and policies loaded from files remained active after the corresponding policy files were removed from the configuration. With this update, conditional policies and policies loaded from files are removed after the corresponding policy files are removed from the configuration. Additional resources RHIDP-3601 5.6.15. Fixed the timestamp inserted by catalog:timestamping Before this update, the timestamp in the catalog-info.yaml created by the catalog:timestamping action by the backstage-scaffolder-backend-module-annotator plugin was different from the execution time of the template. With this update, a unique timestamp is generated on each execution of the template. Additional resources RHIDP-3612 5.6.16. Added missing virtual machine details to the sidebar Before this update, when a user displayed the virtual machine details in the sidebar, the icon corresponding to virtual machine was not shown. With this update, the missing icons have been added. Therefore, when a user displays the virtual machine details in the sidebar, an icon shows the virtual machine status. Additional resources RHIDP-3735 5.6.17. Authenticate with GitHub a user absent in the software catalog when dangerouslyAllowSignInWithoutUserInCatalog is set to true Before this update, authentication with Github failed when the dangerouslyAllowSignInWithoutUserInCatalog field was set to true and the user was absent from the software catalog. With this update, when the dangerouslyAllowSignInWithoutUserInCatalog field is set to true, you can authenticate to Developer Hub with a user absent from the software catalog. Additional resources RHIDP-3896 5.6.18. The Developer Hub image defined in the custom resource takes precedence on the image defined in the environment variable Before this update, when the Developer Hub image was configured in both the custom resource and in the 'RELATED_IMAGE_backstage' environment variable, the image defined in the custom resource was not used. With this update, the custom resource configuration takes precedence and is applied. Additional resources RHIDP-4013 5.6.19. Updated the search dropdown to display results for a large number of users or groups Before this update, in the RBAC administration page, the members dropdown was not able to load a large number of users or groups. Therefore, the Developer Hub administrator was not able to select required users or groups to add to the role. With this update, the dropdown displays initially up to 100 users or groups shown and updates the display once the user starts to search. The search happens across the whole data-set and displays the first 100 results. The user must refine their search to narrow the results to a list containing the desired user or group. Therefore, even with larger numbers or users/groups, the Developer Hub administrator can add required users or groups to the role. Additional resources RHIDP-4046 5.6.20. Bundled ArgoCD plugin with dynamic frontent assets Before this update, the ArgoCD plugin was bundled with dynamic backend plugin assets rather than dynamic frontend plugin assets. Therefore the ArgoCD plugin failed to load. With this update, the ArgoCD plugin is bundled with dynamic frontend plugin assets. Therefore the ArgoCD plugin can load properly. Additional resources RHIDP-4200 5.7. Fixed issues in 1.2.2 5.7.1. Added missing plugin name in the RBAC administration interface Before this update, the RBAC administration user interface Permission Policies table did not display the plugin name. With this update, the RBAC administration user interface Permission Policies table displays the plugin name. Additional resources RHIDP-2374
dynamicPlugins: cache: # -- Spec of the dynamic plugins root volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 5Gi storageClassName: null -- Test pod parameters test: # -- Whether to enable the test-connection pod used for testing the Release using `helm test`. enabled: true image: # -- Test connection pod image registry registry: quay.io # -- Test connection pod image repository. Note that the image needs to have both the `sh` and `curl` binaries in it. repository: curl/curl # -- Test connection pod image tag. Note that the image needs to have both the `sh` and `curl` binaries in it. tag: latest auditLog: # -- Spec of the audit log volume claim. # Note that, by default, this is set to use the default storage class, if available in the cluster. volumeClaimSpec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi storageClassName: null import { unstable_ClassNameGenerator as ClassNameGenerator } from &#39;@mui/material/className&#39;; ClassNameGenerator.configure(componentName =&gt; { return componentName.startsWith(&#39;v5-&#39;) ? componentName : `v5-USD{componentName}`; })