Add possible disable created service and propose new approach about customize ignore_changes

what

Add possible disable created service

why
Sometimes there is a need to add ignore_changes to sites. The current approach is to copy the entire block. I propose to output the necessary variables to the output, and then add the appropriate block that will create the service with your code.
references
Don't create issue :)

Adding @nitrocode as I seem him as the ECS expert 😄

I'm not sure if I completely understand this PR.
It seems like there is an addition of 2 things.

disable the module
output all the parameters for the ecs service

disable the module
The ability to disable the service can be done using var.enabled
module "ecs_alb_service_task" {
  source = "cloudposse/ecs-alb-service-task/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  enabled = false

  # etc
}

The other way to do this in more recent versions of terraform is using count
module "ecs_alb_service_task" {
  source = "cloudposse/ecs-alb-service-task/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  count = 0

  # etc
}

output all the parameters for the ecs service
Not sure how this is valueable. We already copy and paste the input arguments for the ecs service 4 times and this new output will be adding a 5th...
I'm unsure what problem this is trying to solve.

I'm not sure if I completely understand this PR.
It seems like there is an addition of 2 things.

disable the module
output all the parameters for the ecs service

disable the module
The ability to disable the service can be done using var.enabled
module "ecs_alb_service_task" {
  source = "cloudposse/ecs-alb-service-task/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  enabled = false

  # etc
}

The other way to do this in more recent versions of terraform is using count
module "ecs_alb_service_task" {
  source = "cloudposse/ecs-alb-service-task/aws"
  # Cloud Posse recommends pinning every module to a specific version
  # version = "x.x.x"

  count = 0

  # etc
}

output all the parameters for the ecs service
Not sure how this is valueable. We already copy and paste the input arguments for the ecs service 4 times and this new output will be adding a 5th...
I'm unsure what problem this is trying to solve.

Regarding the first one, I would like to add the ability to disable only aws_ecs_service. Currently, this is not possible.
Regarding the second thing: I want to add the possibility that everyone in their scope can configure lifecycle -> ignore_changes. Currently, the entire block is copied to ignore one parameter, and I assume there will be many more use cases.

Oh I see. You want to use all the business logic within the module but none of the ecs services itself because you'd like to add your own custom lifecycle ignore rules. So you output all the business logic, create nothing, and input that logic into your own custom aws_ecs_service resource.
In your PR, most of the outputted information you propose are already module inputs... Instead of outputting all of the information, couldn't you simply just disable the aws_ecs_service creation with a new flag and create your own aws_ecs_service using the module outputs that already exist ?
If you don't create the ecs service, you're basically just creating the iam role and the task definition. You might as well create a custom module.

Oh I see. You want to use all the business logic within the module but none of the ecs services itself because you'd like to add your own custom lifecycle ignore rules. So you output all the business logic, create nothing, and input that logic into your own custom aws_ecs_service resource.
In your PR, most of the outputted information you propose are already module inputs... Instead of outputting all of the information, couldn't you simply just disable the aws_ecs_service creation with a new flag and create your own aws_ecs_service using the module outputs that already exist ?
If you don't create the ecs service, you're basically just creating the iam role and the task definition. You might as well create a custom module.

That's exactly what I meant. However, I wanted all the values to be in one variable. Additionally, some things are not derived:

aws_ecs_service name
task_definition - it consists of several variables
launch_type, platform_version, network_configuration and scheduling_strategy depend on the conditions

If it was a problem to derive this variable, I would like to add only the option to disable the creation of the ecs website.

You could do the following to keep it DRY

Create a local that contains all of the ecs task def inputs
Update the single output to use the local
Reuse the local in each ecs task definition input

We have seen issues in the past with outputting too much information as it can be blocked if passing in sensitive information thus failing the instantiation of the module... so instead of outputting everything in a single output, it would be better to output only what you need (as you described above).
By the way, what is the additional lifecycle hook that you're trying to add?

By the way, what is the additional lifecycle hook that you're trying to add?

I created Blue/Green deploy using terraform and must ignore changes for task_definition and network_configuration.

You could do the following to keep it DRY

Create a local that contains all of the ecs task def inputs
Update the single output to use the local
Reuse the local in each ecs task definition input

create local variable ecs_service_attrs
update output
updated the attributes in 4 aws_ecs_service blocks

I am skeptical of the premise of this PR. We do not, in general, want to be creating modules that do nothing but generate outputs, but you may have a valid exception here. At the moment I do not have time to give it the thought it deserves.
Nevertheless, I am marking this as "do not merge" as we are in a code freeze on this and many other modules until we release a final version of terraform-aws-security-group and associated standards and best practices.

I am skeptical of the premise of this PR. We do not, in general, want to be creating modules that do nothing but generate outputs, but you may have a valid exception here. At the moment I do not have time to give it the thought it deserves.

I do not agree with you. This module, after disabled aws_ecs_service, does the following:

aws_ecs_task_definition
"aws_iam_role" "ecs_task"
"aws_iam_role_policy_attachment" "ecs_task"
"aws_iam_role" "ecs_service"
"aws_iam_role_policy" "ecs_service"
"aws_iam_role_policy" "ecs_ssm_exec"
"aws_iam_role" "ecs_exec"
"aws_iam_role_policy" "ecs_exec"
module "security_group"

I disabled only resource "aws_ecs_service" and add output

@Nuru Do you know when it will be possible to continue this MR?

@Nuru as a follow up to my last comment. Now I'm in need of this 😄
There are times when you want to create task/exec roles, task definition but without the aws_ecs_service. For example, when implementing a task that's run once i.e. runs using a aws ecs run-task command which does not require an aws_ecs_service but does require the other mentioned resources.
As an additional benefit of this PR, the output that creates the aws_ecs_service can then be used to construct your own service with your own lifecycle ignore rules without having to create every permutation as a separate resource.
I'm now a proponent of this PR.

@nitrocode https://github.com/cloudposse/terraform-aws-security-group/pull/17 are merged :tada:
What would I have to do now?

@ByJacob the next step is to create a separate pr to

use the new version of the security group module similar to the way it was used before the pre-releases

I don't believe we have an example for this yet (cc: @Nuru)
This will probably add/subtract module inputs for the sg module

create migration steps for the before pre-releases versions (tf migrations, changes in inputs, etc)

I believe this is already in the works so probably best to wait. If you're feeling ambitions, feel free to start and tag @Nuru to make sure it's setup the way it was intended.
Thanks again for your contribution. I assure you your contribution is helpful and will eventually be merged in.

@nitrocode I'm back to this module and now can finish this MR :D

@goruha Can you look for this PR ? :)

@ByJacob hi, can you update this pr so that all tests pass? otherwise this PR  will be closed due to staleness. thanks!

😿
not helping...
  variables.tf:499:1: warning: variable "service_created" is declared but not used ()
  time=2024-03-07T10:39:30.356Z level=INFO msg="reviewdog: failed to post a review comment: POST https://api.github.com/repos/cloudposse/terraform-aws-ecs-alb-service-task/pulls/119/reviews: 403 Resource not accessible by integration []"
  reviewdog: This GitHub Token doesn't have write permission of Review API [1],
  so reviewdog will report results via logging command [2] and create annotations similar to
  github-pr-check reporter as a fallback.

will do some internal poking...

😿 not helping...
  variables.tf:499:1: warning: variable "service_created" is declared but not used ()
  time=2024-03-07T10:39:30.356Z level=INFO msg="reviewdog: failed to post a review comment: POST https://api.github.com/repos/cloudposse/terraform-aws-ecs-alb-service-task/pulls/119/reviews: 403 Resource not accessible by integration []"
  reviewdog: This GitHub Token doesn't have write permission of Review API [1],
  so reviewdog will report results via logging command [2] and create annotations similar to
  github-pr-check reporter as a fallback.

will do some internal poking...

I check it in evening

Can you check this bit of the failing check?
variables.tf:499:1: warning: variable "service_created" is declared but not used ()


Election candidate select options improvements

Candidate names are pulled from the database into a select list, but they make no reference to the party.

the final candidate in the list is defaulting to selected.  This is often scrolled off the screen so you don't see it as so.  Very least it should be the top one if one has to be selected, so you can see it's wrong.

Needs to have a party option when the candidate is not listed in the case of:
(a) a leaflet for a local election candidate (we want those too)
(b) a leaflet by a non-party organization (eg Young Briton's Foundation)
(c) a leaflet from the central party that makes no reference to the local candidate.  These are being sent to avoid the campaign spending limits set per constituency and are booked as part of the national spending limit, as are billboard posters that just happen to be in the constituency as well.

'Not listed' is now the default.  I'll add party, and I think everything else can be addresses after the leaflet has been uploaded

Fixed in https://github.com/DemocracyClub/electionleaflets/commit/710b3f79fadc524e745b547d3691641083555354


Currently Fucked

Only downloads 1 of many tracks:
~/Music $ sof https://soundcloud.com/samgellaitry
Track already downloaded: låpsley - love is blind (sam gellaitry remix)
Fails totally:
~/Music $ sof https://soundcloud.com/samgellaitry/take-me-back-1
Traceback (most recent call last):
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundscrape/soundscrape.py", line 184, in process_soundcloud
resolved = client.get('/resolve', url=artist_url, limit=200)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundcloud/client.py", line 133, in _request
return wrapped_resource(make_request(method, url, kwargs))
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundcloud/request.py", line 148, in make_request
result.raise_for_status()
File "/Users/rjones/anaconda/lib/python3.6/site-packages/requests/models.py", line 935, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://api.soundcloud.com/tracks/337180749?client_id=175c043157ffae2c6d5fed16c3d95a4c
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/rjones/anaconda/bin/soundscrape", line 11, in
sys.exit(main())
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundscrape/soundscrape.py", line 119, in main
process_soundcloud(vargs)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundscrape/soundscrape.py", line 198, in process_soundcloud
hard_track_url = get_hard_track_url(item_id)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/soundscrape/soundscrape.py", line 518, in get_hard_track_url
json_response = response.json()
File "/Users/rjones/anaconda/lib/python3.6/site-packages/requests/models.py", line 892, in json
return complexjson.loads(self.text, **kwargs)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/simplejson/init.py", line 516, in loads
return _default_decoder.decode(s)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/simplejson/decoder.py", line 370, in decode
obj, end = self.raw_decode(s)
File "/Users/rjones/anaconda/lib/python3.6/site-packages/simplejson/decoder.py", line 400, in raw_decode
return self.scan_once(s, idx=_w(s, idx).end())
simplejson.scanner.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Same as #235. Region issue.


support checking entitlements for a query with runtime that contains more than one connection

What type of PR is this?

Improvement
What does this PR do / why is it needed ?

support checking entitlements for a query with runtime that contains more than one connection
Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

This PR was closed because it has been inactive for 35 days. Please re-open if this PR is still relevant.


Add proper README

This PR populates the README.md file which is displayed on the Grafana.com website for our plugin.

Waiting with merging until the plugin got approved to not interfere with the process.


Display differences have very different values

hello, this idea is really nice, but when I examined the values folder, the values of 390dp and 420dp caught my eye. Since my device is 411dp, it will use 390dp values. but this can really make a big difference. please review the widths I got from real devices

Hello,
This is an inherent issue. I had to balance continuous sizing and memory footprint. Adding more mapping files will improve the continuity of the sizes but will also make a negative impact on the consuming app size.

hello, I would like you to add values such as at least 320dp and 410dp. because 320dp phones are too many in the market and they will use values of 300dp.. that means a huge difference.
also why did you make sw (smallest width)? What is the difference between normal w (width)
And another thing I want to ask is how did you calculate these scalings? i also want to reference for my own device widths


I can't save the files

Issue Type: Bug
all files appear with * and I can't save them
would you please help me out with this problem
Great thanks
Andreea
Extension version: 2020.12.411183155
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.71GB (6.65GB free)

Process Argv
--crash-reporter-id a8a9447a-6e21-4021-9fb5-8da8e57891fd

Screen Reader
no

VM
0%

Thanks for reporting this issue.
Please could you me a bit more specific about what you mean by all files.
Are you using Python files or notebooks or other?
If they are standard files such as Python or the like, then please report this issue in the VS Code repo. If its an issue with Notebooks, then we'll look into that.
A screenshot would help here.

@andreeaman, can you try opting into the Custom Editor experiment? This will likely be the default for all users in the near future.
Add this to your user settings.
    "jupyter.experiments.optInto": [
        "CustomEditor"
    ],


Fix issue #65.

Add KeyLocker and unit test.

I'd like to rewrite this PR later on.

Something wrong with my code?

No no. I just wanna to rewrite it a bit to be more confident with such big change. Thank you for your contribution!


sensu-client fails to restart when a check is not finished yet and may hang forever in a broken state

When sensu-client is running local checks which might take longer (or never end, because of a bug) the sensu-client cannot restart:
Stopping the client fails:
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ /etc/init.d/sensu-client restart
 * Stopping sensu-client                                                                                * Timed out waiting for sensu-client to stop
                                                                                [fail]
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ ps auxw|grep sensu-cl
sensu     5099  0.2  0.0 1440020 27052 ?       Sl   13:31   0:06 /opt/sensu/embedded/bin/ruby /opt/sensu/bin/sensu-client -b -c /etc/sensu/config.json -d /etc/sensu/conf.d -e /etc/sensu/extensions -p /var/run/sensu/sensu-client.pid -l /var/log/sensu/sensu-client.log -L info

Killing the sensu-client only works with -9. When doing so, it cannot start properly again:
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ killall -9 sensu-client
sensu-client: no process found
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ /etc/init.d/sensu-client start
 * Starting sensu-client                           [fail]

The log file only says
/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:859:in `open_udp_socket': no datagram socket (RuntimeError)
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:859:in `open_datagram_socket'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.20.3/lib/sensu/client/process.rb:355:in `setup_sockets'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.20.3/lib/sensu/client/process.rb:413:in `start'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.20.3/lib/sensu/client/process.rb:19:in `block in run'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `call'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.20.3/lib/sensu/client/process.rb:18:in `run'
        from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.20.3/bin/sensu-client:10:in `<top (required)>'
        from /opt/sensu/bin/sensu-client:23:in `load'
        from /opt/sensu/bin/sensu-client:23:in `<main>'

When adding debug output, it says port already in use for 3030/UDP
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ netstat -ntulp|grep 3030
udp        0      0 <IP_ADDRESS>:3030          <IP_ADDRESS>:*                           602/sh
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ kill -9^C
root@xxx- /etc/sensu/conf.d/checks(controller-slave) $ ps auxw|grep 602
sensu      602  0.0  0.0   4448   748 ?         I consider that a bug, I would think it should a) abandon the childs or b) kill the childs c) give a proper log message

@stefanandres I would start by using "timeout": 60 in your check definitions to set a hard stop. We should revisit https://github.com/sensu/sensu-spawn to stop child processes of inheriting fds from the parent (sensu-client).

Okay, I have like a few hundres checks already in different repos and all (directly using sensu::check) - I'd need this as default to properly work, do you have a workaround for that?

This is especially game-breaking when you configure a new check via puppet with sensu::check, it restarts the sensu-client, it stops and then fails to start and you'll get keepalive erros on all your clients. :-(

I've now written a local workaround (deployed via our sensu puppet wrapper ...) which tries to kill all processes via the init script.
$ diff -u sensu-service  /tmp/sensu-service
--- sensu-service	2015-09-30 10:49:04.402828677 +0200
+++ /tmp/sensu-service	2015-09-30 10:49:36.598355487 +0200
@@ -237,25 +237,37 @@
 stop() {
     log_daemon_msg "Stopping $sensu_service"

-    set -x
     # try pgrep
     pid=$(pid_pgrep)

-    local pids
-    local count=0
-    # workaround https://github.com/sensu/sensu/issues/1052 for now
-    pids=$(netstat -apn|grep :3030|awk '{print $NF'}|sed 's/\/.*//')
-    while [[ $pids ]]; do
-      kill -9 $pids || true
-      pids=$(netstat -apn|grep :3030|awk '{print $NF'}|sed 's/\/.*//')
-      ((count >= 5)) && break
-      ((count++))
-    done
-
-    if ((count >= 5)); then
-      log_failure_msg "Timed out waiting for $sensu_service to stop"
-      echo_fail
-      return 2
+    if [ ! -n "$pid" ]; then
+        # try the pid file
+        if [ -f "$pidfile" ] ; then
+            read pid < "$pidfile"
+        fi
+    fi
+
+    if [ -n "$pid" ]; then
+        kill $pid
+
+        retval=$?
+
+        if [ $retval -eq 0 ]; then
+            wait_for_stop
+
+            retval=$?
+
+            if [ $retval -eq 0 ]; then
+                echo_ok
+            else
+                log_failure_msg "Timed out waiting for $sensu_service to stop"
+                echo_fail
+            fi
+        else
+            echo_fail
+        fi
+
+        return $retval
     else
       log_action_msg "$sensu_service is stopped"
       return 3
``

