[Airship-discuss] Aiab Site update with Shipyard fails

[Loic Le Gal]

Hi Airshipers,

We successfully deployed the aiab from treasuremap for a while and
activated the Prometheus monitoring.
Instead of deploying again from Genesis, Now I try to use the site update
mechanism:
(cf.
https://airship-treasuremap.readthedocs.io/en/latest/config_update_guide.html
)

- Pegleg lint + collected yaml generation
- Shipyard create and commit docs (No error)

In fact we only modify the initial site by adding a parameter in Prometheus
Chart using Deckhand substitution mechanism.
The site syntax seems Ok and has been committed, but the update_site action
fails:
Name:                  update_site
Action:                action/01DPTGTT31Y7CVYFGZYJVDV402
Lifecycle:             Complete
Parameters:            {}
Datetime:              2019-10-10 09:43:37.826039+00:00
Dag Status:            success
Context Marker:        649459d0-239e-4a86-ad23-73daa304b588
User:                  shipyard

Steps                                                                 Index
       State                  Footnotes
step/01DPTGTT31Y7CVYFGZYJVDV402/action_xcom                           1
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/dag_concurrency_check                 2
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/get_rendered_doc                      3
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/deployment_configuration              4
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/preflight                             5
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/validate_site_design                  6
       success
step/01DPTGTT31Y7CVYFGZYJVDV402/drydock_build                         7
       failed
step/01DPTGTT31Y7CVYFGZYJVDV402/armada_build                          8
       upstream_failed
step/01DPTGTT31Y7CVYFGZYJVDV402/decide_airflow_upgrade                9
       upstream_failed
step/01DPTGTT31Y7CVYFGZYJVDV402/verify_site                           10
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/prepare_site                          11
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/skip_upgrade_airflow                  12
        upstream_failed
step/01DPTGTT31Y7CVYFGZYJVDV402/upgrade_airflow                       13
        upstream_failed
step/01DPTGTT31Y7CVYFGZYJVDV402/armada_get_status                     14
        None
step/01DPTGTT31Y7CVYFGZYJVDV402/verify_nodes_exist                    15
        failed
step/01DPTGTT31Y7CVYFGZYJVDV402/create_action_tag                     16
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/armada_post_apply                     17
        None
step/01DPTGTT31Y7CVYFGZYJVDV402/ucp_preflight_check                   18
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/deployment_status                     19
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/deckhand_validate_site_design         20
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/drydock_validate_site_design          21
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/promenade_validate_site_design        22
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/armada_validate_site_design           23
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/prepare_and_deploy_nodes              24
        upstream_failed
step/01DPTGTT31Y7CVYFGZYJVDV402/final_deployment_status               25
        success
step/01DPTGTT31Y7CVYFGZYJVDV402/armada_get_releases                   26
        None


As I previously already faced such this error when activating Prometheus, I
wonder whether the aiab site allows the update_site action or if it
contains some specific scripted actions that prevent running this action?

BR,
Loïc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20191010/b915e2c9/attachment.html>