WLS on VMs arm-ttk violations

[edburns]

I ran the arm-ttk against the WLS on VMs offers and ran into these violations.

    [-] URIs Should Be Properly Constructed (303 ms)
    [-] apiVersions Should Be Recent (99 ms)
    [-] URIs Should Be Properly Constructed (130 ms)
    [-] URIs Should Be Properly Constructed (184 ms)
    [-] URIs Should Be Properly Constructed (449 ms)
    [-] apiVersions Should Be Recent (44 ms)
    [-] Password params must be secure (1 ms)
    [-] apiVersions Should Be Recent (59 ms)
    [-] URIs Should Be Properly Constructed (156 ms)
    [-] URIs Should Be Properly Constructed (155 ms)
    [-] URIs Should Be Properly Constructed (98 ms)
    [-] URIs Should Be Properly Constructed (447 ms)
    [-] apiVersions Should Be Recent (81 ms)
    [-] URIs Should Be Properly Constructed (135 ms)
    [-] apiVersions Should Be Recent (45 ms)
    [-] Password params must be secure (1 ms)
    [-] apiVersions Should Be Recent (52 ms)

The complete list of violations is in this attached build output.
message.txt
These violations should be fixed before the next round of publishing.

[edburns]

I am working on this now at #147 . I ran into a problem in the cluster offer when the maven build descends into the deletenode module. I worked around it for now by modifying .github/workflows/buildWlsVm4CcArtifact.yml so that it invokes maven in ${{env.repoName}}/weblogic-azure-vm/${{ env.offerName }}/${{ env.offerName }} instead of ${{env.repoName}}/weblogic-azure-vm/${{ env.offerName }}. Of course, I also had to modify the artifact generation to use echo "##[set-output name=artifactPath;]${{env.repoName}}/weblogic-azure-vm/${{ env.offerName }}/${{ env.offerName }}/target/$artifactName" instead of echo "##[set-output name=artifactPath;]${{env.repoName}}/weblogic-azure-vm/${{ env.offerName }}/target/$artifactName". I am not happy about this. I will not consider this bug closed until that workaround can be removed.

Here is what I observed before applying the workaround:

• The arm ttk tests in deletenode succeed. 0 Failures. However the maven exec plugin failed. I suspect it is one of those non-zero return code problems and may indeed be a bug in arm-ttk.

[edburns]

I observe the same problem in the dynamic cluster as in this comment, also on deletenode. I am applying the same workaround as in the configured cluster.