Bug 1476156

Summary:	Extract upgrade from RPM script to separate executable file
Product:	Red Hat Enterprise Linux 8	Reporter:	Martin Bašti <mbasti>
Component:	bind-dyndb-ldap	Assignee:	Alexander Bokovoy <abokovoy>
Status:	CLOSED WONTFIX	QA Contact:	ipa-qe <ipa-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	---	CC:	pcech, pvoborni
Target Milestone:	rc	Keywords:	Reopened
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-30 14:13:54 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:
Bug Blocks:	1475946

Description Martin Bašti 2017-07-28 07:38:54 UTC

Description of problem:
In containers RPM post update scriptlets are not working. Please extract upgrade to separate executable file, we need to run this script during container upgrade.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install ipa-server-docker container on RHEL 7.3.x
2. Upgrade container to RHEL 7.4 version
3. Error: invalid syntax in named.conf

Actual results:
Named did not start

Expected results:
Named will start

Additional info:
Related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1475946

Comment 2 Martin Bašti 2017-07-28 08:34:27 UTC

We can call RPM postscriptlet manually in containers, so we can close this.

Comment 3 Martin Bašti 2017-07-28 15:03:32 UTC

Reopening, it is not time critical, but it is better to have a single indempotent script responsible for updates than hacking RPM post scriptlets in container.

Comment 10 Petr Čech 2020-11-30 14:13:54 UTC

This BZ has been evaluated multiple times over the last several years and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Time showed that we did not have such capacity, nor have it now nor will have in the foreseeable future. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or open a new support case and create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome!
Thank you for understanding
Red Hat Enterprise Linux Identity Management Team