Prioritize User Experience

Oct 13, 2025 by magicalceylontours.com 14 views

Describe the Bug

When attempting to clone a virtual machine (VM) in Harvester, users may encounter a peculiar issue. Upon inputting a name with an invalid character, the UI displays an error message, but the button's CSS style appears distorted, and a null message is shown next to the error button. This behavior is not only visually unappealing but also confusing for users, as it does not provide clear information about the error.

To Reproduce

To replicate this issue, follow these steps:

Step 1: Create a Harvester Cluster

Create a Harvester cluster with either one or three nodes. The number of nodes does not seem to affect the outcome, so either configuration should work.

Step 2: Clone a VM

Clone a VM and input a name with an invalid character, such as vm1_clone. This name contains an underscore, which is not a valid character for VM names in Harvester.

Expected Behavior

The expected behavior is that the button height should be fixed, and the null error message should be removed or replaced with an appropriate error message. This would provide users with clear information about the error and allow them to correct it.

Support Bundle

Unfortunately, a support bundle is not available for this issue.

Environment

The environment in which this issue was encountered is as follows:

Harvester ISO Version: harvester-v1.5.0-rc1
Number of Nodes: 3

Additional Context

No additional context is available for this issue.

Root Cause Analysis

The root cause of this issue is likely related to the way Harvester handles invalid characters in VM names. When an invalid character is input, the UI displays a null error message, which is not a clear or helpful error message. This can be confusing for users, who may not understand what the error message means or how to correct it.

Solution

To resolve this issue, Harvester developers should modify the code to handle invalid characters in VM names more robustly. This could involve displaying a clear error message that indicates what is wrong with the input, such as "Invalid character in VM name." Additionally, the button height should be fixed to prevent the distorted appearance.

Workaround

Until the issue is resolved, users can work around it by avoiding the use of invalid characters in VM names. This may require users to rename their VMs to use only valid characters.

Conclusion

The issue of cloning a VM with an invalid character showing a null error in the UI is a bug that needs to be addressed. By understanding the root cause of the issue and implementing a solution, Harvester developers can improve the user experience and provide a more robust and user-friendly interface.

Future Development

In future development, Harvester developers should prioritize improving the handling of invalid characters in VM names. This could involve implementing more robust error checking and displaying clear error messages that provide users with helpful information about what is wrong with their input.

Recommendations

Based on the analysis of this issue, the following recommendations are made:

Improve Error Handling: Modify the code to handle invalid characters in VM names more robustly, displaying clear error messages that indicate what is wrong with the input.
Fix Button Height: Fix the button height to prevent the distorted appearance.
Prioritize User Experience: Prioritize improving the user experience by providing clear and helpful error messages that provide users with information about what is wrong with their input.

Q: What is the issue with cloning a VM in Harvester?

A: When attempting to clone a VM in Harvester, users may encounter an issue where the UI displays an error message, but the button's CSS style appears distorted, and a null message is shown next to the error button.

Q: What is the expected behavior when cloning a VM?

A: The expected behavior is that the button height should be fixed, and the null error message should be removed or replaced with an appropriate error message.

Q: What is the root cause of this issue?

A: The root cause of this issue is likely related to the way Harvester handles invalid characters in VM names. When an invalid character is input, the UI displays a null error message, which is not a clear or helpful error message.

Q: How can users work around this issue?

A: Users can work around this issue by avoiding the use of invalid characters in VM names. This may require users to rename their VMs to use only valid characters.

Q: What is the solution to this issue?

A: To resolve this issue, Harvester developers should modify the code to handle invalid characters in VM names more robustly. This could involve displaying a clear error message that indicates what is wrong with the input, such as "Invalid character in VM name." Additionally, the button height should be fixed to prevent the distorted appearance.

Q: Is there a support bundle available for this issue?

A: Unfortunately, a support bundle is not available for this issue.

Q: What is the environment in which this issue was encountered?

A: The environment in which this issue was encountered is as follows:

Harvester ISO Version: harvester-v1.5.0-rc1
Number of Nodes: 3

Q: Is there any additional context available for this issue?

A: No additional context is available for this issue.

Q: What are the recommendations for resolving this issue?

A: Based on the analysis of this issue, the following recommendations are made:

Improve Error Handling: Modify the code to handle invalid characters in VM names more robustly, displaying clear error messages that indicate what is wrong with the input.
Fix Button Height: Fix the button height to prevent the distorted appearance.
Prioritize User Experience: Prioritize improving the user experience by providing clear and helpful error messages that provide users with information about what is wrong with their input.

Q: How can users provide feedback on this issue?

A: Users can provide feedback on this issue by submitting a support request or reporting the issue on the Harvester community forum.

Q: Is this issue a bug or a feature request?

A: This issue is a bug, as it is a problem with the current implementation of Harvester that is causing unexpected behavior.

Q: Can users expect a fix for this issue in the near future?

A: While there is no guarantee of a fix for this issue in the near future, Harvester developers are actively working to improve the user experience and resolve known issues. Users can expect regular updates and improvements to the Harvester platform.