I suspect that Sensu is spawning child processes (for checks etc.) that are hanging onto fds, like the UDP socket. We need to have a good look at https://github.com/sensu/sensu-spawn/blob/master/lib/sensu/spawn.rb

We could potentially improve Sensu's stop signal handling to manage the child process groups.

pids=$(netstat -apn|grep :3030|awk '{print $NF'}|sed 's//.*//') can cause some problems with killing other processes. We recommend filtering a bit more.

Was this ever fixed?
Did adding an explicit timeout work as a viable workaround?

Sensu >= 0.27 using native service managers, or sysvinit with SERVICE_MAX_WAIT, and using Sensu check timeout were applicable is the solution.


Better std.algorithm.iteration.joiner error messages

Needs a rebase to pick up #8686.

another try

thank you for the reviews


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115605

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/115990

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120690


Fix Mongo Scrapbook intellisense

Fix for #28
In the Server class, id used to always be the connection string. However, when I added the Azure resources to the explorer, I refactored id and added a new connectionString field. Apparently I missed updating one of the fields. See here for the previous commit: https://github.com/Microsoft/vscode-cosmosdb/commit/3f5396480c5d2c06cc0ab2436ef8997dabdcceca#diff-566bee68995619b9ddea388ded5443caR162

@EricJizbaMSFT,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@chrisdias FYI - a fix for the issue described in today's sync-up


New image tile source

Duplicate of #15568, to make it work with the changes in main since the creation of that pull request.
Still missing:

[x] Stale key handling (make wmts-dimensions.html example work properly)

I think this is in good shape now. Along with the changes comes at least one improvement: tile transitions now also work on layers with an opacity set.
@tschaub, since this is based on #15568, do you want to review my additional changes here? Your changes from #15568, which are fully included here, look good to me.

Thanks for all the work resurrecting this branch, dealing with all the conflicts, and making additional improvements, @ahocevar.  This was a huge effort.

Thanks for your hard work and the good collaboration on this, @tschaub!


Fix mouse cursor not receiving input events when still visible.

now that we have a clock available, let's load our children aggressively rather than waiting until they come alive.


How to auto create an existing contract?

I had started on ec2 server.
Every time I have a new contract. i will ssh into it and execute.
I want this automatically?
Thanks you.
graph init \
  --product subgraph-studio
  --from-contract <CONTRACT_ADDRESS> \
  [--network <ETHEREUM_NETWORK>] \
  [--abi <FILE>] \
  <SUBGRAPH_SLUG> [<DIRECTORY>]

Hi @tomhardyctl - I am not sure I understand the exact request, what is it you want to automate? The running of the graph init command?

not so sure what we are trying to automate here. The CLI is able to take ABI and generate now how it is consumed is on end user. Feel free to re-open with more details.


[Bug] search suggestions ignore -removals

Describe the bug
Ditto
How to Reproduce
Enter Phone light -selfie
Expected behavior
not get suggestions with selfie
Environment
- DDG App Version:5.216.2
- Device:all
- OS:android

@Noitarud We closed the issue as there is no further action from us.
I see the expectation was for the search suggestions to filter out the word "selfie" when searching for "phone light -selfies". This is a fair feedback, thank you!
Advanced search options provided by search engines like DuckDuckGo support such filters, but it's not commonly integrated into browser suggestion functionalities.

@anikiki are you trying to dodge the request by rephrasing what I said? it is more honest to close it as "won't fix"

@Noitarud It was not my intention to dismiss your request.
The issue was closed with a summary of the request and a short explanation on the current design and implementation scope of our suggestions functionality.
I added the "Won't fix" label. This has been acknowledged and will not be pursued further.


Crash: FileSystemException: Exists failed, path = '<...>\build\app\intermediates\flutter\debug/flutter_assets' (OS Error: Access is denied. , errno = 5)

As per following:
Crash report written to C:\Gustafson\flutter\generate_colors\flutter_01.log;
please let us know at https://github.com/flutter/flutter/issues.
Gradle task assembleDebug failed with exit code 1
Exited (sigterm)

Crash report:
flutter_01.log
Flutter crash report; please file at https://github.com/flutter/flutter/issues.

## command

flutter build bundle --suppress-analytics --target C:\Gustafson\flutter\generate_colors\lib\main.dart --target-platform android-arm64 --depfile C:\Gustafson\flutter\generate_colors\build\app\intermediates\flutter\debug/snapshot_blob.bin.d --asset-dir C:\Gustafson\flutter\generate_colors\build\app\intermediates\flutter\debug/flutter_assets --debug

## exception

FileSystemException: FileSystemException: Exists failed, path = 'C:\Gustafson\flutter\generate_colors\build\app\intermediates\flutter\debug/flutter_assets' (OS Error: Access is denied.
, errno = 5)

