Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 553296

Summary:	Remove unsupported checksum types from DB
Product:	[Retired] Red Hat Network	Reporter:	Denise Hughes <dhughes>
Component:	RHN/Web Site	Assignee:	Sebastian Skracic <sskracic>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Denise Hughes <dhughes>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rhn513	CC:	acarter, nbronson, rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://rhn.webdev.redhat.com/network/software/channels/manage/edit.pxt
Whiteboard:	US451
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-18 12:48:56 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:	519193, 552914

Description Denise Hughes 2010-01-07 15:30:57 UTC

Description of problem:

Remove unsupported checksum types from DB.

Sebastian, please note which pages in the webui will be affected by this change.

Comment 1 Sebastian Skracic 2010-01-07 15:41:03 UTC

The checksum type dropdown widget appears only on custom channel creation page:
https://rhn.webdev.redhat.com/network/software/channels/manage/edit.pxt

Comment 2 Sebastian Skracic 2010-01-07 15:41:37 UTC

The offending checksum types have been removed from WEBDEV database, so setting to ON_DEV.

Comment 3 Denise Hughes 2010-01-07 19:03:57 UTC

Verified the rhnChecksumType table has been updated to only have md5, sha1 and sha-256.
Verified the RPM Checksum Method dropdown list on the Create New Channel page includes md5, sha1 and sha-256.
Verified a new channel can be created with each checksum type.
Verified rhnChannel table updated with new channel and correct checksum type.

Question: Do we need to update the API?

Comment 4 Sebastian Skracic 2010-01-08 12:34:49 UTC

It turned out API did not need any adjustments, bar from the line in the API doc stating what checksum types are available.  This line has been fixed in 84df668699528b7b829636885897b5b14e375743.