Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.0.x: MEN-5290: Several robustness fixes around re-connection #53

Merged

Conversation

lluiscampos
Copy link
Contributor

Cherry-pick of #51.

@mender-test-bot
Copy link

@lluiscampos, Let me know if you want to start the integration pipeline by mentioning me and the command "start pipeline".


my commands and options
You can trigger a pipeline on multiple prs with:
  • mentioning me and start pipeline --pr mender/127 --mender-connect/255

You can cherry pick to a given branch or branches with:

  • mentioning me and:
 cherry-pick to:
 * 1.0.x
 * 2.0.x

* Trigger re-connection when either token or server URL obtained from
  D-Bus signal has changed. Previously, it was enough with having a
  token with "some length" for the code to believe the device was
  authenticated and not trigger a re-connect.
* Abort connecting after 10 retries. Previously it would reconnect
  forever with the same server URL, which will result in a deadlock if
  the url (or the token) changed while re-connecting.

Changelog: Commit

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
(cherry picked from commit e382937)
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
@lluiscampos
Copy link
Contributor Author

@mender-test-bot start pipeline 🪘

@mender-test-bot
Copy link

Hello 😸 I created a pipeline for you here: Pipeline-440080096

Build Configuration Matrix

Key Value
AUDITLOGS_REV 1.0.x
BUILD_BEAGLEBONEBLACK true
BUILD_CLIENT true
BUILD_QEMUX86_64_BIOS_GRUB true
BUILD_QEMUX86_64_BIOS_GRUB_GPT true
BUILD_QEMUX86_64_UEFI_GRUB true
BUILD_VEXPRESS_QEMU true
BUILD_VEXPRESS_QEMU_FLASH true
BUILD_VEXPRESS_QEMU_UBOOT_UEFI_GRUB true
CREATE_ARTIFACT_WORKER_REV 1.0.x
DEPLOYMENTS_ENTERPRISE_REV 2.2.x
DEPLOYMENTS_REV 2.2.x
DEVICEAUTH_REV 2.5.x
DEVICECONNECT_REV 1.0.x
GUI_REV 2.6.x
INTEGRATION_REV 2.6.x
INVENTORY_ENTERPRISE_REV 2.2.x
INVENTORY_REV 2.2.x
MENDER_API_GATEWAY_DOCKER_REV 2.4.x
MENDER_ARTIFACT_REV 3.5.x
MENDER_CLI_REV 1.6.x
MENDER_CONNECT_REV pull/53/head
MENDER_REV 2.5.x
META_MENDER_REV dunfell
META_OPENEMBEDDED_REV dunfell
META_RASPBERRYPI_REV dunfell
MTLS_AMBASSADOR_REV 1.0.x
POKY_REV dunfell
RUN_INTEGRATION_TESTS true
TENANTADM_REV 3.0.x
TEST_QEMUX86_64_BIOS_GRUB true
TEST_QEMUX86_64_BIOS_GRUB_GPT true
TEST_QEMUX86_64_UEFI_GRUB true
TEST_VEXPRESS_QEMU true
TEST_VEXPRESS_QEMU_FLASH true
TEST_VEXPRESS_QEMU_UBOOT_UEFI_GRUB true
USERADM_ENTERPRISE_REV 1.13.x
USERADM_REV 1.13.x
WORKFLOWS_ENTERPRISE_REV 1.3.x
WORKFLOWS_REV 1.3.x

@lluiscampos
Copy link
Contributor Author

@mender-test-bot start pipeline --pr meta-mender/1552

@lluiscampos
Copy link
Contributor Author

Build for Mender 2.6.x @ Pipeline 440088069

Note that only tidying has been done, no changes in vendor folder.

Changelog: None

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
@lluiscampos
Copy link
Contributor Author

@mzedel Can you look at the second commit?

Changelog: None

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Copy link
Contributor

@mzedel mzedel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the changes to the mod files this looks fine, but the check does a way better job than me looking at the hashes...
One other thing though:
Copyright 2022 Northern.tech' not found in LICENSE. Wrong year maybe?
I guess we run into these more frequently this time of a year 😉

@lluiscampos
Copy link
Contributor Author

@mzedel Funny enough, the cherry pick is "from last year" so it passed the check... but the go mod tidy fix is "from this year" 🥳

@lluiscampos lluiscampos merged commit 0afe7b7 into mendersoftware:1.0.x Jan 3, 2022
@lluiscampos lluiscampos deleted the 1.0.x-MEN-5290-fix-reconnect branch January 3, 2022 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants