[instack-undercloud] package upgrade should happen before service configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Emilien Macchi |
Bug Description
We are currently seeing an issue where if you start with a CentOS 7.2 based undercloud, and run `openstack undercloud install`, at the end of the install ironic conductor is in a broken (though not failed) state. This is because the CentOS base repos are now 7.3 so many packages get upgraded. Specifically when trying to register nodes the following trace is seen in the conductor logs:
2016-12-15 18:57:58.927 15490 ERROR paramiko.transport [-] Unknown exception: 'module' object has no attribute 'Cryptography_
2016-12-15 18:57:58.930 15490 ERROR paramiko.transport [-] Traceback (most recent call last):
2016-12-15 18:57:58.931 15490 ERROR paramiko.transport [-] File "/usr/lib/
2016-12-15 18:57:58.931 15490 ERROR paramiko.transport [-] self.kex_
2016-12-15 18:57:58.932 15490 ERROR paramiko.transport [-] File "/usr/lib/
2016-12-15 18:57:58.932 15490 ERROR paramiko.transport [-] return self._parse_
2016-12-15 18:57:58.932 15490 ERROR paramiko.transport [-] File "/usr/lib/
2016-12-15 18:57:58.933 15490 ERROR paramiko.transport [-] self.transport.
2016-12-15 18:57:58.933 15490 ERROR paramiko.transport [-] File "/usr/lib/
2016-12-15 18:57:58.934 15490 ERROR paramiko.transport [-] if not key.verify_
2016-12-15 18:57:58.934 15490 ERROR paramiko.transport [-] File "/usr/lib/
2016-12-15 18:57:58.934 15490 ERROR paramiko.transport [-] algorithm=
2016-12-15 18:57:58.935 15490 ERROR paramiko.transport [-] File "/usr/lib64/
2016-12-15 18:57:58.935 15490 ERROR paramiko.transport [-] self._backend, self, signature, padding, algorithm
2016-12-15 18:57:58.935 15490 ERROR paramiko.transport [-] File "/usr/lib64/
2016-12-15 18:57:58.936 15490 ERROR paramiko.transport [-] self._hash_ctx = hashes.
2016-12-15 18:57:58.936 15490 ERROR paramiko.transport [-] File "/usr/lib64/
2016-12-15 18:57:58.936 15490 ERROR paramiko.transport [-] self._ctx = self._backend.
2016-12-15 18:57:58.937 15490 ERROR paramiko.transport [-] File "/usr/lib64/
2016-12-15 18:57:58.937 15490 ERROR paramiko.transport [-] return _HashContext(self, algorithm)
2016-12-15 18:57:58.937 15490 ERROR paramiko.transport [-] File "/usr/lib64/
2016-12-15 18:57:58.938 15490 ERROR paramiko.transport [-] ctx = self._backend.
2016-12-15 18:57:58.938 15490 ERROR paramiko.transport [-] AttributeError: 'module' object has no attribute 'Cryptography_
2016-12-15 18:57:58.939 15490 ERROR paramiko.transport [-]
Restarting ironic-conductor service allows the nodes to be registered without fail.
This seems like a bug in our puppet manifest that the service configuration (and therefore starting) should always happen after the package upgrade.
Changed in tripleo: | |
assignee: | nobody → Emilien Macchi (emilienm) |
Changed in tripleo: | |
status: | Triaged → In Progress |
Reviewed: https:/ /review. openstack. org/411957 /git.openstack. org/cgit/ openstack/ instack- undercloud/ commit/ ?id=853b4bfbadd a67cf659a8a744b 82d128a4bc3247
Committed: https:/
Submitter: Jenkins
Branch: master
commit 853b4bfbadda67c f659a8a744b82d1 28a4bc3247
Author: Emilien Macchi <email address hidden>
Date: Fri Dec 16 13:55:58 2016 -0500
Run `yum update -y` before Puppet run
This patch run `yum update -y` right before running os-refresh-config
(Puppet).
1) Running `yum` from an Exec in Puppet is a bad idea because Puppet has
no idea which packages resources are touched, so we're loosing the
orchestration control.
2) We need to ensure that `yum update -y` runs before any attempt to
deploy OpenStack services, so we have latest packages from RDO and
CentOS.
Change-Id: Ifbbbdbf1f0c569 791abc712913c7e 0f6bbe533d9
Closes-Bug: #1650374