Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 5264 - no lorax in bugzilla
Summary: no lorax in bugzilla
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.1rC
Hardware: All
OS: Linux
high vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-09-21 02:58 UTC by Eugene Kanter
Modified: 2015-10-28 06:58 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-09-21 15:20:25 UTC

Attachments (Terms of Use)

Description Eugene Kanter 1999-09-21 02:58:39 UTC
Found severity one bug in lorax installer: does not parse
/etc/fstab properly when upgrade requested.

where am I supposed to enter it??? there is no version after
6.0 in bugzilla!

Comment 1 David Lawrence 1999-09-21 15:20:59 UTC
Lorax bugs from the general public should be entered in Bugzilla as
Red Hat Haw Hide bugs which is basically the same thing. Please
reenter your report there and a developer will more likely see it.

Comment 2 openshift-github-bot 2015-10-28 06:58:48 UTC
Commit pushed to master at
Various logs fixes:

- Fix github issue #5264
- Fix github issue #5262 log links missing href
- Fix github #5269 log links for failed, error builds on overview
- Partial fix github #5266, change "connection closed" to "Log complete"
- Add "Logs for build||pod as first line in log viewer
- Fix download log file link in firefox/other browsers w/arbitrary timeout to destroy link
- Limit log link when buildPhase is new, pending on overview page & comment $timeout in function
- Separate closed/err msg, log name out of text, delay init until log tab selected
- Fix github #5428 log error for pod w/2 containers
	*also ensures streamer is closed for a pod log before opening new stream on pod page

Note You need to log in before you can comment on or make changes to this bug.