Fixed problem with package upgrade not trying other migration methods if pg_upgrade fails

[craigcomstock]

Ticket: ENT-12383
Changelog: none

[craigcomstock]

@cf-bottom jenkins please

[cf-bottom]

Alright, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11309/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11309/

[craigcomstock]

@cf-bottom jenkins

[cf-bottom]

Sure, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11314/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11314/

[craigcomstock]

build broken from mission-portal/public/scripts npm package version changes. Maybe a fix here: https://github.com/cfengine/mission-portal/pull/2643

[craigcomstock]

I manually tested 3.21.5 -> 3.25.0a (this package) and pg_upgrade worked fine.
Previously pg_upgrade had trouble when we migrated openssl versions from 1.x to 3.x which was introduced around 3.20.0.
Upgrade from 3.18.8 -> this package worked fine as well! Maybe because we removed LD_LIBRARY_PATH from our pg_upgrade command!?

Anyhow, looks promising as-is.

[craigcomstock]

@cf-bottom jenkins after https://github.com/cfengine/mission-portal/pull/2643 is merged bootstrap-pr should be green again at least.

[cf-bottom]

Alright, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11315/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11315/

[craigcomstock]

This PR timed out in sequential-tests, not sure why. With the debian-12 hub.

20:22:15 52.213.12.49	R: Note: All recommendations can be disabled by defining 'default:cfengine_recommendations_disabled'
21:02:15 Build timed out (after 40 minutes). Marking the build as aborted.

I will retry just the one job.

[craigcomstock]

try again:

[craigcomstock]

@cf-bottom jenkins please.

[cf-bottom]

Sure, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11327/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11327/

[craigcomstock]

Got some packages but sequential-tests didn't make it to the upgrade tests. Seems we are having a lot of build timeout problems. Made a ticket: https://northerntech.atlassian.net/browse/ENT-12416

I will do some manual testing of a few debian and redhat platforms.

[craigcomstock]

@cf-bottom jenkins please

[cf-bottom]

Alright, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11329/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11329/

[craigcomstock]

bootstrap tests failed with a fixed issue somehow: https://northerntech.atlassian.net/browse/ENT-8264

[craigcomstock]

@cf-bottom jenkins

[cf-bottom]

Sure, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11338/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11338/

[craigcomstock]

@cf-bottom jenkins

[cf-bottom]

Alright, I triggered a build:

Jenkins: https://ci.cfengine.com/job/pr-pipeline/11364/

Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11364/

[craigcomstock]

retries
sequential-tests:

fr-tests:

bootstrap-tests:

[craigcomstock]

try sequential-tests again with working CI system :p

sequential-tests:

[craigcomstock]

trying some sshd options to hopefully improve connectivity and avoid errors which are blocking sequential-tests from reaching upgrade tests I need to check with this change.