Update image for springboot devfiles

[feloy]

Updates the springboot devfiles stored in the odo repository with a more up-to-date image.

(devfile/registry@bf3a2ce)

What type of PR is this:

/area testing

What does this PR do / why we need it:

Which issue(s) this PR fixes:

Fixes #6754

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

How to test changes / Special notes to the reviewer:

[netlify]

✅ Deploy Preview for odo-docusaurus-preview canceled.

Name	Link
🔨 Latest commit	6f8fffc
🔍 Latest deploy log	https://app.netlify.com/sites/odo-docusaurus-preview/deploys/6440db4dea9d3e0008f1de3a

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[odo-robot]

NoCluster Tests on commit finished successfully.
View logs: TXT HTML

[odo-robot]

OpenShift Unauthenticated Tests on commit finished successfully.
View logs: TXT HTML

[odo-robot]

Unit Tests on commit finished successfully.
View logs: TXT HTML

[odo-robot]

Validate Tests on commit finished successfully.
View logs: TXT HTML

[odo-robot]

Kubernetes Tests on commit finished successfully.
View logs: TXT HTML

[odo-robot]

Windows Tests (OCP) on commit finished with errors.
View logs: TXT HTML

[odo-robot]

OpenShift Tests on commit finished with errors.
View logs: TXT HTML

[feloy]

/override windows-integration-test/Windows-test

Network error

[FAILED] [142.581 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 [It] should check memory Request and Limit
C:/Users/Administrator.ANSIBLE-TEST-VS/3745/tests/integration/cmd_dev_test.go:2782

[...]

[oc] Unable to connect to the server: dial tcp 149.81.180.122:31700: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
  [FAILED] in [It] - C:/Users/Administrator.ANSIBLE-TEST-VS/3745/tests/helper/helper_oc.go:34 @ 04/20/23 01:34:14.648
  [odo] Cleaning resources, please wait

[openshift-ci]

@feloy: Overrode contexts on behalf of feloy: windows-integration-test/Windows-test

In response to this:

/override windows-integration-test/Windows-test

Network error

[FAILED] [142.581 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 [It] should check memory Request and Limit
C:/Users/Administrator.ANSIBLE-TEST-VS/3745/tests/integration/cmd_dev_test.go:2782

[...]

[oc] Unable to connect to the server: dial tcp 149.81.180.122:31700: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
 [FAILED] in [It] - C:/Users/Administrator.ANSIBLE-TEST-VS/3745/tests/helper/helper_oc.go:34 @ 04/20/23 01:34:14.648
 [odo] Cleaning resources, please wait

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[feloy]

/override OpenShift-Integration-tests/OpenShift-Integration-tests

Flaky test

[FAILED] [174.329 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode [It] should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:247

[openshift-ci]

@feloy: Overrode contexts on behalf of feloy: OpenShift-Integration-tests/OpenShift-Integration-tests

In response to this:

/override OpenShift-Integration-tests/OpenShift-Integration-tests

Flaky test

[FAILED] [174.329 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode [It] should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:247

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rm3l]

/hold

I checked why the 'spring-boot' Maven plugin was surprisingly not found, and I think this has nothing to do with the container image.
It looks like the run command is being executed in the runtime container which has mountSources set to false. So without any local pom.xml files (coming from the project sources), Maven will try to resolve the short spring-boot plugin name from its known plugins by default.
I tested with the registry.access.redhat.com/ubi8/openjdk-11:latest image, and it behaves the same way, except that the command did not return any logs..
At least, the Dev Session started successfully by setting mountSources to true in the runtime container component. Well, it is still great to update the image name too.

[rm3l]

/hold cancel

Unholding as it is still fine, but we can consider updating mountSources in a separate PR.

[feloy]

The error I have seen (and which has been fixed by changing the image) was occuring during the build command.

[rm3l]

Yes, for the build, I think it was a DNS resolution error (from what I can see in the job logs):

 [odo]  ✗  Building your application in container (command: defaultbuild) [2s]
  [odo] [INFO] Scanning for projects...
  [odo] Downloading from central: https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.3.5.RELEASE/spring-boot-starter-parent-2.3.5.RELEASE.pom
  [odo] [ERROR] [ERROR] Some problems were encountered while processing the POMs:
  [odo] [FATAL] Non-resolvable parent POM for com.example:demo:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.3.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.3.5.RELEASE/spring-boot-starter-parent-2.3.5.RELEASE.pom and 'parent.relativePath' points at no local POM @ line 5, column 10
  [odo]  @ 
  [odo] [ERROR] The build could not read 1 project -> [Help 1]
  [odo] [ERROR]   
  [odo] [ERROR]   The project com.example:demo:0.0.1-SNAPSHOT (/projects/pom.xml) has 1 error
  [odo] [ERROR]     Non-resolvable parent POM for com.example:demo:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.3.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.3.5.RELEASE/spring-boot-starter-parent-2.3.5.RELEASE.pom and 'parent.relativePath' points at no local POM @ line 5, column 10: 

Unknown host repo.maven.apache.org: Name or service not known -> [Help 2]

But once that passes, the run command (which runs the spring-boot:run goal) cannot run if the sources are not mounted (or if the Maven settings in the container image do not indicate how to resolve the spring-boot plugin).
I'll create a separate PR to mount the sources so that this can run properly..