David Cassany Viladomat

Closing, release is out marketplace release is already tracked in another issue rancher/elemental-operator#739

Prepared a POC here https://build.opensuse.org/project/show/home:dcassany:branches:isv:Rancher:Elemental:Maintenance:5.5 This requires creating/duplicatin six packages and the adaption of project configuration and former elemetal-channel image. Not really satisfied with this approach. To proceed with this...

Done, isv:Rancher:Elemental:Maintenance:5.5 includes packages for both versions of the operator v1.4 and v1.5

Did some experimentation with the following: ``` # Produce list of packages ready to be diffed $ docker run --rm -ti --entrypoint rpm -qa | sort > packages.old $ docker...

I like the feature request, makes sense to me, but we should be careful with it. I don't think we should use elemental persistent partition to store anything else than...

> I think this is due the hash of the data that the Plan runs, which results in the secret or plan being the same hash that already run, so...

> This should probably be integrated into `rancher-cleanup` thinking Indeed, if technically possible I'd say the best approach would be to have some sort of generic plugins cleanup. From a...

@jitakirin Which is the base image that are you using? I think the easiest way to work around that is to use the PYTHONIOENCODING=UTF-8 environment variable, which will ensure that...

> So I suppose one final question is, shouldn't C.UTF-8 at least be part of the base image? @jitakirin we are currently discussing it, this is not obvious since this...

@yukiisbored removing systemd package from the Docker image is not that easy; currently, any service package including systemd unit files includes a hard requirement for systemd, IMHO the only feasible...