Skip to content

Addition of description field for NIC's secondary IP addresses#12864

Open
erikbocks wants to merge 1 commit intoapache:mainfrom
scclouds:add-description-for-secondary-ip-addresses
Open

Addition of description field for NIC's secondary IP addresses#12864
erikbocks wants to merge 1 commit intoapache:mainfrom
scclouds:add-description-for-secondary-ip-addresses

Conversation

@erikbocks
Copy link
Collaborator

Description

In order to help users to identify more easily the reason that their NIC's secondary IP address were allocated to the VM, a description field was added to the secondary IPs. Now, during secondary IP address allocation, it is possible to inform a descriptive text, that will be displayed along with the IP address in the NIC details or in the API's responses.

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)
  • Build/CI
  • Test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Screenshots (if appropriate):

Figure 1 - Form description field image
Figure 2 - IP's description present at NIC details image

How Has This Been Tested?

In an environment where the PR changes were installed, I opened the secondary IP addition tab and validated that the description field was added successfully to the form (Figure 1 in the Screenshots tab). Via CMK, I validated that the description field was also added to the addIpToNicAPI.

Then, I added a secondary IP address to my VM with an example text in it (Figure 2). After that, I made some tests to features involving secondary IPs, as the addresses management and configuration, as well as a communication test with static NAT assigned to the secondary IP.

With CloudMonkey, I also validated that the description field was now returned in NICs' responses in the listNics API.

@codecov
Copy link

codecov bot commented Mar 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 3.53%. Comparing base (b744824) to head (bedd77f).

❗ There is a different number of reports uploaded between BASE (b744824) and HEAD (bedd77f). Click for more details.

HEAD has 1 upload less than BASE
Flag BASE (b744824) HEAD (bedd77f)
unittests 1 0
Additional details and impacted files
@@              Coverage Diff              @@
##               main   #12864       +/-   ##
=============================================
- Coverage     18.02%    3.53%   -14.50%     
=============================================
  Files          5968      464     -5504     
  Lines        537086    40023   -497063     
  Branches      65961     7530    -58431     
=============================================
- Hits          96819     1414    -95405     
+ Misses       429347    38421   -390926     
+ Partials      10920      188    -10732     
Flag Coverage Δ
uitests 3.53% <ø> (-0.01%) ⬇️
unittests ?

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant