karths/binary_classification_train_main
0185
1Unnamed: 0,id,type,created_at,repo,repo_url,action,title,labels,body,index,text_combine,label,text,binary_label21130,4998415563.0,IssuesEvent,2016-12-09 19:47:07,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,replace: TypeError when run under Python 3,affects_2.2 bug_report waiting_on_maintainer,"##### ISSUE TYPE3 - Bug Report4 5##### COMPONENT NAME6 - files/replace7 8##### ANSIBLE VERSION9```10ansible 2.2.0.0 (detached HEAD cdec853e37) last updated 2016/12/01 10:23:30 (GMT +200)11 lib/ansible/modules/core: (detached HEAD fe9c56a003) last updated 2016/12/01 10:24:42 (GMT +200)12 lib/ansible/modules/extras: (detached HEAD f564e77a08) last updated 2016/12/01 10:24:42 (GMT +200)13 config file = 14 configured module search path = ['/Users/per/Projects/servers/submodules/ansible/library']15```16 17##### CONFIGURATION18 - ansible_python_interpreter=/usr/bin/python319 20##### OS / ENVIRONMENT21 - Local: MacOS22- Remote: Ubuntu 16.04, with Python 3.5.223 24##### SUMMARY25Replace fails with a TypeError when run under Python 326 27##### STEPS TO REPRODUCE28```29ansible *** -m replace \30 -a ""dest=/etc/lsb-release regexp=nomatchfound replace=nomatchfound""31```32 33##### EXPECTED RESULTS34No replacement (since regex doesn't match).35 36##### ACTUAL RESULTS37Command fails with error: `TypeError: cannot use a string pattern on a bytes-like object`38 39```40*** | FAILED! => {41 ""changed"": false, 42 ""failed"": true, 43 ""module_stderr"": ""Shared connection to *** closed.\r\n"", 44 ""module_stdout"": ""Traceback (most recent call last):\r\n File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 180, in <module>\r\n main()\r\n File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 153, in main\r\n result = re.subn(mre, params['replace'], contents, 0)\r\n File \""/usr/lib/python3.5/re.py\"", line 193, in subn\r\n return _compile(pattern, flags).subn(repl, string, count)\r\nTypeError: cannot use a string pattern on a bytes-like object\r\n"", 45 ""msg"": ""MODULE FAILURE""46}47```48 49Readable traceback (from above):50```51Traceback (most recent call last):52 File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 180, in <module>53 main()54 File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 153, in main55 result = re.subn(mre, params['replace'], contents, 0)56 File \""/usr/lib/python3.5/re.py\"", line 193, in subn57 return _compile(pattern, flags).subn(repl, string, count)58TypeError: cannot use a string pattern on a bytes-like object59```60",True,"replace: TypeError when run under Python 3 - ##### ISSUE TYPE61 - Bug Report62 63##### COMPONENT NAME64 - files/replace65 66##### ANSIBLE VERSION67```68ansible 2.2.0.0 (detached HEAD cdec853e37) last updated 2016/12/01 10:23:30 (GMT +200)69 lib/ansible/modules/core: (detached HEAD fe9c56a003) last updated 2016/12/01 10:24:42 (GMT +200)70 lib/ansible/modules/extras: (detached HEAD f564e77a08) last updated 2016/12/01 10:24:42 (GMT +200)71 config file = 72 configured module search path = ['/Users/per/Projects/servers/submodules/ansible/library']73```74 75##### CONFIGURATION76 - ansible_python_interpreter=/usr/bin/python377 78##### OS / ENVIRONMENT79 - Local: MacOS80- Remote: Ubuntu 16.04, with Python 3.5.281 82##### SUMMARY83Replace fails with a TypeError when run under Python 384 85##### STEPS TO REPRODUCE86```87ansible *** -m replace \88 -a ""dest=/etc/lsb-release regexp=nomatchfound replace=nomatchfound""89```90 91##### EXPECTED RESULTS92No replacement (since regex doesn't match).93 94##### ACTUAL RESULTS95Command fails with error: `TypeError: cannot use a string pattern on a bytes-like object`96 97```98*** | FAILED! => {99 ""changed"": false, 100 ""failed"": true, 101 ""module_stderr"": ""Shared connection to *** closed.\r\n"", 102 ""module_stdout"": ""Traceback (most recent call last):\r\n File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 180, in <module>\r\n main()\r\n File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 153, in main\r\n result = re.subn(mre, params['replace'], contents, 0)\r\n File \""/usr/lib/python3.5/re.py\"", line 193, in subn\r\n return _compile(pattern, flags).subn(repl, string, count)\r\nTypeError: cannot use a string pattern on a bytes-like object\r\n"", 103 ""msg"": ""MODULE FAILURE""104}105```106 107Readable traceback (from above):108```109Traceback (most recent call last):110 File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 180, in <module>111 main()112 File \""/tmp/ansible_1wjonocj/ansible_module_replace.py\"", line 153, in main113 result = re.subn(mre, params['replace'], contents, 0)114 File \""/usr/lib/python3.5/re.py\"", line 193, in subn115 return _compile(pattern, flags).subn(repl, string, count)116TypeError: cannot use a string pattern on a bytes-like object117```118",1,replace typeerror when run under python issue type bug report component name files replace ansible version ansible detached head last updated gmt lib ansible modules core detached head last updated gmt lib ansible modules extras detached head last updated gmt config file configured module search path configuration ansible python interpreter usr bin os environment local macos remote ubuntu with python summary replace fails with a typeerror when run under python steps to reproduce ansible m replace a dest etc lsb release regexp nomatchfound replace nomatchfound expected results no replacement since regex doesn t match actual results command fails with error typeerror cannot use a string pattern on a bytes like object failed changed false failed true module stderr shared connection to closed r n module stdout traceback most recent call last r n file tmp ansible ansible module replace py line in r n main r n file tmp ansible ansible module replace py line in main r n result re subn mre params contents r n file usr lib re py line in subn r n return compile pattern flags subn repl string count r ntypeerror cannot use a string pattern on a bytes like object r n msg module failure readable traceback from above traceback most recent call last file tmp ansible ansible module replace py line in main file tmp ansible ansible module replace py line in main result re subn mre params contents file usr lib re py line in subn return compile pattern flags subn repl string count typeerror cannot use a string pattern on a bytes like object ,1119486742,14013318071.0,IssuesEvent,2020-10-29 10:15:47,netdata/netdata,https://api.github.com/repos/netdata/netdata,closed,Netdata Cloud ECN href tag appears to be formatted incorrectly,area/web bug cloud priority/medium,"<!--120When creating a bug report please:121- Verify first that your issue is not already reported on GitHub.122- Test if the latest release and master branch are affected too.123-->124 125##### Bug report summary126<!-- Provide a clear and concise description of the bug you're experiencing. -->127When you navigate to a specific node in Netdata Cloud and scroll to ECN, the raw HTML is visible instead of a link.128129 130I inspected the webpage HTML and found that the <a> tag was using < and > instead of < and >.131132 133Upon changing the HTML with < and > in the <a> tag, I was able to view the link properly.134135136 137 138##### OS / Environment139<!--140Provide as much information about your environment (which operating system and distribution you're using, if Netdata is running in a container, etc.)141as possible to allow us reproduce this bug faster.142 143To get this information, execute the following commands based on your operating system:144- uname -a; grep -Hv ""^#"" /etc/*release # Linux145- uname -a; uname -K # BSD146- uname -a; sw_vers # macOS147 148Place the output from the command in the code section below. 149 -->150```151Linux redacted 4.18.0-193.19.1.el8_2.x86_64 #1 SMP Mon Sep 14 14:37:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux152/etc/centos-release:CentOS Linux release 8.2.2004 (Core) 153/etc/os-release:NAME=""CentOS Linux""154/etc/os-release:VERSION=""8 (Core)""155/etc/os-release:ID=""centos""156/etc/os-release:ID_LIKE=""rhel fedora""157/etc/os-release:VERSION_ID=""8""158/etc/os-release:PLATFORM_ID=""platform:el8""159/etc/os-release:PRETTY_NAME=""CentOS Linux 8 (Core)""160/etc/os-release:ANSI_COLOR=""0;31""161/etc/os-release:CPE_NAME=""cpe:/o:centos:centos:8""162/etc/os-release:HOME_URL=""https://www.centos.org/""163/etc/os-release:BUG_REPORT_URL=""https://bugs.centos.org/""164/etc/os-release:165/etc/os-release:CENTOS_MANTISBT_PROJECT=""CentOS-8""166/etc/os-release:CENTOS_MANTISBT_PROJECT_VERSION=""8""167/etc/os-release:REDHAT_SUPPORT_PRODUCT=""centos""168/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION=""8""169/etc/os-release:170/etc/redhat-release:CentOS Linux release 8.2.2004 (Core) 171/etc/system-release:CentOS Linux release 8.2.2004 (Core)172```173 174##### Netdata version175<!--176Provide output of `netdata -V`.177 178If Netdata is running, execute: $(ps aux | grep -E -o ""[a-zA-Z/]+netdata "") -V179 -->180netdata v1.26.0-43-nightly181##### Component Name182<!--183Let us know which component is affected by the bug. Our code is structured according to its component,184so the component name is the same as the top level directory of the repository.185For example, a bug in the dashboard would be under the web component.186-->187Netdata Cloud188##### Steps To Reproduce189<!--190Describe how you found this bug and how we can reproduce it, preferably with a minimal test-case scenario.191If you'd like to attach larger files, use gist.github.com and paste in links.192-->193 1941. Open Netdata Cloud in your browser1952. Navigate to one of your nodes1963. Scroll down to ECN1974. You will see raw HTML instead of a link to the Wikipedia article198 199##### Expected behavior200<!-- Provide a clear and concise description of what you expected to happen. -->201I expected a link to the article to show up instead of raw HTML. I was able to reproduce this on a few other nodes running different netdata versions in Netdata Cloud. This does not affect the netdata web interface at *:19999, only Netdata Cloud.",1.0,"Netdata Cloud ECN href tag appears to be formatted incorrectly - <!--202When creating a bug report please:203- Verify first that your issue is not already reported on GitHub.204- Test if the latest release and master branch are affected too.205-->206 207##### Bug report summary208<!-- Provide a clear and concise description of the bug you're experiencing. -->209When you navigate to a specific node in Netdata Cloud and scroll to ECN, the raw HTML is visible instead of a link.210211 212I inspected the webpage HTML and found that the <a> tag was using < and > instead of < and >.213214 215Upon changing the HTML with < and > in the <a> tag, I was able to view the link properly.216217218 219 220##### OS / Environment221<!--222Provide as much information about your environment (which operating system and distribution you're using, if Netdata is running in a container, etc.)223as possible to allow us reproduce this bug faster.224 225To get this information, execute the following commands based on your operating system:226- uname -a; grep -Hv ""^#"" /etc/*release # Linux227- uname -a; uname -K # BSD228- uname -a; sw_vers # macOS229 230Place the output from the command in the code section below. 231 -->232```233Linux redacted 4.18.0-193.19.1.el8_2.x86_64 #1 SMP Mon Sep 14 14:37:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux234/etc/centos-release:CentOS Linux release 8.2.2004 (Core) 235/etc/os-release:NAME=""CentOS Linux""236/etc/os-release:VERSION=""8 (Core)""237/etc/os-release:ID=""centos""238/etc/os-release:ID_LIKE=""rhel fedora""239/etc/os-release:VERSION_ID=""8""240/etc/os-release:PLATFORM_ID=""platform:el8""241/etc/os-release:PRETTY_NAME=""CentOS Linux 8 (Core)""242/etc/os-release:ANSI_COLOR=""0;31""243/etc/os-release:CPE_NAME=""cpe:/o:centos:centos:8""244/etc/os-release:HOME_URL=""https://www.centos.org/""245/etc/os-release:BUG_REPORT_URL=""https://bugs.centos.org/""246/etc/os-release:247/etc/os-release:CENTOS_MANTISBT_PROJECT=""CentOS-8""248/etc/os-release:CENTOS_MANTISBT_PROJECT_VERSION=""8""249/etc/os-release:REDHAT_SUPPORT_PRODUCT=""centos""250/etc/os-release:REDHAT_SUPPORT_PRODUCT_VERSION=""8""251/etc/os-release:252/etc/redhat-release:CentOS Linux release 8.2.2004 (Core) 253/etc/system-release:CentOS Linux release 8.2.2004 (Core)254```255 256##### Netdata version257<!--258Provide output of `netdata -V`.259 260If Netdata is running, execute: $(ps aux | grep -E -o ""[a-zA-Z/]+netdata "") -V261 -->262netdata v1.26.0-43-nightly263##### Component Name264<!--265Let us know which component is affected by the bug. Our code is structured according to its component,266so the component name is the same as the top level directory of the repository.267For example, a bug in the dashboard would be under the web component.268-->269Netdata Cloud270##### Steps To Reproduce271<!--272Describe how you found this bug and how we can reproduce it, preferably with a minimal test-case scenario.273If you'd like to attach larger files, use gist.github.com and paste in links.274-->275 2761. Open Netdata Cloud in your browser2772. Navigate to one of your nodes2783. Scroll down to ECN2794. You will see raw HTML instead of a link to the Wikipedia article280 281##### Expected behavior282<!-- Provide a clear and concise description of what you expected to happen. -->283I expected a link to the article to show up instead of raw HTML. I was able to reproduce this on a few other nodes running different netdata versions in Netdata Cloud. This does not affect the netdata web interface at *:19999, only Netdata Cloud.",0,netdata cloud ecn href tag appears to be formatted incorrectly when creating a bug report please verify first that your issue is not already reported on github test if the latest release and master branch are affected too bug report summary when you navigate to a specific node in netdata cloud and scroll to ecn the raw html is visible instead of a link i inspected the webpage html and found that the tag was using lt and gt instead of upon changing the html with in the tag i was able to view the link properly os environment provide as much information about your environment which operating system and distribution you re using if netdata is running in a container etc as possible to allow us reproduce this bug faster to get this information execute the following commands based on your operating system uname a grep hv etc release linux uname a uname k bsd uname a sw vers macos place the output from the command in the code section below linux redacted smp mon sep utc gnu linux etc centos release centos linux release core etc os release name centos linux etc os release version core etc os release id centos etc os release id like rhel fedora etc os release version id etc os release platform id platform etc os release pretty name centos linux core etc os release ansi color etc os release cpe name cpe o centos centos etc os release home url etc os release bug report url etc os release etc os release centos mantisbt project centos etc os release centos mantisbt project version etc os release redhat support product centos etc os release redhat support product version etc os release etc redhat release centos linux release core etc system release centos linux release core netdata version provide output of netdata v if netdata is running execute ps aux grep e o netdata v netdata nightly component name let us know which component is affected by the bug our code is structured according to its component so the component name is the same as the top level directory of the repository for example a bug in the dashboard would be under the web component netdata cloud steps to reproduce describe how you found this bug and how we can reproduce it preferably with a minimal test case scenario if you d like to attach larger files use gist github com and paste in links open netdata cloud in your browser navigate to one of your nodes scroll down to ecn you will see raw html instead of a link to the wikipedia article expected behavior i expected a link to the article to show up instead of raw html i was able to reproduce this on a few other nodes running different netdata versions in netdata cloud this does not affect the netdata web interface at only netdata cloud ,0284892,4553457459.0,IssuesEvent,2016-09-13 04:57:46,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,Bad value substitution in ini_file Module with percent placeholder values,affects_1.7 bug_report P3 waiting_on_maintainer,"##### Issue Type:285 286Bug287 288##### Component Name:289ini_file module290 291##### Ansible Version:292 2931.7.22941.8.2295 296##### Environment:297 298Mac OSX 10.10.1 Yosemite299 300##### Summary:301 302I need special values in an ini-file to configure my supervisor-daemon. For example a value looks like this:303process_name=%(program_name)s304 305##### Steps To Reproduce:306 307To reporduce this issue run following playbook twice.308 309```310---311- hosts: all312 tasks:313 - ini_file: dest=""/tmp/tmp.ini"" section=""program:update"" option=""process_name"" value=""%(program_name)s""314```315 316##### Expected Results:317 318After first run everything OK, after second run I get an error and nothing happens.319 320##### Actual Results:321 322```323ConfigParser.InterpolationMissingOptionError: Bad value substitution:324 section: [program:update]325 option : process_name326 key : program_name327 rawval : %(program_name)s328```",True,"Bad value substitution in ini_file Module with percent placeholder values - ##### Issue Type:329 330Bug331 332##### Component Name:333ini_file module334 335##### Ansible Version:336 3371.7.23381.8.2339 340##### Environment:341 342Mac OSX 10.10.1 Yosemite343 344##### Summary:345 346I need special values in an ini-file to configure my supervisor-daemon. For example a value looks like this:347process_name=%(program_name)s348 349##### Steps To Reproduce:350 351To reporduce this issue run following playbook twice.352 353```354---355- hosts: all356 tasks:357 - ini_file: dest=""/tmp/tmp.ini"" section=""program:update"" option=""process_name"" value=""%(program_name)s""358```359 360##### Expected Results:361 362After first run everything OK, after second run I get an error and nothing happens.363 364##### Actual Results:365 366```367ConfigParser.InterpolationMissingOptionError: Bad value substitution:368 section: [program:update]369 option : process_name370 key : program_name371 rawval : %(program_name)s372```",1,bad value substitution in ini file module with percent placeholder values issue type bug component name ini file module ansible version environment mac osx yosemite summary i need special values in an ini file to configure my supervisor daemon for example a value looks like this process name program name s steps to reproduce to reporduce this issue run following playbook twice hosts all tasks ini file dest tmp tmp ini section program update option process name value program name s expected results after first run everything ok after second run i get an error and nothing happens actual results configparser interpolationmissingoptionerror bad value substitution section option process name key program name rawval program name s ,1373259988,22583305056.0,IssuesEvent,2022-06-28 13:26:41,mozilla/addons-frontend,https://api.github.com/repos/mozilla/addons-frontend,closed,Follow-ups for test_installAddon migration to react-testing-library,component: testing qa: not needed priority: p3,"Follow-ups identified during https://github.com/mozilla/addons-frontend/pull/11612:374- Once all tests have been migrated, replace old `getFakeAddonManagerWrapper` implementation with `getFakeAddonManagerWrapperWithJest`, which we will then be able to remove.375- Refactor `setCurrentStatus` status to use a parameterize style of testing using `it.each()`:376 > I'm wondering if we could combine all these tests that set up a state and then check that `setInstallState` has been called with a particular `status`, using `it.each()`? It seems like the setup is close to identical, and then the assertion is also nearly the same, just that we are looking for a different `status`, so they seem like a good candidate for a set of parameterized tests.377 >378 > (...) the override for `getAddon` would be part of the parameterized data. You'd only have to include what gets returned by the Promise, I think, so the data would look like `{ isActive: true, isEnabled: false }`, for example. I can see how that might be a bit ugly, but I still think getting rid of all of this duplicate code would make sense. 379- Migrate tests still marked as `FIXME` that modify the add-on after it has been loaded. 380 > It's definitely not going to work by dispatching actions. You'll need to render a page and then either use `onLocationChanged` or dispatch a `loadAddon` (I generally use the former as it's more like what a user would do). The problem is that `addon` is a direct prop of `InstallButtonWrapper`, and we cannot set a direct prop of an already loaded component. We need to have the parent re-render the component with the new prop value, which is what happens when the test runs from a page. This can be tested from either the `Addon` page or the `AddonVersions` page, so these tests should live in the test suite for one of those381- Remove `test_installAddon.js` once all of the above is done.",1.0,"Follow-ups for test_installAddon migration to react-testing-library - Follow-ups identified during https://github.com/mozilla/addons-frontend/pull/11612:382- Once all tests have been migrated, replace old `getFakeAddonManagerWrapper` implementation with `getFakeAddonManagerWrapperWithJest`, which we will then be able to remove.383- Refactor `setCurrentStatus` status to use a parameterize style of testing using `it.each()`:384 > I'm wondering if we could combine all these tests that set up a state and then check that `setInstallState` has been called with a particular `status`, using `it.each()`? It seems like the setup is close to identical, and then the assertion is also nearly the same, just that we are looking for a different `status`, so they seem like a good candidate for a set of parameterized tests.385 >386 > (...) the override for `getAddon` would be part of the parameterized data. You'd only have to include what gets returned by the Promise, I think, so the data would look like `{ isActive: true, isEnabled: false }`, for example. I can see how that might be a bit ugly, but I still think getting rid of all of this duplicate code would make sense. 387- Migrate tests still marked as `FIXME` that modify the add-on after it has been loaded. 388 > It's definitely not going to work by dispatching actions. You'll need to render a page and then either use `onLocationChanged` or dispatch a `loadAddon` (I generally use the former as it's more like what a user would do). The problem is that `addon` is a direct prop of `InstallButtonWrapper`, and we cannot set a direct prop of an already loaded component. We need to have the parent re-render the component with the new prop value, which is what happens when the test runs from a page. This can be tested from either the `Addon` page or the `AddonVersions` page, so these tests should live in the test suite for one of those389- Remove `test_installAddon.js` once all of the above is done.",0,follow ups for test installaddon migration to react testing library follow ups identified during once all tests have been migrated replace old getfakeaddonmanagerwrapper implementation with getfakeaddonmanagerwrapperwithjest which we will then be able to remove refactor setcurrentstatus status to use a parameterize style of testing using it each i m wondering if we could combine all these tests that set up a state and then check that setinstallstate has been called with a particular status using it each it seems like the setup is close to identical and then the assertion is also nearly the same just that we are looking for a different status so they seem like a good candidate for a set of parameterized tests the override for getaddon would be part of the parameterized data you d only have to include what gets returned by the promise i think so the data would look like isactive true isenabled false for example i can see how that might be a bit ugly but i still think getting rid of all of this duplicate code would make sense migrate tests still marked as fixme that modify the add on after it has been loaded it s definitely not going to work by dispatching actions you ll need to render a page and then either use onlocationchanged or dispatch a loadaddon i generally use the former as it s more like what a user would do the problem is that addon is a direct prop of installbuttonwrapper and we cannot set a direct prop of an already loaded component we need to have the parent re render the component with the new prop value which is what happens when the test runs from a page this can be tested from either the addon page or the addonversions page so these tests should live in the test suite for one of those remove test installaddon js once all of the above is done ,039021928,11660539337.0,IssuesEvent,2020-03-03 03:41:24,cityofaustin/atd-geospatial,https://api.github.com/repos/cityofaustin/atd-geospatial,closed,Data-Informed PHB Ranking,Epic Service: Geo Type: Enhancement Workgroup: AMD,"Email391> renee.orr@austintexas.gov392 393Describe the problem.394> AMD is working toward a data-based process to identify locations for new PHBs. We would like to investigate the possibility of using existing data developed for Active Trans' Pedestrian Safety Action Plan (PSAP), and revise it to fit our program. Active Trans is also interested in updating this data for the the PSAP.395 396We anticipate needing to coordinate this GIS data with PHB requests in Data Tracker.397 398Also need to discuss the frequency this data can be updated.399 400 401How soon do you need this?402> Flexible — An extended timeline is OK403 404Is there anything else we should know?405> Would like to have this process defined and in use by November, so we can meet the stated annual December ranking.406 407I request a scoping meeting be scheduled to discuss this request further. Please include Joel Meyer in the meeting, 408 409This process is supported by Jen in response to a request from Jim Dale.410 411Request ID: DTS19-100165412 413",1.0,"Data-Informed PHB Ranking - Email414> renee.orr@austintexas.gov415 416Describe the problem.417> AMD is working toward a data-based process to identify locations for new PHBs. We would like to investigate the possibility of using existing data developed for Active Trans' Pedestrian Safety Action Plan (PSAP), and revise it to fit our program. Active Trans is also interested in updating this data for the the PSAP.418 419We anticipate needing to coordinate this GIS data with PHB requests in Data Tracker.420 421Also need to discuss the frequency this data can be updated.422 423 424How soon do you need this?425> Flexible — An extended timeline is OK426 427Is there anything else we should know?428> Would like to have this process defined and in use by November, so we can meet the stated annual December ranking.429 430I request a scoping meeting be scheduled to discuss this request further. Please include Joel Meyer in the meeting, 431 432This process is supported by Jen in response to a request from Jim Dale.433 434Request ID: DTS19-100165435 436",0,data informed phb ranking email renee orr austintexas gov describe the problem amd is working toward a data based process to identify locations for new phbs we would like to investigate the possibility of using existing data developed for active trans pedestrian safety action plan psap and revise it to fit our program active trans is also interested in updating this data for the the psap we anticipate needing to coordinate this gis data with phb requests in data tracker also need to discuss the frequency this data can be updated how soon do you need this flexible — an extended timeline is ok is there anything else we should know would like to have this process defined and in use by november so we can meet the stated annual december ranking i request a scoping meeting be scheduled to discuss this request further please include joel meyer in the meeting this process is supported by jen in response to a request from jim dale request id ,0437745,4350929598.0,IssuesEvent,2016-07-31 15:23:33,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,Apt module - the possibilty to know if a debian package is present or not ,feature_idea waiting_on_maintainer,"##### ISSUE TYPE438 - Feature Idea439 440##### COMPONENT NAME441apt442 443##### ANSIBLE VERSION444```445ansible --version446ansible 2.0.2.0447 config file = 448 configured module search path = Default w/o override449```450 451##### CONFIGURATION452 453No files and no env454 455##### OS / ENVIRONMENT456```457lsb_release -a458No LSB modules are available.459Distributor ID: Debian460Description: Debian GNU/Linux 8.4 (jessie)461Release: 8.4462Codename: jessie463```464##### SUMMARY465 466Just for obtain an little feature : the possibilty to know if a debian package is present or not .467 468After, if the condition is true, we can register the package version.469 470Because, using the shell module is dirty :+1: 471 472```473 - name: test version474 shell: haproxy -v | awk '$0 ~ /HA-Proxy/ {print$3}'475 register: haproxyversion476 tags:477 - status478 - name: status of backends479 shell: echo ""show servers state"" | nc localhost 666 | grep -Ev ""^1|^#|^$"" | awk '{print""frontend:"""" ""$2"" """"backend:"""" ""$4"" """"ip:"""" ""$5"" """"status:"""" ""$6}'480 register: haproxyout481 when: haproxyversion.stdout.find('1.6') != -1482 tags: 483 - status484``` 485 486##### STEPS TO REPRODUCE487 488It's not a bug489##### EXPECTED RESULTS490It's not a bug491##### ACTUAL RESULTS492It's not a bug493",True,"Apt module - the possibilty to know if a debian package is present or not - ##### ISSUE TYPE494 - Feature Idea495 496##### COMPONENT NAME497apt498 499##### ANSIBLE VERSION500```501ansible --version502ansible 2.0.2.0503 config file = 504 configured module search path = Default w/o override505```506 507##### CONFIGURATION508 509No files and no env510 511##### OS / ENVIRONMENT512```513lsb_release -a514No LSB modules are available.515Distributor ID: Debian516Description: Debian GNU/Linux 8.4 (jessie)517Release: 8.4518Codename: jessie519```520##### SUMMARY521 522Just for obtain an little feature : the possibilty to know if a debian package is present or not .523 524After, if the condition is true, we can register the package version.525 526Because, using the shell module is dirty :+1: 527 528```529 - name: test version530 shell: haproxy -v | awk '$0 ~ /HA-Proxy/ {print$3}'531 register: haproxyversion532 tags:533 - status534 - name: status of backends535 shell: echo ""show servers state"" | nc localhost 666 | grep -Ev ""^1|^#|^$"" | awk '{print""frontend:"""" ""$2"" """"backend:"""" ""$4"" """"ip:"""" ""$5"" """"status:"""" ""$6}'536 register: haproxyout537 when: haproxyversion.stdout.find('1.6') != -1538 tags: 539 - status540``` 541 542##### STEPS TO REPRODUCE543 544It's not a bug545##### EXPECTED RESULTS546It's not a bug547##### ACTUAL RESULTS548It's not a bug549",1,apt module the possibilty to know if a debian package is present or not issue type feature idea component name apt ansible version ansible version ansible config file configured module search path default w o override configuration no files and no env os environment lsb release a no lsb modules are available distributor id debian description debian gnu linux jessie release codename jessie summary just for obtain an little feature the possibilty to know if a debian package is present or not after if the condition is true we can register the package version because using the shell module is dirty name test version shell haproxy v awk ha proxy print register haproxyversion tags status name status of backends shell echo show servers state nc localhost grep ev awk print frontend backend ip status register haproxyout when haproxyversion stdout find tags status steps to reproduce it s not a bug expected results it s not a bug actual results it s not a bug ,1550421587,28326197803.0,IssuesEvent,2023-04-11 07:23:43,opensquare-network/statescan-v2,https://api.github.com/repos/opensquare-network/statescan-v2,opened,"runtime, comparison",documentation,"<img width=""1163"" alt=""image"" src=""https://user-images.githubusercontent.com/19513289/231086149-38d40904-ab87-4164-9ee9-8bfdd16c7003.png"">551 552---553 554<img width=""1061"" alt=""image"" src=""https://user-images.githubusercontent.com/19513289/231086221-3b617af5-c084-4ae4-bd39-5b679a791402.png"">555",1.0,"runtime, comparison - <img width=""1163"" alt=""image"" src=""https://user-images.githubusercontent.com/19513289/231086149-38d40904-ab87-4164-9ee9-8bfdd16c7003.png"">556 557---558 559<img width=""1061"" alt=""image"" src=""https://user-images.githubusercontent.com/19513289/231086221-3b617af5-c084-4ae4-bd39-5b679a791402.png"">560",0,runtime comparison img width alt image src img width alt image src ,05611478,6412426005.0,IssuesEvent,2017-08-08 03:12:01,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,Permissions issue when copying directory,affects_2.1 bug_report waiting_on_maintainer,"<!--- Verify first that your issue/request is not already reported in GitHub -->562##### ISSUE TYPE563 564<!--- Pick one below and delete the rest: -->565- Bug Report566##### COMPONENT NAME567 568<!--- Name of the plugin/task/feature -->569 570`copy`571##### ANSIBLE VERSION572 573<!--- Paste verbatim output from “ansible --version” between quotes below -->574 575```576$ ansible --version577ansible 2.1.2.0578 config file =579 configured module search path = Default w/o overrides580```581##### CONFIGURATION582 583<!---584Mention any settings you have changed/added/removed in ansible.cfg585(or using the ANSIBLE_* environment variables).586-->587 588Absolutely nothing has changed in my config, but I _did_ upgrade Ansible from 2.0.2 right before the failure began.589##### OS / ENVIRONMENT590 591<!---592Mention the OS you are running Ansible from, and the OS you are593managing, or say “N/A” for anything that is not platform-specific.594-->595 596I'm unning Ansible from MacOS Sierra (a recent upgrade) to bring up an Ubuntu 14.04 server in a Vagrant/Virtualbox environment.597##### SUMMARY598 599<!--- Explain the problem briefly -->600 601I'm trying to copy a directory (and its files) from `<role-name>/files` to the file system and set appropriate permissions. Ansible seems to think I'm using symbolic permissions when copying a directory. I was running the playbook just fine, but a user was reporting this error and that user was running v2.1.2 so I upgraded. After the upgrade, I was got the issue as well.602##### STEPS TO REPRODUCE603 604<!---605For bugs, show exactly how to reproduce the problem.606For new features, show how the feature would be used.607-->608 609As far as I can tell, just run the task below under Ansible 2.1.2.610 611<!--- Paste example playbooks or commands between quotes below -->612 613```614- name: Dotfiles | Install ViM customizations615 become: yes616 become_user: ""{{ username }}""617 copy:618 src: .vim619 dest: ~/620 mode: 0664621 directory_mode: 0775622 force: yes623```624 625<!--- You can also paste gist.github.com links for larger files -->626##### EXPECTED RESULTS627 628<!--- What did you expect to happen when running the steps above? -->629 630The directory should be copied and permissions set as specified.631##### ACTUAL RESULTS632 633<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->634 635I get an error related to symbolic permissions.636 637<!--- Paste verbatim command output between quotes below -->638 639```640TASK [user : Dotfiles | Install ViM customizations] ****************************641fatal: [default]: FAILED! => {""changed"": false, ""checksum"": ""109d2e70b4a83619eec12768f976177e55168de1"", ""details"": ""bad symbolic permission for mode: 509"", ""failed"": true, ""gid"": 1000, ""group"": ""vagrant"", ""mode"": ""0775"", ""msg"": ""mode must be in octal or symbolic form"", ""owner"": ""vagrant"", ""path"": ""/home/vagrant/.vim"", ""size"": 4096, ""state"": ""directory"", ""uid"": 1000}642```643",True,"Permissions issue when copying directory - <!--- Verify first that your issue/request is not already reported in GitHub -->644##### ISSUE TYPE645 646<!--- Pick one below and delete the rest: -->647- Bug Report648##### COMPONENT NAME649 650<!--- Name of the plugin/task/feature -->651 652`copy`653##### ANSIBLE VERSION654 655<!--- Paste verbatim output from “ansible --version” between quotes below -->656 657```658$ ansible --version659ansible 2.1.2.0660 config file =661 configured module search path = Default w/o overrides662```663##### CONFIGURATION664 665<!---666Mention any settings you have changed/added/removed in ansible.cfg667(or using the ANSIBLE_* environment variables).668-->669 670Absolutely nothing has changed in my config, but I _did_ upgrade Ansible from 2.0.2 right before the failure began.671##### OS / ENVIRONMENT672 673<!---674Mention the OS you are running Ansible from, and the OS you are675managing, or say “N/A” for anything that is not platform-specific.676-->677 678I'm unning Ansible from MacOS Sierra (a recent upgrade) to bring up an Ubuntu 14.04 server in a Vagrant/Virtualbox environment.679##### SUMMARY680 681<!--- Explain the problem briefly -->682 683I'm trying to copy a directory (and its files) from `<role-name>/files` to the file system and set appropriate permissions. Ansible seems to think I'm using symbolic permissions when copying a directory. I was running the playbook just fine, but a user was reporting this error and that user was running v2.1.2 so I upgraded. After the upgrade, I was got the issue as well.684##### STEPS TO REPRODUCE685 686<!---687For bugs, show exactly how to reproduce the problem.688For new features, show how the feature would be used.689-->690 691As far as I can tell, just run the task below under Ansible 2.1.2.692 693<!--- Paste example playbooks or commands between quotes below -->694 695```696- name: Dotfiles | Install ViM customizations697 become: yes698 become_user: ""{{ username }}""699 copy:700 src: .vim701 dest: ~/702 mode: 0664703 directory_mode: 0775704 force: yes705```706 707<!--- You can also paste gist.github.com links for larger files -->708##### EXPECTED RESULTS709 710<!--- What did you expect to happen when running the steps above? -->711 712The directory should be copied and permissions set as specified.713##### ACTUAL RESULTS714 715<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->716 717I get an error related to symbolic permissions.718 719<!--- Paste verbatim command output between quotes below -->720 721```722TASK [user : Dotfiles | Install ViM customizations] ****************************723fatal: [default]: FAILED! => {""changed"": false, ""checksum"": ""109d2e70b4a83619eec12768f976177e55168de1"", ""details"": ""bad symbolic permission for mode: 509"", ""failed"": true, ""gid"": 1000, ""group"": ""vagrant"", ""mode"": ""0775"", ""msg"": ""mode must be in octal or symbolic form"", ""owner"": ""vagrant"", ""path"": ""/home/vagrant/.vim"", ""size"": 4096, ""state"": ""directory"", ""uid"": 1000}724```725",1,permissions issue when copying directory issue type bug report component name copy ansible version ansible version ansible config file configured module search path default w o overrides configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables absolutely nothing has changed in my config but i did upgrade ansible from right before the failure began os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific i m unning ansible from macos sierra a recent upgrade to bring up an ubuntu server in a vagrant virtualbox environment summary i m trying to copy a directory and its files from files to the file system and set appropriate permissions ansible seems to think i m using symbolic permissions when copying a directory i was running the playbook just fine but a user was reporting this error and that user was running so i upgraded after the upgrade i was got the issue as well steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used as far as i can tell just run the task below under ansible name dotfiles install vim customizations become yes become user username copy src vim dest mode directory mode force yes expected results the directory should be copied and permissions set as specified actual results i get an error related to symbolic permissions task fatal failed changed false checksum details bad symbolic permission for mode failed true gid group vagrant mode msg mode must be in octal or symbolic form owner vagrant path home vagrant vim size state directory uid ,1726261538,8237130011.0,IssuesEvent,2018-09-10 00:41:39,PerfectWeek/web-api,https://api.github.com/repos/PerfectWeek/web-api,closed,Change loggedOnly responses code,Priority: Medium Status: In Progress Type: Maintenance,Change response code when the given token is invalid from `400` to `401`,1.0,Change loggedOnly responses code - Change response code when the given token is invalid from `400` to `401`,0,change loggedonly responses code change response code when the given token is invalid from to ,07271029,4822882376.0,IssuesEvent,2016-11-06 03:00:09,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,yum module doesn't validate that RPM could be downloaded before reading,affects_2.3 bug_report in progress waiting_on_maintainer,"##### ISSUE TYPE728 729Bug Report730 731##### COMPONENT NAME732`yum`733 734##### ANSIBLE VERSION735<!--- Paste verbatim output from “ansible --version” between quotes below -->736```737ansible 2.3.0 (type-filter a6feeee50f) last updated 2016/10/28 15:41:12 (GMT -500)738```739 740##### CONFIGURATION741N/A742 743##### OS / ENVIRONMENT744N/A745 746##### SUMMARY747The `yum` module, in `fetch_rpm_from_url` does not attempt to validate that the request made and returned by `fetch_url` was successful, and instead immediately tried to `read` from that response causing:748 749```750'NoneType' object has no attribute 'read'751```752 753##### STEPS TO REPRODUCE754 755Try installing an RPM via `yum` that causes `fetch_url` to fail downloading.756 757##### EXPECTED RESULTS758 759The error message returned from `fetch_url` as part of `info` should be displayed instead of trying to read from None.760 761##### ACTUAL RESULTS762 763```764fatal: [haproxy.dev]: FAILED! => {""changed"": false, ""failed"": true, ""invocation"": {""module_args"": {""conf_file"": null, ""disable_gpg_check"": false, ""disablerepo"": null, ""enablerepo"": null, ""exclude"": null, ""install_repoquery"": true, ""list"": null, ""name"": [""https://centos7.iuscommunity.org/ius-release.rpm""], ""state"": ""present"", ""update_cache"": false, ""validate_certs"": true}, ""module_name"": ""yum""}, ""msg"": ""Failure downloading https://centos7.iuscommunity.org/ius-release.rpm, 'NoneType' object has no attribute 'read'""}765```",True,"yum module doesn't validate that RPM could be downloaded before reading - ##### ISSUE TYPE766 767Bug Report768 769##### COMPONENT NAME770`yum`771 772##### ANSIBLE VERSION773<!--- Paste verbatim output from “ansible --version” between quotes below -->774```775ansible 2.3.0 (type-filter a6feeee50f) last updated 2016/10/28 15:41:12 (GMT -500)776```777 778##### CONFIGURATION779N/A780 781##### OS / ENVIRONMENT782N/A783 784##### SUMMARY785The `yum` module, in `fetch_rpm_from_url` does not attempt to validate that the request made and returned by `fetch_url` was successful, and instead immediately tried to `read` from that response causing:786 787```788'NoneType' object has no attribute 'read'789```790 791##### STEPS TO REPRODUCE792 793Try installing an RPM via `yum` that causes `fetch_url` to fail downloading.794 795##### EXPECTED RESULTS796 797The error message returned from `fetch_url` as part of `info` should be displayed instead of trying to read from None.798 799##### ACTUAL RESULTS800 801```802fatal: [haproxy.dev]: FAILED! => {""changed"": false, ""failed"": true, ""invocation"": {""module_args"": {""conf_file"": null, ""disable_gpg_check"": false, ""disablerepo"": null, ""enablerepo"": null, ""exclude"": null, ""install_repoquery"": true, ""list"": null, ""name"": [""https://centos7.iuscommunity.org/ius-release.rpm""], ""state"": ""present"", ""update_cache"": false, ""validate_certs"": true}, ""module_name"": ""yum""}, ""msg"": ""Failure downloading https://centos7.iuscommunity.org/ius-release.rpm, 'NoneType' object has no attribute 'read'""}803```",1,yum module doesn t validate that rpm could be downloaded before reading issue type bug report component name yum ansible version ansible type filter last updated gmt configuration n a os environment n a summary the yum module in fetch rpm from url does not attempt to validate that the request made and returned by fetch url was successful and instead immediately tried to read from that response causing nonetype object has no attribute read steps to reproduce try installing an rpm via yum that causes fetch url to fail downloading expected results the error message returned from fetch url as part of info should be displayed instead of trying to read from none actual results fatal failed changed false failed true invocation module args conf file null disable gpg check false disablerepo null enablerepo null exclude null install repoquery true list null name state present update cache false validate certs true module name yum msg failure downloading nonetype object has no attribute read ,1804359845,10681675650.0,IssuesEvent,2019-10-22 01:53:31,unoplatform/uno,https://api.github.com/repos/unoplatform/uno,closed,"Folder in solution with name ""Uno"" causes namespace resolution errors",kind/bug kind/consumer-experience priority/backlog triage/needs-information,"I'm trying to add Uno to an existing solution.805I ""logically"" created a Uno folder in the solution. I added MyApp.Uno.UPW, MyApp.Uno.iOS and MyApp.Uno.Shared projects with the proper nuget packages and references. 806When I build the iOS project I had an error like:807 808> The type or namespace name 'UI' does not exist in the namespace 'MyApp.Uno' (are you missing an assembly reference?)809 810I had to rename my folder to UnoApp and projects to MyApp.UnoApp.UWP etc to get it to compile.",1.0,"Folder in solution with name ""Uno"" causes namespace resolution errors - I'm trying to add Uno to an existing solution.811I ""logically"" created a Uno folder in the solution. I added MyApp.Uno.UPW, MyApp.Uno.iOS and MyApp.Uno.Shared projects with the proper nuget packages and references. 812When I build the iOS project I had an error like:813 814> The type or namespace name 'UI' does not exist in the namespace 'MyApp.Uno' (are you missing an assembly reference?)815 816I had to rename my folder to UnoApp and projects to MyApp.UnoApp.UWP etc to get it to compile.",0,folder in solution with name uno causes namespace resolution errors i m trying to add uno to an existing solution i logically created a uno folder in the solution i added myapp uno upw myapp uno ios and myapp uno shared projects with the proper nuget packages and references when i build the ios project i had an error like the type or namespace name ui does not exist in the namespace myapp uno are you missing an assembly reference i had to rename my folder to unoapp and projects to myapp unoapp uwp etc to get it to compile ,08171789,6575881306.0,IssuesEvent,2017-09-11 17:41:33,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,ec2 badly handles non ec2 instance related limits,affects_2.1 aws bug_report cloud waiting_on_maintainer,"<!--- Verify first that your issue/request is not already reported in GitHub -->818##### ISSUE TYPE819 820<!--- Pick one below and delete the rest: -->821- Bug Report822##### COMPONENT NAME823 824<!--- Name of the plugin/module/task -->825 826cloud/amazon/ec2.py827##### ANSIBLE VERSION828 829<!--- Paste verbatim output from “ansible --version” between quotes below -->830 831```832Using:833ansible 2.1.0.0834 config file = /etc/ansible/ansible.cfg835 configured module search path = Default w/o overrides836But, I have checked devel branch in this repo and the issue seems still not handled837```838##### CONFIGURATION839 840<!---841Mention any settings you have changed/added/removed in ansible.cfg842(or using the ANSIBLE_* environment variables).843-->844##### OS / ENVIRONMENT845 846<!---847Mention the OS you are running Ansible from, and the OS you are848managing, or say “N/A” for anything that is not platform-specific.849-->850 851GNU/Linux (Ubuntu 14.04.x and 16.04.x) 64-bit.852##### SUMMARY853 854<!--- Explain the problem briefly -->855 856`ec2.py` module does not report well failures coming from **non instance** related **limits**857##### STEPS TO REPRODUCE858 859<!---860For bugs, show exactly how to reproduce the problem.861For new features, show how the feature would be used.862-->863 864Just try creating `N` instances with `M` EBS volumes each, making sure to exceed volume related limit.865 866<!--- Paste example playbooks or commands between quotes below -->867 868```869- name: create nodes870 local_action:871 module: ec2872 params, args873 count: <positive int>874 875```876 877<!--- You can also paste gist.github.com links for larger files -->878##### EXPECTED RESULTS879 880<!--- What did you expect to happen when running the steps above? -->881 882At the least I need the invocation to fail with meaningful error:8831. fail the module invocation, and print error message explaining which limit was actually exceeded.884 885In a perfect world, I would also expect playbook to gracefully fail with ""rollback"":8861. destroy already created nodes8872. print failure message as explained before8883. fail the task889##### ACTUAL RESULTS890 891<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->892 893```89420:56:39 TASK [my-aws-bootstrap : create cluster nodes] *******************************89520:56:39 task path: /var/lib/jenkins/jobs/lab-start/workspace/mypipeline/playbooks/roles/aws-bootstrap/tasks/main.yml:3289620:56:39 <localhost> ESTABLISH LOCAL CONNECTION FOR USER: jenkins89720:56:39 <localhost> EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 python && sleep 0'89821:16:42 fatal: [localhost]: FAILED! => {""changed"": false, ""failed"": true, ""invocation"": {""module_args"": {""assign_public_ip"": false, ""aws_access_key"": null, ""aws_secret_key"": null, ""count"": 16, ""count_tag"": null, ""ebs_optimized"": false, ""ec2_url"": null, ""exact_count"": null, ""group"": [""group1""], ""group_id"": null, ""id"": null, ""image"": ""ami-xxxxxxxx"", ""instance_ids"": null, ""instance_profile_name"": null, ""instance_tags"": {""Environment"": ""pipeline-lab"", ""Name"": ""node"", ""lab_id"": ""lab-100"", ""user"": ""user1""}, ""instance_type"": ""i2.8xlarge"", ""kernel"": null, ""key_name"": ""userkey"", ""monitoring"": true, ""network_interfaces"": null, ""placement_group"": null, ""private_ip"": null, ""profile"": null, ""ramdisk"": null, ""region"": ""us-east-1"", ""security_token"": null, ""source_dest_check"": true, ""spot_launch_group"": null, ""spot_price"": null, ""spot_type"": ""one-time"", ""spot_wait_timeout"": ""600"", ""state"": ""present"", ""tenancy"": ""default"", ""termination_protection"": false, ""user_data"": null, ""validate_certs"": true, ""volumes"": [{""delete_on_termination"": true, ""device_name"": ""/dev/xvda"", ""volume_size"": 1000}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdl"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdm"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdn"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""device_name"": ""/dev/xvdd"", ""ephemeral"": ""ephemeral0""}, {""device_name"": ""/dev/xvde"", ""ephemeral"": ""ephemeral1""}, {""device_name"": ""/dev/xvdf"", ""ephemeral"": ""ephemeral2""}, {""device_name"": ""/dev/xvdg"", ""ephemeral"": ""ephemeral3""}, {""device_name"": ""/dev/xvdh"", ""ephemeral"": ""ephemeral4""}, {""device_name"": ""/dev/xvdi"", ""ephemeral"": ""ephemeral5""}, {""device_name"": ""/dev/xvdj"", ""ephemeral"": ""ephemeral6""}, {""device_name"": ""/dev/xvdk"", ""ephemeral"": ""ephemeral7""}], ""vpc_subnet_id"": ""subnet-xxxxxx"", ""wait"": true, ""wait_timeout"": ""1200"", ""zone"": ""us-east-1a""}, ""module_name"": ""ec2""}, ""msg"": ""wait for instances running timeout on Mon Sep 26 21:16:42 2016""}899```900 901<!--- Paste verbatim command output between quotes below -->902 903```904 905```906",True,"ec2 badly handles non ec2 instance related limits - <!--- Verify first that your issue/request is not already reported in GitHub -->907##### ISSUE TYPE908 909<!--- Pick one below and delete the rest: -->910- Bug Report911##### COMPONENT NAME912 913<!--- Name of the plugin/module/task -->914 915cloud/amazon/ec2.py916##### ANSIBLE VERSION917 918<!--- Paste verbatim output from “ansible --version” between quotes below -->919 920```921Using:922ansible 2.1.0.0923 config file = /etc/ansible/ansible.cfg924 configured module search path = Default w/o overrides925But, I have checked devel branch in this repo and the issue seems still not handled926```927##### CONFIGURATION928 929<!---930Mention any settings you have changed/added/removed in ansible.cfg931(or using the ANSIBLE_* environment variables).932-->933##### OS / ENVIRONMENT934 935<!---936Mention the OS you are running Ansible from, and the OS you are937managing, or say “N/A” for anything that is not platform-specific.938-->939 940GNU/Linux (Ubuntu 14.04.x and 16.04.x) 64-bit.941##### SUMMARY942 943<!--- Explain the problem briefly -->944 945`ec2.py` module does not report well failures coming from **non instance** related **limits**946##### STEPS TO REPRODUCE947 948<!---949For bugs, show exactly how to reproduce the problem.950For new features, show how the feature would be used.951-->952 953Just try creating `N` instances with `M` EBS volumes each, making sure to exceed volume related limit.954 955<!--- Paste example playbooks or commands between quotes below -->956 957```958- name: create nodes959 local_action:960 module: ec2961 params, args962 count: <positive int>963 964```965 966<!--- You can also paste gist.github.com links for larger files -->967##### EXPECTED RESULTS968 969<!--- What did you expect to happen when running the steps above? -->970 971At the least I need the invocation to fail with meaningful error:9721. fail the module invocation, and print error message explaining which limit was actually exceeded.973 974In a perfect world, I would also expect playbook to gracefully fail with ""rollback"":9751. destroy already created nodes9762. print failure message as explained before9773. fail the task978##### ACTUAL RESULTS979 980<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->981 982```98320:56:39 TASK [my-aws-bootstrap : create cluster nodes] *******************************98420:56:39 task path: /var/lib/jenkins/jobs/lab-start/workspace/mypipeline/playbooks/roles/aws-bootstrap/tasks/main.yml:3298520:56:39 <localhost> ESTABLISH LOCAL CONNECTION FOR USER: jenkins98620:56:39 <localhost> EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 python && sleep 0'98721:16:42 fatal: [localhost]: FAILED! => {""changed"": false, ""failed"": true, ""invocation"": {""module_args"": {""assign_public_ip"": false, ""aws_access_key"": null, ""aws_secret_key"": null, ""count"": 16, ""count_tag"": null, ""ebs_optimized"": false, ""ec2_url"": null, ""exact_count"": null, ""group"": [""group1""], ""group_id"": null, ""id"": null, ""image"": ""ami-xxxxxxxx"", ""instance_ids"": null, ""instance_profile_name"": null, ""instance_tags"": {""Environment"": ""pipeline-lab"", ""Name"": ""node"", ""lab_id"": ""lab-100"", ""user"": ""user1""}, ""instance_type"": ""i2.8xlarge"", ""kernel"": null, ""key_name"": ""userkey"", ""monitoring"": true, ""network_interfaces"": null, ""placement_group"": null, ""private_ip"": null, ""profile"": null, ""ramdisk"": null, ""region"": ""us-east-1"", ""security_token"": null, ""source_dest_check"": true, ""spot_launch_group"": null, ""spot_price"": null, ""spot_type"": ""one-time"", ""spot_wait_timeout"": ""600"", ""state"": ""present"", ""tenancy"": ""default"", ""termination_protection"": false, ""user_data"": null, ""validate_certs"": true, ""volumes"": [{""delete_on_termination"": true, ""device_name"": ""/dev/xvda"", ""volume_size"": 1000}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdl"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdm"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""delete_on_termination"": true, ""device_name"": ""/dev/xvdn"", ""device_type"": ""gp2"", ""volume_size"": ""100""}, {""device_name"": ""/dev/xvdd"", ""ephemeral"": ""ephemeral0""}, {""device_name"": ""/dev/xvde"", ""ephemeral"": ""ephemeral1""}, {""device_name"": ""/dev/xvdf"", ""ephemeral"": ""ephemeral2""}, {""device_name"": ""/dev/xvdg"", ""ephemeral"": ""ephemeral3""}, {""device_name"": ""/dev/xvdh"", ""ephemeral"": ""ephemeral4""}, {""device_name"": ""/dev/xvdi"", ""ephemeral"": ""ephemeral5""}, {""device_name"": ""/dev/xvdj"", ""ephemeral"": ""ephemeral6""}, {""device_name"": ""/dev/xvdk"", ""ephemeral"": ""ephemeral7""}], ""vpc_subnet_id"": ""subnet-xxxxxx"", ""wait"": true, ""wait_timeout"": ""1200"", ""zone"": ""us-east-1a""}, ""module_name"": ""ec2""}, ""msg"": ""wait for instances running timeout on Mon Sep 26 21:16:42 2016""}988```989 990<!--- Paste verbatim command output between quotes below -->991 992```993 994```995",1, badly handles non instance related limits issue type bug report component name cloud amazon py ansible version using ansible config file etc ansible ansible cfg configured module search path default w o overrides but i have checked devel branch in this repo and the issue seems still not handled configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific gnu linux ubuntu x and x bit summary py module does not report well failures coming from non instance related limits steps to reproduce for bugs show exactly how to reproduce the problem for new features show how the feature would be used just try creating n instances with m ebs volumes each making sure to exceed volume related limit name create nodes local action module params args count expected results at the least i need the invocation to fail with meaningful error fail the module invocation and print error message explaining which limit was actually exceeded in a perfect world i would also expect playbook to gracefully fail with rollback destroy already created nodes print failure message as explained before fail the task actual results task task path var lib jenkins jobs lab start workspace mypipeline playbooks roles aws bootstrap tasks main yml establish local connection for user jenkins exec bin sh c lang en us utf lc all en us utf lc messages en us utf python sleep fatal failed changed false failed true invocation module args assign public ip false aws access key null aws secret key null count count tag null ebs optimized false url null exact count null group group id null id null image ami xxxxxxxx instance ids null instance profile name null instance tags environment pipeline lab name node lab id lab user instance type kernel null key name userkey monitoring true network interfaces null placement group null private ip null profile null ramdisk null region us east security token null source dest check true spot launch group null spot price null spot type one time spot wait timeout state present tenancy default termination protection false user data null validate certs true volumes vpc subnet id subnet xxxxxx wait true wait timeout zone us east module name msg wait for instances running timeout on mon sep ,1996218156,16960086212.0,IssuesEvent,2021-06-29 01:41:09,anhdtqwerty/thpt,https://api.github.com/repos/anhdtqwerty/thpt,closed,Major | Quản lý Bộ môn | Thêm Bộ môn | Thêm và hiển thị thành công bộ môn mới bị trùng ,dev-done test-verified,"Thêm Bộ môn mới997Step:9981. Click ""Thêm Bộ môn""9992. Nhập bộ môn có tên bị trùng hoặc có chứa dấu space vị trí đầu/ cuối 10003. Bấm ""Lưu""1001 1002Actual:1003Thêm và hiển thị thành công bộ môn mới có tên bị trùng hoặc chứa space đầu/ cuối1004 1005Expect:1006Thêm mới không thành công1007Thông báo ""Bộ môn đã tồn tại"" 1008<img width=""1320"" alt=""BM1"" src=""https://user-images.githubusercontent.com/82717419/121237176-f6832d00-c8c0-11eb-8811-c227bb2ee264.png"">1009<img width=""1061"" alt=""BM2"" src=""https://user-images.githubusercontent.com/82717419/121237180-f7b45a00-c8c0-11eb-828a-540c785761e2.png"">1010<img width=""1309"" alt=""BM3"" src=""https://user-images.githubusercontent.com/82717419/121237184-f8e58700-c8c0-11eb-81f7-a877ed0df9f3.png"">1011",1.0,"Major | Quản lý Bộ môn | Thêm Bộ môn | Thêm và hiển thị thành công bộ môn mới bị trùng - Thêm Bộ môn mới1012Step:10131. Click ""Thêm Bộ môn""10142. Nhập bộ môn có tên bị trùng hoặc có chứa dấu space vị trí đầu/ cuối 10153. Bấm ""Lưu""1016 1017Actual:1018Thêm và hiển thị thành công bộ môn mới có tên bị trùng hoặc chứa space đầu/ cuối1019 1020Expect:1021Thêm mới không thành công1022Thông báo ""Bộ môn đã tồn tại"" 1023<img width=""1320"" alt=""BM1"" src=""https://user-images.githubusercontent.com/82717419/121237176-f6832d00-c8c0-11eb-8811-c227bb2ee264.png"">1024<img width=""1061"" alt=""BM2"" src=""https://user-images.githubusercontent.com/82717419/121237180-f7b45a00-c8c0-11eb-828a-540c785761e2.png"">1025<img width=""1309"" alt=""BM3"" src=""https://user-images.githubusercontent.com/82717419/121237184-f8e58700-c8c0-11eb-81f7-a877ed0df9f3.png"">1026",0,major quản lý bộ môn thêm bộ môn thêm và hiển thị thành công bộ môn mới bị trùng thêm bộ môn mới step click thêm bộ môn nhập bộ môn có tên bị trùng hoặc có chứa dấu space vị trí đầu cuối bấm lưu actual thêm và hiển thị thành công bộ môn mới có tên bị trùng hoặc chứa space đầu cuối expect thêm mới không thành công thông báo bộ môn đã tồn tại img width alt src img width alt src img width alt src ,01027202992,15326516271.0,IssuesEvent,2021-02-26 03:48:11,kubernetes/kubernetes,https://api.github.com/repos/kubernetes/kubernetes,opened,[Failing Test] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance],kind/failing-test,"<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->1028 1029#### Which jobs are failing:1030`ci-kubernetes-gce-conformance-latest-kubetest2`1031#### Which test(s) are failing:1032`Kubernetes e2e suite.[sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] `1033#### Since when has it been failing:1034Fairly new job, but it's the only Conformance test which is failing consistently.1035#### Testgrid link:1036https://testgrid.k8s.io/conformance-all#Conformance%20-%20GCE%20-%20master%20-%20kubetest21037#### Reason for failure:1038e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-gce-conformance-latest-kubetest2/13650615863890452481039 1040```1041Feb 25 23:28:50.753: INFO: Pod logs: 10422021/02/25 23:28:19 OK: Got token10432021/02/25 23:28:19 OK: got issuer https://kubernetes.io/kubetest210442021/02/25 23:28:19 Full, not-validated claims: 1045openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.io/kubetest2"", Subject:""system:serviceaccount:svcaccounts-5085:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614296299, NotBefore:1614295699, IssuedAt:1614295699, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5085"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""de16732d-7e39-46b8-8d7d-44bde84f9a91""}}}10462021/02/25 23:28:19 Get ""https://kubernetes.io/kubetest2/.well-known/openid-configuration"": x509: certificate signed by unknown authority1047```1048#### Anything else we need to know:1049 1050This is a new job as part of migration to kubetest2 effort: https://github.com/kubernetes/enhancements/issues/24641051 1052Comparing it to: https://testgrid.k8s.io/conformance-all#conformance,%20master%20(dev)1053 1054e.g 1055 1056https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kind-conformance/13650895193841377281057```1058Feb 26 00:43:27.144: INFO: Pod logs: 10592021/02/26 00:42:55 OK: Got token10602021/02/26 00:42:55 OK: got issuer https://kubernetes.default.svc.cluster.local10612021/02/26 00:42:55 Full, not-validated claims: 1062openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.default.svc.cluster.local"", Subject:""system:serviceaccount:svcaccounts-5425:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5425"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""2591919d-84ec-42a0-9976-80803df8dedd""}}}10632021/02/26 00:42:55 OK: Constructed OIDC provider for issuer https://kubernetes.default.svc.cluster.local10642021/02/26 00:42:55 OK: Validated signature on JWT10652021/02/26 00:42:55 OK: Got valid claims from token!10662021/02/26 00:42:55 Full, validated claims: 1067&openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.default.svc.cluster.local"", Subject:""system:serviceaccount:svcaccounts-5425:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5425"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""2591919d-84ec-42a0-9976-80803df8dedd""}}}1068```1069 1070The issuer seems to differ `https://kubernetes.io/kubetest2` vs `https://kubernetes.default.svc.cluster.local`1071would be good to know why/where it's coming from, especially to know if there's a discrepancy/inherent assumptions in how the cluster needs to be created.1072 1073 1074This doesn't seem to be related to another issue regarding the same test: https://github.com/kubernetes/kubernetes/issues/994701075 1076/cc @BenTheElder @spiffxp 1077 1078@kubernetes/sig-auth-bugs 1079",1.0,"[Failing Test] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] - <!-- Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI -->1080 1081#### Which jobs are failing:1082`ci-kubernetes-gce-conformance-latest-kubetest2`1083#### Which test(s) are failing:1084`Kubernetes e2e suite.[sig-auth] ServiceAccounts ServiceAccountIssuerDiscovery should support OIDC discovery of service account issuer [Conformance] `1085#### Since when has it been failing:1086Fairly new job, but it's the only Conformance test which is failing consistently.1087#### Testgrid link:1088https://testgrid.k8s.io/conformance-all#Conformance%20-%20GCE%20-%20master%20-%20kubetest21089#### Reason for failure:1090e.g. https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-gce-conformance-latest-kubetest2/13650615863890452481091 1092```1093Feb 25 23:28:50.753: INFO: Pod logs: 10942021/02/25 23:28:19 OK: Got token10952021/02/25 23:28:19 OK: got issuer https://kubernetes.io/kubetest210962021/02/25 23:28:19 Full, not-validated claims: 1097openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.io/kubetest2"", Subject:""system:serviceaccount:svcaccounts-5085:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614296299, NotBefore:1614295699, IssuedAt:1614295699, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5085"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""de16732d-7e39-46b8-8d7d-44bde84f9a91""}}}10982021/02/25 23:28:19 Get ""https://kubernetes.io/kubetest2/.well-known/openid-configuration"": x509: certificate signed by unknown authority1099```1100#### Anything else we need to know:1101 1102This is a new job as part of migration to kubetest2 effort: https://github.com/kubernetes/enhancements/issues/24641103 1104Comparing it to: https://testgrid.k8s.io/conformance-all#conformance,%20master%20(dev)1105 1106e.g 1107 1108https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-kind-conformance/13650895193841377281109```1110Feb 26 00:43:27.144: INFO: Pod logs: 11112021/02/26 00:42:55 OK: Got token11122021/02/26 00:42:55 OK: got issuer https://kubernetes.default.svc.cluster.local11132021/02/26 00:42:55 Full, not-validated claims: 1114openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.default.svc.cluster.local"", Subject:""system:serviceaccount:svcaccounts-5425:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5425"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""2591919d-84ec-42a0-9976-80803df8dedd""}}}11152021/02/26 00:42:55 OK: Constructed OIDC provider for issuer https://kubernetes.default.svc.cluster.local11162021/02/26 00:42:55 OK: Validated signature on JWT11172021/02/26 00:42:55 OK: Got valid claims from token!11182021/02/26 00:42:55 Full, validated claims: 1119&openidmetadata.claims{Claims:jwt.Claims{Issuer:""https://kubernetes.default.svc.cluster.local"", Subject:""system:serviceaccount:svcaccounts-5425:default"", Audience:jwt.Audience{""oidc-discovery-test""}, Expiry:1614300775, NotBefore:1614300175, IssuedAt:1614300175, ID:""""}, Kubernetes:openidmetadata.kubeClaims{Namespace:""svcaccounts-5425"", ServiceAccount:openidmetadata.kubeName{Name:""default"", UID:""2591919d-84ec-42a0-9976-80803df8dedd""}}}1120```1121 1122The issuer seems to differ `https://kubernetes.io/kubetest2` vs `https://kubernetes.default.svc.cluster.local`1123would be good to know why/where it's coming from, especially to know if there's a discrepancy/inherent assumptions in how the cluster needs to be created.1124 1125 1126This doesn't seem to be related to another issue regarding the same test: https://github.com/kubernetes/kubernetes/issues/994701127 1128/cc @BenTheElder @spiffxp 1129 1130@kubernetes/sig-auth-bugs 1131",0, serviceaccounts serviceaccountissuerdiscovery should support oidc discovery of service account issuer which jobs are failing ci kubernetes gce conformance latest which test s are failing kubernetes suite serviceaccounts serviceaccountissuerdiscovery should support oidc discovery of service account issuer since when has it been failing fairly new job but it s the only conformance test which is failing consistently testgrid link reason for failure e g feb info pod logs ok got token ok got issuer full not validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid get certificate signed by unknown authority anything else we need to know this is a new job as part of migration to effort comparing it to e g feb info pod logs ok got token ok got issuer full not validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid ok constructed oidc provider for issuer ok validated signature on jwt ok got valid claims from token full validated claims openidmetadata claims claims jwt claims issuer subject system serviceaccount svcaccounts default audience jwt audience oidc discovery test expiry notbefore issuedat id kubernetes openidmetadata kubeclaims namespace svcaccounts serviceaccount openidmetadata kubename name default uid the issuer seems to differ vs would be good to know why where it s coming from especially to know if there s a discrepancy inherent assumptions in how the cluster needs to be created this doesn t seem to be related to another issue regarding the same test cc bentheelder spiffxp kubernetes sig auth bugs ,01132865,4534587162.0,IssuesEvent,2016-09-08 15:00:05,ansible/ansible-modules-core,https://api.github.com/repos/ansible/ansible-modules-core,closed,apache2_module fails for php7.0 on Ubuntu Xenial,bug_report waiting_on_maintainer,"##### ISSUE TYPE1133 - Bug Report1134 1135##### COMPONENT NAME1136apache2_module1137 1138##### ANSIBLE VERSION1139<!--- Paste verbatim output from “ansible --version” between quotes below -->1140```1141ansible 2.2.0 (devel 982db58aff) last updated 2016/09/08 11:50:49 (GMT +100)1142 lib/ansible/modules/core: (detached HEAD db38f0c876) last updated 2016/09/08 13:03:40 (GMT +100)1143 lib/ansible/modules/extras: (detached HEAD 8bfdcfcab2) last updated 2016/09/08 11:51:00 (GMT +100)1144 config file = /home/rowan/.ansible.cfg1145 configured module search path = Default w/o overrides1146```1147 1148##### CONFIGURATION1149 1150N/A1151 1152##### OS / ENVIRONMENT1153 1154N/A1155 1156##### SUMMARY1157Ubuntu Xenial lists the php7.0 module as php7_module when running apache2ctl -M this breaks the regexp checking if the module is enabled.1158 1159I've made a work around here https://github.com/rwky/ansible-modules-core/commit/00ad6ef035a10dac7c84b7b68f04b00a739b104b but I didn't make a PR since I expect it may break other distros/versions.1160 1161Not entirely sure what the best solution to this is.1162 1163##### STEPS TO REPRODUCE1164 1165Run apache2_module with name=php7.0 state=present on a xenial server.1166 1167",True,"apache2_module fails for php7.0 on Ubuntu Xenial - ##### ISSUE TYPE1168 - Bug Report1169 1170##### COMPONENT NAME1171apache2_module1172 1173##### ANSIBLE VERSION1174<!--- Paste verbatim output from “ansible --version” between quotes below -->1175```1176ansible 2.2.0 (devel 982db58aff) last updated 2016/09/08 11:50:49 (GMT +100)1177 lib/ansible/modules/core: (detached HEAD db38f0c876) last updated 2016/09/08 13:03:40 (GMT +100)1178 lib/ansible/modules/extras: (detached HEAD 8bfdcfcab2) last updated 2016/09/08 11:51:00 (GMT +100)1179 config file = /home/rowan/.ansible.cfg1180 configured module search path = Default w/o overrides1181```1182 1183##### CONFIGURATION1184 1185N/A1186 1187##### OS / ENVIRONMENT1188 1189N/A1190 1191##### SUMMARY1192Ubuntu Xenial lists the php7.0 module as php7_module when running apache2ctl -M this breaks the regexp checking if the module is enabled.1193 1194I've made a work around here https://github.com/rwky/ansible-modules-core/commit/00ad6ef035a10dac7c84b7b68f04b00a739b104b but I didn't make a PR since I expect it may break other distros/versions.1195 1196Not entirely sure what the best solution to this is.1197 1198##### STEPS TO REPRODUCE1199 1200Run apache2_module with name=php7.0 state=present on a xenial server.