Description of problem: Running inventory job in Beaker using restraint test harness fails to send inventory job results, due to: WARNING **: Internal Server Error: Unable to send Version-Release number of selected component (if applicable): distro: RHEL-ALT-7.5 Server aarch64 kernel-alt: 4.14.0-49.el7a restraint: 0.1.33-1.el7 task: /distribution/inventory 1.2-8 How reproducible: Yes issue is reproducible Steps to Reproduce: 1. Install aarch64 system with 4.14.0-49.el7a using restraint test harness (ks_meta="harness='restraint-rhts beakerlib beakerlib-redhat'") 2. Actual results: https://beaker.engineering.redhat.com/jobs/2533237 http://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2018/06/25332/2533237/5247231/console.log ---<-snip->--- [ 75.578392] restraintd[4182]: ** Running task: 73404341 [/distribution/inventory] [ 78.674527] restraintd[4182]: ** (restraintd:4182): WARNING **: Internal Server Error: Unable to send //recipes/5247231/tasks/73404341/results/, delaying 3 seconds.. [ 82.124102] restraintd[4182]: ** (restraintd:4182): WARNING **: Internal Server Error: Unable to send //recipes/5247231/tasks/73404341/results/, delaying 4 seconds.. [ 86.116172] restraintd[4182]: ** (restraintd:4182): WARNING **: Internal Server Error: Unable to send //recipes/5247231/tasks/73404341/results/, delaying 6 seconds ---<-snip->--- Expected results: Successful completion of inventory task. Additional info:
All, Using the beah test harness, this issue is not reproducible. --------- see here: --------- distro: RHEL-ALT-7.5 Server aarch64 kernel-alt: 4.14.0-49.el7a beah: 0.7.12-1.el7 task: /distribution/inventory 1.2-8 https://beaker.engineering.redhat.com/jobs/2533241 Best, -pbunyan
All, Here is a restraint reproducer: distro: RHEL-ALT-7.5 Server aarch64 kernel-alt: 4.14.0-49.el7a restraint: 0.1.33-1.el7 task: /distribution/inventory 1.2-8 https://beaker.engineering.redhat.com/recipes/5247725 https://beaker.engineering.redhat.com/recipes/5247725/logs/console.log Best, -pbunyan
Thanks for reporting Paul. Hotfix is scheduled for this morning. *** This bug has been marked as a duplicate of bug 1586049 ***