search: Add initialization step on install or upgrade
ClosedPublic
Actions

Authored by ardumont on Dec 8 2020, 4:06 PM.

Details

Reviewers

vsellier

Group Reviewers

System administrators

Maniphest Tasks

T2817: Enable the swh-search environment in staging

Commits

rSPSITEadbef15c22fe: search: Add initialization step on install or upgrade

Summary

Related to T2817

Test Plan

vagrant:

on staging-search0 node (apt uninstall python3-swh.search)
Then vagrant provision staging-search0
logs mention that it did those steps

==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Base_search/Package[python3-swh.search]/ensure: created
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Base_search/Package[python3-swh.search]: Scheduling refresh of Exec[active-initialize]
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Base_search/Package[python3-swh.search]: Scheduling refresh of Service[swh-search-journal-client]
==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Search/Exec[active-initialize]: Triggered 'refresh' from 1 event
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Search/Exec[active-initialize]: Scheduling refresh of Exec[swh-search-initialize]
==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Search/Exec[swh-search-initialize]/returns: executed successfully
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Search/Exec[swh-search-initialize]: Scheduling refresh of Service[gunicorn-swh-search]
==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Search/Exec[swh-search-initialize]: Triggered 'refresh' from 1 event
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Search/Exec[swh-search-initialize]: Scheduling refresh of Service[gunicorn-swh-search]
==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Search_journal_client/Service[swh-search-journal-client]/ensure: ensure changed 'stopped' to 'running'
==> staging-search0: Info: /Stage[main]/Profile::Swh::Deploy::Search_journal_client/Service[swh-search-journal-client]: Unscheduling refresh on Service[swh-search-journal-client]
==> staging-search0: Notice: /Stage[main]/Icinga2::Service/Service[icinga2]: Dependency File[/var/lib/icinga2/certs/search0.internal.staging.swh.network.crt] has failures: true
==> staging-search0: Notice: /Stage[main]/Icinga2::Service/Service[icinga2]: Dependency File[/var/lib/icinga2/certs/ca.crt] has failures: true
==> staging-search0: Warning: /Stage[main]/Icinga2::Service/Service[icinga2]: Skipping because of failed dependencies
==> staging-search0: Warning: /Stage[main]/Icinga2/Anchor[::icinga2::end]: Skipping because of failed dependencies
==> staging-search0: Notice: /Stage[main]/Profile::Swh::Deploy::Search/Profile::Swh::Deploy::Rpc_server[search]/Gunicorn::Instance[swh-search]/Service[gunicorn-swh-search]: Triggered 'refresh' from 2 events
==> staging-search0: Info: Stage[main]: Unscheduling all events on Stage[main]

On subsidiary provision steps, expectedly, nothing more happens.