Eclipse with Galasa 0.25 - Error on initialise frame work

[ChrisAtkinson1]

Describe the bug

A new 22-06-06 Eclipse with Galsasa 0.25.

Eclipse IDE for Java Developers (includes Incubating components) Version: 2022-06 (4.24.0) Build id: 20220609-1112 OS: Windows 11, v.10.0, x86_64 / win32 Java vendor: IBM Corporation Java runtime version: 11.0.17+8 Java version: 11.0.17

Initialise framework fails with

Steps to reproduce

1 Windows 11 2 Download and install eclipse 22-06-06 ( Either Java EE or Java EE with Web) 3 Install zia p2 Galsasa into eclipse 4 Set the Galasa properties - See Screenshot 5 Set up Galasa workspace 6 Initialise Galasa Frame work - Bug appears. See screenshot

Log in console Initialising the Galasa Framework Configuration Property Store is file:///C:/Users/097775866/.galasa/cps.properties Searching for CPS providers Found CPS Provider dev.galasa.cps.etcd.internal.Etcd3ConfigurationPropertyRegistration Found CPS Provider dev.galasa.framework.internal.cps.FpfConfigurationPropertyRegistration Selected CPS Service is dev.galasa.framework.internal.cps.FpfConfigurationPropertyStore Dynamic Status Store is file:///C:/Users/097775866/.galasa/dss.properties Searching for DSS providers

Found DSS Provider dev.galasa.cps.etcd.internal.Etcd3DynamicStatusStoreRegistration Found DSS Provider dev.galasa.framework.internal.dss.FpfDynamicStatusStoreRegistration Selected DSS Service is dev.galasa.framework.internal.dss.FpfDynamicStatusStore

Expected behavior

I expected the framework to initialise

Additional context

If applicable, add screenshots or any relevant output logs to help explain your problem.

[hobbit1983]

Thanks @ChrisAtkinson1 can you attach the content of the bootstrap.properties file please. Also I note that you have a bad value in the OBR version field - this should be left blank or have a specific version i.e 0.25.0 written in there

[ChrisAtkinson1]

That file is empty.

[techcobweb]

@eamansour Is this still a problem on the 0.27.0 pre-release version ?

[eamansour]

This is likely still a problem since the recent eclipse fixes were focused on resolving a different issue. I haven't been able to reproduce this issue on macOS, so will need to try it out on Windows.

[techcobweb]

I tried galasa 0.26.0 on eclipse 2022-06 and it worked fine.

We know 0.27.0 works ok on 2022-09 or beyond, perhaps you could upgrade galasa or eclipse and try it again please @ChrisAtkinson1 ?

[ChrisAtkinson1]

What's happened to the Simbank tests that are supposed to be supplied ?

[techcobweb]

Offhand, no idea. Will investigate. There have been some build changes recently which may have upset things perhaps ? @jadecarino @AaronJhaj

Should we re-purpose this issue to look at the simbank thing, or raise a separate one ?

[techcobweb]

Just tried to import the simbank samples...

Seemed to work fine...

So... that's 0.26.0 on eclipse 2022-06

What version of eclipse + galasa are you using ? If it's not 2022-09/0.27.0 then perhaps you can move to those levels to confirm there are still issues ?

[ChrisAtkinson1]

That's blank

[ChrisAtkinson1]

[ChrisAtkinson1]

[eamansour]

Hi @ChrisAtkinson1, you should be able to find the simbank tests if you navigate to File > New > Example in Eclipse, which will open a New Example dialog. I just tried it on Eclipse 2023-03 / 0.27.0 and I can see the test projects (see below).

Looking at the empty dialog you posted (and correct me if I'm wrong), I think you might be trying to import the simbank projects through the dialog that opens after selecting the Import projects... option in the project explorer, rather than navigating to the New Example dialog.

Hope this helps!

[ChrisAtkinson1]

Thanks that worked

[ChrisAtkinson1]

After running the simbank installs for manager then tests. Trying to run the simbank IVT results in this error

Simbank.zip

[eamansour]

Looks like you might be using Java 17 or above - switching to Java 11 should fix it.

If you go to the "JRE" tab in the run configuration that you created to run the IVT, you can change the Java version by checking the "Alternate JRE" option and selecting Java 11 from the dropdown (see below for an example).

If you don't see Java 11 listed in the dropdown, you can add an installed JDK by clicking the "Installed JREs" button to the right of the dropdown and then you can either add the installed JDK with the "Add" button or let Eclipse search a directory to find the JDK using the "Search" button in the dialog that opens (see below).

[techcobweb]

@eamansour Good answer.

As this issue has sat around for a while in review state, I will close it. Please re-open if this problem persists ...

[ChrisAtkinson1]

This gets further but fails

06/06/2023 14:55:01.177 DEBUG d.g.f.TestRunManagers - dev.galasa.kubernetes.internal.KubernetesManagerImpl 06/06/2023 14:55:01.343 INFO d.g.f.TestRunner - Starting Provision Generate phase 06/06/2023 14:55:01.352 INFO d.g.f.TestRunner - Provision Generate failed dev.galasa.framework.spi.FrameworkException: Problem in provision generate for manager dev.galasa.zos.internal.ZosManagerImpl at dev.galasa.framework.TestRunManagers.provisionGenerate(TestRunManagers.java:478) ~[-1686059698935:?] at dev.galasa.framework.TestRunner.generateEnvironment(TestRunner.java:435) [-1686059698935:?] at dev.galasa.framework.TestRunner.runTest(TestRunner.java:368) [-1686059698935:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?] at dev.galasa.boot.felix.FelixFramework.runTest(FelixFramework.java:235) [galasa-boot.jar:?] at dev.galasa.boot.Launcher.launch(Launcher.java:168) [galasa-boot.jar:?] at dev.galasa.boot.Launcher.main(Launcher.java:122) [galasa-boot.jar:?] Caused by: dev.galasa.zos.ZosManagerException: Unable to locate zOS images for cluster DEFAULT, see property zos.cluster.*.images at dev.galasa.zos.internal.properties.ClusterImages.get(ClusterImages.java:39) ~[?:?] at dev.galasa.zos.internal.ZosManagerImpl.selectNewImage(ZosManagerImpl.java:380) ~[?:?] at dev.galasa.zos.internal.ZosManagerImpl.generateZosImage(ZosManagerImpl.java:327) ~[?:?] at dev.galasa.zos.internal.ZosManagerImpl.generateZosImage(ZosManagerImpl.java:274) ~[?:?] at dev.galasa.zos.internal.ZosManagerImpl.provisionGenerate(ZosManagerImpl.java:234) ~[?:?] at dev.galasa.framework.TestRunManagers.provisionGenerate(TestRunManagers.java:473) ~[-1686059698935:?] ... 9 more

[ChrisAtkinson1]

That's simbank IVT

[hobbit1983]

Hi @ChrisAtkinson1 what have you got set in your CPS properties for this test?

[ChrisAtkinson1]

That is hard to say.

Start has 06/06/2023 14:54:55.900 DEBUG dev.galasa.boot.Launcher.processCommandLine - Supplied command line arguments: --bootstrap file:///C:/Users/097775866/.galasa/bootstrap.properties --overrides file:///C:/Users/097775~1/AppData/Local/Temp/galasa_eclipse_cache_11201292521185936081/galasaoverrides7190067746275333404.properties --localmaven file:/C:/Users/097775866/.m2/repository/ --remotemaven https://repo.maven.apache.org/maven2/ --obr file:/C:/temp/GLTest/GLWS2303/.metadata/.plugins/dev.galasa.eclipse/workspace.obr --obr mvn:dev.galasa/dev.galasa.uber.obr/LATEST/obr --test dev.galasa.simbank.tests/dev.galasa.simbank.tests.SimBankIVT 06/06/2023 14:54:55.927 DEBUG dev.galasa.boot.Launcher.launch - OBR Repository Files: [file:/C:/temp/GLTest/GLWS2303/.metadata/.plugins/dev.galasa.eclipse/workspace.obr, mvn:dev.galasa/dev.galasa.uber.obr/LATEST/obr] 06/06/2023 14:54:55.927 DEBUG dev.galasa.boot.Launcher.launch - Launching Framework...

Then (which should be correct) 06/06/2023 14:54:59.144 INFO d.g.f.FrameworkInitialisation - Initialising the Galasa Framework 06/06/2023 14:54:59.148 INFO d.g.f.FrameworkInitialisation - Environment variable GALASA_HOME used to set value of home location. 06/06/2023 14:54:59.149 INFO d.g.f.FrameworkInitialisation - Galasa home location is C:\temp\GLTest\GLHOME 06/06/2023 14:54:59.150 DEBUG d.g.f.FrameworkInitialisation - galasa home used to determine CPS location. 06/06/2023 14:54:59.150 DEBUG d.g.f.FrameworkInitialisation - Configuration Property Store is file:///C:/temp/GLTest/GLHOME/cps.properties 06/06/2023 14:54:59.184 DEBUG d.g.f.FrameworkInitialisation - Selected CPS Service is dev.galasa.framework.internal.cps.FpfConfigurationPropertyStore 06/06/2023 14:54:59.186 INFO d.g.f.FrameworkInitialisation - Environment variable GALASA_HOME used to set value of home location. 06/06/2023 14:54:59.186 INFO d.g.f.FrameworkInitialisation - Galasa home location is C:\temp\GLTest\GLHOME 06/06/2023 14:54:59.187 DEBUG d.g.f.FrameworkInitialisation - Dynamic Status Store is file:///C:/temp/GLTest/GLHOME/dss.properties 06/06/2023 14:54:59.206 INFO d.g.f.FrameworkInitialisation - Submitting test dev.galasa.simbank.tests/dev.galasa.simbank.tests.SimBankIVT 06/06/2023 14:54:59.258 INFO d.g.f.FrameworkInitialisation - Allocated Run Name U5 to this run 06/06/2023 14:54:59.258 INFO d.g.f.FrameworkInitialisation - Run name is U5 06/06/2023 14:54:59.262 INFO d.g.f.FrameworkInitialisation - Environment variable GALASA_HOME used to set value of home location. 06/06/2023 14:54:59.262 INFO d.g.f.FrameworkInitialisation - Galasa home location is C:\temp\GLTest\GLHOME 06/06/2023 14:54:59.263 DEBUG d.g.f.FrameworkInitialisation - Result Archive Stores are [file:///C:/Users/097775866/.galasa/ras/] 06/06/2023 14:54:59.322 DEBUG d.g.f.FrameworkInitialisation - Credentials Store is file:///C:/Users/097775866/.galasa/credentials.properties

[hobbit1983]

The CPS is detailed in that message it is located in file:///C:/temp/GLTest/GLHOME/cps.properties can we see the content of that please?

[ChrisAtkinson1]

It's broken running Simbank and Java in .28 version using MVN

Can initialise enviroment and workspace.

Run maven install

SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details. SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions 1.7.x or earlier. SLF4J: Ignoring binding found at [jar:file:/C:/temp/GLTest/Eclipse2303/eclipse/plugins/org.eclipse.m2e.maven.runtime_3.8.701.20230209-1606/jars/maven-slf4j-provider-3.8.7.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See https://www.slf4j.org/codes.html#ignoredBindings for an explanation.

[hobbit1983]

@ChrisAtkinson1 does this really break simbank and cause either the sample application or the test to fail in some way? or is it just a warning that - yes - we should work around - but doesn't cause something to break/fail

[ChrisAtkinson1]

That's as far as it gets. Nothing else happens

[ChrisAtkinson1]

That's the run output

[techcobweb]

--localmaven file:/C:/Users/097775866/.m2/repository/ and file:/C:/temp/GLTest/GLWS2303/.metadata/.plugins/dev.galasa.eclipse/workspace.obr look wrong.

[techcobweb]

On windows, should be file:///C:/Users or something like that ?

[ChrisAtkinson1]

Additionally attempting to run the sample CICS test ( which is built in Gradle now ). Run output errors ( this works ok in cmd line)

Eclipse run.zip

[hobbit1983]

@ChrisAtkinson1 that looks like you are running with a JRE that isn't java 11 - can you check please?

[ChrisAtkinson1]

Compiler

Run config for running test

Not sure if I should set something else ?

[hobbit1983]

In the run launcher dialog there is a JRE tab, what's in there?

[ChrisAtkinson1]

It's as per the second screen shot

[ChrisAtkinson1]

Is the p2 site being updated ? Or does the .21 version not match the .29 release ?

Bundle-Name: Galasa Tester Programmer Interface (TPI) Bundle-SymbolicName: dev.galasa Bundle-Version: 0.21.0 Created-By: 1.8.0_292 (AdoptOpenJDK) Export-Package: dev.galasa;uses:="javax.validation.constraints";versio n="0.21.0",dev.galasa.api.ras;version="0.21.0",dev.galasa.api.run;ver sion="0.21.0",dev.galasa.api.runs;uses:="dev.galasa.api.run";version= "0.21.0"

[ChrisAtkinson1]

I guess the later.

[ChrisAtkinson1]

All fixed in .29