[Bug 1658750] Re: fails to add search directive to resolv.conf

2018-06-27 Thread  Christian Ehrhardt 
Revisiting bugs that were triaged but dormant for 6 months I think we
have to realize that this wasn't at the top of anyones todo list.

I didn't hear anything else about it and don't see this bug win against others 
up in the queue atm.
So to be honest we should reflect that in the bugs importance and lower it to 
match what happens.

@Lamont - since this casme from Maas, how did this continue for Maas? Is
it just a remaining low-prio issue or more important than it was handled
so far?

** Tags added: bot-stop-nagging

** Changed in: open-iscsi (Ubuntu)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1658750] Re: fails to add search directive to resolv.conf

2017-03-31 Thread Brian Murray
** Changed in: open-iscsi (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1658750] Re: fails to add search directive to resolv.conf

2017-03-29 Thread Nish Aravamudan
This would appear to be an issue in d/net-interface-handler, which
currently ignores the DNSDOMAIN value.

There is no documentation in this file indicating what variables are
expected or used...

But it seems most reasonable for DNSDOMAIN to translate to domain and
DOMAINSEARCH to search, semantically?

** Changed in: open-iscsi (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1658750] Re: fails to add search directive to resolv.conf

2017-01-23 Thread LaMont Jones
Note that while there is no DOMAINSEARCH, DNSDOMAIN needs to translate
into something (domain or search directive), and only one of those will
be honored by the resolver (they overwrite each other, per the
specification).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658750

Title:
  fails to add search directive to resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1658750/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs