This defaults to None, where before we had a fixed value of 7200.

When options.oz_install_timeout is None, we pass that along, which leads me to wonder:

• is there a difference between passing timeout: None and leaving it out?
• or for that matter, does it have a different meaning from a timeout of 0?
• is the None value useful? If so, should we provide a way for the user to specify it explicitly?

is there a difference between passing timeout: None and leaving it out?

If moving 'timeout' key from imagefactory configuration dict, imagefactory will raise KeyError

or for that matter, does it have a different meaning from a timeout of 0?

Aha, 0 is actually ZERO on oz, it won't wait and throw timeout error immediately

is the None value useful? If so, should we provide a way for the user to specify it explicitly?

None value tells oz to use the number in /etc/oz/oz.cfg.
I added some comments in default kojid.conf. I'm going to add notes in docs.

added explanation in image_build.rst

:+1: Thank you @julian8628 for working on this patch.

We need this patch in F27 koji build in order to configure timeout to fix cloud-base image failure for s390x in F28.

Aha, 0 is actually ZERO on oz, it won't wait and throw timeout error immediately

So presumably no one would ever want to do this.

None value tells oz to use the number in /etc/oz/oz.cfg.
I added some comments in default kojid.conf. I'm going to add notes in docs.

The None value is important, but there is no way explicitly configure this since oz_install_timeout is parsed strictly as an int.

Perhaps we should check for the zero value and pass None in that case instead (unless someone can think of a reason to use a literal timeout of zero).

If we did this, then we could continue to have a default timeout.

@mikem updated

Commit b64151da fixes this pull-request