| airship-irc-bot | <sirajudeen.yasin> Hi Team, needing another +2 and WF for this PS https://review.opendev.org/c/airship/treasuremap/+/804235 => Fix broken links and verify if documents gets published at promote stage | 13:39 |
|---|---|---|
| airship-irc-bot | <mattmceuen> Heads up team, tomorrow's design call will be *one hour earlier* tomorrow to unconflict it with another meeting tomorrow | 14:18 |
| airship-irc-bot | <rp2723> Sent email to mailing list as well, however if you like me forgot to re subscribe with your new email you might not receive it. | 14:45 |
| airship-irc-bot | <ermurugesanbe> Hi Team, I have a query, if anyone having solution then please reply. I have a site manifests for 6 node BM (3 controlplane and 3 worker), using this 3 replica configuration when run BM airship deployment steps then there is one extra controlplane provisioning in pending state (looks like its looking for an extra node to configure) its not considering the controlplane which moved from ephemeral node (first target controlplane) | 16:42 |
| airship-irc-bot | part of its replica count 3 *$kubectl --kubeconfig /home/airship/.airship/kubeconfig --context target-cluster get machines* *cluster-controlplane-22977 metal3://dd33ef25-a348-462a-b125-e20c6a52f1bd Running* *cluster-controlplane-gjvvr metal3://7365c9e8-8322-4969-8db7-916c0f00760b Running* *cluster-controlplane-nqv7p metal3://136a085a-fae8-412d-a4bf-dd331a533437 Running* *cluster-controlplane-xljsc | 16:42 |
| airship-irc-bot | Provisioning* *worker-1-5bc87ff868-2x5qz metal3://534c9542-3250-4806-9f70-2552c75f964e Running* *worker-1-5bc87ff868-6tjhh metal3://32292183-6617-450e-a230-ed4ac02369dd Running* *worker-1-5bc87ff868-dwg5z metal3://fde274cb-cf6e-42ff-b5ca-32ca7310e9d0 Running* then I reduced replica count to 2 for contralplane, then I got error "cluster-controlplane is invalid: spec.replicas: Forbidden: cannot be an even number | 16:42 |
| airship-irc-bot | when using managed etcd" grep replica target/controlplane/patch_controlplane.yaml replicas: 2 then I revered the replica back to 3 and added one extra node (*bm132)* into controlplane node list, then its provisioning that extra node as 3rd controlplane, _*Is there bug in airshipctl it will not consider first target controlplane ( bm129) in it's replica count?*_ *target/controlplane/hostgenerator/host-generation.yaml* *- bm129* *- | 16:42 |
| airship-irc-bot | bm130* *- bm131* *- bm132* $kubectl get bmh --all-namespaces --context target-cluster --kubeconfig /home/airship/.airship/kubeconfig NAMESPACE NAME STATUS PROVISIONING STATUS CONSUMER BMC HARDWARE PROFILE ONLINE ERROR default *bm129* cluster-controlplane-7z8qk | 16:42 |
| airship-irc-bot | redfish+https://10.2.0.129/redfish/v1/Systems/System.Embedded.1 true default *bm130* OK *provisioned* cluster-controlplane-2-spjkj redfish+https://10.2.0.130/redfish/v1/Systems/System.Embedded.1 unknown true default *bm131* OK *provisioned* cluster-controlplane-2-5g78m redfish+https://10.2.0.131/redfish/v1/Systems/System.Embedded.1 unknown true | 16:42 |
| airship-irc-bot | default *bm132* OK *provisioned* cluster-controlplane-2-9hg5n redfish+https://10.2.0.132/redfish/v1/Systems/System.Embedded.1 unknown true | 16:42 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!