Failure: test_yum_refresh_updates_remote RuntimeError: Neutered Exception ForemanTasks::TaskError: Task 5fb81786-9e87-4d12-8261-9c5f0a68e085: VCR::Errors::UnhandledHTTPRequestError: ================================================================================ An HTTP request has been made that VCR does not know how to handle: POST https://fv-az1110-55/pulp/api/v3/acs/rpm/rpm/ VCR is currently using the following cassette: - /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_updates_remote.yml - :record => :none - :match_requests_on => [:method, :path, :params, :body_json] Under the current configuration VCR can not find a suitable HTTP interaction to replay and is prevented from recording new requests. There are a few ways you can deal with this: * If you're surprised VCR is raising this error and want insight about how VCR attempted to handle the request, you can use the debug_logger configuration option to log more details [1]. * You can use the :new_episodes record mode to allow VCR to record this new request to the existing cassette [2]. * If you want VCR to ignore this request (and others like it), you can set an `ignore_request` callback [3]. * The current record mode (:none) does not allow requests to be recorded. You can temporarily change the record mode to :once, delete the cassette file and re-run your tests to allow the cassette to be recorded with this request [4]. * The cassette contains 32 HTTP interactions that have not been played back. If your request is non-deterministic, you may need to change your :match_requests_on cassette option to be more lenient or use a custom request matcher to allow it to match [5]. [1] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/debug_logging [2] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/new_episodes [3] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/ignore_request [4] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/none [5] https://benoittgt.github.io/vcr/?v=6-3-1#/request_matching ================================================================================ foreman-tasks (10.0.2) lib/foreman_tasks.rb:56:in `block in sync_task' foreman-tasks (10.0.2) lib/foreman_tasks.rb:55:in `sync_task' katello/test/actions/pulp3/orchestration/alternate_content_source_refresh_test.rb:62:in `test_yum_refresh_updates_remote' katello/test/support/vcr.rb:24:in `block in run' katello/test/support/vcr.rb:23:in `run'

Process completed with exit code 1.

Failure: test_yum_refresh RuntimeError: Neutered Exception ForemanTasks::TaskError: Task a2d71acf-6d6a-4640-ac02-4665ed108f6d: VCR::Errors::UnhandledHTTPRequestError: ================================================================================ An HTTP request has been made that VCR does not know how to handle: POST https://fv-az802-3/pulp/api/v3/acs/rpm/rpm/ VCR is currently using the following cassette: - /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh.yml - :record => :none - :match_requests_on => [:method, :path, :params, :body_json] Under the current configuration VCR can not find a suitable HTTP interaction to replay and is prevented from recording new requests. There are a few ways you can deal with this: * If you're surprised VCR is raising this error and want insight about how VCR attempted to handle the request, you can use the debug_logger configuration option to log more details [1]. * You can use the :new_episodes record mode to allow VCR to record this new request to the existing cassette [2]. * If you want VCR to ignore this request (and others like it), you can set an `ignore_request` callback [3]. * The current record mode (:none) does not allow requests to be recorded. You can temporarily change the record mode to :once, delete the cassette file and re-run your tests to allow the cassette to be recorded with this request [4]. * The cassette contains 33 HTTP interactions that have not been played back. If your request is non-deterministic, you may need to change your :match_requests_on cassette option to be more lenient or use a custom request matcher to allow it to match [5]. [1] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/debug_logging [2] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/new_episodes [3] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/ignore_request [4] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/none [5] https://benoittgt.github.io/vcr/?v=6-3-1#/request_matching ================================================================================ foreman-tasks (10.0.2) lib/foreman_tasks.rb:56:in `block in sync_task' foreman-tasks (10.0.2) lib/foreman_tasks.rb:55:in `tap' foreman-tasks (10.0.2) lib/foreman_tasks.rb:55:in `sync_task' katello/test/actions/pulp3/orchestration/alternate_content_source_refresh_test.rb:55:in `test_yum_refresh' katello/test/support/vcr.rb:24:in `block in run' katello/test/support/vcr.rb:23:in `run'

Failure: test_yum_refresh_updates_remote RuntimeError: Neutered Exception ForemanTasks::TaskError: Task e7e6bd1f-913b-4429-a091-c0e81461309a: VCR::Errors::UnhandledHTTPRequestError: ================================================================================ An HTTP request has been made that VCR does not know how to handle: POST https://fv-az802-3/pulp/api/v3/acs/rpm/rpm/ VCR is currently using the following cassette: - /home/runner/work/katello/katello/katello/test/fixtures/vcr_cassettes/actions/pulp3/alternate_content_source_refresh/yum_refresh_updates_remote.yml - :record => :none - :match_requests_on => [:method, :path, :params, :body_json] Under the current configuration VCR can not find a suitable HTTP interaction to replay and is prevented from recording new requests. There are a few ways you can deal with this: * If you're surprised VCR is raising this error and want insight about how VCR attempted to handle the request, you can use the debug_logger configuration option to log more details [1]. * You can use the :new_episodes record mode to allow VCR to record this new request to the existing cassette [2]. * If you want VCR to ignore this request (and others like it), you can set an `ignore_request` callback [3]. * The current record mode (:none) does not allow requests to be recorded. You can temporarily change the record mode to :once, delete the cassette file and re-run your tests to allow the cassette to be recorded with this request [4]. * The cassette contains 32 HTTP interactions that have not been played back. If your request is non-deterministic, you may need to change your :match_requests_on cassette option to be more lenient or use a custom request matcher to allow it to match [5]. [1] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/debug_logging [2] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/new_episodes [3] https://benoittgt.github.io/vcr/?v=6-3-1#/configuration/ignore_request [4] https://benoittgt.github.io/vcr/?v=6-3-1#/record_modes/none [5] https://benoittgt.github.io/vcr/?v=6-3-1#/request_matching ================================================================================ foreman-tasks (10.0.2) lib/foreman_tasks.rb:56:in `block in sync_task' foreman-tasks (10.0.2) lib/foreman_tasks.rb:55:in `tap' foreman-tasks (10.0.2) lib/foreman_tasks.rb:55:in `sync_task' katello/test/actions/pulp3/orchestration/alternate_content_source_refresh_test.rb:62:in `test_yum_refresh_updates_remote' katello/test/support/vcr.rb:24:in `block in run' katello/test/support/vcr.rb:23:in `run'

Process completed with exit code 1.

Process completed with exit code 1.

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636