We are using pulpcore.client.pulp_rpm to query pulp remote objects to compare 
the client_key to make sure we always have valid entitlement in pulp. We 
current running 3.7.3

After we upgraded to 3.15.2 and installed pulp-rpm-client 3.15.0. We got the 
following error 
AttributeError: 'RpmRpmRemoteResponse' object has no attribute 'client_key'.

Should the  'RpmRpmRemoteResponse' has client_key attribute as previous 
releases?


class RpmRpmRemoteResponse(builtins.object)
 |  RpmRpmRemoteResponse(pulp_href=None, pulp_created=None, name=None, 
url=None, ca_cert=None, client_cert=None, tls_validation=None, proxy_url=None, 
pulp_labels=None, pulp_last_updated=None, download_concurrency=None, 
max_retries=None, policy=None, total_timeout=None, connect_timeout=None, 
sock_connect_timeout=None, sock_read_timeout=None, headers=None, 
rate_limit=None, sles_auth_token=None, local_vars_configuration=None)


class RpmRpmRemote(builtins.object)
  |  RpmRpmRemote(name=None, url=None, ca_cert=None, client_cert=None, 
client_key=None, tls_validation=None, proxy_url=None, proxy_username=None, 
proxy_password=None, username=None, password=None, pulp_labels=None, 
download_concurrency=None, max_retries=None, policy=None, total_timeout=None, 
connect_timeout=None, sock_connect_timeout=None, sock_read_timeout=None, 
headers=None, rate_limit=None, sles_auth_token=None, 
local_vars_configuration=None)


_______________________________________________
Pulp-list mailing list
Pulp-list@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-list

Reply via email to