ENT-12151: Added possibility to configure Mission Portal web server ports
Ticket: ENT-12151
@craigcomstock I adjusted distributed_cleanup.py please review
@cf-bottom jenkins
Sure, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11201/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11201/
@cf-bottom jenkins
Sure, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11219/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11219/
right, looks like upgrade deployment tests fail with policy related to this change right?
52.18.130.203 error: Promised replacement " $config["cli_rest_server_url"] = "https://localhost:443/api/";" for pattern "^\s*\$config\["cli_rest_server_url"\]\s*=\s*"https://localhost.*/api/";\s*$" is not properly convergent while editing "/var/cfengine/share/GUI/application/config/config.php" (pattern still matches the end-state replacement string " $config["cli_rest_server_url"] = "https://localhost:443/api/";", consider use of a negative look ahead)
52.18.130.203 error: Errors encountered when actuating replace_patterns promise "^\s*\$config\["cli_rest_server_url"\]\s*=\s*"https://localhost.*/api/";\s*$"
@cf-bottom jenkins
Sure, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11239/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11239/
looks like the policy might need some fixing for upgrade deployment tests in sequential-tests job.
yes, trying config changing only if the port is changed. should help 🤞
@cf-bottom jenkins
Sure, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11243/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11243/
@cf-bottom jenkins
Alright, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11247/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11247/
@cf-bottom jenkins
Alright, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11256/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11256/
sequential-tests tests failed, I guess is not related
Errors when installing master version HUB packages:
+ grep -P "(err|fail)" .27351.install.log.filtered
52.214.238.164 check for "/var/cfengine/bin/psql" failed: cannot execute
34.244.0.54 check for "/var/cfengine/bin/psql" failed: cannot execute
34.249.48.171 check for "/var/cfengine/bin/psql" failed: cannot execute
54.75.79.92 check for "/var/cfengine/bin/psql" failed: cannot execute
restarted it
sequential-tests tests failed, I guess is not related
Errors when installing master version HUB packages: + grep -P "(err|fail)" .27351.install.log.filtered 52.214.238.164 check for "/var/cfengine/bin/psql" failed: cannot execute 34.244.0.54 check for "/var/cfengine/bin/psql" failed: cannot execute 34.249.48.171 check for "/var/cfengine/bin/psql" failed: cannot execute 54.75.79.92 check for "/var/cfengine/bin/psql" failed: cannot executerestarted it
Correct, this is a known issue. https://northerntech.atlassian.net/browse/ENT-12383
It isn't a flake so a restart/retry won't help. We/I will fix soon.
sequential-tests tests failed, I guess is not related
Errors when installing master version HUB packages: + grep -P "(err|fail)" .27351.install.log.filtered 52.214.238.164 check for "/var/cfengine/bin/psql" failed: cannot execute 34.244.0.54 check for "/var/cfengine/bin/psql" failed: cannot execute 34.249.48.171 check for "/var/cfengine/bin/psql" failed: cannot execute 54.75.79.92 check for "/var/cfengine/bin/psql" failed: cannot executeCorrect, this is a known issue. https://northerntech.atlassian.net/browse/ENT-12383
It isn't a flake so a restart/retry won't help. We/I will fix soon.
thanks! I will wait then
@cf-bottom jenkins
Sure, I triggered a build:
Jenkins: https://ci.cfengine.com/job/pr-pipeline/11301/
Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-11301/
@nickanderson @craigcomstock now, when tests are passed, please re-review the code. thanks!
looks like the policy might need some fixing for upgrade deployment tests in sequential-tests job.
@craigcomstock can you please re-review?