Deployment failed after MOS8.0 MU2 applied.

Bug #1613321 reported by Andrii Petrenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Critical
Fuel Sustaining
8.0.x
Invalid
Critical
Andrii Petrenko
Mitaka
Invalid
Critical
Fuel Sustaining

Bug Description

Deploment failed after MOS8.0 MU2 applied.
How to reproduce:

1. Install vanilla MOS8.0
2. Create Simple env 3 controller +1 compute
3. Install MOS8 MU2
4. Reset environment
5. start deployment
6. Deployment failed with error:
   Provision has failed: Net::ReadTimeout

Cause: outdated bootstrap images

How to fix:

1. get list of bootstrap images: fuel-bootstrap list
2. build new set of images: fuel-bootstrap build
as result you will have line like:
Bootstrap image 8121bf6c-0389-4d18-a625-70df70186e5b has been built: /tmp/8121bf6c-0389-4d18-a625-70df70186e5b.tar.gz

3. activate new image: fuel-bootstrap import <path to image like: /tmp/8121bf6c-0389-4d18-a625-70df70186e5b.tar.gz" --activate

4. get list of bootstrap images: [root@nailgun ~]# fuel-bootstrap list

| 8121bf6c-0389-4d18-a625-70df70186e5b | 8121bf6c-0389-4d18-a625-70df70186e5b | active |

5. restart and sync cobbler (dockerctl restart cobbler; dockerctl shell cobbler cobbler sync)

6. from fuel web ui reset environment

7. reboot/reset nodes

8. start deployment again

Andrii Petrenko (aplsms)
Changed in fuel:
milestone: none → 8.0-mu-3
assignee: nobody → MOS Maintenance (mos-maintenance)
importance: Undecided → Critical
tags: added: customer-found support
Changed in fuel:
milestone: 8.0-mu-3 → 8.0-updates
milestone: 8.0-updates → none
summary: - Dedeploment failed after MOS8.0 MU2 applied.
+ Deployment failed after MOS8.0 MU2 applied.
tags: added: area-library
Revision history for this message
Rodion Tikunov (rtikunov) wrote :

Can't reproduce in 8.0 lab

Revision history for this message
Andrii Petrenko (aplsms) wrote :

i can provide couple of diagnostic snapshots for deeper investigation.

Revision history for this message
Rodion Tikunov (rtikunov) wrote :

Bootstrap image was not created due to "Network is unreachable" error. fuel-bootstrap tried to connect to mirror.fuel-infra.org by IPv6 protocol which is unreachable.
From diagnostic snapshots:
http://mirror.fuel-infra.org/mos-repos/centos/mos8.0-centos7-fuel/updates/x86_64/repodata/repomd.xml: [Errno 14] curl#7 - "Failed to connect to 2a03:1840:2:602::3: Network is unreachable"
Trying other mirror.
{"failed_urls": ["http://mirror.fuel-infra.org/mos-repos/centos/mos8.0-centos7-fuel/updates/x86_64/"]}
2016-06-17 19:17:32 ERROR (app) {"failed_urls": ["http://mirror.fuel-infra.org/mos-repos/centos/mos8.0-centos7-fuel/updates/x86_64/"]}
{"failed_urls": ["http://mirror.fuel-infra.org/mos-repos/centos/mos8.0-centos7-fuel/updates/x86_64/"]}
*************************************************
There is an issue connecting to the Fuel update repository. Please fix your connection prior to applying any updates. Once the connection is fixed, we recommend reviewing and applying Maintenance Updates for this release of Mirantis OpenStack: https://docs.mirantis.com/openstack/fuel/fuel-8.0/release-notes.html#maintenance-updates
*************************************************
Notification sent
WARNING: Ubuntu bootstrap build has been skipped. Please build and activate bootstrap manually with CLI command `fuel-bootstrap build --activate`. While you don't activate any bootstrap - new nodes cannot be discovered and added to cluster. For more information please visit https://docs.mirantis.com/openstack/fuel/fuel-master/

Revision history for this message
Ivan Suzdal (isuzdal) wrote :

You can completely (system wide) disable ipv6 by these sysctl settings:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

But keep in mind it can cause some issues with selinux: https://bugzilla.redhat.com/show_bug.cgi?id=641836

no longer affects: fuel/newton
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.