Environment hangs after installing Ubuntu, no errors in logs

Bug #1537801 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Vladimir Sharshov
8.0.x
Invalid
High
Vladimir Sharshov
Mitaka
Invalid
High
Vladimir Sharshov

Bug Description

I see this issue the second time.
Deployment hangs after installing Ubuntu, no errors in logs, cause is unknown.

If I create other deployment, all is fine, no hanging, installing OpenStack starts.

Hanging nodes in logs: node-6,1,2

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "478"
  build_id: "478"
  fuel-nailgun_sha: "ae949905142507f2cb446071783731468f34a572"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "481ed135de2cb5060cac3795428625befdd1d814"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "420c6fa5f8cb51f3322d95113f783967bde9836e"
  fuel-ostf_sha: "ab5fd151fc6c1aa0b35bc2023631b1f4836ecd61"
  fuel-mirror_sha: "b62f3cce5321fd570c6589bc2684eab994c3f3f2"
  fuelmenu_sha: "fac143f4dfa75785758e72afbdc029693e94ff2b"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "9f0ba4577915ce1e77f5dc9c639a5ef66ca45896"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "6c6b088a3d52dd0eaf43d59f3a3a149c93a07e7e"

Revision history for this message
Anastasia Palkina (apalkina) wrote :
description: updated
tags: added: area-python
Revision history for this message
Ivan Ponomarev (ivanzipfer) wrote :

Could you please provide step to reproduce

Changed in fuel:
status: New → Incomplete
Revision history for this message
Anastasia Palkina (apalkina) wrote :

Ivan, there is no special steps to reproduce it.
I just starting deploy and it hangs.

Vova Sharshov already investigated this issue last time but he found nothing.

Changed in fuel:
status: Incomplete → New
Revision history for this message
Anastasia Palkina (apalkina) wrote :

I found error on controller node (node-6) in puppet-agent.log:
err: Could not run: SIGTERM

And I found ERROR REPORT in /<email address hidden>

=ERROR REPORT==== 25-Jan-2016::11:02:14 ===
webmachine error: path="/api/nodes"
"Unauthorized"

Dmitry Pyzhov (dpyzhov)
Changed in fuel:
status: New → Confirmed
milestone: 8.0 → 9.0
Dmitry Pyzhov (dpyzhov)
tags: added: team-bugfix
Revision history for this message
Alexander Gordeev (a-gordeev) wrote :
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

In short: we failed in case of sync_time, but most interesting details here was silent raise. Astute run command, fail (fail in case of time sync is well know bug), but instead of send to Nailgun report about fail just finish work.

I've try to understand such behavior. At first looks this is very rare bug, it can be solved by deployment rerun, also problem with ntp was solved in another bug. So i think i can and must be research, but looks like we should release 8.0 without fix for this.

Andrey Maximov (maximov)
tags: added: move-to-9.0
Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

The bug was caused by bug #1533082, and since the original bug is fixed move this one to invalid. There's no way to reproduce it again.

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.