'cloud-init' affects network settings on Ubuntu with image-based provisioning

Bug #1412537 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
Critical
Unassigned

Bug Description

Jenkins jobs example (both of them): http://jenkins-product.srt.mirantis.net:8080/view/6.1_swarm/job/6.1.system_test.Ubuntu.thread_1/6/

When a node is restarted, file /etc/network/interfaces is rewritten by cloud-init. As the result, the string "source /etc/network/interfaces.d/*" disappeared from /etc/network/interfaces, getting a config for 'eth0' instead.
As the result: eth1, eth2, eth3 and eth4 are down, node becomes nonfunctional.

The 'cloud-init' package wasn't installed in fuel 6.0, but it is appeared on the Ununtu nodes after enabling image-based provisioning.

Please see the attached /var/log/apt/history.log from slave-01 after Ubuntu cluster was deployed.

api: '1.0'
astute_sha: 82125b0eef4e5a758fd4afa8917812e09a1f7dac
auth_required: true
build_id: 2015-01-18_22-54-45
build_number: '68'
feature_groups:
- mirantis
fuellib_sha: 5edc8396cbed1d44a097d9997700656f6268709f
fuelmain_sha: ''
nailgun_sha: 21a8b7f0eac58ff8139f436392fceec293cfd619
ostf_sha: 92ad9f8e4c509c82e07ceb093b5d579205c76014
production: docker
release: '6.1'
release_versions:
  2014.2-6.1:
    VERSION:
      api: '1.0'
      astute_sha: 82125b0eef4e5a758fd4afa8917812e09a1f7dac
      build_id: 2015-01-18_22-54-45
      build_number: '68'
      feature_groups:
      - mirantis
      fuellib_sha: 5edc8396cbed1d44a097d9997700656f6268709f
      fuelmain_sha: ''
      nailgun_sha: 21a8b7f0eac58ff8139f436392fceec293cfd619
      ostf_sha: 92ad9f8e4c509c82e07ceb093b5d579205c76014
      production: docker
      release: '6.1'

Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :
Revision history for this message
Christopher Aedo (docaedo) wrote :
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

Bug #1398207 looks similar, but in my case there was the connectivity to the master node from all slaves.

The root of the issue can be the same, but there are no enough details in that bug.

Revision history for this message
Alexander Gordeev (a-gordeev) wrote :
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.