New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 771256 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

chromeos-ddns3.cbf is not retrieving the latest updates.

Project Member Reported by haoweiw@google.com, Oct 3 2017

Issue description

Noticed chromeos-ddns3.cbf dhcp config file is still old 

Example, old on ddns3.cbf
zone cros.corp.google.com. {
  primary 172.24.189.79;
}

zone 115.100.in-addr.arpa. {
  primary 172.24.189.79;
}

should be:
zone cros.corp.google.com. {
  primary 100.109.178.168;
}

zone 115.100.in-addr.arpa. {
  primary 100.109.178.168;
}


 
Since I'm ignorant, how are these files supposed to be updated? Puppet?

Comment 2 by haoweiw@google.com, Oct 3 2017

Yes, i can see puppet is running. But not sync. 

19491 pts/5    S+     0:00 /bin/bash /root/chromeos-admin/puppet/sync_and_run_puppet
19606 ?        Ss     0:00 /bin/sh -c /root/chromeos-admin/puppet/sync_and_run_puppet 2>&1 | /usr/bin/logger -t sync_and_run_puppet -i
19621 ?        S      0:00 /bin/bash /root/chromeos-admin/puppet/sync_and_run_puppet
19622 ?        S      0:00 /usr/bin/logger -t sync_and_run_puppet -i

Do you know if this could this cause http://crbug.com/770632 ?
I see some errors in syslog for sync_and_run_puppet relating to export_to_cloud_trace. I'm uncertain whether they're fatal, or whether puppet is continuing past them.
Status: Fixed (was: Untriaged)
ok dhcp.conf actuall looks up to date now. I'm not sure why it got better, but closing this for now.

Comment 6 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 7 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment