Description of problem: facter does not report correctly mageia operatingsystem. Version-Release number of selected component (if applicable): mageia 2_b2 facter-1.6.6-1.mga2 How reproducible: Steps to Reproduce: 1.install facter 2.try facter operatingsystem lsbdistid lsbdistid => Mageia operatingsystem => Mandriva lsbdistid is ok operatingsystem is KO ! a bug was open to puppet labs cf : http://projects.puppetlabs.com/issues/9929 i have recorded this mageia bug to remind that facter rpm package must be update as soon as puppet labs give the correct value (wait for facter 2.x ?)
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Keywords: NEEDINFO => (none)CC: (none) => r.wobbenAssignee: bugsquad => johnny
Bug is still valid for Mageia 3. @johnny : Can you take this bug and take care for the solution. The bug at puppetlabs is closed a year ago, Roelof
Interesting. Latest version 1.6.17 came in december, and it still have the error. Meaning it isn't fixed upstream yet. I'll see if I can patch it for the time beeing.
Status: NEW => ASSIGNED
Whiteboard: (none) => MGA2TOO
Fixed in Cauldron. Preparing an update for mga2.
I have uploaded a patched package for Mageia 2 in core/updates_testing. Suggested advisory: ======================== When asked about the installed operating system, facter reports Mageia as being Mandriva. This update fixes this. ======================== Updated noarch packages in core/updates_testing: facter-1.6.6-1.1.mga2.noarch.rpm Source RPM: facter-1.6.6-1.1.mga2.src.rpm
Assignee: johnny => qa-bugs
CC: (none) => johnny
Version: Cauldron => 2Source RPM: (none) => facterWhiteboard: MGA2TOO => (none)
Thanks Johnny. Testing complete mga2 32 Before ------ $ facter | grep '^operatingsystem ' operatingsystem => Mandriva After ----- $ facter | grep '^operatingsystem ' operatingsystem => Mageia lsbdist* still reports Mageia however it has thornicroft as lsbdistcodename, AFAIK Mageia doesn't have a codename, maybe we should do! Also it ves architecture as i386 rather than i586, not sure if that's an issue.
Whiteboard: (none) => has_procedure mga2-32-OK
Testing complete mga2 64 All info displays correctly other than those mentioned in comment 6. Johnny do you want to look at those now or should we validate and push this one?
Whiteboard: has_procedure mga2-32-OK => has_procedure mga2-32-OK mga2-64-OK
I don't know what to change, and I suspect facter is not to blame. So my opinion is to validate and push it.
Beside, the «lsbdistcodename» issue was not part of the bug. ;-)=
Have a new bug then :P Bug 8587 created for lsbdistcodename Bug 8588 created for architecture Validating SRPM and Advisory in comment 5 Could sysadmin please push from core/updates_testing to core/updates Thanks!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2013-0001
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED
And it's back. :-) === $ facter operatingsystem lsbdistid lsbdistid => Mageia operatingsystem => Mandrake === It turns out it is looking at the presense of *.release files in /etc. Just their presense, not the contents. And it seems to pick the first one it finds. When I moved out of etc the symlinks mandrakelinux-release and mandrake-release, the operatingsystem was reported as Mandriva. When also moving out mandriva.release, the operatingsystem was reported as Mageia.
Keywords: validated_update => (none)Status: RESOLVED => REOPENEDHardware: i586 => AllVersion: 2 => CauldronResolution: FIXED => (none)Assignee: qa-bugs => shlomifWhiteboard: has_procedure mga2-32-OK mga2-64-OK => MGA5TOO
And I've found the culprit. The package that triggers this is actually «mageia-release-common». rpm -ql mageia-release-common |head -5 /etc/mageia-release /etc/mandrake-release /etc/mandrakelinux-release /etc/mandriva-release /etc/os-release Meaning, this bug will continue to show up until we stop shipping those old mandrake/mandriva files in the mageia-release package.
It's really facter that should be fixed to resolve symlinks, most distros provide some compat symlinks like that.