Miguel Angel Ajo Pelayo

@nilslice ^ does that make sense?

Happy new year, thanks!!! :) Enviado desde mi iPhone > El 1 ene 2020, a las 22:58, Steve Manuel escribió: > >  > That does make sense, feel free...

It works for me: ``` [root@rhel8shift microshift]# subscription-manager repos --list | grep rhocp-4.10 Repo ID: rhocp-4.10-for-rhel-8-x86_64-source-rpms Repo ID: rhocp-4.10-for-rhel-8-x86_64-rpms Repo ID: rhocp-4.10-for-rhel-8-x86_64-debug-rpms ``` What subscription are you using?

Thanks for the suggestion @christianh814 !

@cgwalters @stlaz thanks for looking at this, I'm having a look to the cluster-machine-approver

and yes, @cgwalters MicroShift doesn't manage the OS today, not sure if we would need to look at that at some point.

@fzdarsky

hmm @cgwalters so, it looks like we were proposing the same mechanism used in OpenShift, but in openshift we have the cluster-machine-approver which makes additional checks based on the open...

We need to check the order of shutdown: ``` ago 10 11:05:59 microshiftdevel.local microshift[285432]: I0810 11:05:59.109267 285432 scope.go:110] "RemoveContainer" containerID="171fa9921fdae89c0f5b6e3a34859438804183c8cca083957de80$ 5a3d26d5a5" ago 10 11:05:59 microshiftdevel.local microshift[285432]: I0810 11:05:59.109324 285432 scope.go:110]...

It ends with ``` ago 10 11:06:28 microshiftdevel.local microshift[285432]: I0810 11:06:28.312290 285432 run.go:189] Timed out waiting for services to stop ago 10 11:06:28 microshiftdevel.local microshift[285432]: I0810 11:06:28.312336 285432 run.go:191] MicroShift...