Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Resize volume API validation errors are not displayed in the UI

Open Beginner friendly
#14,222 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend

Research direction

Open ResizeVolume.vue and trace the resize request's error handling, then compare it with the common $notifyError(error) helper. Test the invalid-size resize flow from the Volumes page; done means the backend validation message appears for command-specific responses such as resizevolumeresponse.

Written by the indexing model from the issue text.

Description

bug
problem

When resizing a volume with an invalid value, such as a negative size, the backend returns a validation error, but the UI does not display it.
ResizeVolume.vue expects the error under errorresponse. For known commands such as resizeVolume, CloudStack returns it under resizevolumeresponse. Accessing the wrong response key hides the original validation message.

versions

The versions of ACS, hypervisors, storage, network etc..

checked on 4.23

The steps to reproduce the bug
  1. Open the Volumes page.
  2. Select a volume and choose Resize Volume.
  3. Enter an invalid size, such as 2.5.
  4. Submit the request.
  5. Observe that the backend validation error is not displayed in the UI at all.
What to do about it?

Replace the hardcoded error-response lookup in ResizeVolume.vue with the common $notifyError(error) helper. This helper finds and displays errortext regardless of the command-specific response key.

even after clicking on okay I see no error for it.

Image

after the fix:

Image Image
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 20h
Merged PRs (30d)
27

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/cloudstack

All issues in apache/cloudstack

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.