Bug 1837261

Summary: IncompleteRead error
Product: [Fedora] Fedora Reporter: René van Paassen <rene.vanpaassen>
Component: m2cryptoAssignee: Neal Gompa <ngompa13>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: gholms, ngompa13, python-sig
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: m2crypto-0.35.2-7.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-23 02:44:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description René van Paassen 2020-05-19 08:03:42 UTC 
Description of problem:

Using the application "osc", I get in some conditions/some repositories the following message:

```
repa@pascua mtl]$ osc commit
IncompleteRead(0 bytes read)
```

Version-Release number of selected component (if applicable):

Tried both osc as installed by default in Fedora 32 (0.167.1-281.1.4), and the version in the obs://build.opensuse.org/openSUSE:Tools repository. Found a similar report for arch:

https://github.com/openSUSE/osc/issues/771

where the problem was traced down to python-m2crypto, version 0.35.2, same as installed in Fedora 32

```
base) [repa@pascua mtl]$ rpm -q python3-m2crypto
python3-m2crypto-0.35.2-6.fc32.x86_64
```

How reproducible:


Steps to Reproduce:
1. any `osc` command using the remote repository

Actual results:
```
repa@pascua mtl]$ osc commit
IncompleteRead(0 bytes read)
```

Expected results:

Successful commit or more sensible error message. 

Additional info:

The bug apparently depends on the required communication; sometimes it would occur and an `osc update` would then succeed and set the state of the communication to one that would allow a later commit. 

According to information in the link above, this can be caused by a known bug in python-m2crypto that has a fix in a pull request.
Comment 1 Fedora Update System 2020-05-22 01:38:51 UTC 
FEDORA-2020-a8ac9b4d9f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a8ac9b4d9f
Comment 2 Fedora Update System 2020-05-23 02:44:49 UTC 
FEDORA-2020-a8ac9b4d9f has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 3 René van Paassen 2020-05-24 12:28:28 UTC 
Can confirm that the problem is solved. Kudos for the quick fix.