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

Bug 50667

Summary: %post scriplet fails if /usr is mounted ro
Product: [Retired] Red Hat Linux Reporter: Enrico Scholz <rh-bugzilla>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED RAWHIDE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: fweimer
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-08-08 13:27:27 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:

Description Enrico Scholz 2001-08-01 22:43:58 UTC
Description of Problem:

When having /usr mounted read-only and put into rpm's %_netsharedpath, the
%post scriplet of glibc fails at updating. This leads to an inconsistent
rpm database (two glibc's are installed).

Strace'ing the /usr/sbin/glibc_post_upgrade command says:

[pid 23439] open("/usr/lib/gconv/gconv-modules.cache",
O_RDWR|O_CREAT|O_TRUNC, 0644) = -1 EROFS (Read-only file system)
[pid 23439] _exit(1)                    = ?
<... wait4 resumed> [WIFEXITED(s) && WEXITSTATUS(s) == 1], 0, NULL) = 23439
--- SIGCHLD (Child exited) ---
_exit(1)                                = ?


How Reproducible:

everytime


Steps to Reproduce:
1. mount -o remount,ro
2. echo '%_netsharedpath /usr' >/etc/rpm/macros
3. rpm -U glibc-2.2.3-19.1
4. rpm -q glibc


Actual Results:

(3) execution of %post scriptlet from glibc-2.2.3-19.1 failed, exit status 1
(4) 
glibc-2.2.3-19
glibc-2.2.3-19.1


Expected Results:

(3) no message
(4) glibc-2.2.3-19.1


Additional Information:
	
tested with glibc-2.2.3-19.1 but happens with 2.2.3-19 also.

Comment 1 Glen Foster 2001-08-02 21:43:35 UTC
This defect is considered MUST-FIX for Fairfax

Comment 2 Jakub Jelinek 2001-08-06 20:29:27 UTC
Should be fixed in glibc-2.2.4-2.

Comment 3 Bill Nottingham 2001-08-23 13:19:19 UTC
Please reopen if this persists with that version or later.