#0      _Directory.existsSync (dart:io/directory_impl.dart:101:7)
#1      _Directory.createSync (dart:io/directory_impl.dart:133:11)
#2      _LocalDirectory&LocalFileSystemEntity&ForwardingDirectory.createSync (package:file/src/forwarding/forwarding_directory.dart:22:16)
#3      writeBundle (package:flutter_tools/src/bundle.dart:195:13)
<asynchronous suspension>
#4      assemble (package:flutter_tools/src/bundle.dart:187:9)
<asynchronous suspension>
#5      build (package:flutter_tools/src/bundle.dart:113:9)
<asynchronous suspension>
#6      BuildBundleCommand.runCommand (package:flutter_tools/src/commands/build_bundle.dart:83:11)
<asynchronous suspension>
#7      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:372:18)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:306:33)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#10     _rootRun (dart:async/zone.dart:1124:13)
#11     _CustomZone.run (dart:async/zone.dart:1021:19)
#12     _runZoned (dart:async/zone.dart:1516:10)
#13     runZoned (dart:async/zone.dart:1463:12)
#14     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#15     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:297:20)
#16     CommandRunner.runCommand (package:args/command_runner.dart:194:27)
<asynchronous suspension>
#17     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:347:21)
<asynchronous suspension>
#18     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#19     _rootRun (dart:async/zone.dart:1124:13)
#20     _CustomZone.run (dart:async/zone.dart:1021:19)
#21     _runZoned (dart:async/zone.dart:1516:10)
#22     runZoned (dart:async/zone.dart:1463:12)
#23     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#24     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:303:19)
<asynchronous suspension>
#25     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109:29)
#26     new Future.sync (dart:async/future.dart:224:31)
#27     CommandRunner.run (package:args/command_runner.dart:109:11)
#28     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:211:18)
#29     run.<anonymous closure> (package:flutter_tools/runner.dart:59:20)
<asynchronous suspension>
#30     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#31     _rootRun (dart:async/zone.dart:1124:13)
#32     _CustomZone.run (dart:async/zone.dart:1021:19)
#33     _runZoned (dart:async/zone.dart:1516:10)
#34     runZoned (dart:async/zone.dart:1463:12)
#35     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#36     runInContext (package:flutter_tools/src/context_runner.dart:42:24)
<asynchronous suspension>
#37     run (package:flutter_tools/runner.dart:50:10)
#38     main (package:flutter_tools/executable.dart:52:9)
<asynchronous suspension>
#39     main (file:///C:/Downloads/flutter/flutter_windows_v0.5.1-beta/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#40     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#41     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

## flutter doctor

[✓] Flutter (Channel beta, v0.9.4, on Microsoft Windows [Version 6.1.7601], locale en-US)
    • Flutter version 0.9.4 at C:\Downloads\flutter\flutter_windows_v0.5.1-beta\flutter
    • Framework revision f37c235c32 (4 weeks ago), 2018-09-25 17:45:40 -0400
    • Engine revision 74625aed32
    • Dart version 2.1.0-dev.5.0.flutter-a2eb050044

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at C:\Users\gggustafson\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[✓] Android Studio (version 3.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[✓] VS Code, 64-bit edition (version 1.28.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.19.0

[✓] Connected devices (1 available)
    • SM G925V • 06157df60c7a8e20 • android-arm64 • Android 7.0 (API 24)

• No issues found!

This error may have been caused by a missing import file

FileSystemException: FileSystemException: Exists failed, path = 'C:\Gustafson\flutter\generate_colors\build\app\intermediates\flutter\debug/flutter_assets' (OS Error: Access is denied.
, errno = 5)

seems write permission error on path build\app\intermediates\flutter\debug/flutter_assets

@gggustafson  @hariprasadiit a few times I saw it confirmed that some antivirus tools locked some file inside this directory or some other task that kept a file open and prevented the directory to be deleted.
Try excluding the directory in Antivirus and if it doesn't help restart your computer.

Please add the output of flutter doctor -v.

The only reason that I reported this issue was because I was asked to do so.
I do not believe that your advice regarding an anti virus or restart is useful. The error was a file that could not be found. The error message should make that clear (it did not).
The output of flutter doctor -v is included in the crash report (flutter_01.log) included in the original message).
Regards,

flutter:new project in vscode
Oops; flutter has exited unexpectedly.

This may be fixed by https://github.com/flutter/flutter/pull/43760

Duplicate of https://github.com/flutter/flutter/issues/50880


Auto Refactoring - move local variable as function argument with default value [Python]

I'd like to suggest the following feature: when linting a local variable, constant or literal, VSCode could suggest when hitting ctrl+. (extract), to refactor as a function parameter, with default value as set in it.
Example:
local variable to argument

constant to argument

current behavior - for the example above, only extract method and extract variable are available:

Moving this issue to discussions as an enhancement request for comments and upvotes.


Provisioning not starting soon enough when done repeatedly

What steps did you take and what happened:

Provision and de-Provision a control plane node few times.

At some point, Provisioning does not start at all and the bmh states remains ready.
The waiting time passes 30 minutes. Normally, it should start within 10 minutes.
It is safe assume that the provisioning will not start at all.
What did you expect to happen:

Each time, the provision and de-provision should start and succeed.
The process should be stateless in that previous provisioning should not have an impact on the current one for as long as there are free available bmh.

Anything else you would like to add:

In order to fix the issue, one needs to run make clean && make
Once in a while, even that may not help. And, re-creating the metal3-dev-env machine is the only option
the logs for relevant controllers are added as comment

Environment:

Cluster-api version: v1alpha3
CAPBM version: v0.3.0
Minikube version: v1.8.2
metal3-dev-env
Kubernetes version: v1.17.3

/kind bug

capi-controller-manager-664c75c4df-lxczd.log
I0325 08:25:00.908046       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:25:00.909659       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:25:00.968667       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:25:00.969040       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:25:30.966094       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:25:30.967071       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:26:00.986737       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:26:00.987437       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:26:13.799765       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:26:13.800000       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:26:30.996818       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:26:30.997330       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:27:01.008122       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:27:01.008473       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:27:31.019744       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:27:31.020283       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:28:01.033265       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:28:01.033509       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:28:09.883675       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:28:09.883892       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:28:31.053705       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:28:31.054598       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:29:01.068057       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:29:01.068290       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:29:31.075527       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:29:31.075752       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:30:01.083024       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:30:01.083716       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:30:31.088593       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:30:31.088763       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:31:01.110806       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:31:01.111270       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:31:31.114522       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:31:31.114710       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:32:01.132329       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:32:01.133213       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:32:31.141069       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:32:31.141619       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:33:01.146628       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:33:01.147193       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:33:31.155430       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:33:31.155697       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:34:01.163277       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:34:01.163706       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
I0325 08:34:19.316447       1 machine_controller_noderef.go:53] controllers/Machine "msg"="Machine doesn't have a valid ProviderID yet" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"
E0325 08:34:19.316615       1 machine_controller.go:215] controllers/Machine "msg"="Reconciliation for Machine asked to requeue" "error"="Bootstrap provider for Machine "test1-controlplane-dlxrc" in namespace "metal3" is not ready, requeuing: requeue in 30s" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "namespace"="metal3"

capi-kubeadm-bootstrap-controller-manager-66597cb7f4-ghmqq.log
I0325 08:25:00.875004       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:25:00.875156       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61729"
I0325 08:25:00.939434       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:25:00.940294       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61729"
I0325 08:25:00.956331       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:25:00.956874       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61736"
I0325 08:25:30.879739       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:25:30.880052       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:25:57.940518       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:25:57.940733       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:26:00.893857       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:26:00.894438       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:26:30.898614       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:26:30.899446       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:27:00.904902       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:27:00.905045       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:27:30.907157       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:27:30.908903       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:28:00.913552       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:28:00.913653       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:28:13.477557       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:28:13.477672       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:28:30.915758       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:28:30.915823       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:29:00.917180       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:29:00.917335       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:29:30.918432       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:29:30.918673       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:29:37.715265       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:29:37.723335       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:30:00.920169       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:30:00.920221       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:30:30.923608       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:30:30.925478       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:31:00.931909       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:31:00.932211       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:31:30.935369       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:31:30.935707       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:32:00.937187       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:32:00.937233       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:32:30.941261       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:32:30.941382       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:33:00.943393       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:33:00.943444       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:33:30.944568       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:33:30.945902       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"
I0325 08:34:00.947475       1 control_plane_init_mutex.go:74] init-locker "msg"="Waiting on another machine to initialize" "cluster-name"="test1" "configmap-name"="test1-lock" "machine-name"="test1-controlplane-dlxrc" "namespace"="metal3" "init-machine"="test1-controlplane-rsfz4"
I0325 08:34:00.947730       1 kubeadmconfig_controller.go:286] controllers/KubeadmConfig "msg"="A control plane is already being initialized, requeing until control plane is ready" "kind"="Machine" "kubeadmconfig"={"Namespace":"metal3","Name":"test1-controlplane-hlvtj"} "name"="test1-controlplane-dlxrc" "version"="61737"

capi-kubeadm-control-plane-controller-manager-56d8897c7d-pp9kx.log

I0325 08:25:00.302863       1 controller.go:228] controllers/KubeadmControlPlane "msg"="Initializing control plane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3" "Desired"=1 "Existing"=0
E0325 08:25:02.255521       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:02.303562       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:02.305022       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:08.464251       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:08.481711       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:08.483173       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:14.607820       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:14.630162       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:14.631498       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:20.757361       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:20.757850       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:20.760414       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:33.047321       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:33.048895       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:33.050910       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:39.184642       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:39.185304       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:39.185590       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:45.327885       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:45.329105       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:45.330829       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:58.576836       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:25:58.578458       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:25:58.578915       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:04.719572       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:04.720500       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:26:04.721810       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:10.863508       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:10.864383       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:26:10.865001       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:17.008907       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:17.011540       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:26:17.012763       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:23.152544       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:23.152832       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:26:23.153122       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:29.296110       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:29.296786       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:26:33.394245       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:38.704325       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:26:38.706822       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:27:19.667413       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:27:25.807789       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:27:25.811648       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:28:18.581730       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:28:24.368457       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:28:24.373475       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:28:47.732624       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:28:53.871504       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:28:53.873747       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}
I0325 08:29:42.868067       1 controller.go:170] controllers/KubeadmControlPlane "msg"="Reconcile KubeadmControlPlane" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:29:46.738665       1 controller.go:146] controllers/KubeadmControlPlane "msg"="Failed to update KubeadmControlPlane Status" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host" "cluster"="test1" "kubeadmControlPlane"="test1-controlplane" "namespace"="metal3"
E0325 08:29:46.739343       1 controller.go:258] controller-runtime/controller "msg"="Reconciler error" "error"="failed to create remote cluster client: failed to create client for workload cluster metal3/test1: Get https://<IP_ADDRESS>:6443/api?timeout=30s: dial tcp <IP_ADDRESS>:6443: connect: no route to host"  "controller"="kubeadmcontrolplane" "request"={"Namespace":"metal3","Name":"test1-controlplane"}

capm3-controller-manager-5d6d8c75cd-pvgcz.log

I0325 08:25:00.337174       1 metal3machine_controller.go:98] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for Machine Controller to set OwnerRef on Metal3Machine" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:25:00.634846       1 metal3machine_controller.go:98] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for Machine Controller to set OwnerRef on Metal3Machine" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:25:00.899350       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:25:00.918845       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:25:00.936486       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:25:00.953735       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:26:09.730749       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:27:39.599755       1 metal3cluster_controller.go:108] Metal3Cluster-controller "msg"="Reconciling metal3Cluster" "cluster"="test1" "metal3-cluster"={"Namespace":"metal3","Name":"test1"}
I0325 08:27:39.613196       1 metal3cluster_controller.go:108] Metal3Cluster-controller "msg"="Reconciling metal3Cluster" "cluster"="test1" "metal3-cluster"={"Namespace":"metal3","Name":"test1"}
I0325 08:28:25.107541       1 metal3machine_manager.go:135] controllers/Metal3Machine/Metal3Machine-controller "msg"="Waiting for the Bootstrap provider controller to set bootstrap data" "cluster"="test1" "machine"="test1-controlplane-dlxrc" "metal3-cluster"="test1" "metal3-machine"={"Namespace":"metal3","Name":"test1-controlplane-flzzw"}
I0325 08:29:00.922826       1 metal3cluster_controller.go:108] Metal3Cluster-controller "msg"="Reconciling metal3Cluster" "cluster"="test1" "metal3-cluster"={"Namespace":"metal3","Name":"test1"}
I0325 08:29:00.937756       1 metal3cluster_controller.go:108] Metal3Cluster-controller "msg"="Reconciling metal3Cluster" "cluster"="test1" "metal3-cluster"={"Namespace":"metal3","Name":"test1"}

