Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scalability workflow failed waiting for CHT to be up. #8578

Closed
tatilepizs opened this issue Sep 22, 2023 · 3 comments
Closed

Scalability workflow failed waiting for CHT to be up. #8578

tatilepizs opened this issue Sep 22, 2023 · 3 comments
Assignees
Labels
Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Milestone

Comments

@tatilepizs
Copy link
Contributor

Doing the release process for cht-core 4.4.0 the scalability workflow, specifically the job Set up Medic on EC2 and Execute Jmeter on another EC2 constantly failed waiting for CHT to be up.

Logs here

image

@tatilepizs tatilepizs added the Type: Bug Fix something that isn't working as intended label Sep 22, 2023
@tatilepizs tatilepizs mentioned this issue Sep 22, 2023
28 tasks
@dianabarsan
Copy link
Member

The issue that I know exists is that the condition that another workflow succeeded didn't work (?), so when the scalability workflow starts, it actually tries to install a version that doesn't yet exist on the staging server.
I will check to see if something else is happening.

@dianabarsan dianabarsan self-assigned this Sep 26, 2023
@dianabarsan
Copy link
Member

This is failing on apt-get update with:

Ign:1 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic InRelease
Ign:2 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-updates InRelease
Ign:3 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-backports InRelease
Err:4 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic Release
  404  Not Found [IP: 35.183.6.146 80]
Err:5 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-updates Release
  404  Not Found [IP: 35.183.6.146 80]
Err:6 http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-backports Release
  404  Not Found [IP: 35.183.6.146 80]
Ign:7 http://security.ubuntu.com/ubuntu kinetic-security InRelease
Err:8 http://security.ubuntu.com/ubuntu kinetic-security Release
  404  Not Found [IP: 185.125.190.39 80]
Reading package lists... Done
E: The repository 'http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ca-central-1.ec2.archive.ubuntu.com/ubuntu kinetic-backports Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu kinetic-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

dianabarsan added a commit that referenced this issue Oct 5, 2023
Old API could run apt-get update command any more.
Adds wait for build to be on the market, as opposed to crafting some convoluted GH actions settings (tried and didn't work) to wait for a different workflow to be successful.

#8578
@dianabarsan dianabarsan added this to the 4.5.0 milestone Oct 5, 2023
@dianabarsan
Copy link
Member

Merged to master

@dianabarsan dianabarsan added Type: Technical issue Improve something that users won't notice Testing Affects how the code is tested and removed Type: Bug Fix something that isn't working as intended labels Oct 5, 2023
Benmuiruri pushed a commit that referenced this issue Oct 26, 2023
Old API could run apt-get update command any more.
Adds wait for build to be on the market, as opposed to crafting some convoluted GH actions settings (tried and didn't work) to wait for a different workflow to be successful.

#8578
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

2 participants