yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

Public bug reported:

cloud-init-integration-lxd-b test 200 failed.
Looking at the console log at [1] shows
  boot instance encountered error: ssh: after 120s instance is not reachable
at 2018-06-26 11:23:47,693 which was indeed 120 seconds after starting the
salt minion test.

The summary of the failure is just that salt failed to restart due to dns
lookup problems of a host 'salt'.

The corresponding cloud-init log [2] progresses well until

  2018-06-26 11:22:16,726 - util.py[DEBUG]: Running command ['service', 'salt-minion', 'restart'] with allowed return codes [0] (shell=False, capture=False)
  2018-06-26 11:23:47,032 - handlers.py[DEBUG]: finish: modules-final/config-salt-minion: SUCCESS: config-salt-minion ran successfully

So 'service salt-minion restart' took ~ 90 seconds.
 $ journalctl --file=system.journal --unit=salt-minion.service | pastebinit
 http://paste.ubuntu.com/p/jjkrs3nhYF/

Lines of most interest there are 3 times:
  Jun 26 07:22:17 [1241]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
  Jun 26 07:22:17 [1241]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds

[1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd-b/200/consoleFull
[2] https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd-b/200/artifact/cloud-init/results/lxd/bionic/modules/salt_minion/cloud-init.log

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1778737

Title:
  salt-minion test needs fixing

Status in cloud-init:
  New

Bug description:
  cloud-init-integration-lxd-b test 200 failed.
  Looking at the console log at [1] shows
    boot instance encountered error: ssh: after 120s instance is not reachable
  at 2018-06-26 11:23:47,693 which was indeed 120 seconds after starting the
  salt minion test.

  The summary of the failure is just that salt failed to restart due to dns
  lookup problems of a host 'salt'.

  The corresponding cloud-init log [2] progresses well until

    2018-06-26 11:22:16,726 - util.py[DEBUG]: Running command ['service', 'salt-minion', 'restart'] with allowed return codes [0] (shell=False, capture=False)
    2018-06-26 11:23:47,032 - handlers.py[DEBUG]: finish: modules-final/config-salt-minion: SUCCESS: config-salt-minion ran successfully

  So 'service salt-minion restart' took ~ 90 seconds.
   $ journalctl --file=system.journal --unit=salt-minion.service | pastebinit
   http://paste.ubuntu.com/p/jjkrs3nhYF/

  Lines of most interest there are 3 times:
    Jun 26 07:22:17 [1241]: [ERROR   ] DNS lookup or connection check of 'salt' failed.
    Jun 26 07:22:17 [1241]: [ERROR   ] Master hostname: 'salt' not found or not responsive. Retrying in 30 seconds

  [1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd-b/200/consoleFull
  [2] https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd-b/200/artifact/cloud-init/results/lxd/bionic/modules/salt_minion/cloud-init.log

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1778737/+subscriptions