Set network state to implemented when no services#6838
Conversation
|
Found UI changes, kicking a new UI QA build |
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
Codecov Report
@@ Coverage Diff @@
## main #6838 +/- ##
============================================
- Coverage 10.81% 10.80% -0.01%
+ Complexity 7083 7082 -1
============================================
Files 2485 2485
Lines 245346 245355 +9
Branches 38313 38314 +1
============================================
- Hits 26525 26518 -7
- Misses 215556 215576 +20
+ Partials 3265 3261 -4
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Co-authored-by: Wei Zhou <weizhou@apache.org>
|
@vladimirpetrov As this is a SQL only change, other than what travis does the only testing on this that makes sense is the actual upgrade of a network in state "Setup" as described in the description ;) Can you do the honours? PS don´t be fooled by the first commit, it is already on 4.17 and main: |
|
@blueorangutan package |
|
@vladimirpetrov a 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: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 4518 |
vladimirpetrov
left a comment
There was a problem hiding this comment.
LGTM based on manual testing - successfully upgraded from 4.14 and 4.15 KVM with isolated network in 'Setup' state and no services.
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-5186)
|
Description
This PR fixes an issue where isolated networks without services created in version before 4.17 and in state 'Setup' could not be used even though they require no further implementation
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
implemented in an upgraded environment from 4.15 to 4.17 with a network in setup state
before: a new VM could not be started in the network (as it was in state 'Setup'
after a vm could be started in the network