Fix null host tags while creating a zone#8976
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8976 +/- ##
=============================================
+ Coverage 13.17% 15.28% +2.11%
- Complexity 9214 11524 +2310
=============================================
Files 2725 5425 +2700
Lines 258235 474016 +215781
Branches 40249 57669 +17420
=============================================
+ Hits 34013 72446 +38433
- Misses 219913 393513 +173600
- Partials 4309 8057 +3748
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@DaanHoogland a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
good catch @GaOrtiga I wonder if it is better to consider all the null params |
I do not think this would be necessary, |
that's ok, thanks @GaOrtiga |
|
@blueorangutan package |
|
@borisstoyanov a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 9838 |
borisstoyanov
left a comment
There was a problem hiding this comment.
LGTM, manually deployed a zone and there was no tag on the host
Co-authored-by: Gabriel <gabriel.fernandes@scclouds.com.br>
Description
In the UI, during zone creation, if a new host is created without specifying host tags, ACS adds the
nulltag to it automatically.This behaviour has been fixed, making it so that no host tags are added in this situation
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
How Has This Been Tested?
I created a zone through the UI without specifying host tags and verified that no tags were added.
I also created while specifying host tags and verified that they were added accordingly