[9.1][updates] pkg_upgrade task doesn't start on nodes with plugins

Bug #1657756 reported by Ruslan Khozinov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Unassigned

Bug Description

Detailed bug description:

Fuel has been updated successfully.
Env update has been finished with successful result.

When I've checked the deployment history for the latest deploy
I've not found that pkg_upgrade task has been started for the node with kibana-grafana role
But for contoller+murano and cinder+compute nodes the pkg_upgrade task has been started.

Steps to reproduce:

1. Deploy Fuel9.0
2. Install stacklight and murano plugins from the mirantis catalog
3. Deploy an env:
  - contoller+murano_node
  - compute+cinder
  - kibana+grafana
4. Update fuel and the env up to Fuel 9.1

summary: - [9.1][updates] pkg_upgrade task don't start on nodes with plugins
+ [9.1][updates] pkg_upgrade task doesn't start on nodes with plugins
Revision history for this message
Ruslan Khozinov (rkhozinov) wrote :

I've checked dpkg.log from controller (http://paste.ubuntu.com/23828140/)

...
...
2017-01-19 13:47:47 configure haproxy:amd64 1.6.3-1~u14.04+mos2 <none>
2017-01-19 13:47:47 status half-configured haproxy:amd64 1.6.3-1~u14.04+mos2
2017-01-19 13:47:47 configure python-oslo.service:all 1.8.0-2~u14.04+mos3 <none>
2017-01-19 13:47:47 status unpacked python-oslo.service:all 1.8.0-2~u14.04+mos3
2017-01-19 13:47:47 status half-configured python-oslo.service:all 1.8.0-2~u14.04+mos3
2017-01-19 13:47:47 status installed python-oslo.service:all 1.8.0-2~u14.04+mos3
2017-01-19 13:47:56 startup packages configure
2017-01-19 13:47:56 configure haproxy:amd64 1.6.3-1~u14.04+mos2 <none>
2017-01-19 13:47:56 status half-configured haproxy:amd64 1.6.3-1~u14.04+mos2
2017-01-19 13:48:11 startup packages configure
2017-01-19 13:48:11 configure haproxy:amd64 1.6.3-1~u14.04+mos2 <none>
2017-01-19 13:48:11 status half-configured haproxy:amd64 1.6.3-1~u14.04+mos2
2017-01-19 13:52:12 startup packages configure
2017-01-19 13:52:12 configure haproxy:amd64 1.6.3-1~u14.04+mos2 <none>
2017-01-19 13:52:12 status half-configured haproxy:amd64 1.6.3-1~u14.04+mos2
2017-01-19 13:52:12 status installed haproxy:amd64 1.6.3-1~u14.04+mos2

and from the node with the stacklight plugin (http://paste.ubuntu.com/23828143/)

...
...
2017-01-16 13:17:44 status triggers-awaited grafana:amd64 3.0.4-1464167696
2017-01-16 13:17:44 trigproc ureadahead:amd64 0.100.0-16 <none>
2017-01-16 13:17:44 status half-configured ureadahead:amd64 0.100.0-16
2017-01-16 13:17:44 status installed grafana:amd64 3.0.4-1464167696
2017-01-16 13:17:44 status installed ureadahead:amd64 0.100.0-16

Revision history for this message
Ruslan Khozinov (rkhozinov) wrote :

vsedelnik said that it's normal behavior

Changed in fuel:
status: New → Invalid
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.