Project

Profile

Help

Issue #2655

closed

units_successful is empty for successful ISO assocaiting task

Added by yuzheng about 7 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.12.1
Platform Release:
2.12.2
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 17
Quarter:

Description

Tested version:

# rpm -qa pulp-server
pulp-server-2.12.1-1.el7.noarch

Reproducing steps:

1. Create 2 ISO repos
# pulp-admin iso repo create --repo-id test-repo4
Successfully created repository [test-repo4]

# pulp-admin iso repo create --repo-id test-repo5
Successfully created repository [test-repo5]

2. Upload an ISO to test-repo4
# pulp-admin iso repo uploads upload --repo-id test-repo4 --file 2.iso 
+----------------------------------------------------------------------+
                              Unit Upload
+----------------------------------------------------------------------+

Extracting necessary metadata for each request...
[==================================================] 100%
Analyzing: 2.iso
... completed

Creating upload requests on the server...
[==================================================] 100%
Initializing: 2.iso
... completed

Starting upload of selected units. If this process is stopped through ctrl+c,
the uploads will be paused and may be resumed later using the resume command or
canceled entirely using the cancel command.

Uploading: 2.iso
[==================================================] 100%
2097152/2097152 bytes
... completed

Importing into the repository...
This command may be exited via ctrl+c without affecting the request.

[\]
Running...

Task Succeeded

Deleting the upload request...
... completed

3. Copy ISO from test-repo4 to test-repo5
# pulp-admin iso repo copy --from-repo-id test-repo4 --to-repo-id test-repo5
This command may be exited via ctrl+c without affecting the request.

[\]
Running...

Nothing found that matches the given criteria and repository configuration

4. Get the associating task from DB
db.task_status.find({task_id:"f22583f3-b9a8-4b3e-9532-1f5c0cc450a5"})

/* 0 */
{
    "_id" : ObjectId("58d1e155a2374cc00811e375"),
    "task_id" : "f22583f3-b9a8-4b3e-9532-1f5c0cc450a5",
    "exception" : null,
    "task_type" : "pulp.server.managers.repo.unit_association.associate_from_repo",
    "tags" : [ 
        "pulp:repository:test-repo5", 
        "pulp:repository:test-repo4", 
        "pulp:action:associate"
    ],
    "finish_time" : "2017-03-22T02:28:37Z",
    "_ns" : "task_status",
    "traceback" : null,
    "spawned_tasks" : [],
    "progress_report" : {},
    "worker_name" : "reserved_resource_worker-1@dhcp-136-68.nay.redhat.com",
    "result" : {
        "units_successful" : []
    },
    "error" : null,
    "group_id" : null,
    "id" : null,
    "state" : "finished",
    "start_time" : "2017-03-22T02:28:37Z"
}

Both the output of 'iso repo copy' and '"units_successful" : []' in task result show nothing's copied. But actually the ISO is copied successfully.

# pulp-admin iso repo list --repo-id test-repo5
+----------------------------------------------------------------------+
                            ISO Repositories
+----------------------------------------------------------------------+

Id:                   test-repo5
Display Name:         None
Description:          None
Content Unit Counts:  
  Iso: 1

This affects result checking which depends on searching units in 'units_successful'.

Also available in: Atom PDF