Isolation Segment Smoke Test Fails when upgrading from Isolation Segment Tile version 2.11.20 to 2.11.21
search cancel

Isolation Segment Smoke Test Fails when upgrading from Isolation Segment Tile version 2.11.20 to 2.11.21

book

Article ID: 298314

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

Upgrading from Isolation Segment tile 2.11.20 to 2.11.21 fails when running a smoke test if TAS is v2.11.26 or below. 


The reason for the failure is because Isolation Segment 2.11.21 contains smoke-tests release v4.7.0. There is a bug in smoke-tests release v4.7.0 where it will throw an error if a new property does not exist. This new property it is looking for is introduced in TAS v2.11.27.

Error that appears when applying changes in Ops Manager: 
Cannot generate manifest for product Isolation Segment: 
Error in (( .properties.smoke_tests_isolation.selected_option.parsed_manifest(smoke_tests_isolation) ))
: Error in (( ..cf.router.isolation_segments.parsed_strings )): 
unknown property "isolation_segments" (Product "Isolation Segment" / Job: nil) (Product "Isolation Segment" / Job: nil)

Smoke Test Error: 
CMD> cf7 push SMOKES-APP-fb6e5a6d-0a7d -b ruby_buildpack -p assets/ruby_simple -f /var/vcap/data/smoke_tests_isolation/tmp/runtime-manifest-1746502687.yml 

OUT: Pushing app SMOKES-APP-fb6e5a6d-0a7d to org system / space CF_SMOKE_TEST_SPACE as smoke_tests... 
OUT: Applying manifest file /var/vcap/data/smoke_tests_isolation/tmp/runtime-manifest-1746502687.yml... 
ERR: For application 'SMOKES-APP-fb6e5a6d-0a7d': Specified unknown buildpack name: "ruby_buildpack" 
OUT: FAILED CMD> cf7 delete SMOKES-APP-fb6e5a6d-0a7d -f -r OUT: Deleting app SMOKES-APP-fb6e5a6d-0a7d in org system / space CF_SMOKE_TEST_SPACE as smoke_tests... 
ERR: App 'SMOKES-APP-fb6e5a6d-0a7d' does not exist. 
OUT: OK 
OUT: 
==============================Global After Each============================== 
==============================End of Global After Each============================== Failure [2.364 seconds] 

Application Workflow /var/vcap/packages/smoke-tests/src/base_test.go:13 
Linux Applications /var/vcap/packages/smoke-tests/src/base_test.go:28 can be pushed, scaled and deleted 

[It] /var/vcap/packages/smoke-tests/src/base_test.go:36 
No future change is possible. Bailing out early after 0.343s. 
Failed to push application. 
Expected <int>: 1 to match exit code: <int>: 0 /var/vcap/packages/smoke-tests/src/base_test.go:45 
------------------------------ 

S [SKIPPING] in Spec Setup (BeforeEach) [1.976 seconds] 
Application Workflow /var/vcap/packages/smoke-tests/src/base_test.go:13 
WindowsStack Applications /var/vcap/packages/smoke-tests/src/base_test.go:86 can be pushed, scaled and deleted 
[BeforeEach] /var/vcap/packages/smoke-tests/src/base_test.go:142 
No windows stack provided in configuration /var/vcap/packages/smoke-tests/src/base_test.go:97 
------------------------------ 

Summarizing 5 Failures: 
[Fail] Isolation Segment Workflow A selected isolation segment - Compute isolation enabled. 
[BeforeEach] can be pushed to the isolation segment and receive logs /var/vcap/packages/smoke-tests/src/isolation_segment_test.go:64 

[Fail] Isolation Segment Workflow A selected isolation segment - Compute isolation enabled. 
[BeforeEach] when A custom domain is set for the isolation segment gets a successful HTTP response /var/vcap/packages/smoke-tests/src/isolation_segment_test.go:64 

[Fail] Isolation Segment Workflow A selected isolation segment - Compute isolation enabled. 
[BeforeEach] when PAS can forward requests to the isolation segment gets a successful HTTP response /var/vcap/packages/smoke-tests/src/isolation_segment_test.go:64 

[Fail] Isolation Segment Workflow A selected isolation segment - Compute isolation enabled. 
[BeforeEach] when PAS can not forward requests to the isolation segment gets an unsuccessful HTTP response /var/vcap/packages/smoke-tests/src/isolation_segment_test.go:64 

[Fail] Application Workflow Linux Applications 
[It] can be pushed, scaled and deleted /var/vcap/packages/smoke-tests/src/base_test.go:45 Ran 5 of 7 Specs in 33.069 seconds 

FAIL! -- 0 Passed | 5 Failed | 0 Pending | 2 Skipped --- 
FAIL: Test (33.07s) FAIL Ginkgo ran 1 suite in 33.164043005s Test Suite Failed Stderr Error: failed to run job-process: exit status 1 (exit status 1) 1 errand(s) 

===== 2022-09-27 15:06:12 UTC Finished "/usr/local/bin/bosh --no-color --non-interactive --tty --environment=10.74.85.142 --deployment=p-isolation-segment-a943fc8d2484839dbf20 run-errand smoke_tests_isolation --instance isolated_diego_cell/first"; Duration: 62s; Exit Status: 1 Exited with 1.


Environment

Product Version: 2.11

Resolution

There are 2 available workarounds to choose from: 


1 - Upgrade isolation segments to 2.11.22+ which contains smoke-tests release v4.8.0 where this bug is patched.
2 - Upgrade TAS to v2.11.27+ which contains this new property.

As of 07/25/2024, it would be ideal to upgrade to the later versions of TAS and Isolation Segment: 

Powered by Wolken Software