failed to test because apache timed out

[Jeff Lane ]

Retried maas-test and this time, it failed to do any testing because apache failed to start:

2013-12-12 10:01:56,783 INFO Checking for KVM extensions.
2013-12-12 10:02:00,933 INFO Checking for virtualised hardware...
2013-12-12 10:02:01,292 INFO Checking for running proxy instance...
2013-12-12 10:02:01,292 INFO Starting proxy...
2013-12-12 10:02:01,333 INFO Done starting proxy.
2013-12-12 10:02:01,363 INFO Downloading KVM image for series=saucy, arch=amd64...
2013-12-12 10:02:06,681 INFO Done downloading KVM image for series=saucy, arch=amd64.
2013-12-12 10:02:06,682 INFO Creating virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790, arch=amd64.
..
2013-12-12 10:02:09,498 INFO Done creating virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790, arch=amd64.
2013-12-12 10:02:09,498 INFO Waiting for the virtual machine to come up...
2013-12-12 10:02:30,241 INFO Virtual machine is running.
2013-12-12 10:02:30,242 INFO Waiting for cloud-init to finish its work...
2013-12-12 10:03:09,357 INFO Cloud-init run finished.
2013-12-12 10:03:09,358 INFO Configuring network interface on virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790...
2013-12-12 10:03:17,514 INFO Done configuring network interface on virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790
2013-12-12 10:03:20,084 INFO Virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790 is ready.
2013-12-12 10:03:20,085 INFO Installing MAAS...
2013-12-12 10:05:05,677 INFO Done installing MAAS.
2013-12-12 10:05:26,169 INFO Destroying virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790...
2013-12-12 10:05:27,193 INFO Done destroying virtual machine 5acb2b28-633e-11e3-9f8f-001f16355790.
2013-12-12 10:05:27,194 INFO Killing proxy...
2013-12-12 10:05:27,199 INFO Done killing proxy.
ERROR

======================================================================
ERROR: setUpClass (maastest.main.ConfiguredTestMAAS)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/maastest/cases.py", line 94, in setUpClass
    cls.fixtures.useFixture(cls.maas)
  File "/usr/lib/python2.7/dist-packages/maastest/cases.py", line 45, in useFixture
    super(ClassFixture, self).useFixture(fixture)
  File "/usr/lib/python2.7/dist-packages/fixtures/fixture.py", line 192, in useFixture
    fixture.setUp()
  File "/usr/lib/python2.7/dist-packages/maastest/maasfixture.py", line 212, in setUp
    self.configure_default_maas_url()
  File "/usr/lib/python2.7/dist-packages/maastest/maasfixture.py", line 126, in configure_default_maas_url
    ['sudo', 'service', 'apache2', 'restart'], check_call=True)
  File "/usr/lib/python2.7/dist-packages/maastest/kvmfixture.py", line 364, in run_command
    args, check_call=check_call, input=input)
  File "/usr/lib/python2.7/dist-packages/maastest/utils.py", line 63, in run_command
    stderr.decode('ascii')))
Exception: Command 'ssh -i /home/bladernr/.config/maas-test/vm_ssh_id_rsa -o LogLevel=quiet -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no ubuntu@192.168.122.76 LC_ALL=en_US.UTF-8 'sudo service apache2 restart'' failed (1):
 * Restarting web server apache2
Action 'start' failed.
The Apache error log may have more information.
   ...fail!
 * The apache2 instance did not start within 20 seconds. Please read the log files to discover problems

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
(98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs

----------------------------------------------------------------------
Ran 0 tests in 205.973s

FAILED (errors=1)

Can't get those logs because teh VM has been destroyed

192.168.122.76 is the address I think it's complaining about... but not sure... but either way, I don't know where that IP is being used other than this VM... it's the only thing running on that network.

[Raphaël Badin (rvb)]

I've seen that happen as well. Not sure what we can do apart from catching the error and retrying.