[BUG] Updating the OpenShift Local extension version from PD fails

[rostalan]

General information

• OS: Fedora 38
• Did you run crc setup before starting it (Yes/No)? YES
• Running CRC on: Laptop

CRC version

WARN A new version (2.26.0) has been published on https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/2.26.0/crc-linux-amd64.tar.xz 
CRC version: 2.24.1+81aeeb
OpenShift version: 4.13.6
Podman version: 4.4.4

CRC status

DEBU CRC version: 2.24.1+81aeeb                   
DEBU OpenShift version: 4.13.6                    
DEBU Podman version: 4.4.4                        
DEBU Running 'crc status'                         
CRC VM:          Running
MicroShift:      Running (v4.13.6)
RAM Usage:       1.179GB of 3.84GB
Disk Usage:      5.104GB of 16.1GB (Inside the CRC VM)
Cache Usage:     27.37GB
Cache Directory: /home/rostislavlan/.crc/cache

CRC config

- consent-telemetry                     : no
- preset                                : microshift
- pull-secret-file                      : /home/rostislavlan/Downloads/pull-secret

Host Operating System

NAME="Fedora Linux"
VERSION="38 (Workstation Edition)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

1. open Podman Desktop
2. go to Dashboard
3. click "Update to 2.26.0" under Openshift Local
4. throws error, does not update

Expected

success

Actual

failure

Logs

ProviderUpdateButton.svelte:38 Error: s is not iterable
a @ ProviderUpdateButton.svelte:38
await in a (async)
u @ ProviderUpdateButton.svelte:57
(anonymous) @ lifecycle.js:181
Rk @ lifecycle.js:181
g @ Button.svelte:25

[gbraad]

Were you able to update outside of PD?

ProviderUpdateButton.svelte:38 Error: s is not iterable

Might actually be an issue with PD itself. I would have to try this out.

[gbraad]

@odockal you were able to reproduce this?

Was this on the same platform as the reporter? As we do not actually have an update flow on Linux, which might be the reason. For Windows and macOS we would download the respective packages and run this to start the update process. For Linux, ... well, it would be the binary itself. Not sure where the error now occurs, as the error itself is a PD-issued stacktrace.

[gbraad]

@evidolob @jeffmaury Any idea?

[jeffmaury]

Low priority as it's on Linux but we should probably not advertise Update on this platform

[gbraad]

we should probably not advertise Update on this platform

Probably. We have a more generic task to handle the installation flow for Linux, as several issues remain when it comes to onboarding/preflights.

[mairin]

this hit me today when trying to update to 2.27.

[rostalan]

still present with PD 1.8.0, podman 4.9.1 and update from 2.30.0 to 2.31.0