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

[Bug] CI startup failure #1755

Closed
andrewazores opened this issue Oct 30, 2023 · 8 comments · Fixed by #1756 or #1760
Closed

[Bug] CI startup failure #1755

andrewazores opened this issue Oct 30, 2023 · 8 comments · Fixed by #1756 or #1760
Assignees
Labels
bug Something isn't working

Comments

@andrewazores
Copy link
Member

Current Behavior

Invalid workflow file: .github/workflows/push-ci.yml#L34
The workflow is not valid. .github/workflows/push-ci.yml (Line: 34, Col: 20): Invalid input, skip-itests is not defined in the referenced workflow.

Expected Behavior

CI run on push-to-main should be able to run and pass as normal.

Steps To Reproduce

No response

Environment

Since #1683

Anything else?

image

@andrewazores andrewazores added the bug Something isn't working label Oct 30, 2023
@andrewazores andrewazores moved this to Todo in 2.4.0 release Oct 30, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in 2.4.0 release Oct 30, 2023
@andrewazores
Copy link
Member Author

image

Run redhat-actions/podman-login@v1
Error: Error: Input required and not supplied: username

@andrewazores andrewazores reopened this Oct 30, 2023
@aali309
Copy link
Contributor

aali309 commented Oct 30, 2023

image

Run redhat-actions/podman-login@v1
Error: Error: Input required and not supplied: username

I have no clue why it is saying username not supplied when it is supplied on ci-build-image.yml file

@tthvo
Copy link
Member

tthvo commented Oct 30, 2023

I think the argument to the line below is empty since it is a push event, not a comment event:

https://github.com/cryostatio/cryostat/blob/d33cc44ea19274b3cedddee32846250d6f881a57/.github/workflows/ci-build-image.yml#L71

@andrewazores
Copy link
Member Author

Looks right. @aali309 I'm looking at that build-image step again and I'm still not sure I see why exactly the podman-login action is required. Which subsequent step in that workflow is interacting with ghcr.io? And why would it need to use a commenting user's username as the login while using the secrets.GITHUB_TOKEN as the password?

Can we try just removing the podman-login step and see if anything actually breaks?

@aali309
Copy link
Contributor

aali309 commented Oct 31, 2023

yes when I remove the podman-login

image

workflow LINK: https://github.com/aali309/cryostat/actions/runs/6700548654/job/18206670997

on merge:
image

push-ci workflow LINK: https://github.com/aali309/cryostat/actions/runs/6700624381

@andrewazores
Copy link
Member Author

Okay, so removing the podman-login looks OK then. Now it's failing on downloading from the GH Packages Maven repository, so there needs to be some setup with maven-settings ie. ~/.m2/settings.xml.

@aali309
Copy link
Contributor

aali309 commented Oct 31, 2023

with podman login

/build_test LINK: https://github.com/aali309/cryostat/actions/runs/6700846180

image

retest LINK: https://github.com/aali309/cryostat/actions/runs/6700928824

image

Push to quay fails is expected to fail I assume because of the access restrictions (i.e username+password).
push-ci workflow LINK: https://github.com/aali309/cryostat/actions/runs/6700718429
image

@aali309
Copy link
Contributor

aali309 commented Oct 31, 2023

Okay, so removing the podman-login looks OK then. Now it's failing on downloading from the GH Packages Maven repository, so there needs to be some setup with maven-settings ie. ~/.m2/settings.xml.

I will try this option tomorrow morning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Status: Done
3 participants