Validate the OEG federated Helm flow against the local Federation Manager deployment and confirm that OEG preserves full HTTP(S) Helm repository URLs when building the GSMA artefact payload.
Expected: HTTP `200` and an onboarded app response from OEG.
## 5. Trigger federated deployment through OEG
```bash
curl -sS-X POST 'http://127.0.0.1:8085/oeg/1.0.0/appinstances'\
-H'Content-Type: application/json'\
--data'{
"appId":"550e8400-e29b-41d4-a716-446655440111",
"appZones":[{
"EdgeCloudZone":{
"edgeCloudZoneId":"default",
"edgeCloudZoneName":"unknown",
"edgeCloudProvider":"i2cat",
"edgeCloudZoneStatus":"unknown",
"edgeCloudRegion":"unknown"
}
}]
}'
```
## 6. Inspect OEG payloads
```bash
docker logs --since 2m oeg-local-test
```
Expected artefact payload fragment:
```json
"artefactRepoLocation":{
"repoURL":"https://charts.bitnami.com/bitnami"
}
```
Expected onboard payload fragment:
```json
"appDeploymentZones":[
"default"
]
```
Expected normalized component payload fragment:
```json
"appComponentSpecs":[
{
"componentName":"cmpbitnamihelm0"
}
]
```
## 7. Inspect downstream services
```bash
docker logs --since 2m federation-manager-local
docker logs --since 2m srm-remote
docker logs --since 2m lite2edge-remote
```
Expected current outcome:
- OEG artefact upload reaches FM successfully.
- OEG onboarding reaches FM successfully with HTTP `202`.
- OEG deployment reaches FM and downstream lite2edge Helm install.
- Current remaining failure is downstream Helm repository access, for example:
```text
Helm install failed: Error: INSTALLATION FAILED: looks like "https://charts.bitnami.com/bitnami" is not a valid chart repository or cannot be reached: Get "https://repo.broadcom.com/bitnami-files/index.yaml": EOF
```
## Interpretation
- If OEG logs show `repoURL: https://charts.bitnami.com/bitnami`, the repository parsing fix is working.
- If the flow fails later during Helm install or external repo fetch, OEG is no longer the blocker for this issue.
## Post-VPN Recheck
After disabling the corporate VPN, re-run direct chart access tests from `lite2edge-remote`:
```bash
docker exec lite2edge-remote \
helm show chart nginx --repo https://charts.bitnami.com/bitnami --version 15.14.0
docker exec lite2edge-remote \
helm show chart oci://registry-1.docker.io/bitnamicharts/nginx --version 15.14.0
```
Expected after VPN disable:
- Both commands succeed.
- This confirms the earlier certificate failures were environment-related.
Then replay the federated public Helm deployment through OEG using a fresh app id, for example `550e8400-e29b-41d4-a716-446655440444`.
Observed result in this session:
- OEG artefact payload is correct:
```json
"artefactRepoLocation":{
"repoURL":"https://charts.bitnami.com/bitnami"
}
```
- OEG onboarding succeeds with `202`.
- Deployment reaches real Helm install.
- Remaining failure is downstream Helm TLS/handshake behavior to the Bitnami/Broadcom endpoint:
```text
Helm install failed: Error: INSTALLATION FAILED: looks like "https://charts.bitnami.com/bitnami" is not a valid chart repository or cannot be reached: Get "https://repo.broadcom.com/bitnami-files/index.yaml": remote error: tls: handshake failure
```
Additional direct runtime check:
```bash
docker exec lite2edge-remote python - <<'PY'
import urllib.request
with urllib.request.urlopen("https://repo.broadcom.com/bitnami-files/index.yaml", timeout=20) as r:
print(r.status)
PY
```
Observed in this session:
- Direct Python HTTPS access reached the endpoint and returned HTTP `403` rather than failing TLS.
- That means the remaining issue is narrower than raw connectivity: it is specific to Helm's access path/handshake to that repository in the current runtime.
## OCI Comparison
To distinguish repo-format issues from network/TLS issues, a local plain-HTTP OCI registry can be used.
