New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 654611 link

Starred by 11 users

Issue metadata

Status: WontFix
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

"Channel change will be applied later"

Reported by f...@noltie.org, Oct 10 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 8861.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2878.0 Safari/537.36
Platform: 8861.0.0 (Official Build) dev-channel quawks

Steps to reproduce the problem:
1. Update to 55.0.2878.0 dev (64-bit)
2. Go to settings > About Chrome OS > Click "Change channel…"
3. Select beta or stable as the new channel

What is the expected behavior?
I will be allowed to proceed with the powerwash + switch to my chosen channel

What went wrong?
I get this message when I attempt to switch to beta or stable: "You are changing to a channel with an older version of Google Chrome OS. The channel change will be applied when the channel version matches the version currently installed on your device."

I am unable to switch immediately to beta or stable. See attached screenshot.

Did this work before? N/A 

Chrome version: 55.0.2878.0  Channel: dev
OS Version: 8861.0.0
Flash Version: 23.0.0.185-r1 (disabled)

This appears to be a WAI change in behavior. In the past you could change channels at will; now you can't.

Questions:

* How does this work exactly, so that we can tell people who raise the question in Chromebook Central?

* How much of a version match must there be? Major version-only, or major version + patch level(s)?

* Is there any workaround at all for folks (like me 😃) who didn't know about this new change and may not have intended to stay on dev until M55.x+ hits beta/stable?

Thanks!

#CBC-RS/TC-watchlist
 
Screenshot 2016-10-10 at 18.40.26.png
14.9 KB View Download
Components: -UI Internals>Installer
Issue 651398 has been merged into this issue.
Cc: de...@chromium.org songsuk@chromium.org durga.behera@chromium.org pucchakayala@chromium.org
Labels: -Pri-2 Pri-1
Owner: xiy...@chromium.org
Status: Assigned (was: Unconfirmed)
More reports of this coming in.

xiyuan@ can you take a look?
Cc: mwort...@chromium.org

Comment 6 by xiy...@chromium.org, Oct 14 2016

Digging through history, the message is added since M30 per
https://bugs.chromium.org/p/chromium/issues/detail?id=219292#c28

The message shows up when user goes to a channel that is more stable,
e.g. beta -> stable, dev -> beta, dev -> stable

The CL above is an improvement of messaging to let user know why the Chrome/ChromeOS version stays unchanged after switching channel. The reason is that AU could not go back in versions. And the channel with more stability would have an older version, i.e. stable channel version < beta channel version < dev channel version.

So if user goes to a more stable channel, the device will not receive any update until the version on the new channel goes beyond the existing version.

e.g. 
  Suppose we have beta: M55, stable: M54
  User is on beta and wants to switch to stable.
  After the channel switch, there would be no update until stable channel has M55.

In the past, this is confusing to users. And think that is why the message is added to let user know what to expect. Note this delayed message is only the enterprise managed device. For consumer device, users get a message to do a power wash so that they can get the current version on their new target channel.

I would say this is WAI.

Comment 7 by willg...@gmail.com, Oct 14 2016

This an 180 from previous behavior and will be a PITA for users that like to leave feedback in Dev/Beta and drop down a channel if something is too broken.
I too have this issue lately. But changing to Dev channel also keeps un triggered. What could be wrong? same condition?
Labels: Hotlist-ConOps-CrOS
(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.
Status: WontFix (was: Assigned)

Sign in to add a comment