Fuel upgrade script should configure /updates and /security repositories in the end and show the warning how to update

[Vladimir Kuklin]

To allow user to seamlessly update his environment to the latest update bundle we need to configure update repositories on the master node after upgrade is finished.

The following repo configuration should be applied as per here:

[mos${RELEASE}-updates]
name=mos${RELEASE}-updates
baseurl=http://mirror.fuel-infra.org/mos/centos-6/mos${RELEASE}/updates/
gpgcheck=0
skip_if_unavailable=1

[mos${RELEASE}-security]
name=mos${RELEASE}-security
baseurl=http://mirror.fuel-infra.org/mos/centos-6/mos${RELEASE}/security/
gpgcheck=0
skip_if_unavailable=1

After that we should warn user with a message that he needs to update his ${RELEASE} GA to the lates update bundle with something like

 warning="WARNING: There are issues connecting to Fuel update repository.
   \nPlease fix your connection and update this node with \`yum update\`\
\nThen run \`dockerctl destroy all; bootstrap_admin_node.sh;\`\
\nto repeat bootstrap on Fuel Master with the latest updates."
  echo
  echo "*************************************************"
  echo -e "$warning"
  echo "*************************************************"
  echo "Sending notification to Fuel UI..."
  fuel notify --topic warning --send "$warning"

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/6.1
Review: https://review.openstack.org/193138

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/193138
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=126e50e624b1b97043ab87dbf1298312b9771df3
Submitter: Jenkins
Branch: stable/6.1

commit 126e50e624b1b97043ab87dbf1298312b9771df3
Author: Igor Kalnitsky <email address hidden>
Date: Thu Jun 18 13:36:44 2015 +0300

    fuel_upgrade: setup update/security repos

    In order to deliver bugfixes and improvements to customers we have to
    setup our online repos in case of successful upgrade. These repos
    have to be marked with "skip_if_available" flag so yum won't fall
    if there's no connectivity to them (e.g. no Internet access).

    Closes-Bug: #1466418

    Change-Id: I6626ff5e92c53c487f69491c09c3e0bcf022d5d4
    Signed-off-by: Igor Kalnitsky <email address hidden>

[Kyrylo Romanenko (kromanenko)]

I got this warning in 523 build (seems it`s RC3) after Environment creation wizard passed.
Message looks quite surprisingly like something gone very wrong, and also string breaks "\n" are visible.

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "523"
  build_id: "2015-06-18_17-46-09"
  nailgun_sha: "126e50e624b1b97043ab87dbf1298312b9771df3"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "1ea8017fe8889413706d543a5b9f557f5414beae"
  fuel-library_sha: "2e7a08ad9792c700ebf08ce87f4867df36aa9fab"
  fuel-ostf_sha: "8fefcf7c4649370f00847cc309c24f0b62de718d"
  fuelmain_sha: "237c6ec1e9c022d69e5f8ab859887352fc5cb74b"

[Kyrylo Romanenko (kromanenko)]

Diagnostic snapshot

[Kyrylo Romanenko (kromanenko)]

Looks like this is connected with current issue too

[Ihor Kalnytskyi (ikalnytskyi)]

@Kyrylo, it's not related to this ticket at all. Still, the message you see was done on purpose by Matt. Check out his commit and related bug:

    https://review.openstack.org/#/c/193470/

[Vasily Gorin (vgorin)]

Verified on build #523
Version:
root@nailgun var]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "6.1"
  openstack_version: "2014.2.2-6.1"
  api: "1.0"
  build_number: "523"
  build_id: "2015-06-18_17-46-09"
  nailgun_sha: "126e50e624b1b97043ab87dbf1298312b9771df3"
  python-fuelclient_sha: "4fc55db0265bbf39c369df398b9dc7d6469ba13b"
  astute_sha: "1ea8017fe8889413706d543a5b9f557f5414beae"
  fuel-library_sha: "2e7a08ad9792c700ebf08ce87f4867df36aa9fab"
  fuel-ostf_sha: "8fefcf7c4649370f00847cc309c24f0b62de718d"
  fuelmain_sha: "237c6ec1e9c022d69e5f8ab859887352fc5cb74b"

Log:
.......
Both updates and security repos were setuped. If you want to
retrieve latest updates make sure you have access to these repos
and run:

    # yum update
    # dockerctl destroy all
    # dockerctl start all

For more details, check out Fuel documentation at

    http://docs.mirantis.com/fuel

2015-06-19 12:43:44 INFO 19392 (upgrade) *** UPGRADING MASTER NODE DONE SUCCESSFULLY
2015-06-19 12:43:44 INFO 19392 (upgrade) *** PLEASE REBOOT YOUR BOOTSTRAP NODES IN ORDER TO MAKE SURE THAT THEY USE THE LATEST BOOTSTRAP IMAGE
[root@nailgun var]# ll /etc/yum.repos.d/
total 20
-rw-r--r-- 1 root root 121 Jun 19 12:26 6.1_nailgun.repo
-rw-r--r-- 1 root root 113 Jun 19 12:28 auxiliary.repo
-rw-r--r-- 1 root root 139 Jun 19 12:43 mos6.1-security.repo
-rw-r--r-- 1 root root 136 Jun 19 12:43 mos6.1-updates.repo
-rw-r--r--. 1 root root 100 Jun 19 10:43 nailgun.repo
[root@nailgun var]# cat /etc/yum.repos.d/mos6.1-updates.repo
[mos6.1-updates]
name=mos6.1-updates
baseurl=http://mirror.fuel-infra.org/mos/centos-6/mos6.1/updates/
gpgcheck=0
skip_if_unavailable=1
[root@nailgun var]# cat /etc/yum.repos.d/mos6.1-security.repo
[mos6.1-security]
name=mos6.1-security
baseurl=http://mirror.fuel-infra.org/mos/centos-6/mos6.1/security/
gpgcheck=0
skip_if_unavailable=1

[Robert Duncan (rduncan-t)]

I got this message yesterday, the instructions are a little vague, I spent some time looking for the shell script, there is bootstrap_admin_node in /etc/sysconfig but the script is gloabally available in /usr/local/sbin
setting bootstap_admin_node to enabled in /etc/sysconfig results in a bootstrap loop.

[Ilya Kharin (akscram)]

In custom builds of ISO it should be possible to define proper updates and security repositories.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Fuel DevOps Robot (<email address hidden>) on branch: master
Review: https://review.openstack.org/277274
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.