Closed Bug 566333 Opened 14 years ago Closed 14 years ago

The new batch of rev3 Fedora 64 slaves are not updating with puppet

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: armenzg, Assigned: bhearsum)

References

Details

I deployed a patch on Friday and the new rev3 machines don't have it. I looked into it and I discovered the following:

1) I can't ssh to them with their hostnames (I can use VNC to find out their IP; the /etc/sysconfig/network file seems to be fine)
2) Puppet does not sync up (I think we have to add allow 10.250.51.0/24 to /etc/puppet/fileserver.conf)
3) The clock is in the future up (date -> Mon May 17 16:58:07 PDT 2010)

http://grab.by/4pZa
I'm in the middle of landing my big puppet patch right now. There might be some bustage there. I'm working my way through all the platforms and fixing it.
No longer depends on: 564217
Depends on: 564217
Depends on: 552058
pushing to bhearsum, as he's alreeady working on this.
Assignee: nobody → bhearsum
OS: Mac OS X → Linux
I added this subnet to the fileserver.conf files. I tested one of the new fed64 slaves, which synced up fine now.

Please file an IT bug for the ssh issue.
Status: NEW → RESOLVED
Closed: 14 years ago
OS: Linux → Mac OS X
Resolution: --- → FIXED
Summary: The new batch of rev3 Fedora 64 slaves are not updating with puppet and I can't ssh to them with their hostname → The new batch of rev3 Fedora 64 slaves are not updating with puppet
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.