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

Rollout Advanced Group Definition shows different Groups in Rollout overview. #1400

Open
dcd-arnold opened this issue Jul 26, 2023 · 5 comments

Comments

@dcd-arnold
Copy link
Contributor

dcd-arnold commented Jul 26, 2023

Hi all,

I am pretty sure I found a bug.

Reproduction

Construct a Rollout in the Management UI using Advanced Group definition. This yields a correct distribution of Targets for us:
rollout_1_redact

However, if I save the Rollout, the groups are shown with a different distribution:
rollout_2_redact

Expectation

The overview and the details view of the Rollout should show the same distribution.

We are using 0.3.0M7, as we did not get to migrate yet (the new User Consent Flow does not seem optional). If you need further information, please let me know.

@strailov
Copy link
Contributor

Hey @dcd-arnold
Thanks for using hawkBit!

What do you mean by "the new User Consent Flow does not seem optional" ? Currently I think there is enable/disable option in system config, but once enabled could not be disabled again.

@dcd-arnold
Copy link
Contributor Author

Hi @strailov,

thanks for making hawkbit.

I did not find the setting. The Release Notes only mentions a setting by device. We are managing 700+ devices. Moreover, they are deleted and re-register themselves as needed. The rauc-hawkbit-updater does not support to set the setting on registration. Unless there is a setting for the whole hawkbit instance, we are stuck until we figured out a way moving forward. If there is such a setting, where is it documented?

Thanks in advance,
Arnold

@strailov
Copy link
Contributor

strailov commented Jul 31, 2023

Yes, this seems like a good catch ...
Somehow we've missed this.
You can read at least some basic info here .

And more specifically :
"The consent flow can be activated in the system configuration. By default, the update process is executed as usual. "

Regarding the issue you have described above I will check this, but if this is an User interface issue could be a problem due to this issue

@dcd-arnold
Copy link
Contributor Author

Ah. I see. So if I don't activate the new user consent flow, it will not be activated on upgrade. I will keep that in mind and try an upgrade.

@strailov
Copy link
Contributor

Yes ... And for the documentation we will try updating it as soon as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants