-
Story
-
Resolution: Done
-
Normal
-
None
-
rhel-9.2.0
-
Low
-
Rebase
-
3
-
rhel-sst-rhcos
-
None
-
False
-
-
None
-
Sprint 243 - Update&Remoting, Sprint 244 - Update&Remoting, Sprint 246 - Update&Remoting
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
Description of problem:
We have seen errors during execution of "rpm-ostree rebase" such as
2023-01-24T10:22:58.1065081Z + sudo ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ConnectTimeout=5 -i key/ostree_key admin@192.168.100.51 'sudo rpm-ostree rebase rhel-edge:rhel/9/x86_64/edge'
2023-01-24T10:22:58.2118842Z Warning: Permanently added '192.168.100.51' (ED25519) to the list of known hosts.
2023-01-24T10:24:51.5735033Z Receiving objects; 95% (598/628) 22.2 MB/s 44.4 MB...done
2023-01-24T10:24:51.8932917Z [0m[31merror: [0mWhile pulling rhel/9/x86_64/edge: While fetching http://192.168.100.1/repo/objects/4f/b22270f0a52fb1d6ffafd6a6daaf80711cca57fe4049df3f54176a31bcfe1a.filez: [56] Failure when receiving data from the peer
2023-01-24T10:24:57.1474998Z ##[error]Process completed with exit code 1.
The failure is not persistent, and is normally fixed after retrying several times. Thus, it would be useful to support retry in 'rpm-ostree rebase' as an enhancement.
Version-Release number of selected component (if applicable):
rpm-ostree 2022.19-3.el9
How reproducible:
Steps to Reproduce:
1. Deploy a RHEL-9.2 VM from PSI openstack
2. git clone https://github.com/virt-s1/rhel-edge.git
3. cd rhel-edge && ./ostree-8-to-9.sh
Actual results:
Error [56] Failure when receiving data from the peer
Expected results:
No error
Additional info:
- is incorporated by
-
RHEL-14381 Update to 2023.8
- Closed
- external trackers