This is happening on master, or on the specified release ? how are you deploying ? because there is a bug that could cause this, but only with v1alpha4.

I am deploying as follows.
git clone https://github.com/metal3-io/metal3-dev-env.git
cd metal3-dev-env
export CONTAINER_RUNTIME=docker
export DEFAULT_HOSTS_MEMORY=4096
export IMAGE_OS=Ubuntu
export CAPI_VERSION=v1alpha3
export NUM_NODES=4
make

ok, then this is something that needs to be investigated.

How many control plane nodes do you have ? If one only, you cannot deprovision and reprovision it without completely deleting the cluster. Otherwise it will try to use "kubeadm join" when the cluster has been deprovisioned. you can do that only if you have at least three masters. Is this your case ? and if it is, has the initial provisioning fully completed ?

I have only one control plane node provisioned and three others in ready state.
This use case is a single master upgrade with extra node(s).
And, relevant to this issue is that fact that the work flow successful. as of 16.03.1020
If this is not a valid use case, then the task list needs to be revisited and use cases redefined again.

ok, then this is something that needs to be investigated.

I agree. It might better to split this issue into two, if current investigations do not yield fruit.

Why does it fail to create the new node successfully.
2 .Why is the original node affected/changed before the success of the new one.

@Xenwar Any updates on this? Do you plan to split this issue out?

@Xenwar Any updates on this? Do you plan to split this issue out?

Yes, I intend to split this issue into two. But, we have other issues blocking us from working on it.
Will do that as soon as possible

Any updates on this ?

Not yet. But, will update this issue by tomorrow.

ok, then this is something that needs to be investigated.

I agree. It might better to split this issue into two, if current investigations do not yield fruit.
1. Why does it fail to create the new node successfully.

2. Why is the original node affected/changed before the success of the new one.

For the second case, please refer to https://github.com/metal3-io/cluster-api-provider-metal3/issues/74

ok, then this is something that needs to be investigated.

I agree. It might better to split this issue into two, if current investigations do not yield fruit.
1. Why does it fail to create the new node successfully.

2. Why is the original node affected/changed before the success of the new one.

@maelk @stbenjam
I have created a new issue for second one. #74.
I am still able to reproduce the first one, but not consistently. I will take it as a side task to gather more evidence while working on other upgrade issues.

ok, then this is something that needs to be investigated.

I agree. It might better to split this issue into two, if current investigations do not yield fruit.
1. Why does it fail to create the new node successfully.

2. Why is the original node affected/changed before the success of the new one.

@maelk @stbenjam
I have created a new issue for second one. #74.
I am still able to reproduce the first one, but not consistently. I will take it as a side task to gather more evidence while working on other upgrade issues.

The first case is out of scope and not a valid use case. Closing this issue.


Image to PDF

Description of the new feature / enhancement
Image to PDF
Scenario when this would be used?
Image to PDF
Supporting information
No response

Can you provide more here. There isn’t much benefit since this would just be an image wrapped in a pdf container
you can actually do this in word right now too. Save as pdf.

/needinfo

But when you do this in WORD, you have to set the paper border for a better result to view, or the image will not be its actually size in PDF. So this feature will be "batch select images, then right-click to create a PDF, the sequence will be same as the file what user selected", and provide a shell menu in explorer.


Requesting for ontop-spatial plugin for protege

Dear sir,
We are working in R&D projects sponsored by Govt. of India. We would like congratulate for developing effective tools such as ontop-spatial. In the past we have experience with ontop it really helped us. Now we would like to use ontop-spatial in our project to execute semantic queries (GeoSPARQL) on Geo-spatial data.
Is there ontop-spatial plugin for protege like ontop? if yes, kindly provide the link for us.
Please help us to proceed further.
Thanks & Regards
Dr. Sunitha Abburu & Research Team

Dear @dras130. Thanks for your request.
@ConstantB It seems that the issue system is not enabled in your fork https://github.com/ConstantB/ontop-spatial. That's why the discussion happens here.
As far as I remember, there were some packing issues with the protege plugin. We can work together to fix it.  It is also my interest.
@dras130 Please note that we will not merge this pull request. The development of ontop-spatial has to be kept in its own repository/fork for technical reasons. More specifically, ontop-spatial currently relies on a customized version of sesame library v2 for parsing Geo-SPARQL queries. In the future, once we upgrade sesame to v4, where Geo-SPARQL queries are supported natively, we can work on merging the fork back to the main repository.
Btw, we are collecting use cases of ontop for writing proposals to keep the development of ontop. I would be very grateful if you can drop a few lines on
https://github.com/ontop/ontop/wiki/UseCases

Dear Sir,
Our use case is: Mapping 2D and 3D geometries stored in postgreSQL to any
domain ontology and execute GeoSPARQL using R2RML/ontop mappings.
Please provide any link or document that guide us to proceed further in
these lines.
We have generated R2RML mappings using GeoTriples. Kindly share the
procedure/java library/code to execute GeoSPARQL query on the spatial
database using R2RML mappings.
Thanks & Regards
Research Team.
On Fri, Apr 8, 2016 at 11:59 AM, Guohui Xiao<EMAIL_ADDRESS>wrote:

