Master node sometimes hung after making a snapshot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Fuel DevOps |
Bug Description
ISO version:
{
u'build_id': u'2015-
u'ostf_sha': u'c910026314000
u'build_
u'auth_
u'nailgun_sha': u'62dd628978507
u'production': u'docker',
u'api': u'1.0',
u'python-
u'astute_sha': u'ed5270bf9c6c1
u'fuelmain_
u'feature_
u'release': u'6.1',
u'release_
u'api': u'1.0',
u'release': u'6.1',
}}},
u'fuellib_sha': u'2147da0c583a7
}
Catch error on CI - http://
When we try check status of master node after successful snapshot, node was not available
--==--
2015-02-04 02:54:55,071 - INFO decorators.py:143 -- <<<<<**
2015-02-04 02:54:55,071 - INFO decorators.py:144 -- Make snapshot: deploy_
2015-02-04 02:54:55,071 - INFO decorators.py:153 -- You could revert this snapshot using [dos.py revert 6.1.system_
2015-02-04 02:54:55,072 - INFO decorators.py:158 -- <<<<<**
2015-02-04 02:56:02,000 - ERROR environment.py:387 -- Admin node is unavailable via SSH after environment resume
2015-02-04 02:56:05,001 - ERROR decorators.py:80 -- Fetching of diagnostic snapshot failed: Traceback (most recent call last):
File "/home/
"fail", name)
File "/home/
task = env.fuel_
File "/home/
result = func(*args, **kwargs)
File "/home/
response = func(*args, **kwargs)
File "/home/
return self.client.
File "/home/
return self._open(req)
File "/home/
return self._get_
File "/home/
return self.opener.
File "/usr/lib/
response = self._open(req, data)
File "/usr/lib/
'_open', req)
File "/usr/lib/
result = func(*args)
File "/usr/lib/
return self.do_
File "/usr/lib/
raise URLError(err)
URLError: <urlopen error [Errno 113] No route to host>
--==--
Changed in fuel: | |
status: | New → Confirmed |
How we do a snapshot:
https:/ /github. com/stackforge/ fuel-main/ blob/master/ fuelweb_ test/models/ environment. py#L379- L385
Environment is suspended, then snapshoted, then resumed.
After that, we are waiting for port 22 is available to Fuel master node.
Master node hung after snapshot quite often , see the 'grep' result in the attachment.