@seb128 going forward, I would like subiquity to grow the ability to re-run a step that failed (unless it's fatal) - if instructed to do so. Sporadic connectivity issues would be the most common use-case for it.
This will involve significant changes and it requires UI updates too to support it.
Currently though, we only have /some/ steps here and there that have sleep and retries implemented but not in a consistent way. And they don't retry forever, they would typically do 3 attempts and then give up.
@seb128 going forward, I would like subiquity to grow the ability to re-run a step that failed (unless it's fatal) - if instructed to do so. Sporadic connectivity issues would be the most common use-case for it.
This will involve significant changes and it requires UI updates too to support it.
Currently though, we only have /some/ steps here and there that have sleep and retries implemented but not in a consistent way. And they don't retry forever, they would typically do 3 attempts and then give up.