Bug 2136442 - [IBM Z] - Submariner addon unistallation doesnt work from ACM console
Summary: [IBM Z] - Submariner addon unistallation doesnt work from ACM console
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Submariner
Version: rhacm-2.6.z
Hardware: s390x
OS: Linux
unspecified
medium
Target Milestone: ---
: rhacm-2.7
Assignee: tpanteli
QA Contact: Noam Manos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-20 09:59 UTC by Abdul Kandathil (IBM)
Modified: 2023-01-31 21:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-31 21:49:34 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.7+
nyechiel: rhacm-2.7.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 26506 0 None None None 2022-10-20 14:05:05 UTC
Github submariner-io submariner-operator issues 2304 0 None open subctl uninstall should use the nettest image to pause 2022-10-31 09:45:51 UTC

Description Abdul Kandathil (IBM) 2022-10-20 09:59:40 UTC
**What happened**:
Submariner addon unistallation doesnt work from ACM console due to x86 image being used by submariner-routeagent-uninstall pods.

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  45s                default-scheduler  Successfully assigned submariner-operator/submariner-routeagent-uninstall-9rkr6 to master-2.ocsm1301015.lnxero1.boe by master-1.ocsm1301015.lnxero1.boe
  Normal   Pulled     45s                kubelet            Container image "registry.redhat.io/rhacm2/submariner-route-agent-rhel8:v0.13.0" already present on machine
  Normal   Created    45s                kubelet            Created container submariner-routeagent-uninstall
  Normal   Started    44s                kubelet            Started container submariner-routeagent-uninstall
  Normal   Pulled     42s                kubelet            Successfully pulled image "k8s.gcr.io/pause" in 617.221384ms
  Normal   Pulled     40s                kubelet            Successfully pulled image "k8s.gcr.io/pause" in 544.764611ms
  Normal   Pulling    25s (x3 over 43s)  kubelet            Pulling image "k8s.gcr.io/pause"
  Normal   Created    24s (x3 over 42s)  kubelet            Created container pause
  Normal   Started    24s (x3 over 42s)  kubelet            Started container pause
  Normal   Pulled     24s                kubelet            Successfully pulled image "k8s.gcr.io/pause" in 750.363019ms
  Warning  BackOff    9s (x4 over 39s)   kubelet            Back-off restarting failed container


[root@m1301015 ~]# oc -n submariner-operator logs submariner-routeagent-uninstall-rg46g
Defaulted container "pause" out of: pause, submariner-routeagent-uninstall (init)
exec /pause: exec format error
[root@m1301015 ~]#


**What you expected to happen**:

**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:

**Environment**:
- Submariner version (use `subctl version`):
- Kubernetes version (use `kubectl version`):
- Diagnose information (use `subctl diagnose all`):
- Gather information (use `subctl gather`)
- Cloud provider or hardware configuration:
- OS (e.g `cat /etc/os-release`):
- Kernel (e.g `uname -a`):
- Install tools:
- Others:

Comment 1 Stephen Kitt 2022-10-20 11:37:39 UTC
The problem here is that the pause image (provided through k8s.gcr.io/pause) doesn't have the right architecture. k8s.gcr.io/pause is a "well-known" image name for the pause image, I was under the impression that OCP provided an appropriate image in all cases, but apparently that's not the case...

Comment 2 Maxim Babushkin 2022-11-10 14:54:05 UTC
Hello Abdul,

Unfortunately, we don't have IBM Z platform to verify the fix.
Any chance you could verify the fix, please?

Thank you,
Maxim.

Comment 3 Abdul Kandathil (IBM) 2022-11-11 12:44:52 UTC
Yes, I can try it on my cluster. Please share the steps.


Note You need to log in before you can comment on or make changes to this bug.