Project

Profile

Help

Issue #7511

Pulp Squeezer status module caching API response and failing

Added by chouseknecht 13 days ago. Updated 12 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

When the squeezer modules instantiate OpenAPI(), the refresh_cache options defaults to 'False'. See https://github.com/pulp/squeezer/blob/develop/plugins/module_utils/openapi.py#L43. I believe This causes the cache to retain API responses, negatively affecting multiple calls to the status module.

For example, the following playbook task fails, if the Pulp API is not available during the first iteration:

- name: Ensure Pulp is up and healthy
  pulp.squeezer.status:
    pulp_url: "http://{{ pulp_api_host }}:{{ pulp_api_port }}"
    username: "{{ pulp_admin_username }}"
    password: "{{ pulp_default_admin_password }}"
  register: result
  until: >
    result.status is defined and
    result.status.database_connection.connected == true and
    result.status.redis_connection.connected == true and
    result.status.online_workers | map(attribute='name') | select('match', '^resource-manager$') | list | count > 0 and
    result.status.online_workers | map(attribute='name') | select('match', '^[0-9]+@.*$') | list | count > 0
  delay: 2
  retries: 60

History

#1 Updated by chouseknecht 13 days ago

Think this is an environmental thing and not reproducible.

#2 Updated by mdellweg 13 days ago

  • Status changed from NEW to POST
  • Assignee set to mdellweg

#3 Updated by mdellweg 12 days ago

  • Status changed from POST to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF