🐛 improve upper constraint handling

[Rozzii]

This commit:

• Provides a default value for the UPPER_CONSTRAINT docker file argument
• Changes the prepare-image.sh logic to check the actual size of the upper constraint file and not the presence of it.

Background of this change is that it has been noticed that on release branches during image building the "pinned" upper constraint file is not picked up rather pulled from upstream OpenStack because of a lack of default argument value during image building.

[Rozzii]

If this gets merged I will cherry pick this to other branches.

[Rozzii]

/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main

[Rozzii]

/cc @elfosardo

[tuminoid]

/lgtm

This must be backported to release branches as well, where it actually matters.

[tuminoid]

/cherry-pick release-26.0

[metal3-io-bot]

@tuminoid: once the present PR merges, I will cherry-pick it on top of release-26.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-26.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tuminoid]

/cherry-pick release-25.0

[metal3-io-bot]

@tuminoid: once the present PR merges, I will cherry-pick it on top of release-25.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-25.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tuminoid]

/cherry-pick release-24.1

[metal3-io-bot]

@tuminoid: once the present PR merges, I will cherry-pick it on top of release-24.1 in a new PR and assign it to you.

In response to this:

/cherry-pick release-24.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tuminoid]

/cherry-pick release-24.0

[metal3-io-bot]

@tuminoid: once the present PR merges, I will cherry-pick it on top of release-24.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-24.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elfosardo]

/approve

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [elfosardo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[metal3-io-bot]

@tuminoid: #584 failed to apply on top of branch "release-24.0":

Applying: improve upper constraint handling
Using index info to reconstruct a base tree...
M	Dockerfile
M	prepare-image.sh
Falling back to patching base and 3-way merge...
Auto-merging prepare-image.sh
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 improve upper constraint handling
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-24.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[metal3-io-bot]

@tuminoid: #584 failed to apply on top of branch "release-26.0":

Applying: improve upper constraint handling
Using index info to reconstruct a base tree...
M	Dockerfile
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 improve upper constraint handling
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-26.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[metal3-io-bot]

@tuminoid: #584 failed to apply on top of branch "release-25.0":

Applying: improve upper constraint handling
Using index info to reconstruct a base tree...
M	Dockerfile
M	prepare-image.sh
Falling back to patching base and 3-way merge...
Auto-merging prepare-image.sh
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 improve upper constraint handling
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-25.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[metal3-io-bot]

@tuminoid: #584 failed to apply on top of branch "release-24.1":

Applying: improve upper constraint handling
Using index info to reconstruct a base tree...
M	Dockerfile
M	prepare-image.sh
Falling back to patching base and 3-way merge...
Auto-merging prepare-image.sh
Auto-merging Dockerfile
CONFLICT (content): Merge conflict in Dockerfile
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 improve upper constraint handling
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-24.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[tuminoid]

@Rozzii will make manual cherry-picks to all maintained release branches.

We also need to consider should we make patch release after fix is merged, as this might/will change the Python dependencies quite drastically. @elfosardo thoughts?