Dear @dras130 https://github.com/dras130. Thanks for your request.
@ConstantB https://github.com/ConstantB It seems that the issue system
is not enabled in your fork https://github.com/ConstantB/ontop-spatial.
That's why the discussion happens here.
As far as I remember, there were some packing issues with the protege
plugin. We can work together to fix it. It is also my interest.
@dras130 https://github.com/dras130 Please note that we will not merge
this pull request. The development of ontop-spatial has to be kept in its
own repository/fork for technical reasons. More specifically, ontop-spatial
currently relies on a customized version of sesame library v2 for parsing
Geo-SPARQL queries. In the future, once we upgrade sesame to v4, where
Geo-SPARQL queries are supported natively, we can work on merging the fork
back to the main repository.
Btw, we are collecting use cases of ontop for writing proposals to keep
the development of ontop. I would be very grateful if you can drop a few
lines on
https://github.com/ontop/ontop/wiki/UseCases
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/ontop/ontop/pull/110#issuecomment-207238227

Dear @dras130,
thank you for your request and your interest in our work. I apologize for the very late reply, I was very busy these days.
As @ghxiao mentioned, ontop-spatial cannot be used as a Protege plugin. I plan to do this in the near future.
I created a repository that contains an example (Database dump, mappings) and a pre-compiled instance of ontop-spatial: https://github.com/ConstantB/Ontop-spatial-example, as well as this wiki page that explains its use: https://github.com/ConstantB/Ontop-spatial-example/wiki.
I strongly recommend that you use it as a web application (just drop the .war files into a web server installation, e.g., the webapps folder of an apache tomcat installation and use it from the sesame workbench endpoint as the default version of ontop.
Supporting 3D geometries are not tested, as we have focused on 2D geometries so far, however, as it is the first use case that deals with 3D geometries I am very interested to help with it.
For any further guidance and/support, please contact me at const.di at gmail.com
Kind Regards,
Konstantina

@dras130 In addition to the above, for testing purposes it might also be convinient to import the source code of ontop-spatial into your IDE (eclipse, netbeans, etc.) as a maven project and then create a test class like this example here that demonstrates the use of ontop-spatial via the Sesame API:
https://github.com/ConstantB/ontop-spatial/blob/master/quest-sesame/src/test/java/inf/unibz/ontop/sesame/tests/general/SesameLGDTest.java
Kind Regards,
Konstantina

I justed reported the issue here: https://github.com/ConstantB/ontop-spatial/issues/1

The discussion will be moved to ConstantB#1

Sir,
Could you please provide SF and EH function syntax for GeoSPARQL.
Thanks & Regards
Research Team
On Thu, May 26, 2016 at 2:55 AM, Guohui Xiao<EMAIL_ADDRESS>wrote:

Closed #110 https://github.com/ontop/ontop/pull/110.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/ontop/ontop/pull/110#event-672400570

@dras130 Let's continue our discussion at ConstantB#1
PS: @ConstantB has informed me that she has achieved significant progress in protege plugin.


Add servlet to list add nodes addresses connected in the grid.

Since we can customize the grid-extras-port in nodes https://github.com/groupon/Selenium-Grid-Extras/pull/385, the grid-extras-port of a node can be configured to be different from the value '3000'.
This is an issue, if you intent to communicate with a node through the the selenium grid extras API.
I propose a simple servlet to list all the node addresses (with the grid-extras-port configured) connected to the hub so that we can retrieve this information in an easy way:

@dariosilva Sorry I haven't looked at this PR yet. I will attempt to look at by Monday morning at the latest. Thank you for putting it under the 2.x branch.

This is in 2.0.4 . Please let me know if all is good. I had to remove an unknown exception. @dariosilva

Hi @smccarthy
The servlet is working for version of the selenium server 3.8.1.
Thank You.


added missing dependencies to requirements.txt

Making a PR for fixing the requirements

seaborn is awesome

PR to wrong repo...


Fix sed dd_url

DD_URL often contains slashes so a pipe is more appropriate

Thanks for the contribution! Looks good to me, but we can't merge it right now since master is frozen for the upcoming release. Will get it merged after that :)


Added Blazor UI with shared Models, View Models and services from Froms App

Hi there,
Thanks for a fun challenge.
I've refactored as much code as possible into a .Net standard library with no dependency on forms. This allows me to share the bulk of the code between Xamarin Forms Targets(iOS, Android etc.) and Blazor with only views written differently.
I've run out of time to fully implement it so the UI is pretty darn ugly(and the mobile app is a bit broken) but the concept is sound and I've got blazor successfully using all three services.

Oh wait, I've got 24hours more that I thought. Let's fix some stuff.

Site is online at https://blazortravelmonkey.azurewebsites.net/
Azure Devops build and publish is public at https://dev.azure.com/lachlanwgordon/TravelMonkey/_build
I developed most of this live at twitch, you can watch here https://www.twitch.tv/videos/605607179
Screen shots
Home page is basically the same as the mobile app.

Translation page is a work in progress, I need some flags.

Add Photo page uses file upload and can be expanded to allow webcam.

Solution Structure
Solution has two extra projects. TravelMonkey.Core is mostly code removed from the Forms App. TravelMonkey.Blazor had the UI that sits on top of shared code.

Thanks for completing the challenge! Fill out this form so we can send you the swag! https://aka.ms/cog-svcs-swag


added new issue template

Added a create new issue template to match js and go repos

Looks great! Is there anyway I can test these so I can take a look at it in Github?


Breadcrumb doesn't respect files exclude setting

System:

VSCode Version: 1.26
OS Version: Mac OS El Capitan

Steps to Reproduce:

Make sure you fill the files.exclude setting.
Open up the File Explorer panel, you should see the excluded files are not visible.
Open up the breadcrumb's file picker, you would see the excluded file are visible.

Screen capture:

Does this issue occur when all extensions are disabled? Yes

/duplicate of #55449


DjangoTest: launch manage.py with python

This allows manage.py to have no 'x' flag

Looks good, thanks!