Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1091365 - Push Scout Config Alert Message has wrong tags
Summary: Push Scout Config Alert Message has wrong tags
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 2.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space22
TreeView+ depends on / blocked
 
Reported: 2014-04-25 12:37 UTC by Martin Minar
Modified: 2016-07-04 00:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-17 08:41:44 UTC
Embargoed:

Attachments (Terms of Use)

Comment 2 Jan Pazdziora 2014-04-26 12:12:21 UTC 
Could this Spacewalk bugzilla be made public?
Comment 5 Martin Minar 2014-04-30 09:10:04 UTC 
Push Scout Configs alert message (and all perl pages alert messages) are using old <div class="site-info"> while new styling in SW is using <div class="alert alert-info">

Version-Release number of selected component (if applicable):
SW Nightly, SW 2.1

How reproducible:
100%

Steps to Reproduce:
1. Go to https://<FQDN>/network/monitoring/scout/index.pxt (Monitoring>Scout Config Push)
2. Try to push one config


Actual results:
<div class="site-info">
<strong>Config Push Initiated</strong>
<br>
</div>

Expected results:
Something like:
<div class="alert alert-info">Config Push Initiated</div>
Comment 6 Tomáš Kašpárek 2014-04-30 09:37:36 UTC 
fixed in spacewalk master: 714f4edc4a21e1ce84dc70ee78e4848592a2f31a
Comment 8 Milan Zázrivec 2014-07-17 08:41:44 UTC 
Spacewalk 2.2 has been released:

    https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22
Note You need to log in before you can comment on or make changes to this bug.