Project

General

Profile

Bug #9875

GUMS1 network puppet setup is bad (goes to em* instead to eth*)

Added by Gerard Bernabeu Altayo about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Start date:
08/21/2015
Due date:
% Done:

100%

Estimated time:
Spent time:
Duration:

Description

This is a follow-up from CHG000000009852.

The setup was manually fixed on gums1, puppet is trying to roll it back and it needs to be fixed:

Notice: /Stage[main]/P_virtual_ip::Gums_mysql/P_virtual_ip::Sysconfig[em1:1]/File[/etc/sysconfig/network-scripts/ifcfg-em1:1]/ensure: current_value absent, should be present (noop)
Notice: P_virtual_ip::Sysconfig[em1:1]: Would have triggered 'refresh' from 1 events
Notice: Class[P_virtual_ip::Gums_mysql]: Would have triggered 'refresh' from 1 events
Notice: Class[S_gums::Dcso_specifies]: Would have triggered 'refresh' from 1 events
Notice: /Stage[main]/P_virtual_ip::Gums/P_virtual_ip::Sysconfig[em1:0]/File[/etc/sysconfig/network-scripts/ifcfg-em1:0]/ensure: current_value absent, should be present (noop)
Notice: P_virtual_ip::Sysconfig[em1:0]: Would have triggered 'refresh' from 1 events
Notice: Class[P_virtual_ip::Gums]: Would have triggered 'refresh' from 1 events

Since the impact potential is high (the server does not reboot or does not bring the right networks up), how we go to this situation needs to be understood.

History

#1 Updated by Merina Albert about 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
  • Estimated time deleted (4.00 h)

I am not sure why this happened but OS renamed the network device to eth0. It used to be em* . I have changed puppet to reflect this change. Hopefully the system keep the name eth0.



Also available in: Atom PDF