Merge branch 'add_sample_note_fix_error' into 'release/4.1'

Add a note in the Domain on PV sample to clarify the `hostPath` usage for single node and fix the error message

See merge request weblogic-cloud/weblogic-kubernetes-operator!4343

Author: rjeberhard

documentation/site/content/samples/domains/domain-home-on-pv/sample.md

@@ -131,6 +131,12 @@ Click [here](https://raw.githubusercontent.com/oracle/weblogic-kubernetes-operat
 
 Click [here](https://raw.githubusercontent.com/oracle/weblogic-kubernetes-operator/{{< latestMinorVersion >}}/kubernetes/samples/scripts/create-weblogic-domain/domain-on-pv/domain-resources/JRF/domain-on-pv-JRF-v1.yaml) to view the JRF Domain YAML file.
 
+Modify the PV and PVC specifications defined in the `spec.configuration.initializeDomainOnPV` section of the Domain resource YAML file based on your environment. These specifications often require your Kubernetes cluster administrator to provide the information. See [Persistent volume and Persistent Volume Claim]({{< relref "/managing-domains/domain-on-pv/usage#persistent-volume-and-persistent-volume-claim" >}}) in the user documentation for more details.
+
+{{% notice note %}}
+By default, this sample creates a Persistent Volume (PV) of type `hostPath`. This works only for a single node Kubernetes cluster for testing or proof of concept activities. In a multinode Kubernetes cluster, consider using a Kubernetes `StorageClass`, or PV of `nfs` type. If you use Oracle Container Engine for Kubernetes (OKE) and plan to use Oracle Cloud Infrastructure File Storage (FSS) for PV, then Oracle recommends creating a `StorageClass` and specifying the name of the `StorageClass` in your PersistentVolumeClaim (PVC) configuration in the `initializeDomainOnPV` section. See [Provisioning PVCs on the File Storage Service (FSS)](https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingpersistentvolumeclaim_Provisioning_PVCs_on_FSS.htm#Provisioning_Persistent_Volume_Claims_on_the_FileStorageService) in the OCI documentation for more details.
+{{% /notice %}}
+
   **NOTE**: Before you deploy the domain custom resource, ensure all nodes in your Kubernetes cluster [can access `domain-creation-image` and other images]({{< relref "/samples/domains/domain-home-on-pv#ensuring-your-kubernetes-cluster-can-access-images" >}}).
 
   Run the following command to apply the two sample resources.

operator/src/main/resources/scripts/startServer.sh

@@ -20,10 +20,12 @@ traceTiming "POD '${SERVICE_NAME}' MAIN START"
 
 trace "Starting WebLogic Server '${SERVER_NAME}'."
 
-source ${SCRIPTPATH}/modelInImage.sh
+if [ ${DOMAIN_SOURCE_TYPE} == "FromModel" ]; then
+  source ${SCRIPTPATH}/modelInImage.sh
 
-if [ $? -ne 0 ]; then
+  if [ $? -ne 0 ]; then
       trace SEVERE "Error sourcing modelInImage.sh" && exit 1
+  fi
 fi
 
 exportInstallHomes