The newaliases error durring run puppet fuel-infra manifests

Bug #1427568 reported by Dmitry Kaigarodеsev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Sergey Kulanov

Bug Description

During the second puppet run on clean trusty vm I've faced with error below:

Notice: /Stage[main]/System/Exec[/usr/bin/newaliases]/returns: newaliases: fatal: /etc/mailname: cannot open file: No such file or directory
Error: /usr/bin/newaliases returned 75 instead of one of [0]
Error: /Stage[main]/System/Exec[/usr/bin/newaliases]/returns: change from notrun to 0 failed: /usr/bin/newaliases returned 75 instead of one of [0]

I've check the manifests and made a quick research regarding /etc/mailname.
We have a mention of /etc/mailname in /etc/postfix/main.cf:

# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.

So there should be a record in a file '/etc/mailname' with FQDN like 'yourserver.yourdomain.com'
But there is no such file by default in my case.

It's not critical but it would be nice to have a check with create option of file '/etc/mailname' before creating aliases.

Tags: devops puppet
Changed in fuel:
assignee: nobody → Sergey Kulanov (skulanov)
importance: Undecided → Medium
Igor Shishkin (teran)
tags: added: devops puppet
Changed in fuel:
status: New → Confirmed
milestone: none → 6.1.1
milestone: 6.1.1 → 6.1
Revision history for this message
Sergey Kulanov (skulanov) wrote :
Changed in fuel:
status: Confirmed → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.