Upgrade to 5.1.1 failed

Bug #1404042 reported by Rob Neff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Python (Deprecated)
5.1.x
Invalid
High
Fuel Python (Deprecated)
6.0.x
Invalid
High
Fuel Python (Deprecated)
6.1.x
Invalid
High
Fuel Python (Deprecated)

Bug Description

Scenario - upgrade the Fuel Master VM from 5.1 -> 5.1.1

I verified that the Fuel website is up.

./upgrade.sh --password ####
____

class UnixSocketHTTPConnection(httplib.HTTPConnection):
    def connect(self):
        self.sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
        self.sock.connect(self.host)

error: [Errno 2] No such file or directory
2014-12-18 22:42:02 DEBUG 30503 (upgrade) Run rollback
2014-12-18 22:42:02 DEBUG 30503 (upgrade) DockerUpgrader: rollbacking...
2014-12-18 22:42:02 INFO 30503 (version_file) Switch current version file to previous version
2014-12-18 22:42:02 DEBUG 30503 (utils) Symlinking "/etc/fuel/5.1/version.yaml" -> "/etc/fuel/version.yaml" [overwrite=1]
2014-12-18 22:42:02 DEBUG 30503 (utils) Removing "/etc/fuel/version.yaml"
2014-12-18 22:42:02 DEBUG 30503 (utils) Symlinking "/etc/supervisord.d/5.1" -> "/etc/supervisord.d/current" [overwrite=1]
2014-12-18 22:42:02 DEBUG 30503 (utils) Removing "/etc/supervisord.d/current"
2014-12-18 22:42:02 INFO 30503 (supervisor_client) Stop all services
2014-12-18 22:42:02 ERROR 30503 (cli) [Errno 2] No such file or directory
Traceback (most recent call last):
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/cli.py", line 172, in main run_upgrade(parse_args(sys.argv[1:]))
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/cli.py", line 164, in run_upgrade_upgrade_manager.run()
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/upgrade.py", line 58, in run self.rollback()
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/upgrade.py", line 90, in rollback upgrader.rollback()
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/engines/docker_engine.py", line 107, in rollback self.supervisor.stop_all_services()
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/clients/supervisor_client.py", line 125, in stop_all_services
    self.supervisor.stopAllProcesses()
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1235, in request self.send_content(h, request_body)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1349, in send_content connection.endheaders()
  File "/usr/lib64/python2.6/httplib.py", line 908, in endheaders self._send_output()
  File "/usr/lib64/python2.6/httplib.py", line 780, in _send_output self.send(msg)
  File "/usr/lib64/python2.6/httplib.py", line 739, in send self.connect()
  File "/var/tmp/Update5.1.1/upgrade/site-packages/fuel_upgrade/clients/supervisor_client.py", line 34, in connect self.sock.connect(self.host)
  File "<string>", line 1, in connect
error: [Errno 2] No such file or directory
==================================================
Upgrade failed

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Thanks for the report! Can you upload a diagnostic snapshot?

Changed in fuel:
importance: Undecided → High
assignee: nobody → Fuel Python Team (fuel-python)
milestone: none → 6.1
Revision history for this message
Evgeniy L (rustyrobot) wrote :

From the backtrace I can see, that for some reasons supervisor is dead.
Could you please send us /var/log/fuel_upgrade.log and /var/log/supervisor/* files?

Revision history for this message
Stanislav Makar (smakar) wrote :

This bug was incomplete for more than 4 weeks. We cannot investigate it further so we are setting the status to Invalid. If you think it is not correct, please feel free to provide requested information and reopen the bug, and we will look into it further

Revision history for this message
Rob Neff (rob-neff) wrote :

We had to wipe the machine so it's fine to close Incomplete.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.