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

Usage cache on MP+ #327

Closed
2 tasks
mfocko opened this issue Sep 5, 2023 · 1 comment
Closed
2 tasks

Usage cache on MP+ #327

mfocko opened this issue Sep 5, 2023 · 1 comment
Assignees
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.

Comments

@mfocko
Copy link
Member

mfocko commented Sep 5, 2023

Usage cache doesn't work on MP+. Suspected reason is preconfigured Hairpin NAT on the auto-prod cluster.

  • Trying to access Packit Service API on MP+ yields:

    sh-5.1$ curl -vLk https://stg.packit.dev/api/system
    *   Trying 34.235.66.59:443...
    * Connected to stg.packit.dev (34.235.66.59) port 443 (#0)
    …
    

    API URL resolves to the public IP and hangs

  • Trying to access API on auto-prod OTOH yields:

    sh-5.1$ curl -vLk https://prod.packit.dev/api/system
    *   Trying 52.31.82.208:443...
    * Connected to prod.packit.dev (52.31.82.208) port 443 (#0)
    …
    

    API URL again resolves to the public IP, but it doesn't hang.

Trying to use deployment name for DNS results in 403, since we have HTTPD configured to required FQDN.

TODO:

  • Ideally configure the httpd to accept packit-service too apart from the FQDN {deployment}.packit.dev

  • Adjust the API URL on dashboard

    WARNING
    Only in the API part of the dashboard, don't touch frontend, that's resolved client-side (is not affected by this issue and would break with these changes)

@mfocko mfocko added kind/bug Something isn't working. area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. labels Sep 5, 2023
@mfocko mfocko self-assigned this Feb 8, 2024
@mfocko
Copy link
Member Author

mfocko commented Feb 8, 2024

@mfocko mfocko closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/other Related to some other area/category than the specified ones. complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.
Projects
Archived in project
Development

No branches or pull requests

1 participant