Bug 1780092

Summary:	Module stream mysql:8.0 does not have correct module.md file [rhel-8.3.0]
Product:	Red Hat Enterprise Linux 8	Reporter:	Honza Horak <hhorak>
Component:	mysql-8.0-module	Assignee:	Michal Schorm <mschorm>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	databases-maint
Target Milestone:	rc	Keywords:	ZStream
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1874040 1874042 1874044 (view as bug list)		Environment:
Last Closed:	2020-09-15 19:09:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1780081, 1874040, 1874042, 1874044

Description Honza Horak 2019-12-05 12:03:37 UTC

Based on the content in https://src.osci.redhat.com/modules/mercurial/raw/4.8-rhel-8.2.0/f/mercurial.yaml, the module stream mercurial:4.8 does not define 'name' and 'stream' properly in the module.md file. Reason for doing it was explained in
http://post-office.corp.redhat.com/archives/rhel-devel/2019-March/msg00612.html

Further documentation in RHEL-8 Developer Guide:
https://docs.google.com/document/d/1IFFvXKvNZpLWAMS9-870bahMMtsWru8QOCIREmkd_58/edit#heading=h.lln13r876joj

Building a module in MBS from production branches (those with rhel-x.y.q suffix) might result in a module mercurial:4.8-rhel-x.y.q instead of mercurial:4.8, which is sometimes not that obvious. It is more than recommended to fix the module.md file right away and avoid problems in the future.

Check the tracker https://bugzilla.redhat.com/show_bug.cgi?id=1780081 for more info.