Bug 2181542

Summary:	update_platforms_check is constantly failing due to bad bash scripting
Product:	Red Hat Enterprise Linux 8	Reporter:	Micah Abbott <miabbott>
Component:	greenboot	Assignee:	Paul Whalen <pwhalen>
Status:	CLOSED MIGRATED	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:	Eliane Ramos Pereira <elpereir>
Priority:	unspecified
Version:	8.7	CC:	bbreard, elpereir, jcastran, miabbott, perobins, pwhalen, virt-bugs, xiaofwan
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2170924	Environment:
Last Closed:	2023-09-05 13:11:40 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:
Bug Depends On:	2170924
Bug Blocks:	1269538, 2181296, 2181297

Description Micah Abbott 2023-03-24 13:26:42 UTC

+++ This bug was initially created as a clone of Bug #2170924 +++

See:  https://github.com/fedora-iot/greenboot/issues/93

The 01_update_platforms_check script is failing because the loop over the UPDATE_PLATFORM_URLS variable is treating the list of URLs as a single value.

The URLs need to be split and checked individually.

Comment 1 RHEL Program Management 2023-09-05 13:08:19 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-05 13:11:40 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.