CRI-O: fix crio_image regexp

[runcom]

Make it more robust cause it was failing with weird matches.

@stevekuznetsov @mrunalp PTAL

Signed-off-by: Antonio Murdaca runcom@redhat.com

[stevekuznetsov]

You don't need Perl regex for this

[stevekuznetsov]

And in what case does ORIGIN_PKG_VERSION have more than one line?

[runcom]

never, but if you get "-3.9.0-something3.4-something432" you'll get:
3.9
3.4

so, that's why the head

[runcom]

That's what's happening in openshift/openshift-ansible#6449 for instance

-3.9.0-0.alpha.0.169.a2ec324

$ echo "-3.9.0-0.alpha.0.169.a2ec324" | grep -Po '\d\.\d'        1 ↵
3.9
0.1 

[runcom]

You don't need Perl regex for this

do you have any suggestion about doing this w/o perl regexp? I'll happly use your command

[stevekuznetsov]

The current regex can be written without Perl syntax, but we can be more specific anyway. It is fair to assume that we could do:

crio_tag="$( grep -Po "(?<=^-)[0-9]+\.[0-9]+" ./ORIGIN_PKG_VERSION )"

[runcom]

fixed, thanks a ton @stevekuznetsov

[runcom]

Ping @stevekuznetsov 👼

[stevekuznetsov]

$ sjb/push-update-automatic.sh 
[INFO] Checking for existence of test_branch_origin_extended_conformance_crio...
[INFO] Checking for existence of test_pull_request_openshift_ansible_extended_conformance_install_crio...
[INFO] Checking for existence of test_pull_request_origin_extended_conformance_crio...
[INFO] Updating test_branch_origin_extended_conformance_crio...
[INFO] Updating test_pull_request_openshift_ansible_extended_conformance_install_crio...
[INFO] Updating test_pull_request_origin_extended_conformance_crio...