#117 modularity_install_module fails on Rawhide as nodejs:8 not present
Closed: Fixed 4 years ago by adamwill. Opened 4 years ago by michelmno.

modularity_install_module fails on Rawhide as nodejs:8 not present
as reported for all arches in:
x86_64: https://openqa.stg.fedoraproject.org/tests/562929#step/modularity_install_module/10
ppc64le: https://openqa.stg.fedoraproject.org/tests/563012#step/modularity_install_module/10
aarch64: https://openqa.stg.fedoraproject.org/tests/563052#step/modularity_install_module/10

I do not know if need to support different stream parameter for different releases
or if need to dynamically identify a valid stream after list output.

fedora f29
https://dl.fedoraproject.org/pub/fedora-secondary/updates/testing/29/Modular/ppc64le/Packages/n/
[   ] nodejs-11.14.0-2.module_f29+4062+460da852.ppc64le.rpm              2019-04-26 17:49  108K  
[   ] nodejs-12.4.0-1.module_f29+4532+ea069662.ppc64le.rpm               2019-06-05 12:43  341K  
[   ] nodejs-8.16.0-1.module_f29+3973+0f3d85d2.ppc64le.rpm               2019-04-24 12:29  7.7M  
fedora f30:
https://dl.fedoraproject.org/pub/fedora-secondary/updates/testing/30/Modular/ppc64le/Packages/n/
[   ] nodejs-10.16.0-1.module_f30+4443+ece03b17.ppc64le.rpm              2019-06-03 18:58  101K  
[   ] nodejs-11.14.0-1.module_f30+3903+cd71f01a.ppc64le.rpm              2019-04-12 02:58  108K  
[   ] nodejs-12.4.0-1.module_f30+4533+e9fd3656.ppc64le.rpm               2019-06-05 12:44  341K  
fedora Rawhide (futur f31)
 https://dl.fedoraproject.org/pub/fedora-secondary/development/rawhide/Modular/ppc64le/os/Packages/n/
[   ] nodejs-10.16.0-1.module_f31+4441+699f2347.ppc64le.rpm                     2019-05-31 15:02  102K  
[   ] nodejs-11.14.0-2.module_f31+4061+9eaac59d.ppc64le.rpm                     2019-04-25 16:11  109K  
[   ] nodejs-12.4.0-1.module_f31+4534+11b6d132.ppc64le.rpm                      2019-06-04 22:51  342K  

Hmm. Well, at least at first, that was a real bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1691030

so I've been figuring it's the same ever since. But actually it looks like it's present again, just the stream number in the test needs updating...I'll fix that. Thanks.

Metadata Update from @adamwill:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Yeah, I was surprised to see that that test was failing, so I checked and realized that the version 8 has gone, so I changed the stream :)

Log in to comment on this ticket.

Metadata