- Problem
-
The TCP stack fails to deploy on servers in the Bare Metal Orchestrator cluster that were onboarded with the ESXI operating system installed. (MWV-11322) - Resolution
- The TCP stack deployment now succeeds in the Bare Metal Orchestrator.
|
- Problem
-
During the upgrade process from release 1.3.x to 1.4.0, the Helm pods in the RKE2 cluster are stuck in the pending state. (MWV-11351) - Resolution
- The Helm pods work as expected when upgrading .
|
- Problem
-
When upgrading from release 1.3.x to 1.4.0, the NGINX and TFTP pods get deployed on the CP2 and CP3 nodes instead of the CP1 node. This causes an error when uploading files to the web server. (MWV-11353) - Resolution
-
The NGINX and TFTP pods work on all nodes. |
- Problem
-
After performing an upgrade on HA deployments from 1.4.1 to 1.4.2, the OpenSearch pods are being deleted with only one pod running. (MWV-12497) - Resolution
-
All OpenSearch pods are running as expected after performing the upgrade. |
- Problem
-
In the web user interface, when attempts were made to onboard a large number of servers (500 or more, for example) using a CSV file, only a limited number of servers were successfully migrated. (MWV-12750) - Resolution
- You can now onboard large number of servers from web user interface.
|
- Problem
-
When scaling down the prometheus pod and requesting event APIs, the response time takes too long and returns a 401 error message. (MWV-12826) - Resolution
- Response time is as expected.
|
- Problem
-
Downloading events in the Bare Metal Orchestrator web user interface is failing because of token expiration. (MWV-13179) - Resolution
-
You can now download events using the Bare Metal Orchestrator web user interface. |
- Problem
-
Audit logs for the maintenance mode feature are not being generated in the OpenSearch dashboards. (MWV-13180) - Resolution
- The audit logs for maintenance mode are generated in the OpenSearch dashboards.
|
- Problem
-
Onboarding a server using the Bare Metal Orchestrator web user interface without providing credentials fails, even when the server credentials were previously added under Settings > BMC Credentials. (MWV-13249) - Resolution
-
You can now onboard a server using the Bare Metal Orchestrator web user interface. |
- Problem
-
Logs do not display in the custom installer when using Firefox. This occurs when trying to access an HTTPS resource that has an invalid certificate. (MWV-15424) - Resolution
- Add an exception to Firefox: .
|
- Problem
-
The Customer Installer GUI does not launch with the Firefox browser because of self-signed certificates. (MWV-15855) - Resolution
- Click Help in the Firefox menu, then select More troubleshooting information. Click Refresh Firefox and confirm the action to reset Firefox.
|
- Problem
-
Server deletion fails and the server goes into a crashloopback state. (MWV-15932) - Resolution
- Server deletion works as expected.
|
- Problem
-
When installing Bare Metal Orchestrator on high availability setups with Longhorn, and when auto-discovery is enabled for sites, the discovery-manager or the dhcp-server pod gets stuck at the container creating the state. (MWV-16432) - Resolution
- Installation works as expected.
|