Skip to content

UI - Fixes cannot add new port forwarding rules after auto select VM next time#5690

Merged
DaanHoogland merged 1 commit intoapache:4.16from
EWERK-DIGITAL:feature/fix-port-forwading-rules
Dec 30, 2021
Merged

UI - Fixes cannot add new port forwarding rules after auto select VM next time#5690
DaanHoogland merged 1 commit intoapache:4.16from
EWERK-DIGITAL:feature/fix-port-forwading-rules

Conversation

@utchoang
Copy link
Copy Markdown

This PR fixes #5688

Description

After adding a new port forwarding for the first time, the user cannot add the next time because the OK button is disabled.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

How Has This Been Tested?

@utchoang
Copy link
Copy Markdown
Author

@blueorangutan ui

@blueorangutan
Copy link
Copy Markdown

@utchoang a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan
Copy link
Copy Markdown

UI build: ✔️
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5690 (SL-JID-830)

@yadvr yadvr added this to the 4.16.1.0 milestone Nov 18, 2021
@yadvr
Copy link
Copy Markdown
Member

yadvr commented Nov 18, 2021

Needs testing, lgtm

Copy link
Copy Markdown
Contributor

@Pearl1594 Pearl1594 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified fix. LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants