text:
Notification constantly repeats itself, it fires again and again #180

Referring to #180 Issue by @eyubSalihOzdemir
I am getting the Errors of the Notification Constantly Repeating Itself.
You are really recommended to check this,
The Video, is demonstrating in Person, you must check it
Content
AwesomeNotifications().createNotification(
        content: NotificationContent(
            id: 5000,
            channelKey: 'dailyNotific',
            title: "Champion this Day 🏆",
            body: "Tap to and write toodo"),
        schedule: NotificationCalendar(
          hour: hour,
          minute: minute,
          allowWhileIdle: true,
          repeats: true, // This will help it repeat daily.
          timeZone: AwesomeNotifications.localTimeZoneIdentifier,
        ));

Channel
AwesomeNotifications().initialize(
    // set the icon to null if you want to use the default app icon
    'resource://drawable/res_toodoleeicon',
    [
      NotificationChannel(
        // groupKey: "remainderNotf",

        channelKey: 'dailyNotific',
        channelName: 'Daily Notifications',
        channelDescription:
            'Sends you daily notifications to remind you to write toodolees, to win the day',
        onlyAlertOnce: true,
        defaultColor: Color(0xffFFCC00),
        ledColor: Color(0xffFFCC00),
        importance: NotificationImportance.High,
        defaultPrivacy: NotificationPrivacy.Public,
        playSound: true,
        soundSource: "resource://raw/res_alert_simple",
      ),

Let's schedule a meeting call to solve this problem.

For Sure,
@rafaelsetragni what are you thinking about 6:00 AM, Brazil. Time,
Here in India is 2:30 PM.

Can you help me with that too?, I have the same problem

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!

The issue is still persisting,
Notification is firing over and over again when the repeats: true
for a whole minute...
int? scheduledNotificationId;

// Function to create or update daily notification
Future<void> createDailyNotification(BuildContext context) async {
  try {
    // Cancel any existing notification before scheduling a new one
    if (scheduledNotificationId != null) {
      AwesomeNotifications().cancel(scheduledNotificationId!);
      scheduledNotificationId = null;
    }

    // Show time picker to select notification time with 24-hour format
    TimeOfDay? selectedTime = await showTimePicker(
      context: context,
      initialTime: TimeOfDay.now(),
      builder: (BuildContext context, Widget? child) {
        return MediaQuery(
          data: MediaQuery.of(context).copyWith(alwaysUse24HourFormat: true),
          child: child!,
        );
      },
    );

    if (selectedTime != null) {
      // Generate a unique notification id for each notification
      scheduledNotificationId = DateTime.now().millisecondsSinceEpoch & 0x3FFFFFFF;

      await AwesomeNotifications().createNotification(
        content: NotificationContent(
          id: scheduledNotificationId!,
          channelKey: 'daily_reminders',
          title: 'Daily Reminder',
          body: 'Tap to write your daily diary',
          notificationLayout: NotificationLayout.Default,
        ),
        schedule: NotificationCalendar(
          repeats: true,
          preciseAlarm: true,
          allowWhileIdle: true,
          hour: selectedTime.hour,
          minute: selectedTime.minute,
          // second: 1,
        ),
        actionButtons: [
          NotificationActionButton(
            key: 'write',
            label: 'Write',
          ),
        ],
      );

      // Print confirmation message after notification is scheduled
      print(
          "Daily Reminder Notification set for ${selectedTime.format(context)}");
    }
  } catch (e) {
    print('Error scheduling notification: $e');
  }
}

authors: KiritoDv madd-project rafaelsetragni shaadart


text:
feat(rust): add ifelse snippet

This one is not completed by rust-analyzer (or I couldn't triggered it) and is specially useful when used as an expression (like a ternary operator).

Hi! I don't think this would benefit users overall mainly due to the simplicity of the snippet. And in previous discussions @dev-ardi has mentioned that we should be more selective of the snippets we're adding to the repo, not just for Rust, but the others too.
However as workaround,you can still have it loaded up on your own config if you add it as a local snippet instead of having it sourced from this repos collection of snippets.
That said, if you disagree feel free to share why you think it's a good addition!

I'm not set in stone here, but want to make a consistent effort after past discussions about how snippets get added :slightly_smiling_face:

I still think it would be a good addition for the following reasons:

Rust Analyzer does not have a snippet/action for this.
The snippet is written in way that is useful as both an expression and a statement (notice the absence of semicolons)

I find the second point specially useful for situations where you use an if expression as a ternary operator:
fn f(cond: bool) -> i32 {
    if cond {
        1
    } else {
        2
    }
}

let a = if cond {
    1
} else {
    2
};

That does not address the issue with the simplicity of it. It's not a big win in terms of characters added, it's not clear to whether it saves you time since it's likely that you'll have to edit the snippet further. Also it's very easy to write unlike #![feature(...)] or #[derive(...)].
rust-analyzer autocompletes the if``, elseandelse ifkeyword with{}` too, so there's also not a win there.

Then feel free to close it

source: gharchive/pull-request

authors: OkelleyDevelopment ValdezFOmar dev-ardi

repo: rafamadriz/friendly-snippets

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Personal Blog is down

In 5bedde7, Personal Blog (https://blog.ragnarok22.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Personal Blog is back up in 834ee89 after 9 minutes.

source: gharchive/issue


text:
Couldn't set up WebRTC dataChannel

Thanks for filing a bug report :-)
Steps to Reproduce

Followed steps to deploy artifacts directly from a PR https://github.com/raiden-network/light-client/tree/master/serve_pr
Connect a new address on goerli
mint deposit SVT tokens
Connecting to the TTT token
instead of the default hub account open a channel with another light-client opened similarly  on another browser. Matrix request is success for this.

Expected Result

Webrtc datachannel opening should be possible.

Actual Result

logs of the node.
raiden_0x3de03B8dD112bA12e785f2eFC91D8bf7Ad48806f_2020-09-01T09_13_19.755Z.log

On the current master somehow this issue seems to have solved itself

Hence closing the issue for now. It could be re-opened if we see the issue happening again.

repo: raiden-network/light-client


text:
Converting PFS refucer tests to new pattern

Thank you for submitting this pull request :)
Fixes #1616
Short description
Definition of Done

[ ] Steps to manually test the change have been documented
[ ] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

@andrevmatos you could have a look once more after the tests are done.


text:
Adding tooltip help in the swap RDN DAI

Solves #183

@fredo you can check it out again

repo: raiden-network/raiden-wizard


text:
Add retries for AssertTask

@Dominik1999 The stuff we talked about.
Open question is how big we should make the timeout. Any opinions?

nice merge it ! merge it!

repo: raiden-network/scenario-player


text:
Allow USB Debugging  is not shown  in the oculus

I had follow the instruction :

Turn on the Developer Mode toggle.
Connect your device to your computer using a USB-C cable and then wear the device. ( I used  Ubuntu)

but the  notification Allow USB Debugging  is not shown  in the oculus
is there i miss something..

Hello there.
Not sure if you are still looking, for a fix, or if someone else has the same problem, the window poped up after trying to run python oculus_reader/readter.py

This is the correct answer. Thank you @dosssman !

authors: IndrawanBudiP Jendker dosssman


text:
Use overmind to run Procfiles, if available

Overmind is a process manager (like foreman) for Procfile-based applications. The advantage is that it allows to use debuggers like pry or binding.irb without installing extra gems.

This PR is very simple, as I'm waiting for feedback on whether the maintainers like this idea. I can add tests and a CHANGELOG entry after that. I'll also open a PR on cssbundling-rails if this one is accepted.

@dhh thoughts?

I don't think it's worth carrying this specialization. You can just tweak it yourself after it's setup.

Is there any reason to prefer Foreman vs Overmind?

@semaperepelitsa I believe foreman is prefered because it's a pury-ruby solution. You can just gem install it without worrying about OSes and other packages.

Foreman has this annoying issue, its fork overman addresses that. Would you accept a PR for that @dhh?

authors: MatheusRich dhh glaucocustodio semaperepelitsa

repo: rails/jsbundling-rails


text:
evol:use and for distinct keys and or for the same keys

When a user adds filters for the same field, use "or" instead of "and" with active_record and mongoid.
https://github.com/railsadminteam/rails_admin/issues/3440

Pull Request Test Coverage Report for Build 1525526304

12 of 12 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 95.899%

Totals

Change from base Build 1520678945:
0.03%

Covered Lines:
3625

Relevant Lines:
3780

💛  - Coveralls

I'm sorry but I don't support this change. Same-looking filter entries magically changes its behavior from AND to OR condition is confusing enough for end-users.
Of course I understand the needs for OR filtering, but it should be achieved with a UI that's not confusing.

authors: QPierre1 coveralls mshibuya


text:
Syntax error: redirection unexpected in Gitlab CI

$ curl -fsSL https://railway.app/install.sh | sh
sh: 336: Syntax error: redirection unexpected

change it to this:
bash <(curl -fsSL cli.new)

repo: railwayapp/cli


text:
support running with custom non-root user

This PR adds support for running the start command as a non-root user. The user is frist created with useradd.
This is a very simply implementation of custom user support and if you have a another use case that requires additonal user configuration, please leave a comment or create an issue to open up a discussion.
Closes #449, #990
Configuration
user is added as a field to the start phase and can be configured with a nixpacks.toml file like this
# ...

[start]
user = "myuser"

or via the command line by passing custom config. For example
$ nixpacks build examples/custom-user --name user --json-plan '{ "start": { "user": "myuser2" } }'

When it comes to serving static assets, nginx is used. With the introduction of the custom non-root user, would this break that?  As nginx needs root access to write /var/log/nginx, /var/cache/nginx and for whatever else I'm not 100% familiar what nginx needs to run.

This will not change anything by default so nothing should break when nginx is used unless a non-root user is manually specified.

repo: railwayapp/nixpacks


text:
fix: avoid chain switch on connect if already on supported chain

Thanks @jxom for showing me the (currently undocumented) connector.getChainId() API which makes this possible 🙏

Confirmed that this doesn't interrupt iOS deep linking too 🙌

Thank you, this is much appreciated!

authors: kasparkallas markdalgleish

repo: rainbow-me/rainbowkit


text:
fix [Android] Support 16KB Page Size #294

fix: #294
Support android 16KB Page Size

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.03%. Comparing base (c0c1b6c) to head (4e96ed1).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #295   +/-   ##
=======================================
  Coverage   92.03%   92.03%
=======================================
  Files          49       49
  Lines        9129     9129
=======================================
  Hits         8402     8402
  Misses        727      727

Flag
Coverage Δ

unittests
92.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

authors: codecov-commenter rainyl


text:
🛑 RiotSkin4CN-Download is down

In 0b654b4, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in 7f3a577.


text:
🛑 RiotSkin4CN-Download is down

In 76659e4, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in d042569.


text:
🛑 RiotSkin4CN-Download is down

In f570f36, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in 86a0d0a.


text:
Push registered, no notification [possible fix]

I had an issue that I see some others have.
In Xcode, it appears with messages printing the Plugin is registered and active.
I was not receiving the notification because I had not changed the Bundle Identifier in my mobile-config.js file to reflect that of the App ID through the developer portal. Once I did, everything worked flawlessly.
Hope this helps.

Can we improve the documentation or guides?

repo: raix/push

license: mit

license_source: bigquery


text:
Fix issue with tracing

Currently only order-service and inventory-service is printing traceId and spanId, Rest all are not printing it. Fix this

61ad3191493e483befec58d6cc2de27bdccf2a1e


text:
🛑 PlayStore API is down

In acf7f6a, PlayStore API (https://api-playstore.rajkumaar.co.in) was down:

HTTP code: 502
Response time: 272 ms

Resolved: PlayStore API is back up in 5c643c2.


text:
Not able to run due to error in solargraph

Wonderfull idea of an extension, looking forward to using it. But when i installed and try running it, I am getting the following error which is not allowing me to proceed.
[Error - 9:54:15 am] Request textDocument/foldingRange failed.
  Message: [Solargraph::FileNotFoundError] Host could not find vscode-notebook-cell:/home/coderhs/sandbox/notebooks/ruby/hello-world.rubybook#ch0000001
  Code: -32603

Ack. I have a bunch of Ruby extension but don't have Solargraph, so thanks for posting this!
One possible reason that I can immediately think of is that VS Code invoke Solargraph for any Ruby code but the Solargraph server only handles Ruby files and not other entities like notebook cells.
I will look into this issue. Unfortunately, it would be difficult for me to look into this until the weekend. I'll try to have an update over the weekend.
If there is a way to disable Solargraph for certain file extensions, then maybe you can try that for now.

I tried both disabling and uninstalling the solargraph extension.
Without the solargraph extension, the code just hangs. With the extension the error is as reported by @coderhs

@abhijitnandy I am going to look at the issue with solargraph installed. But the issue without solargraph seems strange.

Do you have ruby and pry installed?
Can you invoke the pry shell by typing pry in command line?

Yes, have both ruby and pry installed.
[1] pry(main)> puts 'Hello!'
Hello!
=> nil
[2] pry(main)>

@abhijitnandy This extension spawns a Node.JS child process to run pry in the background. Looks like those don't work well with Windows systems. I am thinking of changing the extension architecture to a client-(pry) server model so that it works on Windows as well. But till then UNFORTUNATELY will have to make this a Mac only extension. I have updated the README as well. Sorry for the inconvenience.
@coderhs Created an issue with Solargraph for the error.

authors: abhijitnandy coderhs rajshah11


text:
Header values cannot contain semicolons

The header parsing precludes headers with values that have semicolons. The following code will fail header parsing because it tries to split on semicolons before processing the name/value pairs:
boom -h "cookie:foo=1;bar=2" http://example.com

this is fixed in PR #89
@rakyll , could you have a review on let?
thanks

authors: michaelcameron missedone

repo: rakyll/boom


text:
Better error handling when loading a dead Storylines product

Better error handling of an invalid Storylines product would be useful.
The as-is: loading a bunk Storylines ID just leads to an infinite loading spinner. Libraries download but otherwise nothing happens. The user might be expecting something to load, unaware that they're accessing a bad URL.
Example: https://environmental-maps.canada.ca/RAMP-Storylines/index-ca-en.html#/en/asdf
It would be great if we could simply display a broken link, a message that the Storylines product couldn't be loaded, something to that affect.

Previous efforts on this may have been made and lost?


text:
Cloning on windows and PyCharm

Hi, When you cloning your project on windows 8.1/PyCharm, I get the following error:
Clone failed
unable to create file Icon?: Invalid argument
unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
It seems that one of the file is name with a question mark"?"?
Thanks for the help

This is still an issue. Cannot be cloned on windows.

authors: nono-london pquan

repo: ranaroussi/qtpylib


text:
No data found for this date range, symbol may be delisted

I got the following error. I am not sure what is wrong. Does anybody know what is the problem?
>>> import yfinance as yf
>>> ticker = 'MSFT'
>>> data = yf.Ticker(ticker).history(interval='1m', start='2021-11-06', end='2021-11-07')
- MSFT: No data found for this date range, symbol may be delisted

That date is Saturday ...

repo: ranaroussi/yfinance


text:
Update quote.py

To add topHoldings and price for ETF weighting
https://github.com/ranaroussi/yfinance/issues/1554

The reason there are other changes is you created your branch from main, but it should be from dev. Branch from dev to merge into dev, understand?

And move major_holdings into a separate pull request, because it's a different feature. Also, note that for non-ETF symbols e..g 'AMZN', major_holdings returns price information instead, maybe should return None.

@AKwoKWH Do you plan to complete this?

i have a branch that replicates and finishes this work.
unless #1784 is the preferred direction.

@bot-unit

@ValueRaider
sorry. i'm busy and cann't help. I think we can accept any working code for now, and replace it later.

authors: AKwoKWH ValueRaider bot-unit dotJoel


text:
Set concurrency to 1 for publish artifacts

Temporary set concurrency to one while pushing artifacts to avoid
hitting a concurrency issue on luet-cosign
Signed-off-by: Itxaka igarcia@suse.com

should not affect PR workflows

repo: rancher-sandbox/cOS-toolkit


text:
Convoy mount options does not take effect

I did some test as this:

root@mesos002:/var/lib/docker# convoy mount dvd1 foo=bar
/var/lib/convoy/devicemapper/mounts/42d1d61d-db66-4c44-b8c6-47a94b30638e

Check convoy log, no mount options

DEBU[8407] Calling: POST, /volumes/mount, request: POST, /v1/volumes/mount  pkg=daemon
DEBU[8407]                                               event=mount object=volume opts=map[MountPoint:] pkg=daemon reason=prepare volume=42d1d61d-db66-4c44-b8c6-47a94b30638e
DEBU[8407] Volume 42d1d61d-db66-4c44-b8c6-47a94b30638e is being mounted it to /var/lib/convoy/devicemapper/mounts/42d1d61d-db66-4c44-b8c6-47a94b30638e, with option []  pkg=util
DEBU[8407]                                               event=list mountpoint=/var/lib/convoy/devicemapper/mounts/42d1d61d-db66-4c44-b8c6-47a94b30638e object=volume pkg=daemon reason=complete volume=42d1d61d-db66-4c44-b8c6-47a94b30638e

Also test with dvdcli mount with mount options, but the options also does not work.
root@mesos002:/var/lib/docker# dvdcli  mount --volumedriver=convoy  --volumename=dvd1 --volumeopts=foo1=bar1
INFO[0000] /var/lib/convoy/devicemapper/mounts/42d1d61d-db66-4c44-b8c6-47a94b30638e
/var/lib/convoy/devicemapper/mounts/42d1d61d-db66-4c44-b8c6-47a94b30638e

Oops, currently the support of mount option was removed. Keep this open as enhancement.

authors: jay-lau yasker

repo: rancher/convoy


text:
"HTMLElement is not defined" is displayed when starting with yarn dev in v2.6.5

Setup

Rancher version: v2.6.5
Browser type & version: Chrome 102.0.5005.61

Describe the bug

When I start Rancher in development mode with yarn dev and open the Rancher login screen in Chrome,
The following error screen is displayed.
To Reproduce

It started by this steps.
GitHub - rancher/dashboard: Rancher new Dashboard UI
yarn install
API=https://my-rancher-domain yarn dev

Result
No error is displayed on the console when launching Rancher with yarn dev.
yarn dev
yarn run v1.22.17
$ ./node_modules/.bin/nuxt dev
Build: Development                                                                                12:01:25
API: http://localhost:8989                                                                                12:01:25

   ╭─────────────────────────────────────────────╮
   │                                             │
   │   Nuxt.js @ v2.14.6                         │
   │                                             │
   │   ▸ Environment: development                │
   │   ▸ Rendering:   server-side                │
   │   ▸ Target:      server                     │
   │                                             │
   │   Listening: https://192.168.68.107:8005/   │
   │                                             │
   ╰─────────────────────────────────────────────╯

ℹ Preparing project for development                                                                                12:01:28
ℹ Initial build may take a while                                                                                12:01:28
✔ Builder initialized                                                                                12:01:28
✔ Nuxt files generated                                                                                12:01:28
ℹ Warming up worker pools                                                                                12:01:31
✔ Worker pools ready                                                                                12:01:31

✔ Client
  Compiled successfully in 2.39m

✔ Server
  Compiled successfully in 2.33m

ℹ Waiting for file changes                                                                                12:03:55
ℹ Memory usage: 1.43 GB (RSS: 11.2 GB)                                                                                12:03:55
ℹ Listening on: https://192.168.68.107:8005/                                                                                12:03:55
No issues found.

Expected Result
The Rancher login screen should be displayed.
Screenshots

When I access https://localhost:8005 with a browser, the following error screen is displayed.

Additional context

Detailed Description

The code that is directly causing the error
https://github.com/rancher/dashboard/blob/v2.6.5/components/ActionMenu.vue#L57
Context

Can you confirm which branch you're using, also the node version?
This kind of error is usually a sign of switching between master and a previous branch/version. Would suggest the following

yarn clean
Removing local node_modules folder
yarn install

Thank you for your reply.
The branch I'm using is release-2.6.5,
Here are the versions of node and yarn.
node -v
v14.17.2

yarn -v
1.22.17

I started with this step.
git checkout release-2.6.5
yarn clean
rm -rf ./node_modules/
yarn install
API=https://my-rancher-domain yarn dev

I also have this problem.

@yhidai @heyhaiyon Can you both try re-cloning the repo? I hit this once a few weeks back and a yarn clean, rm node modules and yarn install failed to resolve it, but a rebase did. If all else fails the re-clone should work

@nwmac This cleanup mechanism isn't working for me.  Here is what I just did to try to recover:

git clone git@github.com:rancher/dashboard.git
cd dashboard
git checkout release-2.6.5
yarn install
Create .env with API and KUBECONFIG variables set to the correct values.
yarn dev

In the yarn dev window, I see tons of these "caniuse-lite is outdated" messages but it starts fine:
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating
ℹ Waiting for file changes                                            15:25:07
ℹ Memory usage: 1.39 GB (RSS: 2.21 GB)                                15:25:07
ℹ Listening on: https://192.168.1.144:8005/                           15:25:07
No issues found.                                                      15:25:08

But when I try to access using Firefox, I get this:

Here are the node/yarn versions:
rpatrick@rpatrick-mac dashboard % node --version
v16.15.1
rpatrick@rpatrick-mac dashboard % npm --version
8.11.0
rpatrick@rpatrick-mac dashboard % yarn --version
1.22.19
rpatrick@rpatrick-mac dashboard %

@nwmac After spending some time searching through the message boards, I came across a common theme where web frameworks that perform Server-Side Rendering seem to be hitting this issue because the SSR framework does not define HTMLElement as a global.
By editing ActionMenu.vue and replacing lines 57 and 63 and setting their values to Object (instead of HTMLElement and PointerEvent, respectively), the problem goes away and the application works properly.
As such, I believe that this is a real bug and not an anomaly.   Thoughts?

@nwmac As another data point, disabling SSR in nuxt.config.js (without changing the ActionMenu.vue code) also eliminates the issue and allows the application to work properly so it really seems like this is a bug...

@robertpatrick Thanks for taking the time to look in to this. Please note though SSR support has been removed in the upcoming release (2.6.7) and was only enabled in dev mode and not production.

authors: heyhaiyon richard-cox robertpatrick yhidai

repo: rancher/dashboard


text:
Constraint polish

This is not all of the OPA changes and isn't fully tested yet. This was getting long and I felt that splitting up the PR would make things easier to review. This is just the Constraint edit page. Yaml still has a bug that needs to be resolved.

Moving gatekeeper-constraint to be a spoofedType
Pick the template first before seeing the tabs
Styling The header for the inputs don't look like header
Kinds

Style of the boxes should be consistent ⇒ Make a component "Group list" (cody)

Outer "Kind" ⇒ called "Rule"
Change the tab to be called "Rule"

Parameters

Show yaml all the time and remove the add parameter option

Enforcement

Move the radio buttons out of the tabs to the section above and add a description

Namespace list:

Multi-select on two separate rows for Namespaces and Excluded Namespaces
Any rules needed on filtering the namespaces (confirm with Prachi)
Add description on what this does if needed

Selectors:

Label Selector should be moved to "Rules" tab
Namespace selector should be moved to "Namespace" tab

Still WIP. I noticed some big issues. That only showed up after doing a full refresh.

Resolved the refresh issues so this should be ready to look at. Still not complete but I think it's a good merge point.

Updated to include the rest of the polish.


text:
bump rancher/system-agent to v0.2.8

Bump system-agent to latest

Blocked by #21

authors: Itxaka mudler

repo: rancher/elemental-operator


text:
Split arm and x86_64 tests

This commit splits arm64 and x86_64 tests. With this PR arm64 tests on self hosted runners can only be executed on demand, they are no longer possible in PRs.
Later on we can consider making them executable on scheduled basis if we consider them to be stable enough.

Once approved I will update the required build checks, as they got renamed due to the matrix change and now expected ones are simply not happening.

repo: rancher/elemental-toolkit


text:
/usr/libexec missing on aarch64

After copying firmware and bootloader files on aarch64, cOS comes up nicely but then fails to mount /usr/libexec, resulting in a locked root account and no way out.
(Not sure if this is a ros-installer or a cOS-toolkit issue 🤷🏻 )

This looks like an issue while creating the base image. os2 requires the /usr/libexec path in the container image used to boot.

aarch64 support depends on https://github.com/rancher/elemental-toolkit/issues/1258 - otherwise can be achieved using the arm_image_builder.sh script in the toolkit repository.

This is considered fixed.

authors: kkaempf mudler

repo: rancher/elemental


text:
[FEATURE] Add Rancher to the Harvester on HCI mode

Is your feature request related to a problem? Please describe.
Add Rancher to the Harvester by default on the HCI mode, allow the Harvester admin/user to manage and create k8s cluster directly using the harvester node driver.
Describe the solution you'd like

install and configure the Rancher by default using Harvester ISO mode installation
allow the Harvester admin/user to manage and create k8s cluster directly on the Rancher UI using the Harvester node driver
configure centralized RBAC and authorization between the Rancher and Harvester

Describe alternatives you've considered
N/A
Additional context
N/A

+1

Validated on v0.2.0-rc1
Following test cases are verified:

Launch the harvester via iso (single node and multiple nodes), and the harvester will install Rancher Server by default.
You need to set a password to log in to the harvester for the first time. This user and password can also log in to Rancher Server
Create a user in Rancher Server, and this user can log in to the harvester UI
After the harvester becomes Ready, first log in to the Rancher Server to set a password, and then use the username/password to successfully log in to the harvester.

authors: guangbochen kingsd041 liorkesos

repo: rancher/harvester


text:
cri_stats_provider.go:576] Unable to fetch container log stats for path ...

Version:
k3s version v1.17.3+k3s1 (5b17a175)
Describe the bug
After fresh install on Arch linux, this messages repeatdly shown in logs,
Mar 08 20:59:30 a k3s[13751]: E0308 20:59:30.121369   13751 cri_stats_provider.go:576] Unable to fetch container log stats for path /var/log/pods/kube-system_helm-install-traefik-nhfpw_1a87f658-fd48-4743-986c-eb1f8fc5c1a4/helm: failed command 'du' ($ nice -n 19 du -x -s -B 1) on path /var/log/pods/kube-system_helm-install-traefik-nhfpw_1a87f658-fd48-4743-986c-eb1f8fc5c1a4/helm with error exit status 1
Mar 08 20:59:40 a k3s[13751]: E0308 20:59:40.150052   13751 cri_stats_provider.go:576] Unable to fetch container log stats for path /var/log/pods/kube-system_helm-install-traefik-nhfpw_1a87f658-fd48-4743-986c-eb1f8fc5c1a4/helm: failed command 'du' ($ nice -n 19 du -x -s -B 1) on path /var/log/pods/kube-system_helm-install-traefik-nhfpw_1a87f658-fd48-4743-986c-eb1f8fc5c1a4/helm with error exit status 1

To Reproduce
Expected behavior
Actual behavior
Additional context
Arch linux
k3s installed via aur pkg.

https://aur.archlinux.org/packages/k3s-bin/

NAMESPACE     NAME                                          READY   STATUS      RESTARTS   AGE
kube-system   pod/helm-install-traefik-nhfpw                0/1     Completed   0          120m
kube-system   pod/local-path-provisioner-58fb86bdfd-n7ck9   1/1     Running     1          120m
kube-system   pod/svclb-traefik-pd957                       2/2     Running     2          119m
kube-system   pod/metrics-server-6d684c7b5-7ppzb            1/1     Running     1          120m
kube-system   pod/traefik-6787cddb4b-2xcb2                  1/1     Running     1          119m
kube-system   pod/coredns-d798c9dd-h656h                    1/1     Running     1          120m
default       pod/kuard-6wf94                               1/1     Running     0          89m

NAMESPACE     NAME                         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
default       service/kubernetes           ClusterIP      10.43.0.1       <none>        443/TCP                      137m
kube-system   service/kube-dns             ClusterIP      10.43.0.10      <none>        53/UDP,53/TCP,9153/TCP       137m
kube-system   service/metrics-server       ClusterIP      10.43.127.132   <none>        443/TCP                      137m
kube-system   service/traefik-prometheus   ClusterIP      10.43.4.40      <none>        9100/TCP                     119m
kube-system   service/traefik              LoadBalancer   10.43.20.246    172.30.1.23   80:32744/TCP,443:30859/TCP   119m

NAMESPACE     NAME                           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
kube-system   daemonset.apps/svclb-traefik   1         1         1       1            1           <none>          119m

NAMESPACE     NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/metrics-server           1/1     1            1           137m
kube-system   deployment.apps/local-path-provisioner   1/1     1            1           137m
kube-system   deployment.apps/traefik                  1/1     1            1           119m
kube-system   deployment.apps/coredns                  1/1     1            1           137m

NAMESPACE     NAME                                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/metrics-server-6d684c7b5            1         1         1       120m
kube-system   replicaset.apps/local-path-provisioner-58fb86bdfd   1         1         1       120m
kube-system   replicaset.apps/traefik-6787cddb4b                  1         1         1       119m
kube-system   replicaset.apps/coredns-d798c9dd                    1         1         1       120m
default       replicaset.apps/kuard                               1         1         1       89m

NAMESPACE     NAME                             COMPLETIONS   DURATION   AGE
kube-system   job.batch/helm-install-traefik   1/1           26s        137m

kuard rs is my own test pods.

journalctl -u k3s.service -b > k3s.log
k3s.log

@dontdieych do u still have this problem?

authors: dontdieych liyimeng


text:
kernel panic/soft lock CPU

RancherOS Version: (ros os version)
1.5.4
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VM in kvm qemu 2.11.1 under ubuntu 18.04.3 4.15.0-70-generic
since last kernel update of ubuntu most probably, I have kernel panic in my rancherOS vm/ soft lock CPU
The VM can stay alive if I let only 3 containers alive, Can't do any docker pull, I haven't change anything to the VM. rancher-server container was making the whole VM crash.
It seems be an I/O problem and I don't have any clue how to debug this. Don't know if it a RAID-related problem either.
Any ideas where I could look to know what's happening?

no lead or idea about what to look for? Why this VM is crashing while it doesn't seem to be corrupted or anything. Can anyone do a test on a ubuntu server and put a rancherdocker VM in kvm-qemu?

repo: rancher/os


text:
'Application Development Engine with Epinio' Landing Page

SURE-6866
Request description:
Add landing page as top page in hierarchy for each 'Integrations' section.
Page should include:

brief description of integrated product/project

benefits of integrating product/project with Rancher

additional benefits received by Prime customers

Reopening as additional review/updates need to be made. Initial PR was merged so some stakeholders had access to a preview.

repo: rancher/rancher-docs


text:
Update rollbacks.md

Added the warning about 2.6.4+ rollbacks from the restore docs so that people doing rollbacks can see them without having to know to look at the restore docs

@celidon I made some copy edits to the PR, let me know if you're ok with the changes. Also, can you link to the restore docs you mentioned so we can make a corresponding update to the wording there? Thanks!

@martyav I think your changes look great. As you said, I didn't make any wording updates. I just copied the existing docs so that customers trying to rollback from 2.6.4+ quit having issues when they just tried a restore. Original doc page in GitHub: https://github.com/rancher/rancher-docs/blob/main/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/restore-rancher.md

authors: celidon martyav


text:
Launch kubectl security issues

Currently found UI Launch kubectl This is connected to the cattle-node-agent pod perform kubectl command, but because this pod is a privileged pod, need kube-apiserver permission privileged pod exec permissions, remove the DenyEscalatingExec parameters, If these containers are compromised, An attacker can easily compromise the underlying host. Given that particular pods require privileged access, can you make some changes to Launch kubectl?

Useful
Info

Versions
Rancher v2.0.2 UI: v2.0.48

Access
local admin

Route
global-admin.clusters.index

Close in favor of https://github.com/rancher/rancher/issues/13612

authors: loganhz wanshaoyuan

repo: rancher/rancher


text:
If no organization entered, the word "none" showing up at bottom of list is confusing

v0.27.0-rc1
Steps;

Authenticate
Open site access area on access control screen
Add a user (not a organization)

Results:  the word none appears at the bottom until you add an org

Expected:
None should not be down there since I have users.

v0.27.0-rc1 (ui latest)
Verified fixed


text:
Error when log out then try to log back in to Rancher UI

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Log in to Rancher. Log out.
Try to log back in.

response:
{"baseType":"error","code":"InvalidCSRFToken","message":"Invalid CSRF token","status":422,"type":"error"}

Other details that may be helpful:
Same as https://github.com/rancher/rancher/issues/25714
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): 2.3.6-rc9
Installation option (single install/HA): single

Verified on 2.3-head latest - ui tag: latest-2.3

logout and login Rancher as admin, in the same window, user does not see the error anymore.


text:
Hairpin rules are not added when using IPVS with a cloudprovider enabled

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Create a node driver cluster with a cloud provider enabled, EC2 with the AWS cloud provider was used in this example
Enable IPVS, eg:

  services:
    kubeproxy:
      extra_args:
        ipvs-scheduler: rr
        proxy-mode: ipvs

Create a workload with a ClusterIP service (1 replica is best for testing)
The workload cannot reach itself via the ClusterIP or service DNS name using the service port (hairpin connectivity)

Result:

The hairpin iptables rule is not added to the KUBE-POSTROUTING chain.

# iptables -nvL -t nat | grep POSTROUTING -A5

Chain KUBE-POSTROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
  187 18489 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match ! 0x4000/0x4000
   88  6857 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            MARK xor 0x4000
   88  6857 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes service traffic requiring SNAT */

The following hairpin rule is expected:

 pkts bytes target     prot opt in     out     source               destination
    0     0 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* Kubernetes endpoints dst ip:port, source ip for solving hairpin purpose */ match-set KUBE-LOOP-BACK dst,dst,src
[..]

The ipset KUBE-LOOP-BACK table is not populated:

# docker exec kube-proxy ipset list KUBE-LOOP-BACK
Name: KUBE-LOOP-BACK
Type: hash:ip,port,ip
Revision: 5
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 136
References: 0
Members:

Other details that may be helpful:
This appears to relate to the IsLocal condition not being matched due to different names for the node being populated with the cloudprovider metadata, the difference in nodeName and kubernetes.io/hostname prevents the hairpin rule and ipset list being added to the nodes, as no “local” pods are detected as endpoints.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.5
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): EC2 / infrastructure
Kubernetes version (use kubectl version): v1.16.15

gz#11904
JIRA: SURE-2373, SURE-3284

https://github.com/kubernetes/kubernetes/issues/71851#issuecomment-545734034

https://github.com/kubernetes/kubernetes/issues/71851#issuecomment-545734034

Root cause
kubelet uses nodename set by aws cloud provider, but kube-proxy doesn't. kube-proxy expects the hostname to be the same as the nodename, otherwise it doesn't set the right iptables rules.
What was fixed, or what changes have occurred

change in RKE to remove hostname-override arg from kubelet and kube-proxy https://github.com/rancher/rke/pull/2803
change in rke-tools to set the correct hostname for kube-proxy if hostname-override doesn't exist.

Areas or cases that should be tested

rke1 cluster with aws cloud provider and ipvs enabled to confirm the original issue is fixed
rke1 cluster without cloud provider to confirm kubelet and kube-proxy continue to get the correct hostname-override

What areas could experience regressions?
Are the repro steps accurate/minimal?
yes

Re-opening the issue

Verified on rancher v2.6.3, KDM pointing to dev-2.6

Steps followed :

Provisioned a single node AWS node driver cluster (k8s v1.22.5-rancher2-2). Selected Amazon (In-Tree) cloud provider and added below args :

 services:
    kubeproxy:
      extra_args:
        ipvs-scheduler: rr
        proxy-mode: ipvs

Created a nginx deployment with a ClusterIP service (port 80).
Exec into nginx pod and ran curl to ClusterIp and getting Connection timed out
Whereas getting the correct response when running the curl to nginx ClusterIp from other pod.

iptables output as mentioned here.
# iptables -nvL -t nat | grep POSTROUTING -A5
--
Chain KUBE-POSTROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
   15   900 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match ! 0x4000/0x4000
    7   420 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            MARK xor 0x4000
    7   420 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes service traffic requiring SNAT */ random-fully

docker exec kube-proxy ipset list KUBE-LOOP-BACK
Name: KUBE-LOOP-BACK
Type: hash:ip,port,ip
Revision: 6
Header: family inet hashsize 1024 maxelem 65536 bucketsize 12 initval 0x36182ee0
Size in memory: 208
References: 0
Number of entries: 0
Members:

The issue is rke-tools is dependent on the RKE fix, but rancher 2.6.3 doesn't have this fix vendored. Looking into it to see if the fix can be in rke-tools alone.

The command args for kube-proxy don't pass cloud provider aws, so there isn't a way to override hostname-override flag without the corresponding RKE fix. Need to move this issue to v2.6.4 because that's when the RKE fix will be vendored to Rancher. cc @sowmyav27 @snasovich
Note:

we do not need to revert the fix in rke-tools because it's no op, it updates hostname-override only if it's not set
we do not need to update KDM to use older version of rke-tools because the current version of rke-tools has a CVE fix

Fix now available to test with the latest k8s versions (v1.23.4, v1.22.6-rancher1-2, v1.21.9-rancher1-2, v1.19.16-rancher1-4) - they use new rke-tools v0.1.79.

Verifed this on rancher v2.6-head(4df2214), docker install.
Case 1 : AWS cloud provider enabled
Validation steps followed :

Created 4 downstream ec2 node driver cluster(single node), using k8s version -> v1.23.4-rancher1-1, v1.22.6-rancher1-2, v1.21.9-rancher1-2 and v1.19.16-rancher1-4. Selected Amazon (In-Tree) cloud provider and added below args :

services:
    kubeproxy:
      extra_args:
        ipvs-scheduler: rr
        proxy-mode: ipvs

Created nginx deployment with a ClusterIP service (port 80) in default ns.
Exec into nginx pod and ran curl to ClusterIp and getting the correct response.
SSH'ed into control plane, hairpin rule is also present :

Chain KUBE-POSTROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* Kubernetes endpoints dst ip:port, source ip for solving hairpin purpose */ match-set KUBE-LOOP-BACK dst,dst,src
   30  1800 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match ! 0x4000/0x4000
   11   660 MARK       all  --  *      *       0.0.0.0/0            0.0.0.0/0            MARK xor 0x4000
   11   660 MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0            /* kubernetes service traffic requiring SNAT */ random-fully

Case 2 : Verify kubelet and kube-proxy continue to get the correct hostname-override if cloud provider is not selected
Validation steps followed :

Created 4 downstream ec2 node driver cluster(single node), using k8s version -> v1.23.4-rancher1-1, v1.22.6-rancher1-2, v1.21.9-rancher1-2 and v1.19.16-rancher1-4.
SSH'ed into control plane node and verified the hostname-override arg value:

ps -ef | grep -i kubelet | grep -i over
root        8619    8599  2 06:59 ?        00:09:04 kubelet --resolv-conf=/etc/resolv.conf --cni-conf-dir=/etc/cni/net.d --cni-bin-dir=/opt/cni/bin --client-ca-file=/etc/kubernetes/ssl/kube-ca.pem --hostname-override=rishabh-cluster-1-23-none1 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-node.yaml
...

ps -ef | grep -i kube-proxy | grep -i over
root        9262    9238  0 06:59 ?        00:00:03 kube-proxy --healthz-bind-address=127.0.0.1 --v=2 --hostname-override=rishabh-cluster-1-23-none1 --kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml
...

kubectl get node
NAME                         STATUS   ROLES                      AGE     VERSION
rishabh-cluster-1-23-none1   Ready    controlplane,etcd,worker   5h35m   v1.23.4

Similarly did this for other k8s cluster as well.

Result :

Both scenarios passed, hence closing the issue.

authors: dkeightley kinarashah rishabhmsra


text:
Rancher chart post-delete hook fails on hardened cluster

What kind of request is this:
bug
Steps to reproduce:

Install Rancher on CIS 1.5 compliant cluster RKE1

Details on pre-requirements here.

Uninstall the Rancher chart helm uninstall rancher -n cattle-system

Result:
Events:
  Type     Reason        Age                From            Message
  ----     ------        ----               ----            -------
  Warning  FailedCreate  18s (x3 over 48s)  job-controller  Error creating: pods "rancher-post-delete-" is forbidden: PodSecurityPolicy: unable to admit pod: []

Other details that may be helpful:
Environment information

Rancher version: 2.6 master-head (05/25/2021) f90b36e
Installation option: HA RKE1

Rancher version 2.6 master-head (06/06/2021) b0c0eb4
This is failing now with:
k describe job rancher-post-delete -n cattle-system
Name:           rancher-post-delete
Namespace:      cattle-system
Selector:       controller-uid=65e6336a-20c8-4984-a894-657184783487
Labels:         app=rancher
                chart=rancher-2.5.8
                heritage=Helm
                release=rancher
Annotations:    helm.sh/hook: post-delete
                helm.sh/hook-delete-policy: before-hook-creation,hook-succeeded
                helm.sh/hook-weight: 3
Parallelism:    1
Completions:    1
Pods Statuses:  0 Running / 0 Succeeded / 0 Failed
Pod Template:
  Labels:           app=rancher
                    chart=rancher-2.5.8
                    controller-uid=65e6336a-20c8-4984-a894-657184783487
                    heritage=Helm
                    job-name=rancher-post-delete
                    release=rancher
  Service Account:  rancher-post-delete
  Containers:
   rancher-post-delete:
    Image:      rancher/shell:v0.1.6
    Port:       <none>
    Host Port:  <none>
    Command:
      /scripts/post-delete-hook.sh
    Environment:
      NAMESPACES:          fleet-system cattle-system rancher-operator-system
      TIMEOUT:             120
      IGNORETIMEOUTERROR:  false
    Mounts:
      /scripts from config-volume (rw)
  Volumes:
   config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      rancher-post-delete
    Optional:  false
Events:
  Type     Reason        Age                  From            Message
  ----     ------        ----                 ----            -------
  Warning  FailedCreate  46s (x5 over 3m16s)  job-controller  Error creating: pods "rancher-post-delete-" is forbidden: PodSecurityPolicy: unable to admit pod: [spec.containers[0].securityContext.runAsUser: Invalid value: 0: running with the root UID is forbidden]

Cluster has these pre-requirements configured/applied: https://rancher.com/docs/rancher/v2.x/en/security/rancher-2.5/1.6-hardening-2.5/

@izaac Sorry that I add the wrong label to the issue. We can not validate the fix until we have v2.6.0 rc

Available to test in v2.6.0-rc1

Rancher version: v2.6.0-rc1
The post delete seems to be working now on a CIS install but there's a separate issue as fleet seems not getting cleared from the install.
Opened separate issue here: https://github.com/rancher/rancher/issues/33986
Original post-delete hook fix:  https://github.com/rancher/rancher/issues/30924

authors: deniseschannon izaac jiaqiluo


text:
[2.5]Corrupted Backup - No Restore Rancher Management Cluster / Rancher Server

Rancher Server Setup

Rancher version: 2.5.9
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Info:
Cluster Type (RKE1, RKE2, k3s, EKS, etc): rke1 1.2.9
Node Setup: (3 Nodes HA Cluster for Rancher)
Version: 2.5.9

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Describe the bug

Rancher recovers from backup file failed on works case scenario where nodes were deleted.
ERRO[2021/07/21 09:21:04] Error restoring namespaced resources [error restoring m-gd5n4 of type management.cattle.io/v3, Resource=nodes: namespaces "c-kg7bm" not found]
ERRO[2021/07/21 09:21:04] error syncing 'restore-dgl9z': handler restore: error restoring namespaced resources, check logs for exact error, requeuing
To Reproduce

1.) Created a manual backup with rancher 2.5.9 running
2.) Destroyed rancher management server/cluster (complete wipe with "terraform destroy") Or delete the nodes on the provider side.
3.) Create an new RKE cluster with "terraform apply"
10 min wait... check rancher: everything perfectly fine. new and fresh rancher
4.) Follow documentation for migration https://rancher.com/docs/rancher/v2.x/en/backups/v2.5/migrating-rancher/
4a.) start a restore job pointing to the manual backup file
4b.) backup starts - renders rancher "unreachable" ( 503 Service Temporarily Unavailable )
Result
Fail to Restore from Backup.
Expected Result

Restore from Backup successfully..
Screenshots

Additional context

Complete infrastructure is set up with Terraform (Rancher Management Cluster - 3 vSphere VMs, RKE Cluster, Rancher Install, Rancher Bootstrapping,...)
Upgrade of Rancher RKE with Terraform (charming, worked perfectly)
Upgrade of Rancher Server with Terraform (")
After the upgrade planned a DR test (destroy complete Rancher Management Cluster infrastructure, re-deploy it via Terraform , restore Rancher Backup).
Currently doing Rancher Backups to an NFS PV with an EncryptionConfig and a recurring backup job (also setup with Terraform).
# k logs -f -n cattle-resources-system rancher-backup-74db9fdd57-rj4bj
ERRO[2021/07/21 09:21:04] Error restoring namespaced resources [error restoring m-gd5n4 of type management.cattle.io/v3, Resource=nodes: namespaces "c-kg7bm" not found]
ERRO[2021/07/21 09:21:04] error syncing 'restore-dgl9z': handler restore: error restoring namespaced resources, check logs for exact error, requeuing

Hint: namespace "c-kg7bm" is the namespace of the deleted cluster regarding the "cannot delete node template" ticket

After the job is "done" :

INFO[2021/07/21 09:21:04] Successfully restored ctr-r87n4-ctr-a
INFO[2021/07/21 09:21:04] Processing controllerRef apps/v1/deployments/rancher
INFO[2021/07/21 09:21:04] Scaling up controllerRef apps/v1/deployments/rancher to 3
ERRO[2021/07/21 09:21:04] Error restoring namespaced resources [error restoring m-gd5n4 of type management.cattle.io/v3, Resource=nodes: namespaces "c-kg7bm" not found]
ERRO[2021/07/21 09:21:04] error syncing 'restore-dgl9z': handler restore: error restoring namespaced resources, check logs for exact error, requeuing

Rancher Pods are scaled up to 3 and Rancher is "usable again" - we can also see the downstream clusters

BUT

The restore job runs again after a while in an "infinite loop" --> rancher is unusable!

We tried restore with "prune: true" and "prune: false". No difference.

@StrongMonkey , is this customer issue hence the "internal" label?

@snasovich yes that's right

There is a way to reproduce this issue:

Create a cutsom cluster on rancher 2.5.9.
Wait for it to be provisioned. Once it is provisioned, modify v3 management.cattle.io/node and add a fake finalizer(in real user case there is an existing finalizer controller.cattle.io/node-controller that could make this node stuck at deletion if clean up failed, to reproduce the bug adding a fake finalizer should be enough to test)
Go and delete the cluster. You will see that the cluster is gone in UI but the underlying namespace c-xxxx and v3 node are stuck at deletion.

The root cause here is that we don't restore namespace even if it has deletionTimestamp and finalizers, because namespace has the finalizer in spec.finalizer instead of metadata.finalizers. The stucking resource in that namespace is being restored, but not the namespace itself, causing the error above.

@StrongMonkey is a fix for Rancher 2.5.x planned?

(i'm the guy who spotted this issue and provided the logs above). THX Sebastian

@smangelkramer yes it is planned to land in 2.5.10.

@StrongMonkey is this related to #32888? Because I've been unable to figure out why the backups are completely lost in my case

It is likely not related. In your issue it is an etcd backup, not the backup from rancher-backup-operator(CRD basedb backup)

Regardless, I think we need to add a new api field in restore to ignore failure. If there are corrupted backup configuration being applied, the controller will try to restore the backup file in a loop, causing rancher pod to be scaled up and down. If the restore never succeed, rancher will become unable to use.

Is this related to #34768?
I've tried to migrate rancher to a new cluster on new servers and now I can't controll my custom rancher managed clusters.

can be validated in rancher-backup 1.2.0-rc6

authors: MSandro StrongMonkey abhi1693 jiaqiluo smangelkramer snasovich


text:
When a cluster member is deleted from the cluster errors like RoleBinding.rbac.authorization.k8s.io is invalid: roleRef: scroll through in the rancher pod logs

Information about the Cluster
Rancher Server Setup

Rancher version: v2.6.3-rc6
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, v1.21.7, 1.3.3-rc6

Proxy/Cert Details: Selfsigned

Information about the Cluster

Kubernetes version: v1.21.7
Cluster Type (Local/Downstream): Downstream node driver 3 worker, 1 etcd, 1 cp RKE1

Describe the bug
Following error logs scroll through continuously in the rancher pods when a cluster member is removed from a cluster
2021/12/16 21:01:09 [ERROR] error syncing 'c-9xgmk/crtb-nkfsr': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-nkfsr-4fbnnnodir rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-nkfsr: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-nkfsr-4fbnnnodir" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-member"}: cannot change roleRef, requeuing

To Reproduce

Create a cluster node driver rke1 RHEL OS
Delete the cluster member from the cluster via v3 API

Result
See the following error logs scroll through continously in the rancher logs:
2021/12/16 20:20:52 [ERROR] error syncing 'c-9xgmk/crtb-db24q': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-db24q-cbdbzqm5xv rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-db24q: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-db24q-cbdbzqm5xv" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:21:09 [ERROR] error syncing 'c-9xgmk/crtb-nkfsr': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-nkfsr-4fbnnnodir rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-nkfsr: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-nkfsr-4fbnnnodir" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-member"}: cannot change roleRef, requeuing
2021/12/16 20:22:03 [ERROR] error syncing 'c-ttk4t/crtb-fswcd': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-fswcd-ctpx3zhqov rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-fswcd: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-fswcd-ctpx3zhqov" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:22:28 [ERROR] error syncing 'c-ttk4t/crtb-qfdf7': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-qfdf7-ybge7twrfl rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-qfdf7: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-qfdf7-ybge7twrfl" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-member"}: cannot change roleRef, requeuing
2021/12/16 20:22:52 [ERROR] error syncing 'c-9xgmk/crtb-db24q': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-db24q-cbdbzqm5xv rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-db24q: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-db24q-cbdbzqm5xv" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:23:09 [ERROR] error syncing 'c-9xgmk/crtb-nkfsr': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-nkfsr-4fbnnnodir rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-nkfsr: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-nkfsr-4fbnnnodir" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-member"}: cannot change roleRef, requeuing
2021/12/16 20:24:03 [ERROR] error syncing 'c-ttk4t/crtb-fswcd': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-fswcd-ctpx3zhqov rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-fswcd: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-fswcd-ctpx3zhqov" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:24:28 [ERROR] error syncing 'c-ttk4t/crtb-qfdf7': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-qfdf7-ybge7twrfl rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-qfdf7: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-qfdf7-ybge7twrfl" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-member"}: cannot change roleRef, requeuing
2021/12/16 20:24:52 [ERROR] error syncing 'c-9xgmk/crtb-db24q': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-db24q-cbdbzqm5xv rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-db24q: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-db24q-cbdbzqm5xv" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:25:09 [ERROR] error syncing 'c-9xgmk/crtb-nkfsr': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-9xgmk-crtb-nkfsr-4fbnnnodir rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-9xgmk/crtb-nkfsr: RoleBinding.rbac.authorization.k8s.io "crt-c-9xgmk-crtb-nkfsr-4fbnnnodir" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-9xgmk-cluster-member"}: cannot change roleRef, requeuing
2021/12/16 20:26:03 [ERROR] error syncing 'c-ttk4t/crtb-fswcd': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-fswcd-ctpx3zhqov rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-fswcd: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-fswcd-ctpx3zhqov" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-owner"}: cannot change roleRef, requeuing
2021/12/16 20:26:28 [ERROR] error syncing 'c-ttk4t/crtb-qfdf7': handler auth-prov-v2-crtb: failed to update fleet-default/crt-c-ttk4t-crtb-qfdf7-ybge7twrfl rbac.authorization.k8s.io/v1, Kind=RoleBinding for auth-prov-v2-crtb-rolebinding c-ttk4t/crtb-qfdf7: RoleBinding.rbac.authorization.k8s.io "crt-c-ttk4t-crtb-qfdf7-ybge7twrfl" is invalid: roleRef: Invalid value: rbac.RoleRef{APIGroup:"rbac.authorization.k8s.io", Kind:"Role", Name:"crt-c-ttk4t-cluster-member"}: cannot change roleRef,

Expected Result
Expected no errors as mentioned above be seen in the rancher pods.

This issue is a dupe of https://github.com/rancher/rancher/issues/35824
See the comments on there for additional information


text:
Aurora catalog scheduler is in unhealthy state after power off and power on

Rancher Version: Master
OS and where are the hosts located? (cloud, bare metal, etc): Ubuntu, Cloud
Environment Type: (Cattle/Kubernetes/Swarm/Mesos): Mesos
Steps to Reproduce:

Create a mesos environment and add one host
Add elastic search, aurora catalogs. The catalog comes up correctly and are healthy.
Power off the host and power on
After the host is up again, the aurora scheduler container is unhealthy.

Aurora scheduler container logs:
5/18/2016 3:38:31 PM++ echo aurora
5/18/2016 3:38:31 PM+ export AURORA_CLUSTER_NAME=aurora
5/18/2016 3:38:31 PM+ AURORA_CLUSTER_NAME=aurora
5/18/2016 3:38:31 PM++ metadata self/host/agent_ip
5/18/2016 3:38:31 PM+++ curl -s rancher-metadata.rancher.internal/2015-12-19/self/host/agent_ip
5/18/2016 3:38:31 PM++ echo 104.236.194.206
5/18/2016 3:38:31 PM+ export AURORA_HOSTNAME=104.236.194.206
5/18/2016 3:38:31 PM+ AURORA_HOSTNAME=104.236.194.206
5/18/2016 3:38:31 PM+ export AURORA_HTTP_PORT=8080
5/18/2016 3:38:31 PM+ AURORA_HTTP_PORT=8080
5/18/2016 3:38:31 PM+ export AURORA_NATIVE_LOG_QUORUM_SIZE=1
5/18/2016 3:38:31 PM+ AURORA_NATIVE_LOG_QUORUM_SIZE=1
5/18/2016 3:38:31 PM++ zk_hosts
5/18/2016 3:38:31 PM++ ZK_STRING=
5/18/2016 3:38:31 PM+++ zk_service containers
5/18/2016 3:38:31 PM+++ IFS=/
5/18/2016 3:38:31 PM+++ read -ra ZK
5/18/2016 3:38:31 PM++++ metadata stacks/Mesos/services/zookeeper/containers
5/18/2016 3:38:31 PM+++++ curl -s rancher-metadata.rancher.internal/2015-12-19/stacks/Mesos/services/zookeeper/containers
5/18/2016 3:38:32 PM++++ echo 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM+++ echo 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM++ for container in '$(zk_service containers)'
5/18/2016 3:38:32 PM+++ zk_container_primary_ip 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM+++ IFS==
5/18/2016 3:38:32 PM+++ read -ra c
5/18/2016 3:38:32 PM++++ zk_service containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM++++ IFS=/
5/18/2016 3:38:32 PM++++ read -ra ZK
5/18/2016 3:38:32 PM+++++ metadata stacks/Mesos/services/zookeeper/containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM++++++ curl -s rancher-metadata.rancher.internal/2015-12-19/stacks/Mesos/services/zookeeper/containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM+++++ echo 10.42.36.179
5/18/2016 3:38:32 PM++++ echo 10.42.36.179
5/18/2016 3:38:32 PM+++ echo 10.42.36.179
5/18/2016 3:38:32 PM++ ip=10.42.36.179
5/18/2016 3:38:32 PM++ '[' '' == '' ']'
5/18/2016 3:38:32 PM++ ZK_STRING=10.42.36.179:2181
5/18/2016 3:38:32 PM++ echo 10.42.36.179:2181
5/18/2016 3:38:32 PM+ export AURORA_ZK_ENDPOINTS=10.42.36.179:2181
5/18/2016 3:38:32 PM+ AURORA_ZK_ENDPOINTS=10.42.36.179:2181
5/18/2016 3:38:32 PM++ zk_string
5/18/2016 3:38:32 PM+++ zk_hosts
5/18/2016 3:38:32 PM+++ ZK_STRING=
5/18/2016 3:38:32 PM++++ zk_service containers
5/18/2016 3:38:32 PM++++ IFS=/
5/18/2016 3:38:32 PM++++ read -ra ZK
5/18/2016 3:38:32 PM+++++ metadata stacks/Mesos/services/zookeeper/containers
5/18/2016 3:38:32 PM++++++ curl -s rancher-metadata.rancher.internal/2015-12-19/stacks/Mesos/services/zookeeper/containers
5/18/2016 3:38:32 PM+++++ echo 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM++++ echo 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM+++ for container in '$(zk_service containers)'
5/18/2016 3:38:32 PM++++ zk_container_primary_ip 0=Mesos_zookeeper_1
5/18/2016 3:38:32 PM++++ IFS==
5/18/2016 3:38:32 PM++++ read -ra c
5/18/2016 3:38:32 PM+++++ zk_service containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM+++++ IFS=/
5/18/2016 3:38:32 PM+++++ read -ra ZK
5/18/2016 3:38:32 PM++++++ metadata stacks/Mesos/services/zookeeper/containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM+++++++ curl -s rancher-metadata.rancher.internal/2015-12-19/stacks/Mesos/services/zookeeper/containers/Mesos_zookeeper_1/primary_ip
5/18/2016 3:38:32 PM++++++ echo 10.42.36.179
5/18/2016 3:38:32 PM+++++ echo 10.42.36.179
5/18/2016 3:38:32 PM++++ echo 10.42.36.179
5/18/2016 3:38:32 PM+++ ip=10.42.36.179
5/18/2016 3:38:32 PM+++ '[' '' == '' ']'
5/18/2016 3:38:32 PM+++ ZK_STRING=10.42.36.179:2181
5/18/2016 3:38:32 PM+++ echo 10.42.36.179:2181
5/18/2016 3:38:32 PM+++ mesos_stack
5/18/2016 3:38:32 PM+++ IFS=/
5/18/2016 3:38:32 PM+++ read -ra X
5/18/2016 3:38:32 PM+++ echo Mesos
5/18/2016 3:38:32 PM++ echo zk://10.42.36.179:2181/Mesos
5/18/2016 3:38:32 PM+ export AURORA_MESOS_MASTER_ADDRESS=zk://10.42.36.179:2181/Mesos
5/18/2016 3:38:32 PM+ AURORA_MESOS_MASTER_ADDRESS=zk://10.42.36.179:2181/Mesos
5/18/2016 3:38:32 PM+ export AURORA_SERVERSET_PATH=/aurora/scheduler
5/18/2016 3:38:32 PM+ AURORA_SERVERSET_PATH=/aurora/scheduler
5/18/2016 3:38:32 PM+ export AURORA_NATIVE_LOG_ZK_GROUP_PATH=/aurora/replicated-log
5/18/2016 3:38:32 PM+ AURORA_NATIVE_LOG_ZK_GROUP_PATH=/aurora/replicated-log
5/18/2016 3:38:32 PM+ export AURORA_NATIVE_LOG_FILE_PATH=/var/db/aurora
5/18/2016 3:38:32 PM+ AURORA_NATIVE_LOG_FILE_PATH=/var/db/aurora
5/18/2016 3:38:32 PM+ export AURORA_BACKUP_DIR=/var/lib/aurora/backups
5/18/2016 3:38:32 PM+ AURORA_BACKUP_DIR=/var/lib/aurora/backups
5/18/2016 3:38:32 PM+ export AURORA_THERMOS_EXECUTOR_PATH=/aurora/dist/thermos_executor.pex
5/18/2016 3:38:32 PM+ AURORA_THERMOS_EXECUTOR_PATH=/aurora/dist/thermos_executor.pex
5/18/2016 3:38:32 PM+ export AURORA_ALLOWED_CONTAINER_TYPES=MESOS,DOCKER
5/18/2016 3:38:32 PM+ AURORA_ALLOWED_CONTAINER_TYPES=MESOS,DOCKER
5/18/2016 3:38:32 PM+ export AURORA_GLOBAL_CONTAINER_MOUNTS=/opt:/opt:rw
5/18/2016 3:38:32 PM+ AURORA_GLOBAL_CONTAINER_MOUNTS=/opt:/opt:rw
5/18/2016 3:38:32 PM+ export AURORA_USE_BETA_DB_TASK_STORE=true
5/18/2016 3:38:32 PM+ AURORA_USE_BETA_DB_TASK_STORE=true
5/18/2016 3:38:32 PM+ export AURORA_ENABLE_H2_CONSOLE=true
5/18/2016 3:38:32 PM+ AURORA_ENABLE_H2_CONSOLE=true
5/18/2016 3:38:32 PM+ export AURORA_RECEIVE_REVOCABLE_RESOURCES=true
5/18/2016 3:38:32 PM+ AURORA_RECEIVE_REVOCABLE_RESOURCES=true
5/18/2016 3:38:32 PM+ mesos-log initialize --path=/var/db/aurora
5/18/2016 3:38:32 PMI0518 22:38:32.533704    45 leveldb.cpp:174] Opened db in 11.959846ms
5/18/2016 3:38:32 PMI0518 22:38:32.535693    45 leveldb.cpp:181] Compacted db in 1.849577ms
5/18/2016 3:38:32 PMI0518 22:38:32.535769    45 leveldb.cpp:196] Created db iterator in 20379ns
5/18/2016 3:38:32 PMI0518 22:38:32.536159    45 leveldb.cpp:202] Seeked to beginning of db in 359259ns
5/18/2016 3:38:32 PMI0518 22:38:32.536388    45 leveldb.cpp:271] Iterated through 5 keys in the db in 181825ns
5/18/2016 3:38:32 PMI0518 22:38:32.536465    45 replica.cpp:779] Replica recovered with log positions 0 -> 3 with 0 holes and 0 unlearned
5/18/2016 3:38:32 PMThe log is not empty

Aurora was removed from the catalog; it's offer system doesn't play nicely with other frameworks.

authors: LLParse soumyalj


text:
Virtual Machine missing from menu

Rancher Version: master 11/11
Steps to Reproduce:

Go to infrastructure menu

Results: Virtual machine is missing (also missing from services)
Expected:  Should be there.

Not supported in 1.2.0 backend...

Version - Removed VMs and when we add them back in there will be a full test pass.  So don't need this bug anymore.


text:
Update docker-machine for new AWS regions

ca-central-1
eu-west-2
https://github.com/rancher/machine-package/blob/master/scripts/package + UI

Canada central and EU west 2 does not work and not in machine.  moving it out of 1.3

https://github.com/rancher/machine-package/pull/19

eu-west-2 is merged now.  https://github.com/rancher/machine-package/pull/19

Version - master 3/2
Verified fixed/added