Bug 1104175

Summary:	When publishing content view, it always shows same next version number
Product:	Red Hat Satellite	Reporter:	Matej Kollar <mkollar>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bbuckingham, cperry, daviddavis, jcallaha, omaciel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/8255
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 05:09:09 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:

Description Matej Kollar 2014-06-03 12:45:30 UTC

Description of problem: When publishing content view, it always shows same next version number


How reproducible: always/deterministic


Steps to Reproduce:
  1. create content view
  2. click "Publish New Version"
  3. click "Save"
  4. wait for publish to happen
  5. goto 2 unless bored

Actual results: When publishing, next version (Version) is always indicated to be 1 (can be different, depending on when you entered the loop).

Expected results: Either correct version is indicated, or no next version is indicated (after all, someone may create next version somewhere else... just before this...).

Additional info: If you do some action that forces reload page, then version is ok... till next loop iteration.

Comment 1 RHEL Program Management 2014-06-03 13:15:31 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Brad Buckingham 2014-08-05 16:28:04 UTC

*** Bug 1124524 has been marked as a duplicate of this bug. ***

Comment 4 Brad Buckingham 2014-08-11 12:51:22 UTC

*** Bug 1127732 has been marked as a duplicate of this bug. ***

Comment 5 Justin Sherrill 2014-11-04 02:56:50 UTC

Created redmine issue http://projects.theforeman.org/issues/8255 from this bug

Comment 6 Bryan Kearney 2014-11-05 15:02:06 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/8255 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|cd7a27d674a1bca63fbd076bc4ff57c3765e5cc3.

Comment 7 jcallaha 2014-11-14 18:13:47 UTC

*** This bug is verified in upstream. This fix should eventually land in future downstream builds ***
RHEL65 / RHEL7

Version Tested:
foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch
yttrium.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch
foreman-gce-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch
foreman-vmware-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
foreman-release-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch
foreman-postgresql-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch
rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch
foreman-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
foreman-ovirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch
foreman-libvirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
foreman-compute-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch
ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch
yttrium.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch

Comment 9 Bryan Kearney 2015-08-11 13:28:30 UTC

This bug is slated to be released with Satellite 6.1.

Comment 10 errata-xmlrpc 2015-08-12 05:09:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592